A clear compliance workflow connects document collection with the reviews needed for a placement. Direct uploads and automated reminders reduce manual follow-up, while linked agency and client checklists keep requirements visible to recruiters and reviewers. This guide sets out how to design that workflow so it holds up when the agency is busy, when a client changes its requirements and when a candidate's documents start to expire.

Why compliance workflows break down

Most agencies already have a compliance process. The difficulty is that it often lives in several places at once: a spreadsheet maintained by one person, client requirements saved in old email threads and follow-up held in individual consultants' inboxes. It works while volume is low and the same people are in the office. It starts to fail when the agency grows, takes on a new client or loses a key member of staff.

The symptoms are usually familiar:

An agency nurse is ready for a shift except for one client-specific document nobody asked for until the day before.
Three consultants request the same certificate from the same locum doctor in one week.
A file is marked complete because the documents have arrived, although nobody has reviewed them.
A care worker's training expires partway through a block booking and is only noticed when the client raises it.

Each of these is a workflow problem rather than an individual failing. The sections below address them in turn.

Set the requirements once

Define the agency's baseline and the additional documents each client requires. Keep them as structured checklists, rather than relying on individual consultants to remember the latest request.

The agency baseline

The baseline is what your agency needs from every candidate in a given role type, whatever the client. For an agency supplying nurses, allied health professionals and care workers, that usually differs by role group: the evidence you hold for a locum doctor is not the same as for a healthcare assistant. Define the baseline per role group so recruiters are not left to interpret a single long list.

Client-specific requirements

Hospitals and health services often add their own requirements on top of the baseline, such as particular training, induction forms or a specific format of reference. Record these against the client as a checklist rather than in a note on the account. When a candidate is put forward to that client, the additional items should appear on the candidate's record without anyone having to remember them. In RecSphere, adding a candidate to a shortlist adds that client's documents to their record, so the request starts from the checklist rather than from memory.

Keep the lists maintained

A checklist is only useful if it is current. Give each client checklist an owner, usually the account manager working with compliance, and agree how a change is made and communicated. When a client updates its requirements, decide whether the change applies to new placements only or also to workers already on shift, and record that decision so the team applies it consistently.

Separate collection from approval

Track requested, submitted and reviewed items distinctly. Receiving a document does not establish that the required check is complete. The appropriate reviewer should assess it and record the outcome.

A useful set of statuses separates each stage where a different person needs to act:

Requested: the candidate has been asked and knows what is needed.
Submitted: a file has arrived and is waiting for review.
Approved: a reviewer has assessed the evidence and recorded the outcome.
Returned: the evidence was not acceptable, with a reason the candidate can act on.
Expiring or expired: previously approved evidence that now needs renewing.

When a reviewer approves an item, record who reviewed it, when, and any expiry or renewal date. Without the date, the record shows that a document was approved but not whether it still covers the shifts being booked.

Keep the reviewer role distinct from the consultant filling the shift where you can. A consultant under pressure to cover a night shift is not best placed to judge whether a blurred certificate is acceptable. Where the team is small and roles overlap, agree in writing which items a consultant may approve and which always go to a named compliance lead.

Reduce repeated chasing

Use portal uploads, one-time links and scheduled reminders to handle the routine collection work. Give candidates a clear view of what is still needed and avoid requesting the same existing evidence unnecessarily.

Good collection makes it easy for the candidate to respond once. A single request that lists every outstanding item, explains briefly why each is needed and gives one place to upload them will usually get a better response than a series of separate emails. A candidate portal suits people who are already registered and working with you, while a one-time upload link suits someone at an earlier stage who does not yet have an account.

References are often the slowest item because they depend on someone outside the agency. Send online reference forms to referees as soon as the candidate has provided their details, rather than when the rest of the file is complete, and decide in advance who follows up when a referee does not respond.

Before requesting anything, check what is already held. Asking an experienced agency nurse for evidence she supplied last month, and which remains valid, tells her the agency does not know what it has.

Show the next action

Let automated reminders handle routine outstanding requests and upcoming renewals. Identify the evidence checks or unresolved exceptions that still need an action and give those a clear owner.

Routine work and exceptions

Routine work follows a predictable path: request, reminder, submission, review. Exceptions do not. Examples include a reference that raises a concern, an unexplained gap in employment history, a name that differs between two documents or a training certificate that expires before the end of a booking. These need judgement, and they stall if nobody is clearly responsible. For each type of exception, agree:

who owns it, by role rather than by name, so cover works during leave
what information they need to resolve it
how quickly it should be picked up when a booking depends on it
where the outcome is recorded so the next person can see it

A shared view of outstanding work

Recruiters need to see which of their candidates are held up and why. Compliance needs a queue of items waiting for review, ordered by the shifts that depend on them. When both groups work from the same records, the conversation moves from "is this done yet?" to "this reference is the only item left for Monday's booking".

Plan for renewals as well as onboarding

Compliance does not end when a candidate starts work. Training certificates, checks and registrations all have renewal cycles, and an active worker whose evidence lapses causes more disruption than a new candidate who is not yet ready. Record expiry dates when evidence is approved, and set reminders far enough ahead to collect and review the replacement before it is needed.

Look at the booking horizon as well as today's date. If a care worker is booked on a six-week block, check that nothing they hold expires during that block, not just that everything is valid on the first day. Automated reminders for approaching renewals handle the routine part of this once the agency has configured its reminder rules. Reviewing and approving the new evidence still sits with the team.

Keep a record you can rely on

Clients may ask what was held for a worker on the date of a particular shift. Answering that from a shared mailbox is slow and unreliable. A document history that shows each version, when it was received and who approved it lets the team answer from the record. As a simple test, pick a recent placement and check whether you can answer these questions without asking a colleague:

What did the agency baseline and the client checklist require for this role?
Which evidence was supplied, and when?
Who reviewed each item, and what was the outcome?
Which items had expiry dates, and were any renewed during the placement?
Were any exceptions raised, and how were they resolved?

If any answer depends on someone's memory, that part of the workflow needs attention.

Review the workflow together

Discuss delayed placements with consultants and compliance. Identify whether the issue is a missing request, unclear requirement, review queue or candidate response, then change the relevant step.

What to look at

A short, regular review is more useful than an occasional large one. Useful measures include:

time from request to submission, which reflects how clear and easy the request was
time from submission to review, which reflects capacity in the review queue
items returned to candidates, and the most common reasons
placements delayed by compliance, grouped by the item that held them up

Look for patterns rather than individual cases. If the same client form causes delays every week, the fix may be to request it earlier or to clarify the instructions with the client. If submissions sit unreviewed at the end of the week, the issue is cover rather than candidate response.

Change one step at a time

When you change the workflow, change one step, tell the team what has changed and why, and check the effect at the next review. Updating checklists, reminder rules and ownership all at once makes it hard to see which change helped.