UK-built · CDM · CIS · MTD
Every gate scan, every overtime day and every hour in the van is already on your system. Advanced Fatigue Manager counts them against your own limits and warns the planner and the operative before the shift, not after the incident. No second system to keep fed: it reads the timesheet you already have.
Almost every firm we speak to records the hours properly and still cannot answer the one question that matters, which is how long this particular person has actually been awake and working this week.
Nothing here asks an operative to do anything new. They scan the QR code poster at the gate exactly as they do now, and the hours that land on the job also land on their fatigue record. Everything below happens between that scan and the next shift being planned, without anybody opening a spreadsheet.
Most fatigue systems fail for one reason: somebody has to key the hours into them. This one is wired into the timesheet, so it is as current as this morning's gate scan and it costs nobody an extra minute. What follows is what the module does today.
Every day line on the timesheet feeds the fatigue record as it saves: the project, the start, the finish, the pay type and the travel. There is no import, no overnight sync and no second place to keep current.
Travel time is already tracked separately on the timesheet, with its own daily ceiling. The fatigue count adds it back at both ends, because the tired part of a fifteen-hour day is usually the drive home and it is the part a gate-to-gate figure hides.
The thresholds are yours, set during implementation and changed when your policy changes. Shift length, door-to-door ceiling, minimum rest between turns, consecutive shifts, hours in a rolling week, night shifts in a row. Different rules for different roles where you need them.
A breach that surfaces on Friday is a report. A breach that surfaces on Tuesday is a decision somebody can still make. Alerts fire when the rule is approached and again when it is crossed, to the people who can move the labour.
The person doing the hours is told as well as the office. A push notification through your own app tells them where they stand and what the next rest period means, which is the part that turns a policy into something the workforce believes in.
Fatigue status shows on the labour run planner next to the person's name, in the screen where next week is actually built. Somebody at their limit is visible while the gang is being picked, rather than afterwards.
Per person, per project, per week, on your letterhead. Hours worked, hours door to door, rest taken, consecutive shifts, nights, and every warning raised with what was done about it. An auditor's sample is a lookup rather than a fortnight of reconstruction.
Night shifts are counted separately from the day total, because that is how the Working Time Regulations treat them and how a run of nights actually affects people. Consecutive nights and the recovery after a run are both on the record.
A fatigue record is only worth anything if it cannot be quietly tidied up afterwards. Amendments are appended rather than overwritten, with who made them and when, and an override carries the reason the planner typed at the time.
Two very different things get called fatigue management in this country. A handful of trades have a regime written for them by name, with limits somebody else enforces. Everybody else has the same legal duty under general health and safety law and almost no record of discharging it. Both columns below are the ones we built this for.
| The trade | What binds them | Why it bites |
|---|---|---|
| Rail and infrastructure contractors | Regulation 25 of ROGS 2006, plus Network Rail's fatigue standard NR/L2/OHS/003 for anyone in the supply chain on managed infrastructure. | A civils, piling or groundworks firm on a weekend possession becomes a controller of safety critical work. The industry reference figures are a twelve-hour shift, fourteen hours door to door, twelve hours rest between turns, no more than thirteen shifts in fourteen days and no more than seventy-two hours in a week. This is the one trade where the records are genuinely audited. |
| Highways and surfacing contractors | General duties, plus fatigue requirements written into National Highways and local authority contracts, and drivers' hours for much of the same workforce. | Night closures, hot-lay working windows and runs of consecutive nights, on top of long travel to a site that moves every few weeks. Most of the gang holds a second duty as a driver. See highways and surfacing. |
| Anyone running tippers, skips, mixers or plant transport | GB and EU drivers' hours rules, tachographs, and the Working Time (Road Transport) Regulations 2005. | Enforced at the roadside and by DVSA, so this is the one regime where a breach has a price list. The yard hours and the driving hours are usually kept in two systems that never meet. |
| Scaffolding, roofing and facade contractors | HSWA 1974 section 2, MHSWR 1999 regulation 3, the Working Time Regulations 1998 and CDM 2015. | The door-to-door problem at its purest: early starts, several sites in a day, heavy handling, and work at height where one lapse is fatal rather than expensive. Written up for scaffolding contractors, roofers and facade and cladding firms. |
| Demolition and groundworks contractors | The same general duties, with the plant operators also carrying a driving duty. | High-consequence plant, long shifts in heat and dust, continuous concrete pours that run past the shift they were planned for. See demolition. |
| M&E, fire protection and temporary site services | General duties, plus whatever the client's site rules impose on out-of-hours work. | Shutdowns and switching happen at night and at weekends, retrofit runs in occupied hospitals and schools, and a standby rota produces fatigue that never appears on a timesheet at all. See electrical, fire protection and temporary site services. |
| Principal contractors on any site | CDM 2015 regulations 13 and 15, which put the planning, managing and monitoring of the construction phase on you. | You carry the duty for a workforce most of which is not yours. A subcontractor's operative who did a night shift for somebody else on Tuesday is your problem on Wednesday, and only the gate record knows. |
Nothing here is legal advice, and no software
makes a business compliant on its own. Unibuild
records, measures, warns and evidences. The duty
stays with the employer in every case below.
Fatigue reporting is normally the bit that gets promised and never built, because it needs hours nobody has in one place. These come off the same day lines the job is costed from, so they are produced rather than assembled.
A fatigue policy the workforce only meets when they are sent home is a policy the workforce resents. Telling the operative at the same time as the office is the difference between a control and a punishment, and it is the reason this one gets used rather than switched off.
Five things a firm asks for that are not in the module as it stands. Unibuild is bespoke, so each one is a scoping conversation rather than a dead end: customer specific rules, fields and reports are written on request and included in the monthly fee.
The trades where a fatigue record is asked for by a client rather than only by a conscience, and where the same gate scan does both jobs.
Same platform, same login. These are the modules that plan the work, record it, and hold the evidence it was done properly.
What an inspector does on the day, what has to be reported and when, why a message thread is not a site record, and what makes a risk assessment survive contact with a site.
Two minutes. A written figure by email, usually the same day. Unlimited users, and no charge per operative or per alert.
Sent.
Darshan will reply within one working day.
