Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
How Matching Works Between Auditees and Auditors
Short answer
Matching on AI Audit Exchange runs in five recorded steps: the auditee creates an evidence room for a regime and period; posts an engagement brief against that room; vetted auditors respond; the auditee accepts one response; and acceptance records the match, names the auditor of record and grants that auditor read access to that room only. Work then happens in the room — manifest, sampling, questions — until close-out, when the grant is revoked and the record retained. Every step is a platform record, so the match can always be reconstructed exactly.
What is auditor matching?
Auditor matching is the engagement flow on AI Audit Exchange connecting auditees with vetted independent auditors. It is recorded in the platform's data as engagements attached to rooms, responses from listed auditors, and acceptance events that create room-scoped read grants and set the room's auditor of record. The room's completeness view tracks two matching states directly: engagement posted and auditor matched.
Step one and two: the room, then the brief
Matching starts before any auditor is involved, because the match is to a room, not to a company in the abstract. The auditee creates the room — regime (SB 1119 or CPPA), period, title — and files the period's evidence into it. Then the engagement brief is posted against that room: what is to be examined, for which period, on what timeline, with the room's evidence shape described. Posting is a tracked state of the room itself — 'engagement posted' is step one of its completeness view — so a room's matching status is visible on its face, not buried in someone's inbox. The brief craft is covered in writing an engagement brief.
Step three: responses from the vetted directory only
Responses come from the listed directory — auditors whose registrations have passed the owner-run vetting workflow. That single constraint shapes the whole market's quality: every respondent is an accountable registration whose claims are on record as stated. Auditors respond where their regime experience, method and calendar fit; self-selection does the first round of sorting before the auditee reads a word. There is no open bidding wall and no published auditor count to game — the platform's copy rules forbid network claims and counts until its verified threshold is crossed, keeping responses about fit rather than scale theatre.
Step four: acceptance is three events in one
When the auditee accepts a response, the platform records the match, sets the room's auditor of record, and creates the scoped grant — read access to that room only. Three consequences, one act, all recorded. This is the hinge of the whole design: access never exists before acceptance, never extends beyond the room, and never needs a separate sharing step that could drift out of sync with the engagement's reality. The room's completeness view flips 'auditor matched' to done in the same moment. If the fit conversation before acceptance was thorough, the engagement now starts at full speed: the auditor's first session can already open the manifest and plan sampling.
The working phase: inside the room
With the match made, the engagement's life is the room's life. The auditor samples from the manifest, verifies hashes, reviews validation and its freshness flags, and raises questions in the room's thread; the auditee answers there, importing any missing evidence through the proper paths so answers can point at new manifest entries. Access is logged. Nothing about the work requires either side to maintain a parallel channel — and both sides benefit from refusing to: the retained thread becomes the engagement's memory, readable by any successor and by future cycles' auditors under their own grants.
Close-out and the end of the match
A match ends as deliberately as it began. Substance complete, the auditee exports the final manifest, confirms retention for the room's afterlife, and revokes the grant. The match record persists — who was auditor of record, for which room and period, is a permanent platform fact — while access returns to none. If the same pair works together next period, it is a fresh engagement on a fresh room: new brief, new acceptance, new grant. The rhythm looks repetitive on paper and is, in practice, the cheapest accountability ever sold: every engagement's authority to access evidence begins and ends on the record, with nothing standing in between cycles.
Succession: when the match must change mid-flight
Matches occasionally break mid-engagement — an auditor withdraws, a conflict surfaces, capacity fails. The room absorbs the shock: revoke the outgoing grant, accept the successor through the same flow, and the new auditor of record inherits the room complete — sealed evidence, current manifest, the full question thread including the predecessor's exchanges. The match history shows both engagements' records against the room, so the change of examiner is itself documented rather than whispered. Succession done this way costs days; succession across email-and-drive evidence costs the engagement. The handover pattern is detailed in handing over to a new auditor.
Five actions to take
- Build the room and file its evidence before posting — matches are made to rooms, not intentions.
- Post the brief against the room with regime, period, evidence shape and dates.
- Compare responses only from vetted, listed auditors; test claims with consistent fit questions.
- Let acceptance do its triple work: match recorded, auditor of record set, scoped grant created.
- Close every match deliberately: manifest exported, retention confirmed, grant revoked.
Worked example
A fictional agritech firm, Rio Seco Agriculture Systems, posts its CPPA engagement in February for the 2028 period: room at 52 artifacts and growing, brief stating regime, period, evidence shape and a May conclusion date. Two vetted auditors respond within the fortnight. Fit calls are held with both; the auditor whose sampling method is described in manifest terms is accepted on 3 March — match recorded, auditor of record set, grant live on that room only.
The engagement runs six weeks entirely in the room: 16 sampled artifacts, 16 hashes verified, 7 questions asked and answered in the thread. Close-out on 18 April: final manifest exported, retention confirmed at 120 months, grant revoked in the same sitting. The room's completeness view reads 5 of 5, and its record can reconstruct the entire match — brief, acceptance, access, work, close — without a single email being consulted.
Frequently asked questions
Can an unvetted auditor respond to my engagement?
No. Only auditors who have passed the owner-run vetting workflow are listed and may respond. Pending registrations cannot see or answer briefs.
What does acceptance actually do?
Three recorded things at once: it records the match, names the auditor as the room's auditor of record, and grants them read access to that room only, revocably.
Is the match exclusive?
An engagement has one auditor of record. If the engagement must change hands, the outgoing grant is revoked and the successor is accepted on the same room, with the match history preserved.
Where is the match recorded?
On the engagement and the room: the brief, the acceptance, the auditor of record, plus downstream records the work creates — grants, access log, question thread and manifest exports.
What happens to the match record after close-out?
It persists with the room for the room's retained life. Access ends at revocation; the fact of the match — who examined what, when — remains part of the audit record.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: Auditor Credentials: Claims vs Verified Facts, Explained · Next: Multi-Client Evidence Rooms: An Auditor's Practice Guide
Evidence Rooms for AI Audit Agencies and Teams · AI Audit Exchange Plans: Rooms, Retention and What Each Tier Includes · The Free Evidence Room: What 'No Sign-In' Actually Gives You