Check In and Out at Work in 2027: site threshold and ready-mix concrete scope

What the source actually says

The July 2026 announcement extends IN and OUT registration to qualifying property works and ready-mix concrete deliveries from 1 April 2027, while excluding cleaning activities from this construction extension. This page does not turn that source into an automatic conclusion; it translates the verified boundary into a construction workflow that can still stop on uncertainty.

The practical value comes from applying the boundary consistently to every relevant person, document and project rather than remembering it only when an exception appears.

Data to capture before action

The primary source makes several boundaries explicit: 1. the published threshold is EUR 500,000 excluding VAT for the place where work is carried out; 2. ready-mix concrete delivery is expressly included; 3. the person starts and ends registration in real time; 4. breaks are separate registration events. Keep the official page with the operational rule so a later reviewer can see which wording and date supported the decision.

Record both the source value and the normalised value used by the workflow. Preserve later corrections as additions so the original evidence remains understandable.

A usable decision route

Turn the rule into a repeatable sequence: 1. aggregate the value at the correct site level; 2. identify delivery drivers and every other person in scope; 3. separate cleaning from construction activities in mixed contracts; 4. run a full arrival-break-departure rehearsal. Give every step an owner, a timestamp and the relevant project or counterparty, rather than storing only the final status.

Before any external message, payment, status change or import, show the affected entity, amounts, dates and consequences. Require a fresh confirmation when those inputs change.

Where the workflow can fail

The most important failures appear when context or timing is lost: 1. testing only office employees; 2. treating a delivery ticket as attendance registration; 3. splitting contracts to avoid looking at the total site value. Use a visible exception state instead of guessing. A blocked item should explain what evidence is missing and who can resolve it.

Test at least one normal case, one ambiguous case and one late correction. The safe outcome for missing evidence is a question or escalation, not a confident default.

Control and ownership

Assign one authorised owner, keep the source, date, inputs and decision in one record, and send exceptions to a qualified adviser. Software can structure evidence, but it does not replace legal, tax or employment advice.

Review the procedure when the official source, contract, channel or product capability changes. Track prevented errors as well as speed so governance produces visible value.

Official or primary guidance: Official or primary guidance.

Explore Enfin, review pricing, or discuss your workflow.