Build a defensible, job-relevant recruiting process — structured screening, decision documentation, and audit-ready records

ZeroTwo helps recruiting agencies standardize the process documentation that makes hiring decisions defensible: structured screening questions tied to job requirements, rejection rationale templates that cite specific criteria, internal notes that use job-relevant language, and audit trails for client files. This is operational support for a more consistent process — not legal advice. Broker and attorney review owns final compliance interpretation.

Build your compliance documentation

Compliance Documentation — Sr. PM Search

Screening Process Audit

Structured questions5 knockout + 8 phone screen — all job-relevant

Decision documentationAdvance rationale — rubric evidence cited

Rejection rationaleCriterion-based — no protected class language

Internal notes audit3 risky phrases flagged and replaced

Client file documentationAudit trail complete — ready for review

ZeroTwo

I've flagged 3 internal notes with language that's potentially risky: (1) 'She seemed unsure' — replaced with 'Candidate did not provide a specific example for the leadership dimension — see Q3 transcript note.' (2) 'Overqualified' — flagged as potentially age-related — replaced with 'Candidate's comp expectations ($185K) exceed the approved budget ceiling.' (3) 'Not a culture fit' — replaced with 'Candidate's preferred work structure (independent, low-collaboration) does not match the cross-functional alignment requirement in dimension 3.'

Structured Screening Questions

Q1: FinTech domain (job-relevant)'What payment infrastructure have you shipped end-to-end?'

Q2: Leadership (job-relevant)'Describe a performance conversation you led with a direct report.'

Q3: Cross-functional (job-relevant)'Give an example of driving alignment between eng and a business stakeholder.'

Q4: Decision-making (job-relevant)'Walk me through a product decision where data and instinct conflicted.'

Q5: Availability (neutral)'What does your start-date timeline look like?'

Decision Documentation — Jordan M.

Advance rationaleDomain: confirmed payment infra at Stripe — 3/4 criteria met

Leadership rationale2 direct reports — flagged vs. 3 spec — documented

Communication rationaleCross-functional example: Checkout v2 — eng/design/legal aligned

Comp documented$142K confirmed — within range

Next stepAdvance to panel — flag leadership criterion with HM

Rejection Rationale Templates

Failed domain criterion'No B2B payment infrastructure experience per Q1 response.'

Failed leadership criterion'Direct report experience not confirmed — IC-only background per Q2.'

Comp mismatch'Comp expectation ($185K) exceeds approved budget ceiling ($145K).'

Availability mismatch'Start date required: 30 days. Candidate requires 90-day notice.'

Multiple criteria'Did not meet domain or leadership threshold — see rubric scores.'

Internal Note Audit — Flagged Phrases

'She seemed unsure'Replace: 'Candidate did not provide specific leadership example per Q2.'

'Overqualified'Replace: 'Comp expectation exceeds approved budget — documented.'

'Not a culture fit'Replace: 'Preferred work style conflicts with dimension 3 (cross-functional alignment).'

'Great energy'Insufficient — add: 'Stakeholder communication example: [specific detail].'

No flags (baseline)All job-relevant language — documented rubric evidence

Compliance documentation tools built for recruiting agencies

Structured questions tied to job requirements, not gut feel

ZeroTwo generates screening questions that are explicitly tied to job-relevant competencies — so every question has a clear job-relevance rationale and a specific criterion it tests. EEOC guidance on selection procedures is clear: job-relevance is the foundation of defensibility.

Rejection rationale that cites criteria, not impressions

ZeroTwo produces rejection rationale templates that cite the specific criterion not met, the evidence from the screening conversation, and the documented threshold — not impressions, hunches, or language that could be misconstrued as protected-class-related.

Internal note audit that flags risky language before it's in the file

ZeroTwo reviews internal recruiter notes and flags phrases that are vague, impression-based, or potentially associated with protected characteristics — and suggests replacements that are job-relevant and evidence-based. The replacement language is always stronger, not just safer.

How to build compliant recruiting documentation with ZeroTwo

Step 1

Generate job-relevant structured questions

