Hailey's evidence validation capability is being extended into the Custom Registers architecture, starting with the Tests and Evidence registers. With richer context available -- test definitions, linked controls, framework mappings, and connected organisational data -- Hailey can validate evidence the way an experienced auditor would, not just check that something was submitted.

The capability is designed around three personas: control owners who define requirements, evidence submitters who respond to tasks, and evaluators who review submissions.

Key Components:

• Validation Guide Generation: When a test is created, Hailey automatically generates a guide defining what valid evidence looks like for that context. Guides are editable by the control owner to accommodate organisation-specific requirements.
• Submitter Experience: Submitters see the validation guide before uploading, can ask Hailey plain-language questions about what to provide, and receive specific feedback on any gaps before submission is confirmed. Iterative rounds are supported.
• Auditable Override: If a submitter believes their evidence is valid despite Hailey's assessment, they can override with a written explanation -- creating a record visible to the evaluator.
• Evaluator Experience: Evaluators receive submissions with Hailey's full validation history attached, including any overrides and the submitter's rationale.
• Knowledge Graph-Powered Validation: Hailey reasons across linked organisational data -- asset registers, system inventories, existing evidence -- to catch discrepancies that a document-only review would miss.
• Manual and Automated Test Modes: Automated tests are validated through integrations with no task required. Manual tests use the task workflow. Both surface validation status on the test record.

Benefits:

• Eliminates the evidence back-and-forth loop -- submitters get clear guidance upfront, evaluators receive pre-validated submissions.
• Validation uses linked organisational context, not just the submitted document, catching gaps that would otherwise reach the reviewer.
• Full audit trail across every submission round, override, and automated validation result.
• Works across file uploads, written descriptions, and pasted content -- no submission format is treated as second-class.

Example use case:

A systems administrator is assigned a task to provide evidence for a quarterly privileged access review. They ask Hailey what to submit and receive specific guidance. They upload a PAM export -- Hailey flags that it covers 47 accounts but the linked asset register shows 112 systems in scope. The administrator uploads a second export to address the gap. Hailey confirms coverage and the task is submitted. The evaluator receives the submission with the full validation history attached and can review with confidence, without performing a manual first-pass quality check.