Persona: Operations Lead

Your phone pings at 06:15 because the SPAN scanrange file is late. By 09:15 you’ve cleared three pre-open glitches. By the second peak-margin snapshot you’re watching one client’s RMS position with a small worry. By 17:00 you’re approving the daily margin file. By 22:30 the ledger batch is running and you’d like to go home. Tomorrow you’ll do it again, with an extra layer of weekly CFR, monthly client funding, and a quarterly running-account settlement.

This page is your shortcut.

What you’ll find useful here

You operate at the intersection of every other persona’s concerns — the engineer’s systems, the compliance officer’s evidence, the finance officer’s funds, the product manager’s edge cases. You don’t need depth in all of it; you need a working mental model of the whole.

Two layers matter most:

• The Broker Process Narrative — chronological story of the operational day, week, month, quarter, year. Your reading list.
• The Integration DAG — when things break, you want to know what downstream depends on what.

Then specific deep-dives for the items that keep coming up in your day.

Suggested reading path (in this order)

1. Broker Process Narrative — the whole thing, 8.2K words. This is your foundational reading. Sections 2 (Trading Day), 4 (Daily Reporting), and 5 (Recurring Cycles) you’ll keep coming back to.

2. Integration DAG Overview — orientation to the dependency layer. Then specifically:

   • BOD DAG — your morning playbook.
   • Trading-Hours DAG — 4 peak margin snapshots, surveillance loops, block-deal windows.
   • EOD & Settlement DAG — the evening playbook.
   • Recurring Cycles DAG — your weekly / monthly / quarterly compliance calendar.
   • Lifecycle Events DAG — what your team handles when a client modifies / dormants / closes.

3. Compliance Blueprint — skim the domain headers; come back to specific rows when a deadline approaches.

4. Lifecycle Overview — six post-onboarding scenarios your team will run.

5. Deep dives on the operational items that hit your queue most:

   • Short-Delivery Auction — the T+2 auction process and recovery.
   • Payin Default + Core SGF — worst case; needs an understood escalation path.
   • Direct Payout to Demat — the post-Jun-2024 mechanics.
   • BCP / DR Drill — what your team does quarterly.

6. Error Handling + Status Machine + Admin Workflow — your runbooks.

Tip

Build a compliance calendar. Take the Compliance Blueprint’s reporting and audit domains plus the Recurring Cycles DAG. Slot every item into a master calendar by day-of-week / day-of-month / date-of-quarter. That calendar runs your weekly standup agenda, your month-end checklist, and your quarter-end project plan. Done well, this is the most-referenced document in the ops function and survives staff turnover better than most operational systems.

Added in September 2026

Four new sections cover account variants, product activation, funds and tax, and trading risk. For your role, start with these:

• Payout and running account — quarterly and monthly settlement runs.
• Corporate actions — bonus, split, rights, buyback and IEPF handling.
• Demat servicing — demat, remat, off-market and freeze requests.
• Exercise, assignment and physical settlement — expiry-week delivery obligations.
• Expiry-day operations — the expiry-day runbook.
• Margin pledge — pledge, unpledge and invocation servicing.

Common questions in your role

• A BOD file didn’t arrive by 09:00 — what’s my escalation? → BOD DAG escalation note — alternate FTP endpoint, then clearing-corp helpdesk for SPAN files, then DR-site failover.
• A peak-margin snapshot was breached — what’s the consequence? → RMS / SPAN deep-dive penalty section.
• A modification request is stuck — where in the chain? → Lifecycle modifications — rejection-cascade patterns.
• Quarterly running-account settlement is approaching — what’s the procedure? → Compliance Blueprint client-funds domain plus Broker Process Narrative Section 5.
• A client went dormant and now wants to reactivate — what’s required? → Lifecycle: Dormancy & Reactivation.
• A death certificate just arrived — what’s the transmission procedure? → Lifecycle: Transmission — 4 sub-cases.
• Quarterly BCP drill is next week — what’s the scope? → BCP / DR Drill deep-dive.
• A short-delivery happened on a client’s sell — what now? → Short-Delivery Auction deep-dive.
• Where are the FIU-IND STR / CTR reporting templates? → AML / FIU destination page + FIU-IND Circulars.

What to skip (and why)

• All persona pages other than this one — you don’t need them; you handle the cross-cutting view.
• Vendor Atlas detailed pages — backend-engineer territory; you only need to know which vendor categories your firm uses.
• Master Dataset, Field Atlas section pages, individual circular sub-pages — reference material; you’ll search them when needed.
• Most of the architecture/ pages* — backend-engineer territory.

When you’d hand off

• “How do we fix the underlying integration bug?” → Backend Engineer reading path.
• “Are we exposed to a particular regulatory action?” → Compliance Officer reading path.
• “How much does this incident cost us?” → Finance / CFO reading path.
• “Should we onboard this segment?” → Product Manager reading path with Compliance Officer sign-off.

Verified through

2026-05-14

---

AI-generated and not legal, financial, or compliance advice. See the project README for full disclaimer.