An employment gap is a period when a candidate was not employed. A date discrepancy is a conflict between the dates a candidate reported and the dates a previous employer or record confirms. They look similar on a timeline, but they call for different verification steps, different documentation, and in some cases different legal handling. Classifying a flagged case correctly is the first decision an HR reviewer has to make, not an afterthought to it.
Key Takeaways
- A gap is an absence of employment; a discrepancy is a conflict between two sources describing the same employment.
- Misclassifying one as the other leads to the wrong verification request and can delay or derail a hiring decision unnecessarily.
- Both can trigger the Fair Credit Reporting Act’s pre-adverse action process when the underlying report came from a consumer reporting agency, but the documentation that resolves each is different.
- A short checklist, applied consistently, prevents reviewers from defaulting to suspicion when a case is genuinely ambiguous.
- Some cases are both at once: a reported continuous timeline that turns out to hide a gap, or a reported gap that turns out to be a simple date error.
What Separates an Employment Gap From a Date Discrepancy
An employment gap is a period of time, typically 30 days or longer, during which a candidate reports no traditional employment. A date discrepancy is a specific conflict: the start or end date a candidate lists does not match the date confirmed by a previous employer, a payroll record, or another verified source. The difference is structural. A gap is defined by what is missing from the record. A discrepancy is defined by what the record contains that contradicts something else in the record.
This distinction matters because the two produce different documents. A gap shows up as empty space between two confirmed employment periods. A discrepancy shows up as two pieces of information about the same period that do not agree, such as a candidate listing March 2022 as a start date while the former employer’s records show April 2022. One is silence. The other is disagreement.
Reviewers sometimes use “discrepancy” as a general label for anything unusual on a timeline, which blurs the two together. That habit is worth resisting, because the response to a gap (asking what the candidate did during that time) is a different question from the response to a discrepancy (asking which of two conflicting dates is correct).
Why the Classification Changes What Happens Next
Once a timeline issue is flagged, the classification determines the next verification step.
What a Gap Review Requires
The reviewer’s task is to understand the period: what happened, whether it is job-relevant, and whether documentation exists. A gap review typically asks for context (education, caregiving, contract work, health recovery) and supporting material such as transcripts, tax documents, or a written explanation. There is no second date to reconcile because there is no conflicting record; there is only an absence to explain.
What a Discrepancy Review Requires
The reviewer’s task is reconciliation: determining which source is accurate. That usually means checking the original source, the former employer’s HR system, a pay stub, a 1099, or an offer letter, to confirm which date is correct. The candidate’s explanation matters, but resolution depends on matching records rather than context alone.
Why Misclassifying Either Wastes a Verification Cycle
Treating a discrepancy like a gap wastes a verification cycle asking a candidate to explain a period that was never empty, just misdated. Treating a gap like a discrepancy sends the reviewer looking for a second employer record that does not exist.
What Causes Each Type of Timeline Issue
Gaps and discrepancies tend to arise from different situations, which is part of why they call for different verification responses.
What Causes Gaps
Gaps commonly trace back to a genuine period without traditional employment, such as education, caregiving, health recovery, or a job search that took longer than expected. They can also trace back to work that does not appear in standard employer databases, such as short-term contract or gig work, which can look like an absence even when the candidate was actually engaged.
What Causes Discrepancies
Discrepancies commonly trace back to simple misremembering of an exact start or end date, informal date ranges recorded as “spring 2022” rather than a specific day, clerical errors in an employer’s own payroll or HR system, or a candidate rounding a date to make a transition look cleaner than it was. Less commonly, a discrepancy reflects an intentional attempt to obscure a short tenure or an unfavorable departure by shifting a date.
Why the Distinction in Causes Matters
A candidate off by a few days because they rounded to the first of the month is in a different position than one whose reported dates contradict a verified record by several months. Reviewers who understand the common, mostly benign causes behind each issue type are less likely to treat every flagged item as equally serious.
Comparing the Two at a Glance
| Employment Gap | Date Discrepancy | |
| What it is | A period with no employment confirmed by any source | A conflict between two sources describing the same employment |
| Typical trigger | Absence of a record for a stretch of time | Two dates that do not match for a shared period |
| Common causes | Career break, caregiving, education, unreported contract or gig work | Misremembered dates, informal date ranges, clerical error, occasionally deliberate rounding |
| What the reviewer verifies | Whether the period is job-relevant and documented | Which of the conflicting dates is accurate |
| Documentation typically requested | Transcripts, tax records, caregiving confirmation, freelance references | Pay stubs, offer letters, employer HR system confirmation |
| Resolution path | Individualized review of context and supporting material | Reconciliation against the original source record |
A Decision Framework for Classifying a Flagged Timeline Issue
A short, consistent checklist applied at the point a timeline issue is flagged keeps reviewers from guessing case by case.
- Is there a period with no employment reported by either the candidate or any verified source? If yes, this is a gap. Move to gap review: request context and supporting documentation for that period.
- Is there a period where employment is reported by the candidate, a former employer, or another source, but the specific dates disagree? If yes, this is a discrepancy. Move to discrepancy review: identify the conflicting sources and attempt to confirm the correct dates.
- Is the disagreement about whether employment happened at all, rather than when? This usually signals a discrepancy rather than a gap, since the dispute is about the existence of a record, not the length of an absence.
- Does the candidate’s account and the verified record disagree by a small margin, such as a few days or a couple of weeks, around a transition between two jobs? This is a minor discrepancy and commonly resolved without escalation, since off-by-a-few-days conflicts around job transitions are common and rarely material.
This checklist does the same work for every candidate. A consistent classification standard, applied the same way regardless of who the candidate is, is what keeps a screening program defensible if a decision is ever challenged. Because gap and discrepancy documentation often includes sensitive material such as tax records, pay stubs, or identity documents, collect only what the classification requires, store it securely, and retain it no longer than policy and applicable law require.
When a Gap Turns Out to Be a Discrepancy, and a Discrepancy Turns Out to Be a Gap
Some cases do not resolve cleanly on the first pass.
When a Continuous Timeline Hides a Gap
A candidate lists two jobs as back to back, but employer verification shows a period of several months between the confirmed end date of one and the confirmed start date of the other. What looked, at first read, like a possible date discrepancy (the dates do not match what the candidate wrote) is actually an undisclosed gap. The correct next step is a gap review: ask what happened during the unreported period, not simply which date is right.
When a Reported Gap Is Actually a Discrepancy
A candidate discloses what looks like a gap on their resume, but a closer check shows they were working in a role or arrangement that did not surface in a standard database search, such as contract, freelance, or gig work. Once that employment is confirmed, the “gap” collapses into a straightforward date discrepancy: the resume’s informal date range simply did not match the confirmed record for that engagement. The correct next step shifts from asking what the candidate did to confirming the correct start and end dates for the work that did happen.
The Practical Lesson
The first read of a flagged timeline issue is a hypothesis, not a conclusion. Building in one verification step before finalizing a classification, rather than routing straight to a resolution, catches both of these misreads before they affect a hiring decision.
How FCRA Notice Requirements and Individualized Assessment Apply to Both
The Fair Credit Reporting Act‘s adverse action process applies whether the flagged issue is a gap or a discrepancy, when the finding comes from a report obtained through a consumer reporting agency rather than an employer’s own direct, unassisted inquiry. Because both a gap and a discrepancy can be information in that report that influences a hiring decision, before an employer can rescind an offer based on either, standard practice under the FCRA’s two-step process requires a pre-adverse action notice that includes a copy of the background report and the Summary of Rights, followed by a reasonable window for the candidate to respond before a final adverse action notice is issued (FTC, Using Consumer Reports: What Employers Need to Know). What counts as a reasonable response window, and whether additional state or local notice requirements apply, varies by jurisdiction; multistate employers should confirm the applicable local rule rather than apply a single national timeline.
What differs is not whether the FCRA notice process applies, but what a reviewer is assessing for during that window. The Equal Employment Opportunity Commission’s guidance on individualized assessment, developed specifically in the context of criminal history review under Title VII, establishes the underlying principle that hiring decisions should consider the specific circumstance in front of the reviewer rather than apply a fixed rule regardless of context (EEOC, Enforcement Guidance on the Consideration of Arrest and Conviction Records in Employment Decisions Under Title VII, April 25, 2012). That principle, extended by analogy rather than by direct legal requirement, is a useful discipline for gap and discrepancy review as well. For a gap, that means considering the explanation and its documentation on its own terms. For a discrepancy, that means considering which record is accurate and whether the size of the conflict is material to the role, rather than treating every date mismatch as equivalent to every other one.
A blanket rule such as automatic disqualification for any gap over a fixed length, or automatic disqualification for any date mismatch regardless of size, removes that individualized review and, under the same Title VII disparate-impact reasoning EEOC guidance applies to criminal history policies, raises the risk that a policy which is neutral on its face could disproportionately screen out protected groups without being job-related and consistent with business necessity (EEOC, Enforcement Guidance on the Consideration of Arrest and Conviction Records in Employment Decisions Under Title VII, April 25, 2012).
How Verification Tools Flag Each Type Differently
Automated employment verification tools generally detect gaps and discrepancies through different mechanisms, which is worth understanding even for HR teams that rely on a third-party screening partner rather than building detection logic themselves.
How Gaps Are Flagged
A gap is typically flagged by comparing the full timeline a candidate reports against what any source can confirm and identifying the empty space between two confirmed periods. The system is looking for absence: no record, from any source, covering a given stretch of time. Because absence is the trigger, a verification tool has to distinguish a true gap from a period covered by employment that simply is not in a traditional database, such as freelance platforms or short-term contracts, before it flags anything to a reviewer.
How Discrepancies Are Flagged
A discrepancy is typically flagged by comparing two populated data points against each other, the date a candidate entered versus the date a former employer’s record shows, and identifying where they do not match. The system is looking for conflict, not absence, which means the detection depends on having at least two sources to compare in the first place. A single unverifiable date, with no second source to check it against, cannot technically produce a discrepancy; it can only produce an open question.
Why Continuous Verification Surfaces More
This is one reason continuous, ongoing verification tends to identify discrepancies earlier than a one-time check performed only at the point of hire. A single snapshot compares a candidate’s stated timeline against whatever records are available at that moment. Ongoing verification has more opportunities to surface a new source or a corrected date after the initial check, information that would otherwise leave a discrepancy undetected until a later screening cycle.
Building a Consistent Classification Process Across Your Hiring Team
Consistency across reviewers is what makes a classification framework defensible rather than a matter of individual judgment. A few practices support that consistency.
- Standardize the intake question. Application materials should ask candidates for complete employment history with specific start and end dates, rather than approximate ranges, since approximate dates are a common source of discrepancies that are not actually deception, just imprecision.
- Document the classification decision, not only the resolution. Recording that a case was classified as a gap or a discrepancy, and why, gives a reviewer’s later decision context if a candidate or a regulator ever questions it.
- Set a materiality threshold in writing for discrepancies. Many organizations treat a date conflict of a few days to a few weeks around a job transition differently from a conflict of several months, since the first is common and rarely indicates more than imprecise recordkeeping.
- Route escalations the same way every time. When a case does not resolve cleanly on the first classification pass, whether it looks like a hidden gap or a reclassified discrepancy, send it through the same secondary review step rather than an ad hoc judgment call.
- Separate the classification decision from the hiring decision. Classifying an issue as a gap or a discrepancy is a fact-finding step, not a verdict on the candidate. Deciding what the verified facts mean for the role is a separate step that follows.
- Give candidates a clear channel to respond. A generic “please explain” request can leave a candidate unsure what would resolve their case. Naming the specific issue, an unexplained period versus a specific date conflict, and what documentation would help, makes the request easier to answer and evaluate consistently.
Getting the Classification Right Is a Fairness Decision
Classifying a flagged timeline issue correctly is not a procedural nicety. It is what Fair Compliance, one of the pillars of GCheck’s Compliance for Good® standard, looks like in practice: applying an individualized, consistent standard rather than letting an ambiguous case default to the worst-case reading. Pairing that with Transparent Compliance, telling a candidate specifically what was flagged and what would resolve it, turns a confusing verification step into a clear, dignified request. Both matter more in exactly the moment a case does not sort itself neatly into “gap” or “discrepancy” on the first read.
Frequently Asked Questions
What is the difference between an employment gap and a date discrepancy?
An employment gap is a period with no employment reported by the candidate or confirmed by any source. A date discrepancy is a conflict between two sources describing dates for employment that did happen, such as a candidate-reported date not matching an employer-verified date.
Can a background check show both a gap and a discrepancy for the same period?
Yes. A period can start out looking like one and resolve as the other once verification is complete, such as a reported continuous timeline that verification reveals actually contains an undisclosed gap, or a reported gap that verification reveals was actually a period of contract or freelance work with a mismatched date range.
Does the Fair Credit Reporting Act treat gaps and discrepancies differently?
The FCRA’s pre-adverse action and adverse action notice requirements apply to both, when the finding comes from a report obtained through a consumer reporting agency and could influence a hiring decision. What differs is the individualized assessment itself: reviewing context and documentation for a gap, and reconciling conflicting records for a discrepancy, rather than the notice process, which is the same.
How big does a date discrepancy need to be before it’s a concern?
There is no single legal threshold. Many employers treat a difference of a few days to a few weeks around a job transition as a minor discrepancy that rarely raises concern, and reserve closer review for conflicts of several months or more, or for a pattern of repeated discrepancies across a candidate’s history. Writing this threshold into policy helps apply it consistently.
How should HR handle a case that looks like a gap but might actually be a discrepancy?
Verify before classifying. Check whether any source, including contract, freelance, or gig-work records, confirms employment during the period in question. If employment is confirmed, the case is a discrepancy about the correct dates, not a gap about an absence of employment, and the next step is reconciling the dates rather than asking the candidate to explain an empty period.
Sources cited
- Fair Credit Reporting Act §604(b) and §615(a), 15 U.S.C. §§ 1681b(b), 1681m(a) (pre-adverse action and adverse action notice requirements)
- U.S. Equal Employment Opportunity Commission, Enforcement Guidance on the Consideration of Arrest and Conviction Records in Employment Decisions Under Title VII, April 25, 2012 (individualized assessment principle, applied here by extension to non-criminal background check findings)
- Federal Trade Commission, Using Consumer Reports: What Employers Need to Know
ABOUT THE CREATOR
Charm Paz, CHRP
Recruiter & Editor
Charm Paz is an HR professional at GCheck, specializing in background screening, fair hiring, and regulatory compliance. She holds from the Professional Background Screening Association (PBSA) and helps organizations navigate employment regulations with clarity and confidence.
With a background in Industrial and Organizational Psychology, she translates policy into practice to build ethical, compliant, human-centered hiring systems that strengthen decision-making over time.
