Mobilisation Pack Drafter
Reads the sales handoff on a won job, splits it into one job card per crew leg — scope, treatment, spec, quantities, site constraints — and lays the pack out for the works manager to check and approve before any crew is booked.
The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.
Reads the won job's handoff, splits it into one card per crew leg with the scope, treatment, spec and site constraints each crew actually needs, and lays the pack out for the works manager to approve before anything is booked.
It does the whole ritual every time, and the ritual is what the volume is made of.
- Best where jobs are small and frequent rather than long and few — a crew on several jobs a week, each carrying the full delivery ritual at small scale, is where the per-job overhead multiplies.
- Every card carries the same fields in the same places, so a supervisor reads the same sheet on every job instead of decoding a different whiteboard photo each morning.
- The recaptured time goes back to the works manager for the judgement calls — which crew, what sequence, whether the site is really ready — not the transcription underneath them.
It only knows what the handoff says — and a handoff that leaves things out still produces a confident, tidy pack.
- It does not know who is actually free. It reads the dates the job carries; it has no view of the crew already committed to another site that Tuesday, so it will happily draft a card that cannot be worked.
- It does not know the weather, and spray sealing is weather-dependent — a seal that cannot be laid wet or below the binder's temperature floor is a decision for the person reading the forecast, not for a document reader.
- If your jobs are won by phone and programmed straight onto a whiteboard with nothing written down in between, there is no handoff to read, and getting one written is the real work before any of this helps.
Pick last week's most awkward job. If the sequencing, the site access restriction and the specification were all written down somewhere before the crew left the yard — this helps. If they were in someone's head, this makes the gap faster to reach, not smaller.
It drafts the pack. The works manager books the crews. That line is deliberate.
Mobilising a crew is the moment the job stops being paperwork. A crew sent with the wrong treatment lays the wrong surface; a crew sent into a school zone in the wrong window is a traffic management failure. Those sit under the Work Health and Safety Act 2020 (WA) and its General Regulations, and under the temporary traffic management frame Main Roads works to — AS 1742.3, the Austroads Guide to Temporary Traffic Management, and the Traffic Management for Works on Roads Code of Practice. The consequence lands on the business and on the crew, so the manager stays on the decision.
A written handoff on every won job, with the sequencing and the site conditions actually in it.
The handoff itself is usually the weak point. In a lot of surfacing businesses the job goes from won to programmed with nothing written in between, because everyone involved already knows. Getting that handoff into a consistent written form — including the sequencing and the site conditions — is normally the real first piece of work, and it is worth doing whether or not anything is ever drafted on top of it.
The worried-buyer questions, answered straight
Fixed scope, fixed price, fixed dates.
Programming work off a whiteboard every week?
The honest place to start is one job type, one crew mix, low risk. Tell us what happens between winning the job and the crew leaving the yard; we'll play it back, scope it, and show you what's possible.