Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
AI Auditor Vetting: How the Owner-Run Workflow Works
Short answer
Vetting on AI Audit Exchange is an owner-run workflow with three outcomes: a registration sits pending and unlisted, passes and becomes a vetted listing in the auditor directory, or is declined. Auditors state their credentials as their own claims; vetting records the platform's onboarding decision about listing — not a state licence, not registry membership, not a guarantee of any auditor's work. Only vetted auditors appear in the directory and may respond to engagements, and the directory publishes no auditor counts and no network claims.
What is auditor vetting?
Auditor vetting is the owner-run onboarding workflow on AI Audit Exchange that decides whether a registered auditor is listed in the directory. It operates on the auditor's registration — firm name and credentials stated as claims — and produces a status: pending, vetted or rejected. The platform's owner statistics track vetted auditors against a copy threshold of 25, below which no network-of-auditors language or auditor counts appear in public copy.
Why a gate exists at all
A directory anyone can join by typing is not a directory; it is a wall of claims. Auditees making independence decisions need to know that the auditors responding to their briefs have passed some accountable human review before listing. Vetting is that review — deliberately owner-run rather than automated, because the judgements involved (does this registration describe a real practice, are its claims coherent, does it belong in a directory for California SB 1119 and CPPA work) are judgement calls. The gate is narrow on purpose: it governs listing, nothing more. It does not certify competence, and the platform says so everywhere the directory is described, because a gate oversold becomes a liability for everyone who relied on its overselling.
The three states of a registration
Pending is the starting state: registered, not listed, unable to respond to engagements. A pending auditor is invisible to the marketplace — auditees cannot find or accept them — which protects both sides from half-formed profiles entering live engagements. Vetted is the listed state: the profile appears in the directory, engagements can be responded to, and acceptances can make the auditor an auditor of record under scoped grants. Rejected closes the registration. The states are platform facts recorded per auditor, and the owner-facing side of the platform lists auditors with their statuses so the directory's population is always an auditable fact, not an impression.
Claims in, decision out: what vetting evaluates
The auditor's side of the record is claims: firm name, credentials, regime experience — stated in the auditor's own terms and preserved as stated. The platform never rewrites claims into endorsements. Vetting reads those claims and the registration around them and records a decision: list or do not list. That clean separation — their words, our decision — is maintained in the directory's presentation, where credentials appear as the auditor states them and vetted status appears as the platform's fact. Auditees are equipped to weigh both layers for what they are. See claims vs verification for how to read the two layers when choosing.
What vetting is not: three disclaimers that matter
First, vetting is not a state licence: the AI Auditor Registry framework reported under SB 813 / AB 1405 belongs to the state, and this private platform is not affiliated with or endorsed by any state registry, agency or government body. Second, vetting is not a quality guarantee for any specific engagement: fit — regime, evidence fluency, calendar — is judged by the auditee through the brief-and-response exchange. Third, vetting is not a numbers game the platform markets with: until 25 vetted auditors are verified in the platform's own database, public copy carries no network-of-auditors language and no auditor counts. That restraint is itself part of the vetting story: a directory that refuses to inflate itself is telling you how it treats every other claim.
Vetting from the auditee's side
As an auditee, treat vetted status as the floor of your diligence, not its ceiling. The floor matters: every respondent to your brief has passed the listing gate, so your comparison starts among accountable registrations. The ceiling is your own work: read the claims, ask the regime and method questions, and let the acceptance decision be yours. If an engagement ends badly, the record of it — brief, match, grants, thread — exists in the room, which is the accountability loop a paper directory never closes. And if an auditor's circumstances change, statuses can change with them; the directory you consult at engagement time is the current fact, not a cached reputation.
Vetting from the auditor's side
For auditors, the workflow asks patience and precision. Register with claims stated exactly as you can defend them; a registration under review is read by a human who will notice the difference between a practice described and a practice inflated. While pending, you are not listed and cannot respond — build nothing on expected timing. Once vetted, your listing is live in the directory and your claims represent you in every fit conversation. The auditors who thrive under this gate are the ones who treat it as the first exhibit of their professional standard: claims they can stand behind, in a directory that refuses to oversell them. The registration path is walked through in becoming a vetted auditor.
Five actions to take
- Auditors: register with firm name and credentials stated precisely as claims you can defend.
- Expect three states — pending (unlisted), vetted (listed), rejected — and plan nothing on pending timing.
- Auditees: treat vetted status as the floor of diligence and complete it with your own fit questions.
- Never describe vetting as a state licence or registry membership — it is the platform's listing decision.
- Check the directory at engagement time; statuses are current facts, not permanent reputations.
Worked example
A fictional solo practice, Ines Duarte Assurance, registers on a Monday with claims stated narrowly: CPPA cybersecurity examinations, mid-size deployers, evidence-room method described in two sentences. The registration sits pending while under owner review — unlisted, unable to respond — and is then vetted. Within the directory, the profile shows exactly what was claimed and the vetted status, nothing more: no counts of fellow auditors, no network language, because the platform's verified vetted population has not crossed the threshold at which such copy would even be considered.
Two engagements follow in the quarter. In both fit conversations, auditees say the same thing in different words: the narrowness of the claims is what they believed. Vetting's quiet design — human gate, claims preserved as claims, no marketing inflation around either — did exactly the work it exists to do.
Frequently asked questions
Who runs vetting?
The platform owner, through an owner-run workflow on each registration. It is a human listing decision, not an automated check or a purchased badge.
Can a pending auditor respond to my brief?
No. Only vetted auditors are listed in the directory and may respond to engagements. Pending registrations are invisible to auditees.
Does vetted mean licensed by California?
No. Vetting records the platform's onboarding decision. It is not a state licence or registry entry, and the platform is not affiliated with or endorsed by any state registry.
Why does the site publish no auditor counts?
By a standing copy rule: until 25 vetted auditors are database-verified, public copy carries no auditor counts and no network-of-auditors claims. The directory lists auditors; it does not inflate them.
Can vetting status change after listing?
Statuses are platform records and are managed through the same owner workflow — treat the directory state at the time you engage as the operative fact.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: How to Verify an Artifact Hash in an Evidence Room · Next: Auditor Credentials: Claims vs Verified Facts, Explained
How Matching Works Between Auditees and Auditors · Multi-Client Evidence Rooms: An Auditor's Practice Guide · Evidence Rooms for AI Audit Agencies and Teams