BookKeptevidence chain
Guide · enforcement

The Fair Work Agency and what it means for agencies

Enforcement in this industry used to be split across three bodies that rarely spoke to each other. The Employment Rights Act 2025 puts it in one place. The obligations barely move; what moves is how easily a gap is seen.

What is being consolidated

Labour market enforcement has historically been divided. The Employment Agency Standards Inspectorate covered the Conduct Regulations and how agencies treat work-seekers. The Gangmasters and Labour Abuse Authority covered licensing and exploitation in specific sectors. HMRC enforced the national minimum wage. Each held a slice of the picture.

The Fair Work Agency brings that work under one body. For an agency, this is less a new rulebook than a new vantage point.

Why one inspector is harder than three

Split enforcement had a quiet consequence: a question could usually only be asked from one side. A minimum wage query did not naturally reach into whether a Key Information Document was issued. A Conduct Regulations question did not naturally reach into what the umbrella in the chain was doing with payroll.

Consolidation removes that shelter. The questions that were previously hard to ask are the ones that cross the old boundaries: was this worker told what they would be paid before they agreed, did the money that reached them match it, and was the company that paid them one you had checked. Those are one question to a single body.

What that asks of an agency

Nothing on the list below is new law. What is new is that they now have to be answerable together, about the same worker, on the same day.

An agency that holds these in four systems can produce four answers. It cannot easily produce the one answer that joins them, which is the answer being asked for.

The solution

BookKept keeps the whole chain against one placement

The Key Information Document, the right-to-work check, the umbrella evidence, the approved weeks and both invoices all hang off the same placement record, and every compliance-relevant act writes a hash-chained audit row that is never edited or deleted. One click assembles the full chain for a placement as an evidence pack. The join an inspector asks for is the product's spine rather than an export somebody builds the night before.

See what it does