The auditor's sample arrives
The framework you supply under schedules an audit. The auditor sends a sample: a list of nurses and a list of shifts. For each nurse, they want to see the compliance evidence held at the time each sampled shift was worked. For each shift, they want the booking, the rate, any approvals, and the signed timesheet.
Your compliance manager and a colleague spend days opening folders, looking up bookings, finding timesheet photos, and trying to work out whether the DBS on file now is the one that was on file six months ago. Some documents have been replaced by renewals and the old ones are gone.
Why audit evidence is hard to produce
Most agencies hold compliance documents as the current set of files. An audit asks about the past. It also asks for connections between records, the nurse, the shift, the rate, the timesheet, which live in different systems.
- Renewed certificates overwrite old ones, so historic evidence is lost.
- Checks, such as register and update service checks, are not dated in a way you can show.
- Bookings, rates and approvals are in one system, timesheets in another.
- Profiles sent to clients are not stored, so you cannot show what was sent.
- Every audit is prepared from scratch.
What that costs
Senior staff lose days to each audit. Gaps found in the sample become findings, even when the nurse was compliant at the time but you cannot prove it. Findings can lead to improvement plans or affect your standing on the framework. And the stress of audit week falls on the people who also keep day-to-day compliance running.
Preparation under pressure also tempts people into mistakes of their own: a renewed certificate sent in place of the one that was valid at the time, or a timesheet from a different week. An auditor who spots one of those will look much harder at everything else.
| Auditor asks | Hard today because | With a record history |
|---|---|---|
| Evidence at the time of the shift | Old documents were replaced | Every version kept with its dates |
| When checks were done | Not recorded consistently | Each check dated with who did it |
| What was sent to the client | Not stored | Every profile sent is logged |
| Rate and approval for the shift | Separate systems | Linked to the booking |
| Signed timesheet | Photo in an inbox | Attached to the shift |
How we build audit-ready records
- Compliance documents are versioned: a renewal adds a new version, and the old one is kept with its dates.
- Every check your policy requires is recorded with its date, method, result and who carried it out.
- Every profile sent to a client is stored as sent, with the date and booking it related to.
- Bookings hold the rate, any approvals, the booker and the client's reference, linked to the timesheet and invoice.
- An audit screen takes the auditor's sample of nurses, shifts and dates and generates a pack for each, showing what was held and done at the time.
- Gaps in the sample are shown before the pack is sent, so you can investigate and explain rather than be surprised.
What the auditor expects to see is set by the framework and your agreements. We build the records so you can show it.
The next audit
The sample arrives, is entered, and the packs are generated. Your compliance manager reviews them, looks into any gaps, and sends them. The evidence shows what was true at the time, because nothing was overwritten. And the day-to-day compliance work carries on during audit week.
Keeping this history also helps outside audits, for example when a client queries a nurse's compliance on a shift months ago.
Is audit week like this for you?
- Audit samples take days to prepare.
- Renewed documents replace old ones with no history.
- You cannot show what profile was sent for a shift.
- Timesheets and bookings are in different places.
- Findings have come from evidence you could not produce, not from actual non-compliance.