Read the scope before the summary
Begin with the candidate and case reference, the requested checks, the report version and release status. A report should identify which claims were reviewed and which sources or methods were used. A summary cannot tell you what was never included.
Do not compare two reports as if they are equivalent when they cover different employers, qualifications, addresses, periods or jurisdictions. Ask for clarification of scope before relying on the comparison.
Separate the candidate claim from the source response
The candidate-provided information describes what was claimed. The verified details describe what the selected source confirmed. Review the comparison at field level: an employer trading-name variation, a missing date and a material contradiction are not the same finding.
- Check the employer or institution and record period.
- Identify the source and the date of verification.
- Read the specific discrepancy or limitation.
- Check whether candidate clarification is still outstanding.
Interpret outcomes responsibly
Consistent information means the compared fields aligned within the recorded scope. A discrepancy needs review against the underlying evidence and employer policy. An incomplete or unavailable response should explain what prevented a conclusion.
A pending item should not be converted into an adverse conclusion merely to finish the case. Likewise, a possible name match needs identity review before it is attributed to the candidate.
Use the correct version and protect the evidence
Use the released report version rather than an internal draft or an outdated attachment. Where a report includes an authenticity reference, use the designated verification page to check that reference; authenticity checking does not expand the report's scope.
Restrict access to people with an approved business need. Do not publish candidate reports, personal identifiers or evidence as marketing examples. A demonstration report must be labelled as fictional and must not be used for an actual hiring decision.
Check report identity, scope and version
Confirm the candidate and case reference, client, requested checks, covered records, release status and report version. A final report should be distinguishable from a draft, interim view or internal quality-review screen.
If an authenticity reference is provided, use the designated verification route. Authenticity confirms the reference and version; it does not add checks that were never in scope.
Read each status with the finding
A status such as consistent, discrepancy, incomplete, unavailable or pending needs the underlying candidate claim, source response and limitation. The same label can represent very different operational situations when that context is omitted.
Review check-level data before using a case summary. One pending education check should not obscure completed identity and employment work.
Distinguish facts, limitations and employer decisions
Verification findings state what was compared and returned. Limitations describe what the source or method could not establish. The employer's decision applies its own policy and role context after reviewing those facts.
Keeping these layers separate supports consistent candidate treatment and prevents a verification provider from making an unsupported hiring recommendation.
Handle revisions and report sharing
Use the newest authorised release while retaining the reason and audit history for a supported correction. Do not edit a downloaded report or circulate an internal draft as the final version.
Share reports only with authorised recipients and avoid placing candidate reports in public examples. Demonstration reports should use fictional data and be labelled clearly.
Frequently asked questions
What should a background verification report contain?
It should identify the candidate and case, scope, source or method, compared values, findings, discrepancies, limitations, review state, release date and version.
Does a green or clear status guarantee future conduct?
No. It records the result within the documented scope and date. It is not a guarantee of future behaviour or information outside the checks performed.
How should an updated report be handled?
Use a controlled new version with the correction reason and review trail. Authorised users should be able to distinguish it from the earlier release.