
A red flag in a background verification (BGV) report means one check found something that doesn't match what the candidate told you, or found a record that might be theirs. It's a question to answer. It isn't a verdict. Read what the candidate claimed next to what the source found, confirm the record belongs to them, ask them to explain with evidence, then decide using your written policy for that role. Plenty turn out to be a rounded date or a namesake. The ones that don't are much easier to defend once you've followed those steps.
If your team reads these reports every week, we built SpringVerify for this moment. Every flag comes with the evidence behind it: the employer's or university's reply, the graded court match, the contact log. You decide on facts, not on a colour.
It's 4:45 on a Friday. Four checks are green and one is red. The hiring manager messages: "Can she start Monday?" This guide is for the next ten minutes.
In summary
A red flag means a check returned a discrepancy (the candidate's claim and the source's answer differ) or an adverse finding (such as a court record that may match them). It tells you where to look. It doesn't tell you what to decide. Whether it matters depends on what was found, whether it's confirmed and whether it affects the job.
Colour codes help you triage, but they aren't standard. Each provider defines its own, so one vendor's "amber" can be another's "red". Before you act on a colour, read the reason written beside it.
Here's how the common statuses usually read, and what to do with each:
| Status you see | What it usually means | What to do next |
|---|---|---|
| Green / Clear | The source confirmed what the candidate declared | Check that every check the role needs was ordered, then close |
| Amber / Minor discrepancy | Mostly confirmed, with a small difference (a date, a title format) | Read the exact fields; ask a quick question if it matters for the role |
| Red / Discrepancy or adverse | The source contradicts the claim, or a record may match the candidate | Confirm identity and evidence, ask the candidate to explain, then apply policy |
| Insufficiency | Something is missing: a document, a contact, a full address | Get the candidate or your team to supply it; the check can't finish without it |
| Unable to verify (UTV) | The source couldn't or wouldn't confirm, despite repeated attempts | Look for another source; don't treat silence as proof of fraud |
| In progress / Pending | The check isn't finished | Track what it's waiting on and when it will next update |
| Closed | The check was stopped, for example because the candidate withdrew | Not a result; nothing to adjudicate |
Adjudication is the employer's decision on a finding, weighed against its hiring policy. Keep it separate from the vendor's status. A report can say "discrepancy" and your decision can still be "proceed", as long as you write down why.
Work through five questions, in order, before you contact anyone. They tell you whether you're dealing with a real contradiction, a mistaken match or an unfinished check, and each needs a different next step.
A good report answers questions 1 to 3 before you open it. That's why our employment verification report records the joining date and last working day confirmed by each past employer, the designation they confirm, their answers on exit formalities, rehire eligibility and integrity issues, and the source for each point, timestamped and exportable as a PDF.
Many red flags have an ordinary explanation: a rounded date, a staffing-agency payroll, a company that changed its name. The serious ones are a confirmed fabrication, a credential the role depends on that turns out to be false, or a relevant court matter that's confirmed as the candidate's. This table sets out how to tell them apart for each check.
| Finding | Often innocent because | Becomes serious when | Ask for |
|---|---|---|---|
| Employment dates differ | Candidates round dates; probation start and confirmation dates get mixed up | The gap inflates experience the role required, or the employer contradicts it outright | Offer and relieving letters, payslips for the disputed months |
| Designation differs | Internal titles differ from LinkedIn titles; group companies use different grades | A senior title was claimed to meet a role requirement | Appointment or promotion letter |
| Employer can't be found | Brand name differs from the registered name; company merged or closed | No registration, no EPFO trace and no other evidence of the job | Registered company name, PF details, Form 16 |
| Negative exit feedback or "not eligible for rehire" | A dispute over notice period or full and final settlement | The employer reports an integrity issue tied to the role | The candidate's account, plus any settlement or relieving letter |
| Two jobs overlap | A PF contribution posted late, or a notice period served while starting elsewhere | Both jobs were active at once and your policy or contract bars dual employment | Actual last working day and joining date from both employers |
| Degree, year or marks differ | Universities record enrolment, exam and convocation years differently | The institution isn't on the UGC, AICTE or DEB recognition lists, the degree doesn't exist or the marks were altered | Marksheets, provisional and final certificates |
| Address not verified | The candidate moved, or the house was locked when the agent visited | The address doesn't exist and the role involves field work or customer visits | Current address proof and a fresh check |
| Identity details differ | A spelling variant, or a name changed after marriage | The documents belong to someone else | Supporting ID and a re-check |
| Court record match | A namesake with a similar name in the same district | Identifiers match and the case is relevant to the role | See the court section below |
Notice what's missing from the table: fixed rules such as "reject anything over three months". A number like that is easy to apply and hard to defend, because the same difference can be trivial for one role and decisive for another. Write the rule around what the role requires.
Two flags we'd always escalate to a senior HR owner: an employer or institution that turns out not to exist, and a document the issuer says it never issued. Both point to deliberate fabrication rather than a memory slip.
Confirm the case belongs to your candidate before you think about what it means. Then read what kind of case it is: civil or criminal, pending or decided, and whether your candidate is the accused, the complainant or a witness. Being named in a case isn't the same as being convicted, and a pending case doesn't mean someone is guilty.
Namesakes are a common cause of false alarms. Court records often leave out the father's name or address, and spellings vary, so a raw name search can pin a stranger's case on your candidate. That's why our court record check grades every hit against the candidate's name, father's name and address:
| SpringVerify grade | What it means | What happens next |
|---|---|---|
| Exact Match | The available identifiers point to the candidate | Read the case details: nature, status, court, dates |
| Partial or Possible Match | Some identifiers fit, some don't or are missing | Handled under the grading rules you set |
| Inconclusive | The match can't be confirmed or ruled out | The candidate is asked for a PCC; our team validates it and re-grades the case |
| Clear | No matching record found in the digitised courts searched | Close |
You set how strict the grading is: flag only exact name-and-address matches, or escalate every partial match for review. The standard court check searches India's digitised eCourts records from 2000 onwards and returns in 1 to 2 hours. For banking, financial services and other high-trust roles, there's a law-firm version where an attorney visits the police station for the candidate's declared area and reviews the last seven years, in about 2 working days. Every grade and grading decision is logged, so you can show exactly how a hiring call was made.
Once a match is confirmed, weigh three things: what the case is about, how it relates to the job (a cheating case matters more for a finance role) and where it stands. On disclosure and acquittals, the Supreme Court in Avtar Singh v. Union of India (21 July 2016) said the decision should rest on "objective criteria on due consideration of all relevant aspects", and that the yardstick depends on the nature of the post. A candidate can only be said to have hidden something the verification form specifically asked about. And an acquittal on a technical ground, or on the benefit of the doubt, doesn't stop an employer weighing the facts. That case concerned government jobs, so don't treat it as a ready-made rule for private hiring. What it does show is that blanket rules either way ("any case means rejection", "an acquittal always clears") are hard to defend. For a specific case, take legal advice.
A PCC tip that saves a week: the most common reason we see a PCC rejected is the wrong issuer. A certificate from the Passport Office isn't accepted for BGV purposes; it needs to come from the state police. A PCC is typically valid for 6 months from issue. Some states, such as Gujarat and West Bengal, issue offline certificates with no QR code or portal record. We can confirm those are consistent and authentic, but we'll tell you plainly that they can't be validated online. Our guide to police clearance certificates vs court records covers when you need each.
Find another source before you draw any conclusion. "Unable to verify" means the source didn't confirm, usually because a past employer's HR team never replied, the company closed or a university is slow. It says nothing about whether the candidate told the truth. Treat it as an open case with an owner and a date, not as a red flag and not as a pass.
Here's how we work to stop a check reaching that point in the first place:
If you still need other evidence, ask for specific documents: a relieving letter, payslips for the months in question or Form 16 from that employer. Ask for what proves the point and no more. Never ask a candidate for a password or an OTP, and don't ask them to show a whole bank account on a screen share. You don't need it, and it puts both of you at risk.
Name the exact fact that differs, say what evidence would settle it, and give a reasonable date to reply. Don't accuse anyone. Most candidates are honest, and the ones who made a typo will fix it in a day. A fair question also gives you something better than a guess if the explanation doesn't hold up.
A message you can adapt:
Hi [Name], your background verification shows a difference between the employment dates you shared for [Company] and the dates their HR team confirmed. Could you send your appointment and relieving letters, or payslips for [months], by [date]? If a document will take longer to get, just let me know. We'll review what you send before we close this check.
Set the reply date under your policy, and allow for the document. Correcting a typo takes minutes. Getting a record out of a university can take weeks. On SpringVerify, the candidate uploads the documents securely through their own portal, so copies don't end up in panel members' inboxes.
The Digital Personal Data Protection Act, 2023 governs how you collect and keep this information. Its commencement is phased: under G.S.R. 843(E) of 13 November 2025, the core duties, including notice, consent and the rights of the person whose data it is, apply from 13 May 2027. Build your process for them now: ask only for what the check needs, say why, and decide how long you'll keep it.
That's a policy decision, and it should be written down before the Friday it comes up. One workable approach: for lower-risk roles, let the candidate join on a conditional offer, with limited access to money, client data and systems until the check closes. For high-risk or regulated roles, hold the joining date until the flag is resolved.
If you do allow conditional joining, have your legal team draft the clause: that the appointment depends on verification, how long the open check can stay open, what access is restricted in the meantime and what happens if the result is adverse.
Plan joining dates around the slowest check you need. Our published turnarounds: basic checks in under 60 seconds, 80% of verifications done within 48 hours, a court check in 1 to 2 hours, digital address verification in 24 to 48 hours, most employment checks in 5 to 6 working days (depending on how quickly the past employer's HR responds) and official education verification in 15 to 90 days. Our guide to how long a background check takes shows how to sequence them.
If the person has already joined, don't reuse your pre-hire process. Acting on a finding about a current employee raises employment-law questions. For a specific case, take legal advice.
Write a short decision record for every flag you clear or act on, and keep it with the report. An enterprise client's auditor, or your own leadership, will ask why two similar flags got different answers. "We used our judgement" is a weak reply. A record with the evidence and the policy clause is a strong one.
| Field | What to write |
|---|---|
| Report and date | Which report you reviewed, and any later correction |
| Candidate's claim | The exact field as declared |
| Verified finding | What the source said, which source, and when |
| Still unresolved | What remains unknown, and why |
| Candidate's response | Their explanation and the documents received |
| Re-check | What was checked again, and the result |
| Role relevance | Which requirement of the role it affects, and the policy clause applied |
| Decision and owner | Proceed, ask for more, approve an exception or decline, with the approver's name |
| Follow-up | Anything still open, who owns it and the next review date |
SpringVerify's reports already supply the first four rows. Every verification is timestamped and source-cited, court grading decisions are logged, and the gap check keeps a contact log. You add the decision.
HR teams choose SpringVerify because our reports give them the evidence to make the decision, not just a colour, and because we do the chasing that turns a flag into an answer. Here's what that looks like, with proof.
No more strangers' court cases on your candidate's report. We grade every court hit against father's name and address, send unclear matches through a PCC check instead of guessing, and let you set how strict the grading is. Ritika Raj, Senior Manager I, HR Shared Services at LoadShare Networks: "SpringVerify gave us what we were missing - the ability to actually see court case risks clearly. It has meaningfully reduced our BGV delays and given our HR team the visibility to move faster with confidence."
The evidence is in the report, not in your inbox. Prathima Shetty, HR Manager at Pazcare: "The verification report is the most helpful for me. I get to see each and every detail starting from document copies, email conversations, summaries of verifications, etc."
You only step in when it matters. Asmita Paul, Senior HR Generalist at HackerEarth, said interim reports and quick turnaround "easily saved us 3-4 hours daily", and added: "We only step in to talk to the candidate about an issue with their documentation." This account comes from HackerEarth's 2023 case study.
Fewer dead-end "unable to verify" results. When an old employer's HR goes quiet, we escalate to the reporting manager over WhatsApp, and for companies that have closed we use EPFO and MCA records.
Status you can see without asking. Before switching, Loina Dhal, Executive, Human Resources at Signeasy, waited "15 days to 1 month for a status update" with a previous provider. With SpringVerify: "I see a status update being available almost immediately on the SpringVerify portal." This account comes from Signeasy's 2022 case study.
Candidate data you can defend. SpringVerify holds ISO/IEC 27001:2022 and SOC 2 Type II certifications, listed on our security page. Candidates give consent and upload documents online, and Aadhaar numbers are masked after processing.
It works with the tools you already use. Checks start from the HRIS, ATS or HRMS you already run: we integrate with 100+ platforms, including Darwinbox, Keka, Zoho People, Zimyo and Workday, and offer an API.
SpringVerify is a strong fit if you hire in India regularly, your team reviews flagged reports and needs the evidence behind each one, and you want court matches graded rather than raw name hits. It suits teams that answer to auditors or enterprise clients and need a record of how each call was made.
Not the right fit if:
Pick SpringVerify if you want every flag to arrive with the evidence to settle it, so the right people join on time and the wrong ones don't.
No. A red flag means one check found a discrepancy or a possible adverse record. Confirm the record belongs to the candidate, read the evidence, ask them to explain, then apply your policy for the role. The report's status and your hiring decision are two separate things.
A discrepancy means the source contradicts what the candidate declared. "Unable to verify" means the source couldn't or didn't confirm anything at all, often because a past employer didn't reply or has closed. Look for another source, such as EPFO records or a relieving letter, before treating it as a discrepancy.
An insufficiency means the check is missing something it needs to finish: a document, a contact or a complete address. It's a request, not a finding. On SpringVerify's gap check, an insufficiency is raised only after three attempts to reach the candidate by call and email.
A pending case isn't a conviction, so an automatic rejection is hard to justify. Confirm the record is the candidate's, then weigh what the case is about, how it relates to the role and where it stands. SpringVerify's court report shows whether a matter is pending or convicted, and civil or criminal, so you can see the difference before you decide.
Not on its own. Most gaps have ordinary reasons, such as study, caregiving, health or a course. A gap matters when it hides a job the candidate left off, or when it conflicts with dates they declared. SpringVerify's gap check records the candidate's own explanation and any supporting document.
For BGV, the Police Clearance Certificate needs to come from the state police. A certificate issued by the Passport Office is the most common reason we see a PCC rejected. A PCC is typically valid for 6 months from the date of issue.
Set it in your written policy, and allow for the document you're asking for. Fixing a typing error takes a day. Getting a record from a former employer or university can take weeks. Give a clear date and a named contact in HR.
Next step: see how a flagged report looks on SpringVerify. Book a demo and we'll show you a graded court match, an employment discrepancy and the evidence behind each.
.png)