Background Verification · Recruiting Automation · Compliance · Hiring Process

Automated Background Verification: Run BGV Without the Back-and-Forth

Background verification stalls offers because it is run as a manual chase: forms, follow-ups, waiting. How to run BGV as a step in the hiring workflow, with the candidate's consent first and a person still owning the decision.

Aryan Vasishta· Co-founder, 100Networks··5 min read

Automated background verification means the check starts itself when a candidate reaches the right stage, asks for their consent first, and tracks its own status until a person reviews the result. It removes the chasing, not the judgement. Background verification rarely delays a hire because a check comes back bad. It delays a hire because nobody started it, or because it is stuck waiting on a form. The offer is out, the start date is set, and then someone realises BGV has not been kicked off.

Here is how to run BGV as a step in the workflow instead of a task on someone's mental to-do list.

Why manual BGV stalls hiring

Run background verification by hand and it becomes a chase: remember to start it, send the candidate a form, follow up when they do not fill it in, follow up with whoever is verifying, check back for the result, update your records. Each hop is a place to lose a day. And because it is easy to forget, it often starts after the offer, which is exactly when a delay costs most.

The problem is not the check. It is that a multi-step process is being run from memory.

Before any automation, get the order right. A background check is the processing of someone's personal data, and in India, as in most markets, it should start with the candidate's informed, written consent.

  • Tell them what will be checked and why. Identity, education, previous employment and address are common; criminal-record and reference checks are usually reserved for roles that need them. Scope the check to the role.
  • Say who will see it. If a third party is verifying documents, say so.
  • Collect only what you need. A copy of every document the candidate owns is not a background check; it is a liability.
  • Keep it secure, and delete it when you are done. Decide how long you keep BGV documents before you collect any.
  • Leave the current employer alone unless the candidate explicitly agrees. Many candidates in India are serving a 30 to 90 day notice period when the check runs.

India's data-protection law is built around notice and consent. If you are unsure what applies to a particular check, take legal advice; the practical habits above are good practice whichever rules apply.

BGV as an automated workflow step

Once consent sits at the front, the rest is coordination, and coordination is what a workflow should own:

  • Trigger it by stage. When a candidate moves to the stage you have chosen, such as a verbal offer, the check starts without anyone remembering.
  • Consent, then documents. The candidate gets a consent request first, then a clear list of what to provide, with reminders if something is missing.
  • Wait, then branch. The next step waits for the check to finish. Clear results move on to the offer; anything unusual goes to a person.
  • One status, in one place. No "where are we on the background check?" thread.

Manual BGV vs. automated BGV

Manual BGV Automated BGV
How it starts Someone remembers Triggered at a chosen stage
Consent Often a form sent late Asked for before anything is checked
Follow-ups Manual chasing Reminders and status tracked
Timing Often late, after the offer Starts at the same stage every time
Records Re-keyed by hand Updated in the pipeline
The pass-or-fail call A person Still a person

Automate the process, not the judgement

Automation here removes the logistics, not the decision. Starting the check, collecting consent, chasing documents and tracking status are coordination. Whether a result clears the bar, and how to handle a discrepancy, stays with a person. A good process also gives the candidate a chance to explain a mismatch before any decision is made: a wrong date on a relieving letter is far more common than a fabricated degree.

How it works in the 100Networks Workspace

The 100Networks Workspace is an AI hiring team for the roles a company fills itself, and background checks are one of the steps its automations can run. When a candidate reaches a stage you choose, the automation starts a check: the candidate is emailed a consent request before anything is checked, and a later step can wait until the check finishes before moving the candidate on. Pilot, the Workspace's plain-words assistant, can also propose starting a check, and it waits for your confirmation.

An automation only goes live after your team has previewed what it would have done on recent candidates and switched it on for the roles you pick. Nothing reaches a candidate until the team approves it. The automation steps that come after a check are covered in building an automated hiring pipeline.

Access to the Workspace is by request at workspace.100networks.com/access; pricing is set with each team, with no per-hire fee. For the hardest roles, the ones where the right person is not applying anywhere, send the role to the 100Networks marketplace instead.

The bottom line

Background verification should start itself the moment a candidate reaches the right stage, ask for consent before it checks anything, track its own status and hand a clean result to a person. Making BGV a workflow step turns a start-date risk into a non-event, without taking the decision away from the people who own it.

Frequently asked questions

What is automated background verification?
Automated background verification means running BGV as a step in the hiring workflow rather than as a manual chase. The check starts when a candidate reaches a stage the team has chosen, the candidate is asked for consent before anything is checked, and the status is tracked in one place. A person still reviews the result and makes the decision.
When in the hiring process should background verification run?
Usually once a candidate is a serious finalist or has a verbal offer: late enough that you are not verifying everyone, early enough that it does not push back the start date. Making it a workflow step means it starts at exactly that stage every time, without someone having to remember to kick it off.
Do you need the candidate's consent for a background check in India?
Yes. Treat informed, written consent as the starting point in India, as in most markets. Tell the candidate what will be checked, by whom and why, collect only what the role genuinely needs, keep the documents secure and delete them when they are no longer needed. India's data-protection law is built around notice and consent, and a background check that starts without consent damages trust with a candidate you are about to hire.
Should you contact a candidate's current employer during BGV?
Not without the candidate's explicit permission. In India many candidates are serving a 30 to 90 day notice period when the check runs, and an unannounced call to their current employer can cost them their job or their goodwill. Verify past employers first and leave the current one until the candidate agrees, or until after they have joined.
Does automation decide whether a candidate passes a background check?
It should not. Automation is for the logistics: starting the check, collecting consent and documents, chasing what is missing and tracking status. Whether a result clears the bar, and how to handle a discrepancy, should stay with a person, who should also give the candidate a chance to explain before any decision is made.
Can the 100Networks Workspace run background checks?
Yes. In the 100Networks Workspace, an automation can start a background check when a candidate reaches a stage the team chooses. The candidate is emailed a consent request before anything is checked, and a later step can wait for the check to finish before moving on. Pilot can also propose starting one, which waits for the team's confirmation. The pass-or-fail call stays with the team.