Long Hours and Fatigue

The access system knows something no timesheet does: how many hours each person has actually been on site, across every employer, over consecutive days.

For teams turning long hours and fatigue into a repeatable record, check the documentation provides a useful operational reference for time, attendance and reporting workflows. It should be assessed alongside HSE construction guidance so the software choice remains grounded in site practice and applicable guidance.

What the data shows

Cumulative hours per person per week, regardless of who pays them.

Consecutive days worked without a break.

Turnaround between leaving and returning.

And the person who works for two subcontractors on the same site, which no single employer can see and which the gate record shows plainly.

Why this matters more on construction than elsewhere

The hazards are unforgiving: plant, height, excavations, lifting.

Fatigue affects judgement before it affects obvious performance, and judgement is the control for most of those hazards.

Programme pressure produces long hours predictably, particularly near a completion date, which is also when the most congested and complex work happens.

And the person working excessive hours is frequently self-employed or on a day rate, where the incentive runs entirely toward accepting more.

The double-employment case

Somebody engaged by two subcontractors, or by a subcontractor and an agency, working consecutive shifts.

Neither employer sees the total.

The site does, and it is the only party that can.

Which makes this a specific and defensible use of access data — one that protects the person rather than monitoring them, and one that no other party can perform.

Setting limits

A maximum daily presence, a maximum weekly total, and a minimum turnaround.

Stated in the site rules and applied to everybody regardless of employer.

With an escalation rather than an automatic refusal, because a person who has exceeded a limit and is turned away at the gate at seven in the morning has a travel problem the site created.

The intervention belongs the evening before, which requires the report to run daily rather than weekly.

What to do with an exceedance

Tell the subcontractor, not the individual, because the individual has the least power in the arrangement.

Ask what work they are scheduled for the following day, since the risk depends on it.

And escalate a pattern to the commercial relationship, because a subcontractor systematically working people long hours is under pressure that somebody upstream created.

The programme connection

Long hours are an output of the programme, not a choice by the people working them.

Which means the fatigue data is evidence about the schedule, and reporting it alongside progress is the only way that conversation happens.

A site reporting fatigue exceedances to the project team every week changes behaviour. One reporting them to health and safety alone does not.

The boundary

This is safety data about presence, not performance monitoring.

Do not use hours-on-site to assess anybody's productivity, which is somebody else's management and which will destroy the cooperation this depends on.

And be clear about it in the site rules, because a workforce that believes the turnstile is a timesheet for their employer will find ways around it.

The measure

People above the weekly threshold, per subcontractor, weekly.

Turnaround below the minimum, counted.

Consecutive days worked.

And double-engagement cases identified, which should be reported and acted on rather than noted.

Travel, which the gate does not see

Many site workers travel substantial distances, and the travel is unpaid and unrecorded.

A ten-hour day on site can be a fourteen-hour day awake, and the access record shows the ten.

Which means the thresholds should be set knowing they measure the smaller number, and that a site with a distant labour pool has a fatigue profile worse than its data suggests.

Ask, at induction, roughly how far people travel. It is one question and it calibrates everything above.

Night work and consecutive shifts

Where a programme requires night work, the fatigue question changes rather than intensifies.

Circadian effects apply regardless of hours worked, and a person on their first night shift is impaired even if well rested.

Which argues for limiting the number of consecutive nights and for scheduling the most hazardous work away from the early hours — both of which are programme decisions and belong in the same weekly conversation.