Field notes › Compliance
Fit-for-work declarations: what good looks like
A fit-for-work declaration is a simple idea. Before a shift, the worker confirms they are in a state to do it safely: rested, sober, not impaired by medication or injury, not carrying something that makes them a risk to themselves or the crew. Simple idea, and one of the easiest compliance processes to do badly. Most versions of it drift into ritual within months. Here is the difference between a declaration that means something and one that just makes paper.
What the declaration is actually for
Licences and inductions establish that a worker is qualified in general. The fit-for-work declaration covers the one thing those records never can: the worker's state today. It does two jobs at once. It prompts the worker to honestly consider whether they should be working, and it creates a record that the question was asked and answered before the shift started.
That second job matters more than it looks. If something goes wrong on shift, one of the first questions asked is whether the person was fit to be there. A firm that can show a declaration made before the shift, by the worker, is in a very different conversation to a firm that can show nothing. What your declarations must cover, and how they interact with drug and alcohol testing and site requirements, varies by state and by site, so anchor your process to the site operator's rules and check anything uncertain with your state work health and safety regulator.
Where declarations go wrong
The failure pattern is nearly always the same, and it is procedural, not moral:
- Paper forms filled in at the gate, in a hurry, in the rain, then filed in a box no one opens.
- Tick-and-flick. The worker learns the fastest path is ticking yes down the page, and the declaration stops carrying information.
- Declarations that exist for some sites and not others, because each client asked for something different and no one reconciled it.
- No connection to the roster, so nobody can say afterwards which declaration belonged to which shift.
- Answers that trigger nothing. A worker declares they are not fit, and the process has no next step.
That last one is the worst, because it teaches workers that honesty is pointless. If declaring a problem produces no response, people stop declaring problems.
What good looks like
A declaration process worth keeping has a few plain characteristics. It is short, because a long form gets skimmed. It is done on the worker's own phone, because that removes the gate-side scrum and the paper. It is tied to a specific shift, so the record answers the question that will actually be asked later. It is stored where you can retrieve it months on, by worker and by date, without an archaeology project. And a declaration that raises a concern goes to a person whose job is to act on it before the shift starts, every time.
Just as important is what good does not look like. It does not punish honesty. A worker who declares they are underslept after a rough night needs a conversation and maybe a reassignment, not a mark against their name. The declaration is an early warning system, and early warning systems only work when people are willing to trip them.
Making it part of the roster, not another system
The practical reason declarations decay is that they usually live in a separate system from everything else, one more app, one more folder, one more thing to chase. They hold up better when they sit inside the tool that already runs the shift. In Mustr, fit-for-work declarations are part of the platform alongside the roster, workers handle their side through the worker portal on any phone with no app to install, and the audit trail keeps the history so a declaration can be produced when a client or auditor asks.
The goal is a declaration that takes the worker under a minute, means what it says, and can be found in seconds a year later. If your current version is a box of damp gate forms, book a demo and see it on your own roster.