Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Auditor Questions and Answers Inside the Evidence Room
Short answer
Inside an AI Audit Exchange room, the granted auditor can raise a question and the auditee can answer it in the same thread — attached to the room, visible to both sides, and retained with the evidence for the room's full retention life. That one design choice ends the audit's worst habit: questions scattered across email, answered against files nobody can identify later. Ask and answer in the room, and the examination's conversation becomes part of the record it examines.
What is the in-room question workflow?
The in-room question workflow is the evidence room's built-in exchange: questions are listed per room, each raised against the engagement with who asked it, and answers are recorded against the question. It operates alongside the room's validation results and access log as part of the room's working record, under the same access scope — the owner and the auditor granted to that room.
Why questions belong with the evidence
Every audit question is about some artifact, some gap, some period. Detached from the room, a question loses its referent: 'your March export' means one file in the room and five in an inbox. Inside the room, the question is asked in the presence of the manifest, the sealed artifacts and the validation results, and the answer is given in the same presence — both sides looking at the same hashes, the same source badges, the same dates. Misunderstandings that take a week of email threading to untangle simply fail to form. And when the engagement closes, the thread stays: a successor auditor reads not just what the evidence was, but what was asked about it and what was said.
How the workflow runs
The auditor of record, working under their scoped grant, adds a question to the room. The auditee sees it in the room's question list, works the answer — importing a missing artifact, explaining a date, pointing to the manifest entry — and answers against the question itself. Questions and answers accumulate as a readable thread: who asked, what was asked, what was answered. There is no separate ticketing system to reconcile and no channel discipline to enforce; the room is the channel. Access follows the room's scope exactly: nobody outside the owner and the granted auditor participates, which keeps the exchange as confidential as the evidence it discusses.
Writing questions that get answered in one round
Auditors: anchor every question to the record. Name the artifact by its manifest entry — filename, source, import date — or name the absence precisely: 'no CompanionGuard export for June in the manifest'. Ask one thing per question so answers can be complete per question. And ask about the evidence's story, not just its presence: which configuration produced this export, why do these two files share a recorded date, what superseded that stale artifact. Auditees reading well-anchored questions can answer from the room itself, which is the fastest loop an examination can have. Vague questions produce vague answers and second rounds; the room gives you every tool to avoid them.
Answering well: point at the record, then explain
Auditees: the strongest answer has two parts — a pointer and an explanation. The pointer is a fact of the room: the manifest entry, the newly imported artifact, the validation run, the hash verification. The explanation is the short human context the record cannot carry: why a gap existed, what changed, which file supersedes which. Answers that are only explanations ask the auditor to trust you; answers anchored to sealed, dated, badged artifacts ask the auditor to check you — and checking is what auditors are for. If an answer requires new evidence, import it properly first, then answer pointing at the new manifest entry. The thread thereby documents its own resolution.
The thread as part of the audit record
Because the thread lives in the room, it inherits the room's retention — up to 10 years on paid plans — and its hold protection. That longevity cuts both ways, healthily. It disciplines both sides to write as professionals whose words will be read in year six by people who were not in the room. And it preserves the examination's reasoning: a finding in the final report that traces to question 14 and its answer is a finding a reviewer can re-walk step by step. Audits are judged, sometimes years later, on exactly that re-walkability. Email cannot offer it; a retained, room-scoped thread can.
Questions outside the audit too
The workflow earns its keep beyond the auditor's own enquiries. Use the thread in rehearsal: have your own team raise the questions an auditor would ask — where is June's export, why is this artifact stale, which file evidences this control — and answer them in the room before the engagement starts. Gaps found this way are filing tasks with weeks to run, not findings with deadlines attached. Some teams formalise it: five rehearsal questions a month, rotating authorship. By the time the real auditor arrives, the thread already demonstrates the habit the examination rewards — a room whose owners interrogate their own evidence.
Five actions to take
- Keep every audit question and answer inside the room — no parallel email threads about evidence.
- Auditors: anchor each question to a manifest entry, an absence or a validation result; one question per item.
- Auditees: answer with a pointer to the record first, then the explanation; import missing evidence before answering.
- Use the thread in rehearsal — raise the auditor's likely questions monthly and answer them from the room.
- Treat the thread as permanent: it is retained with the room for its full retention life.
Worked example
A fictional fintech firm, Three Rivers Payments, runs its CPPA engagement across 44 artifacts. The auditor raises 13 questions in the room over three weeks. Nine are answered by pointing at the record — manifest entries, a validation run, two hash verifications. Three require new evidence: current-period exports that existed in the producing products but had never been imported; they are imported, sealed, and the answers point at the new entries with their import dates. One question — why a March artifact carries a February recorded date — is answered with the producing product's export schedule, and the auditor closes it in the thread.
At close-out the thread reads 13 asked, 13 answered, none outstanding. Eighteen months later a successor auditor, granted the room for the next cycle, reads the thread before her first meeting and arrives already knowing which three areas were probed hardest last cycle. The conversation, retained in place, did onboarding work no handover document ever has.
Frequently asked questions
Who can ask and answer questions in a room?
The room's owner (the auditee side) and the auditor granted to that room. Access follows the room's scope exactly — there is no public or account-wide visibility of the thread.
Are questions retained after the engagement ends?
Yes. The thread is part of the room's record and is retained for the room's retention life — up to 10 years on paid plans — and protected while a legal hold stands.
What if an answer needs a new document?
Import it first, through the proper path — suite import unchanged, or direct upload badged as such — then answer pointing at the new manifest entry. The thread then documents both the gap and its closure.
Can I use the thread before an auditor is engaged?
Yes — as a rehearsal tool. Teams raise the questions they expect, answer them from the room, and convert gaps into filing tasks while there is still time.
Does the thread replace the auditor's report?
No. The thread is the examination's working exchange; the auditor's findings and report remain the auditor's own professional output. The thread supports the report by preserving what was asked and answered, in context.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: Stale Audit Evidence: The 365-Day Freshness Rule Explained · Next: How Auditees and Auditors Share Evidence Securely
Evidence Room vs Shared Drive: An Honest Comparison · How to Organise AI Audit Evidence by Period · What Evidence Does a CPPA Cybersecurity Audit Need?