DBS checks for agency workers: make the handoff clear

An agency says its worker is checked. A school or care provider has a shift to fill. The receiving manager sees a name and a start time but no clear record of which checks were done, what role they covered or whether the person at the door is the person in the agency file. That is the handoff problem. It is not solved by adding a generic “DBS complete” badge to a supplier list.

DBS eligibility still depends on the work the person will actually perform. The agency and the receiving organisation may each hold part of the information needed to assess that work. The agency knows the worker's identity, application history and existing certificate. The receiving organisation knows the setting, the duties and the people the worker will encounter. A sound placement process makes those facts meet before work begins. It names who will confirm the lawful check level, who will submit or status-check an application where appropriate, what written assurance is provided, and what the receiving site will verify on arrival.

The detailed legal requirements vary by sector. Keeping children safe in education 2026 requires schools in England to obtain written agency notification about checks they would otherwise perform. It also says schools should match the arriving person to the person checked. The Care Quality Commission's Regulation 19 guidance includes agency and bank staff within the people whose fitness a provider must address. These sources show why the receiving organisation cannot treat a supplier's general promise as the entire decision. This page offers a cross-sector workflow, then sends school and care readers to their sector guidance.

Agree the actual assignment before selecting a DBS level

An agency may place the same person in different settings. A worker could support patients in one assignment, handle reception duties in another and work at a school during the following term. The certificate for the first role is not automatically the correct evidence for the others. Before ordering a new check or accepting an existing one, describe the actual duties of this assignment, who the person will work with, any regulated activity and any special sector condition. Confirm the relevant workforce and whether barred-list information is lawfully available.

The receiving organisation should give the agency a usable role description, not only a shift code. The agency should challenge ambiguous phrases such as “general support” or “safe to work with vulnerable people”. A title does not decide DBS access. The DBS eligibility collection and the employer guide explain the role-based approach. If the parties disagree about eligibility, the placement should be escalated for a reasoned decision rather than submitted at the highest level by default.

The decision should be made early. If the agency learns at the last minute that the worker will undertake regulated activity with children, it cannot assume a certificate without a children's barred-list check covers the assignment. A clear change-control step is better than hoping the receiving site will notice the mismatch when the worker arrives.

Set out who does each part of the check

Different agency arrangements use different application routes. Some agencies may be registered with the DBS, some use an umbrella body and some rely on a worker's existing certificate with a lawful Update Service status check. The receiving organisation may carry out certain checks itself. The contract and placement request should identify who will do what. A generic statement that “the agency handles compliance” is too broad to show what happened in a particular case.

At minimum, assign responsibility for the role description, eligibility assessment, application route, identity verification, certificate review, any Update Service status check, written confirmation to the receiving organisation, arrival identity check and review after a role change. Keep the checklist tied to the individual placement. The agency's process should identify which worker it cleared, not merely how it usually screens candidates.

This allocation does not erase a regulated provider's own responsibilities. In England, CQC Regulation 19 covers people engaged in a service, including volunteers, contractors, agency and bank staff. Schools have their own statutory safeguarding framework. Other sectors may have different rules. The receiving organisation must understand its sector obligations even when the agency has performed the application work.

What written confirmation should tell the receiving site

A receiving manager needs enough information to verify that the worker and role match the completed checks, without receiving a routine copy of every sensitive document. For a placement requiring DBS assurance, the written handoff should identify the worker, the assignment, the level and workforce of the check, whether barred-list information was included where legally required, the check or status-check date, and who completed the process. It should note any outstanding checks and any restrictions on work. The precise fields should follow the receiving sector's requirements and an agreed retention policy.

The 2026 DfE statutory guidance requires schools in England to obtain written notification that checks they would otherwise do have been completed. It also sets a specific exception to the general principle of avoiding routine certificate copies: where an agency obtained an Enhanced DBS certificate before the worker starts and it disclosed information, the school must obtain a copy from the agency. The school must then handle that information under the applicable safeguarding and data-protection rules. This is a school-sector rule, not an automatic checklist for every industry. In a care service, the CQC guidance calls for robust recruitment procedures and relevant checks across agency and bank staff. A receiving provider should decide with its safeguarding lead what confirmation is needed for each kind of role.

Avoid vague wording such as “fully vetted” or “DBS approved”. DBS does not approve a worker's suitability for a role. It issues information to support the employer's decision. A high-level certificate obtained for another role may not match this one, and a status result is not a fresh certificate containing all original details. Written assurance should say what was checked and what decision remains with the receiving organisation.

Verify the worker who arrives

A perfect agency file is of limited value if the receiving site cannot establish that the person who arrives is the person described in the handoff. Give the site a secure way to compare the worker's identity with the placement notice. Arrange that comparison as part of a routine welcome process, not as an improvised challenge in front of service users. If a replacement worker is sent, the earlier worker's assurance cannot simply be transferred to the substitute.

Identity checks used for a DBS application follow DBS rules. The on-site identity comparison serves an additional operational purpose: matching this person to this placement. Where names have changed or differ across documents, clarify the reason and record it securely. A site manager should know whom to contact if details do not match, the confirmation is missing or a different person appears. The response may be to pause the assignment until the agency can resolve the gap.

The DBS identity-checking guidance should be used for the application process. It was updated in July 2026, so older copies of a supplier policy may need review. Neither an agency badge nor a worker passport by itself establishes that a check was legally eligible or correctly performed.

Reusing a certificate and the Update Service

