Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
How to Hand Over Evidence to a New Auditor
Short answer
Handing over to a new auditor on AI Audit Exchange takes three platform acts: revoke the outgoing auditor's grant on the room, accept the successor through the engagement flow so a fresh scoped grant is created, and walk the successor through the room's own memory — the current manifest, the question thread (including the predecessor's exchanges), the validation runs and the access log. Nothing is copied, emailed or rebuilt: the room persists, sealed and retained, and the new auditor of record inherits context no handover document could match.
What is auditor handover?
Auditor handover is the transfer of an engagement's examination from one auditor of record to another on the same evidence room. It is executed by revoking the predecessor's scoped grant and recording a new match through acceptance, which creates the successor's grant. The room's artifacts, manifest, validation results, access log and question thread persist across the handover under the room's retention setting.
Why rooms make handover a non-event
In attachment-based audits, an auditor change is a small disaster: the record of what was shared lives in the departed auditor's mailbox, the 'current' evidence set is a matter of opinion, and the successor's first month re-buys discovery the engagement already paid for. A room removes every element of that. The evidence set is the room — sealed, manifested, unambiguous. The sharing history is the access log. The conversation history is the thread. The successor does not receive a handover; they receive access, and the room briefs them. Your three acts — revoke, accept, walk through — take a sitting. The predecessor's departure costs the engagement days, not its memory.
Act one: close the predecessor's access cleanly
Begin with the outgoing grant. Confirm the predecessor's work state: questions they raised that remain open, samples in progress, anything they flagged informally that should be formalised in the thread before access ends — ask them to put pending observations in the room while they still hold the grant, so their knowledge enters the record rather than leaving with them. Export a fresh manifest as of the handover date. Then revoke the grant and confirm the grants list. The record shows the sequence honestly: match, work, handover manifest, revocation — a chain a reviewer can follow without interviewing anyone.
Act two: the successor's acceptance and first session
The successor is engaged like any auditor: brief (updated if the engagement's framing has evolved), response, fit conversation, acceptance — which records the new match, names the new auditor of record, and creates the new scoped grant on the same room. Resist any shortcut that skips the flow 'because the room already exists'; the match record is the engagement's legitimacy, and it costs nothing to create properly. In the successor's first session, they can already work: read the thread end to end, run their own coverage pass over the manifest, sample-verify a set of hashes to establish their own confidence in the seals. A well-kept room lets a successor reach examining speed in days.
Act three: the walkthrough that transfers judgement, not just access
Access transfers facts; a walkthrough transfers judgement. Spend one session on the room's story as you understand it: which areas the predecessor probed hardest and what they concluded in-thread, which stale flags you worked and how, which artifacts carry corrections and why, where the honest gaps are. Say the gaps out loud — a successor who hears them from you calibrates trust upward; one who finds them alone calibrates it downward, permanently. Close the walkthrough by agreeing the open-question list: the thread's unanswered items become the successor's starting queue, each already anchored to the evidence it concerns.
Mid-engagement vs next-cycle handover
The mechanics are identical; the emphasis differs. Mid-engagement, the priority is continuity of the live examination: pending observations captured, open questions queued, sampling state (what has been verified, what remains) stated in the thread so the successor does not silently re-sample or silently skip. Next-cycle handover is calmer: a new room for the new period, the prior room retained as history — and if the successor needs the prior record, that is a deliberate grant on the old room, decided as its own question. Never let 'the new auditor might need history' become standing access by default; grant it as deliberately as the first grant was made.
What never to do in a handover
Three prohibitions protect the record. Never copy the room's evidence out to brief the successor — access replaces copies, and copies created at handover become uncontrolled records with your name on them. Never let both auditors hold grants casually 'for overlap' beyond a defined, brief transition you can justify in the thread — overlapping access blurs accountability for reads during the overlap. And never edit history to tidy the transition: the predecessor's questions, the gaps, the corrections stay as they are. The successor is an examiner; a room that shows its own past honestly is the strongest possible introduction to it.
Five actions to take
- Before revoking, have the outgoing auditor place all pending observations in the room's thread.
- Export the manifest at handover and revoke the outgoing grant; confirm the grants list.
- Engage the successor through the full flow — brief, response, acceptance — so the new match is recorded properly.
- Walk the successor through manifest, thread, validation and gaps in one session; agree the open-question queue.
- Grant any historical-room access deliberately, as its own decision — never by default.
Worked example
A fictional consumer-electronics firm, Saguaro Sound Systems, loses its auditor of record mid-engagement when her practice withdraws from the regime. Week one: she places 4 pending observations in the thread at the auditee's request, the handover manifest is exported (71 artifacts), and her grant is revoked. Week two: the successor is accepted through a refreshed brief; his first session verifies 6 seals sampled across sources and reads the 19-question thread end to end.
By week three he is examining at full depth, working an open-question queue of 5 items inherited in writing rather than reconstructed in meetings. Total engagement time lost to the transition: roughly the walkthrough session. The firm's post-engagement note attributes the save entirely to the room's persistence — evidence, conversation and access history surviving the examiner's change because none of them ever lived in the examiner's possession.
Frequently asked questions
Does the successor see the predecessor's questions and our answers?
Yes — the thread is part of the room's record and persists under its retention. That continuity is the handover's core asset: the successor inherits the examination's memory, not just its files.
Must the outgoing auditor finish all their questions first?
No. Open items remain in the thread as the successor's starting queue. Ask the outgoing auditor to record pending observations before revocation so nothing exists only in their head.
Can both auditors hold access briefly for overlap?
Only as a defined, brief, justifiable transition — and the default answer is no. Sequential grants keep accountability for access unambiguous, which is worth more than a few days of overlap.
What if the handover is between cycles, not mid-engagement?
Open the new period's room and engage the successor there. If they need the prior room, grant it deliberately as its own decision; do not let historical access become standing access.
Is anything copied or exported to the successor?
The handover manifest export is a document for the record; the evidence itself is never copied out. The successor works the originals in the room, under their own grant, with seals verifiable in place.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: API Keys for Audit Evidence Workflows: A Practical Guide · Next: Version Control for Audit Evidence Without Editing the Past
What Is Source Badging on Audit Evidence? · Importing ProvenanceGuard Evidence Into an Audit Room · Importing ReviewDesk — ADMT Decision Review Evidence Into an Audit Room