Drop the work on the board, and the crew can see it.
Book visits against the people you actually have. Whoever’s booked gets the job on their phone, the client gets told, and double-bookings, leave and impossible travel show up as warnings before anyone drives anywhere.
This week
4 on siteMatt
Science blockMon–Tue
Priya
Warehouse rewireTue–Wed
Sam
SwitchboardWed–Thu
Jake
Corio fit-outMon–Wed
A booking is a person, a day and a window. The maths happens underneath.
You book a morning, an arvo or a specific time, and set how long it runs. Underneath, that becomes a real start and duration so the conflict checks have something hard to work with — while the crew still sees a window rather than a stopwatch. Multi-day work is several visits on one piece of work, each its own card on the board.
Move a visit without restating its length and it keeps the length you gave it. A card drag never quietly shrinks a six-hour booking back to a default.
Finished visits lock, so the record of what actually happened on site stays intact. A no-show is rebooked as a fresh visit and both are on the day.
The board keeps you booking forward. Work that’s underway right now can still be dispatched to whoever is free.
Booking someone is what lets them see the job.
Access to a job comes from being on it, and crewing a visit grants that. A field staff member who isn’t on the job doesn’t get a permission error — they get “not found”. Re-crewing or cancelling a visit never takes that access back, because silently blinding somebody who is still involved is how work goes missing.
Nobody on a current or upcoming visit can be taken off the job by accident — the job holds them until the visit is un-booked.
A teammate who hasn’t finished their compliance onboarding won’t take a drop — their lane shows the lock and links to what’s outstanding, instead of the booking failing after the fact.
The board carries everybody, including the people with nothing on, so you can see who’s free before you drag rather than after.
Science block rewire
New job- Client
- Geelong Grammar School
- Site
- 50 Biddlecombe Ave, Corio
Warnings, not blocks — and the client hears about it.
Two visits overlapping for the same person, somebody on leave, or not enough gap to drive between two sites all surface as warnings on the board. None of them stop you, because the office knows things the software doesn’t. What goes out to the client is your call too: a booking confirmation and a reminder if you switch them on, and an on-my-way text the crew fires from site.
Consecutive visits with less gap than the drive between the two site addresses are flagged before anyone commits to the day.
Booking confirmations and reminders to the client are yours to switch on — SMS and email to the on-site contact, sent once per visit.
A booked, moved or cancelled visit tells the people on it, in words that describe what actually changed for them.
Who it’s for.
The same feature reads differently depending on which end of the business you’re standing at.
Whoever runs the week
Every teammate, every booking and every warning for the day or the week — and a filter down to just the trouble, or just the people with nothing on.
The crew
The day on their phone, plus everything they’re responsible for, including work that hasn’t been given a time yet.
The client
A confirmation when it’s booked, a reminder before the day, and a text when someone’s on the way — so they know when you’re coming without ringing the office.
Next door.
The parts of the system this one hands off to.
Put a week on the board.
Fourteen days with your own crew, your own sites and your own jobs on it.