Start with the whiteboard
Bring the jobs into one shared view.
Your job board
Move jobs forward with a clear view of what’s next.
Know what is waiting, who owns it and what happens next.
Try it: open a job to see its next step, or move it along. Nothing you do here is saved beyond this visit.
Jobs arrive, the Monday page goes out
And no crew leaves for a job that is not ready.
Sources connected
New jobsFrom the quote tool export, nightlyStage: quoted
Crews and promised datesFrom the shared calendarTwo-way
Monday pageEmailed to the owner at 6:30 am, before toolboxBoard, this week, needs attention, parked
Readiness check, tomorrow's jobs
Firle Physio, accessible bathroomReadyAccess, materials, permit, customer confirmed
Magill Primary, tap replacementNot readyNo after-hours access contact
P. Oyelaran, rainwater tankNot readyPump not on the truck list
The checklist came from their last twenty knockbacks, written down on day one.
The sprint delivers personal software: durable, shaped around the client's own files and vocabulary, with visible errors and a manual fallback to Step 1. Built in their accounts.
What it grows into
Two booked days a month, decided each quarter on the numbers.
| When | Event | Handled |
|---|---|---|
| Daily 4 pm | Readiness check on tomorrow | 2 of 9 jobs flagged, office fixes both |
| Daily | Promised-date reminders | To crews, the evening before |
| On completion | Invoice trigger | Draft invoice in the accounting file, office sends |
| Monthly | Knockbacks: count and top three reasons | One line to the owner |
- Promised-date reminders to crews, and an invoice trigger on completion.
- A supplier order list from scheduled jobs.
- The knockback log becomes a likely-knockback flag before dispatch, once a season of reasons exists. That is the horizon, not the first version.
- A customer-facing status page is production software, scoped and priced as its own step.
Illustrative month. The retainer is booked days, not a support arrangement.
