Console desks · Asset review desk

From inbound asset to committee decision

The pipeline desk decides what gets listed. Its guarantees: every stage move is legal-next-only, diligence items are evidence-gated, the committee separates recommendation from decision on a frozen input hash, and every decline carries a reason the submitter reads. This journey runs a submission across the whole board.

A recorded run of this exact journey — every step below, performed live on the platform, with every click shown (about 3 minutes).

You are

Selorm Amankwah

Open the operator console → admin.blackant.tech

Triage the board

1
Open the Pipeline.
http://admin.blackant.tech/pipeline
Expect · A seven-stage board: received → screening → diligence → committee → accepted → structuring → ready to launch. Cards age-dot from green to red; amber tags mark “waiting on submitter”.
2
Drag a card one stage (only legal targets light up), or open its workbench.
/pipeline
Expect · Illegal jumps are not droppable. Dragging to the red bar declines, with a mandatory reason the submitter sees.

Work a submission’s record

3
Open a submission workbench.
http://admin.blackant.tech/pipeline/[reference]
Expect · The asset record, the sponsor organisation, attachments (content-addressed), stage history and SLA state.
4
Request information from the submitter (action required).
/pipeline/[reference]
Expect · The card leaves its column into “waiting on the submitter”; their answer returns it to the exact stage it left, with the exchange preserved.
5
Put a submission on hold with a reason; resume later.
/pipeline/[reference]
Expect · Hold pauses SLAs honestly; resume restores the stage.

Run diligence

6
Work the diligence checklist in the workbench.
http://admin.blackant.tech/pipeline/[reference]
Expect · Each item needs linked evidence before it can pass; without evidence it cannot be marked complete.
7
Attach or reference legal-entity records for the SPV.
/pipeline/[reference]
Expect · Entities carry registration data and status; they follow the deal into structuring.

Committee: recommend, then decide

8
Record the committee recommendation on the frozen submission input.
http://admin.blackant.tech/pipeline/[reference]
Expect · The recommendation hashes the exact inputs it saw. If the record changes afterwards, the decision step refuses on input drift.
9
Have a different member decide (accept/decline).
/pipeline/[reference]
Expect · Acceptance can attach conditions; waiving a condition later is a dual-control act.
10
Watch acceptance hand off to Issuance.
http://admin.blackant.tech/issuance
Expect · The accepted deal appears in “ready to structure”, and one click starts the draft offering.

That is every act this role can take.Pick another user type →