Agency workers often move among clients, so certificate reuse is a recurring question. A certificate is not a universal licence to work anywhere. The receiving organisation needs to compare its assignment with the certificate's level, workforce and any barred-list element. It should consider the date and its own sector policy. An existing certificate for one workforce does not automatically cover another.

The DBS Update Service allows a status check for a subscribed Standard or Enhanced certificate when the employer has consent and the conditions are met. Basic checks are not on the service. The official employer guide explains what must match. The agency and client should agree who views the original certificate, who conducts any status check, how the result is communicated and what happens if a new certificate is needed. Complys does not perform Update Service checks.

If the worker is assigned through a second agency, do not assume a prior agency's checking process binds everyone downstream. Establish what evidence is available and who obtained it. A chain of suppliers can make responsibility less clear, not more. The DBS employer guidance explains certificate reuse. This page concentrates on the agency-to-client handoff.

A school supply example

Suppose an agency offers a supply worker for an English school. The school provides the actual assignment and asks for written confirmation that the appropriate recruitment checks have been completed. The agency confirms the worker's identity, the relevant DBS check and any required barred-list information. The school verifies the identity of the person arriving and records the confirmation in the way required by its safeguarding process. If the role differs from the one the agency assessed, the parties revisit it before the worker is placed with pupils.

The DfE's 2026 Keeping children safe in education collection is the statutory guidance owner for schools in England. Its paragraphs 364 to 367 cover agency notification, a disclosed Enhanced certificate, barred-list checks and arrival identity matching. The separate DfE supply-agency deal guidance describes the checks required of agencies participating in that deal. This cross-sector page does not apply the deal's contract terms to every agency and does not reproduce the school's full single central record requirements.

The example also shows a wider principle. An agency can complete checks while a receiving organisation still has duties at placement. The handoff should make both visible. A school that has received an agency's certificate number but has not matched the person or role has an incomplete operational picture.

A care-provider example

Imagine a care home covering a night shift with an agency worker. The provider asks the agency to confirm the worker's identity, relevant recruitment checks and evidence of suitability for the actual tasks. It checks any professional registration or training relevant to the shift through the appropriate route. Before work starts, the person arriving is matched to the agency notice and oriented to the service's safeguarding and incident procedures. The provider records who accepted the assignment and any limitation on duties.

CQC's Regulation 19 applies to the fitness of people employed in regulated care, including agency and bank staff in its guidance. That does not mean every care assignment has identical DBS eligibility. A worker providing personal care may be assessed differently from someone with a non-care task. The DBS adult eligibility guidance explains the role test. This page owns the evidence handoff and substitution problem.

If the agency sends a replacement halfway through the shift, repeat the identity and assurance steps for that person. A roster entry saying “agency nurse” does not prove the individual has the right check or registration. Where a document is delayed, use the service's sector-specific rules and risk decision process. Do not infer from this general page that a worker may start before a required check is complete.

Changes, renewals and failed handoffs

An agency-worker file is not a one-time transaction. The assignment may change from short-term reception cover to direct support. A school may ask the worker to take a different class or accompany an overnight trip. A care provider may move someone to duties involving personal care. Any such change should trigger a fresh role assessment and, if necessary, a new check-level decision. The contract should tell the receiving organisation how to notify the agency of changes and who has authority to pause work.

A DBS certificate does not have a universal statutory expiry date. The agency and client may each have a review policy or sector requirement. Their records should say which rule they are using rather than label a certificate legally expired on an invented date. An Update Service status check is a different event from a new DBS application and should be recorded as such.

If confirmation is missing, unclear or inconsistent, the receiving manager should know the escalation route. Ask for the missing fact. If the agency cannot show that a legally necessary check was completed, do not use a generic “supplier approved” flag to bypass the issue. If the worker's identity cannot be matched, stop the handoff until resolved. Record the decision, who made it and whether the assignment was cancelled, delayed or restricted under sector advice.

For a last-minute booking, agree a short minimum handoff that can be completed before the shift. It should still identify the individual, the actual duties, the check level and workforce, any barred-list element, the agency's written confirmation and the person who accepted it. If the only available message is “cleared”, ask the agency to specify what was done. A quick telephone assurance may help locate the right contact, but the receiving site should obtain the written evidence its sector requires. Pressure from an empty rota is a reason to make the escalation route fast, not a reason to leave it undefined.

An adverse certificate or safeguarding concern is not merely a supplier performance issue. It may require the agency and receiving organisation to cooperate under their respective safeguarding and referral duties. DBS barring referral guidance discusses personnel suppliers. A specialist should examine the facts, who holds information and which duty applies. This page does not attempt to decide a referral from a short scenario.

A compact placement record

A useful placement record should answer six questions without turning the system into an unrestricted archive of sensitive certificates.

The contents of a DBS certificate are sensitive. The DBS handling guidance addresses limited use, access and retention. A provider's privacy owner should decide how long its written confirmation and other recruitment records are kept under sector rules and data-protection law. The agency may hold different records for its own purpose. The two organisations should not exchange more sensitive material than the placement decision needs.

Product fit and next step

Complys can help organise worker-document records, dates, placement records and reminders. It does not determine the legal DBS check level or replace the agency's written assurance and the receiving organisation's safeguarding decision. The live Complys recruitment overview describes its worker and placement record features. Use those features under a documented privacy policy rather than assuming every DBS certificate should be uploaded.

For an active placement, send the agency a role description and request a written, individual assurance for that role. Confirm the receiving site's own checks and match the person who arrives. Use the DBS employer guidance for the general process, the relevant sector regulator for additional requirements and the DBS certificate handling guidance for information handling. A clean handoff is one the agency, receiving manager and later reviewer can all reconstruct from the same record.