recruiters
Identify the recruitment employer without collecting candidate databases.
Industry verification planning
Focus on recruiters, payroll processors and HR operations providers handling another organisation's workforce processes.
Start with the actual job
The legal employer, deployment client and assignment history should remain separate in high-volume intake.
Identify the recruitment employer without collecting candidate databases.
Confirm payroll-processing duties without sharing salary or bank datasets.
Separate HR-provider employment from assignment to a client organisation.
Use repeatable consent and document requests while preserving each candidate's individual source responses and opportunity to clarify.
These are planning examples, not client case studies, mandatory check lists or a guarantee of hiring suitability.
Purpose before package
These are starting points for agreeing a scope, not a blanket package for every person in this sector. Confirm duties, consent, source access and the employer's requirements first.
Match the candidate's identity to the records being checked. Explain name changes or spelling differences before approaching sources.
Capture HR-services employer, function, client-assignment context and dates; access to a client's HR system is not employment evidence.
An authorised manager can clarify recruitment or HR operations responsibility without disclosing candidate or employee records.
Court, police, database and other checks are not automatic additions. Agree their purpose, permitted sources and limitations separately. A name-only match is not a confirmed adverse finding. Review available services.
Prepare records, not excess data
Capture HR-services employer, function, client-assignment context and dates; access to a client's HR system is not employment evidence.
An authorised manager can clarify recruitment or HR operations responsibility without disclosing candidate or employee records.
Collect candidate documents only through the agreed secure intake. The public enquiry below is for business scope, not identity documents, employee records or account credentials.
Read the document preparation guideResolve ambiguity before a finding
No. Seek employer confirmation and permitted role-level evidence. A background check should not collect other employees' financial or personal records merely to establish the candidate's duties.
Request clarification, identify any agreed alternative source and distinguish an unavailable response from a confirmed discrepancy. The report should state which claim was checked, what the source returned and what remains unresolved. The employer makes its own policy decision.
Share candidate numbers, hiring roles, locations and the employers or qualifications per candidate. The quote and expected window depend on that scope, record completeness, source response and any field method. This guide does not publish a fixed price or guaranteed deadline.
Agree a practical scope
Share the roles and hiring locations. We will confirm the proposed checks, evidence requirements, exclusions and next steps.
No candidate documents are needed in this enquiry. Include only business requirements, not another person's sensitive records.