What does the feature influence?
Record whether the feature screens, ranks, scores, summarizes, routes, recommends, or flags candidates, employees, or workers.
Small-team evidence
One AI hiring feature can still create a repeat evidence job.
A single ATS screen, ranking step, assessment summary, interview helper, or promotion workflow can still need an owner, purpose, vendor evidence, human review notes, and change tracking.
Evidence checklist
Small scope does not remove the need for basic records.
What evidence supports the feature?
Keep vendor summaries, limitations, reviewer instructions, disabling options, and change notices beside the tool record.
Who checks the output?
Write down reviewer ownership, override paths, exception handling, and the date the record was last refreshed.
Monthly workflow
Use the first feature as the start of the evidence file.
AI Hiring Compliance Radar turns one-off questions into a recurring operating rhythm for source notes, tool inventory, vendor questions, and evidence updates. It is operational readiness material, not legal advice.
After the first AI feature is mapped
Turn one feature into a maintained evidence workflow.
A single feature still needs a practical path from inventory to vendor evidence, reviewer notes, refresh cadence, and subscription access if the team wants monthly upkeep.
Route the feature record.
Use the Evidence Hub to decide whether this single feature belongs in tool inventory, vendor diligence, pre-audit prep, or the monthly operating file.
Open evidence hubDecide if the feature can change.
Vendor defaults, model providers, ranking logic, reviewer instructions, and evidence records can change after rollout. Compare monthly updates with a one-time checklist.
Compare monthly workflowReview the paid pack path.
Check the Pro contents, checkout access, and sample update before moving one-feature tracking into the paid operating file.
Review checkout access