A dossier should show the path, not just the conclusion
A traditional candidate submission often compresses a resume into a persuasive summary. That can help a client scan the file, but it can also detach the statement from its source and hide where a recruiter made an inference.
A reviewable dossier uses a different structure. It keeps the job requirement, candidate-supplied evidence, unresolved detail, and recruiter judgment together. The client can inspect the source behind a claim and see what remains open.
The dossier is not a candidate scorecard. It is a requirement-by-requirement review packet.
Start with the reviewed requirement set
The top of the dossier should identify the exact requirement-set version used for review. For each requirement, include:
- A stable requirement ID.
- The atomic requirement text.
- Essential, preferred, or unclear classification.
- The source wording from the job description.
- The author review status.
- Confirmation status for the job-related rationale.
If the client changes the role brief, the dossier should identify the new requirement-set version. An older submission should not silently inherit later requirements.
Attach exact evidence to supported statements
For an evidenced or partially evidenced requirement, include the exact candidate-supplied excerpt and enough source location detail to find it again. Depending on the document format, that can include page, line, section label, and character offsets.
An evidence entry should answer:
- Which requirement does this support?
- What exact text was found?
- Where did it appear in the submitted source?
- Was the citation verified against the processed text?
- What part of the requirement remains unresolved?
A summary can sit beside the source, but it should not replace the source.
Make the verdict language precise
Use verdicts that describe the evidence state:
- Evidenced: a verified citation directly supports the requirement.
- Partially evidenced: a verified citation supports part of the requirement.
- Not evidenced: no verified citation was found in the submitted source.
- Needs review: processing or interpretation is uncertain.
Avoid verdicts that imply a final employment decision. The dossier helps a person review evidence. It does not determine whether the candidate should be hired, rejected, ranked, or advanced.
Show unresolved details as work to do
A useful dossier does not hide gaps. It turns them into specific review prompts.
Instead of "certification missing," write: "No current certification citation was found in the submitted resume. Confirm current status with the candidate."
Instead of "no VMS experience," write: "The resume describes a client vendor portal but does not name the system. Recruiter review is required."
The wording stays tied to the source and gives the recruiter a next action.
Include the suppression manifest
The dossier should explain which categories were suppressed before inference and how many instances were found. It should not reproduce the suppressed values.
Useful fields include:
- Category name.
- Suppressed count.
- Total suppressed count.
- Suppression-rule version.
The manifest helps the reviewer understand what context the model did not receive. It is not proof that every proxy was removed or that a process is free from bias.
Preserve system and prompt identifiers
Results can change when the model, model revision, prompt, extraction rules, or output schema changes. Keep the identifiers needed to reconstruct the processing context:
- Model identifier and pinned revision.
- Prompt version.
- Output-schema version.
- Document parser version when relevant.
- Suppression-rule version.
- Request and result timestamps.
These fields belong in the decision record even when the client-facing view presents them in a compact technical appendix.
Record human review and overrides
The recruiter remains responsible for the final review. The dossier should therefore include:
- Reviewer reference.
- Review timestamp.
- Decision stage.
- Any override to a system-produced binding.
- The reason for the override.
- A reference to the previous record version.
An override is not an error to hide. It is evidence that a person reviewed the source and made a documented judgment.
Keep product boundaries visible
Every evidence dossier should state "Evidence output requires human review." It should also show the fixed constraints that matter to interpretation:
- External enrichment sources: 0.
- Uploaded documents retained: 0.
- The result is limited to the submitted job description and resume.
- The result cannot be the sole basis for an employment decision.
These statements keep a polished document from looking more authoritative than the process behind it.
Design for two levels of reading
A client may first scan the dossier, then inspect a disputed item. Support both tasks.
The scan view should make the requirement, verdict, and open question easy to find. The inspection view should expose the exact source excerpt, location, explanation, and record context. Do not make the client choose between a dense technical export and an unsupported summary.
The strongest dossier is useful precisely because it does not ask the reader to trust the summary alone.