Operations coordinator
Prepares cross-engagement exceptions, obligations, people handovers and supplier decisions for their owners.
The saved work
A handover with named responsibilities
Nadia, the accountable fictional lead, owns receipt and internal review of the remaining handover. Elena, in the departing fictional role, owns preparation: identify remaining clarification support, record the retention obligation, and identify permitted Northline-only material. Rowan is the named fictional receiver. The stated 29 October 2026 date is an internal target, not a client promise.
Completed preparation is limited to the simulated receiving record: Rowan acknowledged the Northline-only preparation checklist and named support/retention responsibilities, recorded by Nadia in an authored local scenario. That is receipt of preparation only. It does not verify an access grant, access revocation, retention period, deletion, or completion of a client duty.
A related local example. It shows the stated part of the work, not every step in this design. Read it in saved outputs
- What it works from
- Approved role/permission data, current portfolio, obligations, commitments and vendor/service records
- What it prepares
- Operating brief, handover/access requests, role brief and supplier/licence options
- Who keeps the decision
- Operations owner
- Where its responsibility ends
- Cannot make employment/access/procurement decisions or alter retention outside authorised owner scope.
Part of a larger job
A responsibility can contribute to several workflows. Each one names the inputs, the human decision and the next handover.
- Fit and conflict checkLeads this job · Win work
- Firm operating reviewLeads this job · Run the firm
- People and access handoverLeads this job · Run the firm
- Role case preparationLeads this job · Run the firm
- Supplier and licence reviewLeads this job · Run the firm
- Time and expense checksContributes · Run the firm
