How Staffing Agencies Verify Candidate Claims Before Submission

A staffing agency can verify candidate claims before submission in three layers: a ten-minute read of the CV against itself, a check on the two or three claims the role depends on, and a one-page evidence note the client can read. Formal background verification stays with the client or its vendor, after the offer.

How is pre-submission verification different from background verification?

Pre-submission verification asks whether a candidate's story holds together and whether the claims that matter can be supported. Background verification (BGV) confirms facts with employers, institutions, courts and ID sources, and it needs written consent and days of waiting. An agency racing to submit cannot wait for BGV, and a client does not expect it to. The client expects the agency not to send a CV that falls apart on the first read.

That gap is where the answers a buyer gets today fall short. Search results and AI assistants describe the BGV workflow: consent, then identity, employment, education, address and court checks, then a report marked verified, discrepant or unable to verify. That is the right process for a verifier. It does not say what an agency should do in the hours between receiving a CV and sending it. Our post on what to check before background verification in India covers the step before the referral. This one covers the step before the client.

What can a ten-minute consistency read catch?

It catches contradictions the CV contains on its own: overlapping jobs, a degree dated after the job that needed it, a title that does not fit the employer, and a skill claimed for longer than the job allowed. None of these needs an outside record, so none of them slows a submission. Each one is a question for the candidate, never a reason to reject.

Dates: overlaps, gaps and impossible sequences

Write every job and degree as a start month and an end month, one line each. Flag overlaps longer than a notice period, jobs that begin before the qualification the CV says they needed, and unexplained gaps. Overlap is also what moonlighting looks like on paper: EY's analysis of more than one million pre-employment screenings across 90-plus Indian organisations, as reported by SHRM India in July 2026, found 45% of flagged IT/ITeS candidates were moonlighting. Our piece on the overemployment blind spot in hiring explains why this matters most for remote roles.

Employers and titles: do they fit each other?

Check that each employer exists under the name given, that the same company is not written two different ways, and that the title is plausible for the employer's size. Ask for the legal entity name, because a verifier or client will search for it. A senior title at a very small firm may be true. It is still worth one question before the CV goes out.

Skills against tenure

A CV that lists a tool or domain for six years under a job that began two years ago has made a claim its own dates cannot support. This is the check where a consultant's domain knowledge beats any checklist, so route it to whoever knows the role.

Which claims deserve a deeper check before submission?

Check the claims the role depends on and leave the rest for BGV. Pick two or three per requisition, write them down before sourcing starts, and apply them to every candidate on it. Written scope keeps the depth the same across consultants, which matters the day a client asks why one candidate was checked harder than another.

Experience-led technical roles: confirm current employer and tenure from something the candidate does not control, such as an offer letter they agree to share, and ask one specific question about the project the role hinges on.

Roles with a licence or qualification requirement: the certificate is the claim. Ask for it before submission and compare its issuer and dates with the CV.

Senior and client-facing roles: add a short reference call by the consultant, aimed at the single claim that carries the most weight.

High-volume entry-level roles: identity and internal consistency only. A deeper check on every CV costs more than it returns before the client has shown interest.

These tiers are a starting rule, not a standard. Change them to match what your clients' contracts require.

What should the client see with each submission?

A one-page evidence note beside the CV. It lists the role criteria, how the candidate matches each, what the agency checked and how, and what it did not check. Clients judge the agency when a placement turns out to be inflated, so the note shows the work. It also protects the agency by saying plainly where the checking stopped.

Criteria and match: one line per criterion, with the candidate's evidence.
Checks done: what was compared, against which source, and the result.
Open questions: anything the CV raised, the candidate's answer, and whether it settled the point.
Left for BGV: the checks the agency did not run, named.

Choose the verbs carefully. Write "consistent with" when a CV was checked against itself or a public profile, and "confirmed by" only when a document or a source the agency contacted said so. Never write "verified" for the first.

Where do agencies usually get this wrong?

The three common failures are checking once and stopping, clearing a red flag without writing down why, and applying different depth to different candidates. The second is the costly one. The same SHRM India piece reports that ACFE's 2022 Report to the Nations found 21% of organisations hit by employment fraud had gone ahead with onboarding despite red flags raised in screening. The tool had worked. The process around it had not.

A flag should always produce a note: what was asked, what the candidate said, and what the consultant decided. If the note is missing, the flag was ignored, whatever the intention. Collecting documents also needs the candidate's consent, which is covered in our guide to AI screening under the DPDP Act.

How often do claims fail, and how long do formal checks take?

Roughly four in every hundred white-collar files carried a discrepancy in one verifier's data, and formal checks take weeks. AuthBridge's Workforce Fraud Files for H1 FY26 (February 2026) recorded a 4.33% discrepancy rate for white-collar hires and 5.61% for on-demand workers, with employment verification the most affected check for white-collar roles.

Read that with care. AuthBridge is a verification vendor, and the release does not give a sample size or define a discrepancy, so a minor date error and a fabricated employer may sit in the same figure. It describes files that reached background verification, which is not the same population as an agency's incoming CVs. Treat it as the order of magnitude: a small share of files, but enough that a client who finds one will remember which agency sent it.

The speed side is why BGV cannot be the pre-submission step. ThePeoplesBoard's guide to BGV timelines puts typical turnaround at 7 to 15 business days, with employment checks taking 3 to 7 days per employer (as of July 2026). Experience is also where the claims are: EY's data, as SHRM reports it, found that in IT/ITeS 79% of fraud incidents involved previously employed candidates rather than freshers.

What does AgentR do here, and where does it stop?

AgentR reads every application in full against criteria the recruiter sets, checks what the candidate claims for consistency against public and organisational signals, and gives the team a ranked shortlist with the evidence attached, in a form that can go to a client. Inconsistencies in dates, titles and employers are surfaced for a person to review, which is the work of the consistency read above. The pre-BGV filter and resume verification pages describe the approach.

The limits are real. AgentR does not contact employers or institutions, does not produce BGV-equivalent output, and does not replace a verifier, so a client who requires BGV still needs one. Nobody is auto-rejected and every decision stays with a person. It is not an applicant tracking system: there is no pipeline view and no public API as of October 2026. AgentR is in private beta, so we have no published data on how much a pre-submission check changes client rejections. If you screen a few CVs a week for one client, the worksheet above may be all you need. For the ChatGPT route, see whether an agency can just use ChatGPT to screen candidates.

Questions people ask

Do staffing agencies run full BGV before submitting a candidate?

Often the client or its vendor runs it after the offer, though contracts differ, so read yours. Full BGV takes 7 to 15 business days by one guide (ThePeoplesBoard, as of July 2026), which is longer than most requisitions allow before a submission.

Get specific written consent for each check that involves a document or a third party, before you run it. Under India's DPDP framework consent has to be free, specific and informed. This is general information, not legal advice.

What if the CV contradicts itself?

Ask the candidate, write down the answer, and decide with the note in hand. An overlap has ordinary explanations, such as a consultancy, a delayed relieving letter or a typo. Submit with the note attached, or hold the CV if the answer does not settle it.

Can an agency tell a client a candidate is verified?

Only for what it confirmed with a source. Say what was checked and against what, and name what was left for the client's BGV. A precise "consistent with" protects the agency better than a loose "verified".

Run a closed role through AgentR and see what a pre-submission consistency check finds.

See how resume verification works on a real role.