Field notes › Industries
Civil crews: tickets, weather and scopes that will not sit still
Civil work looks orderly on the program and chaotic on the ground. The client's schedule says the crew starts Monday. Then it rains for three days, the scope changes, and the operator you had lined up is suddenly needed on a different job with a different set of tickets. If you supply crews to civil contractors, your roster is never finished. It is only current.
Tickets expire at the worst possible time
Civil crews carry a stack of tickets and verifications, and a fair few roles need a high risk work licence. The rules around what is required for which task are set by the regulator in your state, so check with them rather than taking anyone's word for it, including ours. What is universal is the failure mode: a ticket quietly expires mid-project, nobody notices, and the worker keeps getting rostered.
The fix is not more diligence. Diligence is what you were already doing. The fix is a system that knows every worker's tickets and their expiry dates, surfaces anything expiring up to 60 days out, and lets you send a renewal reminder with one click. Mustr goes a step further at booking time: every booking is checked server-side against the worker's competencies before it is confirmed, and if a required ticket is missing or expired, the booking is blocked. Not flagged. Blocked. The compliance page covers how those checks work.
Weather rewrites the week
Rain days are the tax civil work pays. A wet week means shifts cancelled, crews stood down, and then a scramble when the site dries out and the client wants everyone back at once, plus extras to catch up. Doing that scramble by phone tree is slow and error-prone. You call ten people to fill four spots and then have to remember who said yes.
Open shifts turn the scramble around. Post the shifts, let qualified workers register interest through the worker portal on their own phones, and confirm the ones you want. The people chasing work come to you, and the roster stays the single record of who is actually on. Workers also keep their availability current in the same portal, so when you are rebuilding a rained-out week you are choosing from people who can genuinely take the work, not ringing your way down a list of guesses.
Scope changes mean crew changes
A variation lands and suddenly the job needs different plant, which means different operators, which means different competencies. On a spreadsheet this is where mistakes creep in, because the person reshuffling the crew is moving fast and trusting memory about who holds what. When the competency check runs automatically on every booking, reshuffling is safe by default. You can move fast because the system will not let you move wrong.
Keep the record straight
When something does go wrong on a civil site, the questions come quickly. Who booked this worker, when, and what did their tickets look like at the time? A spreadsheet cannot answer that. An audit trail can. Mustr keeps one, along with fit-for-work declarations, so the paper trail exists before anyone asks for it rather than being reconstructed afterwards.
Built for work that moves
The instinct is to blame the chaos on the industry, and partly that is fair. Weather and variations are not going away. But there is a difference between chaos you absorb and chaos you amplify. A roster that checks every booking, fills gaps through open shifts and keeps its own records absorbs the chaos. A spreadsheet passed around by email amplifies it.
If your crews and scopes never sit still, see it on your own roster.