Employee verification: what to check before you hire

Some hires carry more risk than others. A guard at your gate, a housekeeping team in your offices, a worker at your warehouse — these people hold access to your premises, your people and your assets, and their history matters in a way it does not for most roles. Verification is the step that turns a resume into a hiring decision you can defend. It is also the first layer of a wider posture: once a hire starts, employee security awareness is what keeps them from becoming the weak link.

This guide covers the checks that matter for blue-collar, security and support staff, and how to run them without it becoming a full-time job.

Why verification matters

• A criminal record is a direct risk when someone is trusted with premises, keys, cash or people — for security and housekeeping staff this risk is structural, not hypothetical.
• Employment history that has not been verified means you are hiring on the candidate’s own account of their experience.
• A bad hire at the perimeter affects your whole site. Falsified documents and unverified references surface in exactly the roles where the stakes are highest.
• For regulated or contract-heavy operations, verification also protects you in an audit: you can show who you hired and what you checked.

The checks that matter

• Criminal record / police verification — the non-negotiable check for security, housekeeping and any role with unsupervised access, and a statutory condition of employment for licensed security guards.
• Employment history — previous employers confirmed, including reasons for leaving, so the claimed experience is real.
• Address verification — a physical check that the person is who and where they say they are.
• Identity documents — verification of the original documents against the individual presenting them.
• Educational qualification — where the role requires a specific qualification, confirm it rather than accepting it.
• Reference checks — conversations with previous employers about conduct and reliability, which surface what a certificate cannot.
• Where relevant: court records, medical checks, and financial/credit checks for roles that carry handling money or sensitive assets.

Match the checks to the role

Running every check on every candidate is slow, expensive and hard to justify to a candidate. Running too few is how the wrong person reaches a stock room. The practical answer is to set a minimum standard by the level of access the role carries, decide it once, and apply it consistently.

Role type	Minimum checks
Unguarded premises, no access to stock	Identity, prior employment, one reference
Routine access to premises (general housekeeping, maintenance)	Above, plus address verification and police verification
Unsupervised access to people or assets (security guards, warehouse staff handling high-value goods)	Above, plus full employment history with reasons for leaving, and reference conversations rather than certificates
Handling cash, keys or sensitive records	Above, plus the role-specific checks those duties justify

The line is drawn at unsupervised access, not seniority. A site’s biggest exposure is rarely the newest manager; it is whoever can reach valuable and portable goods without anyone checking what they are doing.

Where verification usually fails

Most verification failures are process failures rather than difficult candidates:

• Checking after the start date. Once someone is working, the incentive to complete an awkward check disappears. Verification belongs before day one.
• Accepting documents at face value. A photocopy is a claim, not a check. Original documents, seen against the person presenting them, plus a reference conversation that is actually held.
• Reference calls that never happen. Requesting references and receiving them are different things; a list of names with no notes is not evidence.
• Verifying the senior hire and skipping the perimeter. The inverse of the risk. Security, housekeeping and warehouse roles carry the access that matters.
• No record. If the file cannot show what was checked and when, the organisation cannot demonstrate it did anything at all when a question is later asked.
• Treating verification as a one-off. Someone’s circumstances change. Roles that involve money, children, or the highest-value stock justify re-verification, and any sensitive redeployment is a natural trigger.

One more obligation that is easy to overlook: verification collects personal data. Collect only what the role justifies, tell the candidate what is being checked, keep the records in a controlled place rather than a shared mailbox, and delete what you no longer need.

Making verification a repeatable process

For a small team it is tempting to verify the senior hires and skip the rest. That is exactly the risk inversion — the staff with unsupervised access need the checks most. Make verification part of onboarding:

1. Define the checks for each role type once, and apply them consistently.
2. Run the checks before the candidate starts, not after.
3. Keep the evidence — a register of who was checked, when, and with what result — so the process survives an inspection or a dispute.
4. Re-verify on sensitive redeployments, not just at first hire.

When a staffing or security provider supplies the people, the verification and its records should sit with them as part of the engagement. That is one of the things an accountable security agency and a staffing provider carry — see also the due-diligence guide.

Ask a prospective provider two questions before you accept that transfer: what exactly do you check for this role type, and can you show me the record for a current deployment. A provider who cannot answer the second is describing a policy, not a practice.

Frequently asked questions

Do we need police verification for every hire?

Not for every hire, but for any role with unsupervised access to premises, people or valuable goods — which in practice means security, housekeeping, warehouse and maintenance staff. For roles with no such access, identity, employment history and a reference are a proportionate baseline.

What if a candidate has a gap in their employment history?

Ask, and record the answer. A gap is not disqualifying; an unexplained gap that changes when asked twice is worth investigating. The purpose of the check is to make the history verifiable, not to eliminate anyone with an imperfect one.

Who should run the checks — us or the staffing agency?

Either, as long as the responsibility is explicit and the evidence is available to you. Where a provider supplies the workforce, verification normally sits with them. Test that by asking to see the records for people currently deployed on your site.

Can verification be done after the candidate starts, if we are in a hurry?

Only with a defined restriction in the meantime — no unsupervised access, no keys, no handling of valuables — and a date by which the checks complete. Once the person is embedded and the site depends on them, the check that was inconvenient usually stops being chased.

How long should verification records be kept?

Long enough to answer an inspection, a client audit or a dispute about the hire, and no longer than necessary. Agree the retention period when you design the process, and make sure whoever holds the records applies the same period.

Does this apply to contract and temporary staff?

The proportion of checks may differ by role, but the principle does not. Contract, agency and temporary staff frequently have the same access as permanent employees and are usually the group where verification is weakest — which makes them the group worth checking most consistently.

The bottom line

Verification is not bureaucracy; it is the cheapest protection you can buy against the risk that walks in through the front door. Decide which checks each role needs, run them before the start date, keep the records, and make sure whoever supplies your workforce can prove the same.