People and access handover
Brings joiner, leaver, account-handover and obligation checklists together for authorised owners.
Run the firm
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
- Starts when
- Joiner/leaver, access or obligation change
- What it works from
- Role, client obligations, permissions and retention records
- What it prepares
- Access-change requests, due items and handover checklist
- What your team decides
- Authorised humans execute HR/access/retention decisions
What this helps your team do
This path has been checked in the fictional local build.
Responsibilities connected
See what each agent is responsible for preparing in this workflow. These are designs and local examples, not a set of independently running agents.
When it stops and asks
Stale/missing finance, people or effort data remains unknown; the owner receives bounded options rather than an invented operational fact.
Supported scope, source access and authority are agreed for each installation.