Share the role brief and competency rubric. ZeroTwo generates screening questions explicitly tied to each job requirement — with a one-line job-relevance rationale for each question that documents why it was asked.

Step 2

Document advance and rejection decisions

After each screening conversation, ZeroTwo generates the decision documentation: what criterion was evaluated, what evidence the candidate provided, what score was assigned, and what the advance or rejection rationale is — all in job-relevant language.

Step 3

Audit internal notes for risky language

ZeroTwo reviews recruiter internal notes for phrases that are vague, impression-based, or potentially associated with protected characteristics — and suggests job-relevant, evidence-based replacements that are also more accurate.

Step 4

Build the audit trail for the client file

ZeroTwo compiles the structured screening records, decision documentation, and rejection rationales into an audit-ready client file — organized by candidate and search — so the documentation is complete if the process is ever reviewed. Not a substitute for legal review.

Step 1

Generate job-relevant structured questions

More ways to use ZeroTwo for structured screening and compliance

Generate structured screening questions

Generate 5 structured screening questions for this role — each tied to a specific job requirement with a one-line job-relevance rationale, a follow-up probe, and a pass/fail threshold description.

Write advance decision documentation

Write advance decision documentation for this candidate — what criterion was evaluated, what evidence they provided per question, the rubric score per dimension, and the rationale for advancing to the next stage.

Write rejection rationale from rubric

Write a rejection rationale for this candidate — which specific criterion they did not meet, what the evidence from the screening supports, and the documented threshold they fell below — in job-relevant language only.

Audit internal notes for risky language

Review these internal recruiter notes and flag any phrases that are vague, impression-based, or potentially associated with protected characteristics — and suggest job-relevant, evidence-based replacements for each flagged phrase.

Replace 'culture fit' language

Review these internal notes for any use of 'culture fit,' 'not a fit,' or similar vague language — and replace each with a specific, job-relevant observation tied to a documented competency or observable behavior.

Write note-taking guidelines for recruiters

Write recruiter note-taking guidelines — what language to use and avoid, how to document evidence from screening conversations, what constitutes a sufficient vs. insufficient note, and how to document a rejection without creating risk.

Build audit-ready candidate file summary

Build an audit-ready candidate file summary — screening questions asked, candidate responses summarized, rubric scores per dimension, advance or rejection rationale, and the timeline of each interaction.

Write job-relevance rationale for each question

For each screening question in this guide, write a one-sentence job-relevance rationale — why this specific question is directly relevant to the job requirement and how it evaluates a specific competency.

Write consistent rejection email template

Write a candidate rejection email template — professional, warm, and honest — that does not contain language referencing protected characteristics or vague impressions, and that keeps the door open appropriately.

Build screening compliance checklist

Build a screening compliance checklist for this agency — what structured elements must be present in every search, what language to avoid in notes, what documentation is required per candidate, and what the review process is before closing a search.

Generate structured screening questions

Generate 5 structured screening questions for this role — each tied to a specific job requirement with a one-line job-relevance rationale, a follow-up probe, and a pass/fail threshold description.

Write advance decision documentation

Write rejection rationale from rubric

Audit internal notes for risky language

Replace 'culture fit' language

Write note-taking guidelines for recruiters

Build audit-ready candidate file summary

Write job-relevance rationale for each question

Write consistent rejection email template

Build screening compliance checklist

More ways to use ZeroTwo

Skills-first screening and interview rubrics
The structured rubric is the foundation of defensible screening — ZeroTwo builds it from the role requirements.
Resume screening and shortlist creation
ZeroTwo scores resumes against the same job-relevant rubric — consistent, criterion-based, documentable.
Agency SOPs and recruiting playbooks
Compliance documentation becomes part of the agency's operating system — ZeroTwo builds the playbooks.

A consistent, job-relevant process is easier to defend — and it produces better hires.

Structured screening isn't just a risk-reduction strategy — it's also how you improve quality of hire. Use ZeroTwo to build the job-relevant questions, document every decision with rubric evidence, and audit your internal notes for language that creates risk — so your process is both defensible and effective. Not legal advice.

Build your compliance documentation