What is automated background verification?

It's running BGV as a triggered step in your hiring workflow rather than a manual, off-platform chase. On 100Networks, background verification can be launched by Pilot or fired automatically by a workflow at the right stage, so it starts the moment a candidate reaches it.

When in the process should BGV run?

Usually once a candidate is a serious finalist or has a verbal offer — late enough that you're not verifying everyone, early enough that it doesn't delay the start date. Automating it as a workflow step means it fires at exactly that stage, every time, without someone remembering to kick it off.

Does the AI decide whether someone passes?

No. Automation handles initiating the check and tracking its status; the recruiter or hiring manager reviews the result and makes the call. The point is to remove the coordination overhead, not the human judgment.

How does BGV fit with the rest of hiring?

It's an action in the same visual workflow engine that handles screening, interviews, and offers — so 'run BGV' can sit right next to 'extend offer' in a pipeline, with branching logic based on the stage or outcome.

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

Background verification rarely fails because a check comes back bad. It fails because nobody started it, or it's stuck waiting on a form. The offer is out, the start date is set, and then someone realizes BGV hasn't been kicked off — so the whole timeline slips. The verification itself isn't the bottleneck; the manual coordination around it is. Automating that coordination is the fix.

Here's how BGV works when it's 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 don't fill it, follow up with the vendor, check back for the result, update the ATS. Each hop is a place to lose a day. And because it's easy to forget, it often starts after the offer — exactly when a delay is most expensive.

The problem isn't the check. It's that a multi-step process is being run from memory.

BGV as an automated workflow step

On 100Networks, background verification is a first-class action in the visual workflow engine. That means you can wire it into the pipeline so it fires at the right moment automatically:

Trigger it by stage — e.g. when a candidate is moved to "Offer Extended," run BGV fires without anyone remembering.
Branch on the outcome — route cleared candidates straight to offer management, and flag exceptions for a human to review.
Let Pilot initiate it — Pilot can start BGV as one of its tools, staged under the usual proposal-and-confirm approval.

The status is tracked in one place, so there's no "where are we on the background check?" thread.

Manual BGV vs. automated BGV

	Manual BGV	Automated BGV
How it starts	Someone remembers	Triggered by stage/workflow
Follow-ups	Manual chasing	Tracked automatically
Timing	Often late (post-offer)	Fires at the defined stage, every time
ATS/status update	Re-keyed by hand	Updated in the pipeline
The pass/fail call	Human	Still human

Automate the process, not the judgment

The important line: automation here removes the logistics, not the decision. Initiating the check, chasing the form, tracking the status — all of that is coordination a machine should own. Whether a result clears the bar, and how to handle an exception, stays with a person. That's the same control model behind every consequential action on the platform.

The bottom line

Background verification should start itself the moment a candidate reaches the right stage, track its own status, and hand a clean result to a human — not sit forgotten until it threatens the start date. Making BGV a workflow step turns a timeline risk into a non-event. See how it connects to offers and the rest of the pipeline in the product overview.