Documents & evidence

Ask for the evidence you need.

Set document requirements, collect secure uploads and review what has been supplied. Keep requests, replacements and review history connected to the application.

See the workflow

Keyholder document settings with controls for payslip count, pay frequency, maximum payslip age, tax year and amount tolerance. — Real Keyholder screen · example document requirements. Payslip count, frequency, age and tax year are configurable.

Conditional evidence requirements.

Make evidence requirements conditional on answers, household circumstances, scheme rules or the type of application.

Reusable rules help teams request supporting material at the right point in the process, including follow-up requests where evidence is missing or unclear.

Evidence requirements: Specify the document required and the period it should cover. For payslips, configure the number, frequency and acceptable age.
Conditional document requests: Ask for supporting documents when the applicant’s answers or circumstances make them relevant.
Decision context: Keep the supporting material beside the application, policy rule or assessment it informed.

A test application in Keyholder showing a bank statement upload, a check result, a Replace file action and a question about income. — Real Keyholder screen · test application. The upload, check result and replacement action sit together. Requirements shown are examples.

Upload, check, review.

Give applicants a clear place to provide supporting material from their device. Keep the upload and its check result together.

Document-type recognition: Check whether a supported upload appears to match the type of evidence requested.
Extracted information: Use information read from supported documents to help with the review. The source document remains part of the evidence.
Structured review: Keep reviewer actions, notes and status changes tied to the evidence being assessed.

Make the next step clear when a file is unsuitable.

A missing pay period, the wrong document type or an unsuitable identity file needs a specific response.

Show the issue beside the upload and let the applicant replace the file. Where the workflow permits an acknowledgement to continue, that is distinct from the document passing a check.

A document result is evidence for review. It does not, on its own, establish identity or decide eligibility.

Keyholder flags unsuitable test files supplied as proof of income and identity, explains the issues and offers Replace file or an acknowledgement to continue. — Real Keyholder screen · deliberately unsuitable demonstration files. The applicant can replace a file or acknowledge the warning where permitted.

Retain the review history.

Keep a record of what was requested, what was supplied and what happened next. Follow-up evidence should stay connected to the review that prompted it.

The record connects the evidence requirements, uploads, missing or unsuitable material, replacement requests and reviewer notes to the assessment and recorded decision.

Eligibility & decisioning Security & compliance

Ask for the evidence you need.

Conditional evidence requirements.

Upload, check, review.

Make the next step clear when a file is unsuitable.

Retain the review history.

Strictly necessary

Functional