USER JOURNEYS · A GUIDED TOUR OF THE PLATFORM · NOTHING HERE IS INVESTMENT ADVICE
← All user types
Console desks · Operations desk

Asset servicing, disclosures and controlled exits

Operations watches the assets investors already own: performance reporting, manager updates, material events, and at end of life the exit that turns a building back into money. The desk also carries cross-domain exceptions and the operational half of account recovery. The rule everywhere: investors hear the truth on a schedule, and money only moves against reconciled positions.

A recorded run of this exact journey — every step below, performed live on the platform, with every click shown (about 3 minutes).
You are
Yaw Antwi
Open the operator console → admin.blackant.tech
01

Triage the portfolio

  1. 1

    Open Operations.

    http://admin.blackant.tech/operations

    Expect · Every asset with occupancy, reserve cover and last update. Problem assets (reserve below policy, stale updates) sort first and glow amber.

  2. 2

    Expand an asset row and post a manager update.

    /operations

    Expect · The update lands on the investor-facing asset timeline; silence longer than 35 days flags the asset.

02

Run governed reporting

  1. 3

    Open an asset’s servicing workbench.

    http://admin.blackant.tech/operations/[ticker]

    Expect · Reporting periods, performance reports, material events and the exit rail.

  2. 4

    Open a reporting period; review the issuer’s submitted report; publish it.

    /operations/[ticker]

    Expect · Publication is the regulated act; investors see the report only after your review.

  3. 5

    Record a material event with its disclosure.

    /operations/[ticker]

    Expect · The event carries severity and an investor-facing disclosure note.

03

Wind down a deal (asset exit)

The exit runs under the platform’s tightest controls: every position is frozen as evidence, and redemption only runs against a three-way-matched register.

  1. 6

    Propose the exit with its rationale; have it approved.

    http://admin.blackant.tech/operations/[ticker]

    Expect · Proposal and approval are separate acts by separate people.

  2. 7

    Finalize sale accounting: gross, liabilities, expenses, reserves, taxes.

    /operations/[ticker]

    Expect · The waterfall to net proceeds is computed and hash-frozen; per-holder snapshots pin record-date units.

    Finalize refuses while cash or transfer workflows are open, or if the three-way reconciliation does not match.

  3. 8

    Execute redemptions.

    /operations/[ticker]

    Expect · Each holder’s units burn on the ledger against their snapshot; proceeds pay out through the payment machinery with per-holder evidence.

  4. 9

    Watch investors’ statements.

    http://app.blackant.tech/income

    Expect · Redemption lines show gross proceeds, deductions and net, matching the frozen accounting exactly.

04

Exceptions and recovery

  1. 10

    Work the exception queue.

    http://admin.blackant.tech/actions (Exceptions)

    Expect · Each exception names its exposure, last-known-good state and recovery route; resolution requires evidence text.

  2. 11

    Report a lost/compromised digital account and walk the recovery.

    http://admin.blackant.tech/investors (Account recovery)

    Expect · Report suspends the old account immediately. The lifecycle then demands: fresh identity verification → compliance approval → operations approval (different person, step-up) → replacement account → ledger recovery per holding → three-way reconciliation → completed. A failed ledger command holds the recovery honestly with an exception until retry confirms.

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