Research note
How often do background check decisions lack a date?
A local method for measuring whether each background check decision records when the report was reviewed, when the candidate was notified, and who approved the result.
Published

Table of contents
Question and scope
The question covers decisions about a candidate or employee after a background check report has been received. It excludes the ordering step, the vendor's own quality process, and cases where no report was ever ordered. The scope is one employer, one role family, and one review window. The result describes that population and should not be read as a legal standard.
A decision is eligible when the record shows a final outcome such as proceed, hold, or withdraw. A case that is still open at the end of the window is counted separately. The reviewer should record the report identifier and the role for every case. This keeps the sample from mixing completed decisions with pending work.
The review records three dates: when the report was completed, when a person reviewed it, and when the candidate was notified if the outcome was adverse. A decision without any of these dates cannot show the sequence that the process requires. Report the dates separately because each one answers a different question. A missing notice date is not the same as a missing review date.
Definitions and evidence standard
Define a decision date as the date a named person accepted the outcome under the written criteria. A report completion date from the vendor is not a decision date. A status change in the applicant tracking system may be a decision only if the policy says so. The definition must be fixed before any case is reviewed.
Record the name and role of the reviewer and the approver for each case. A decision with a date but no named person cannot show that the authority was correct. The evidence standard includes both the person and the timestamp. A system log that shows only a status change is weaker than a signed decision note.
Separate a missing date from an inconsistent date. A missing date means the record has no timestamp, while an inconsistent date means two records disagree about when the decision happened. The two failures need different repairs. Report them separately so the team can fix the right problem.
Sampling and measurement
Freeze the list of completed decisions before reviewing any of them. Include more than one role family and more than one reviewer, and record the export time and the filter used to build the list. Do not remove a case because the record is hard to find. A sample drawn after seeing the result is not a fair test.
If the list is large, take a random sample and record the selection method. Keep the full population count beside the sample so a reader can see the coverage. A replaced case should be reported as a deviation. The sample should be large enough to show a pattern across reviewers.
Measure the number of decisions, the number with a report date, the number with a reviewer date, the number with a notice date, and the number with all three. Add the number with a named approver and the number where the dates are inconsistent. Report the counts by role family and reviewer group. A single percentage hides which part of the record is missing.
Findings and interpretation
Present the distribution before suggesting a cause. A cluster of missing notice dates may mean the notice is sent by a different team that does not update the record. A cluster under one reviewer may mean the decision note template is unclear. Read the actual cases behind the largest cluster before naming a reason.
Compare the missing-date rate with the age of the case. A decision made during a system migration may have a different record path. Report the migration or policy change with the result. The comparison keeps a temporary disruption from being read as a permanent habit.
Check whether decisions without a date were later repaired. A repaired case may have closed the file without proving that the original decision was controlled. Report the repair date and the evidence used. The timing matters for the control, not only for the file.
Limitations
The review measures the record attached to the decision, not whether the decision was fair or correct. A complete date can still support a poor outcome. It also cannot show whether the candidate understood the notice. The result describes documentation and sequence, not the full experience.
The written criteria may change during the window, and an older decision may follow a rule that was appropriate at the time. Record the criteria version rather than applying the current rule retroactively. A missing date under an old process may not be a current defect. The reviewer should state which version applied.
Deciding whether a status change counts as a decision requires judgment. Two reviewers may disagree about a case that was later reversed. Record the disagreements and resolve them with examples. A calibration set improves consistency across reviewers.
Practical next step
Add a decision date and an approver field to the adjudication record if the system allows it. The fields should accept a reference rather than a copy of the report. A visible date is easier to review than a note in a shared inbox. Start the fields with the next decision rather than waiting for a system change.
Assign one owner to check the dates and one approver to accept the record. The owner and approver should be named in the written process. A shared queue is not an owner. The approver should be able to return an incomplete case.
Test the fields for one month and compare the missing-date rate with the baseline. Keep the change if it catches a gap before the candidate is notified. If it adds work without changing the result, remove a field. The goal is a controlled decision, not a longer form.
Sources
References supplied with this research note.
| Source | Publisher | Context |
|---|---|---|
| U.S. Equal Employment Opportunity Commission, Background Checks | eeoc.gov | Primary reference supplied with this article. |
| Federal Trade Commission, What Employers Need to Know About the Fair Credit Reporting Act | ftc.gov | Primary reference supplied with this article. |
| National Institute of Standards and Technology, Privacy Framework | nist.gov | Primary reference supplied with this article. |
| U.S. Department of Labor, Recordkeeping | dol.gov | Primary reference supplied with this article. |