The Thursday Board That Remembers Everything

Operations at an industrial services business is a constant act of rearrangement, and AAA carries an extra dose of it. Alongside the scheduled maintenance and cleaning work sits a steady share of emergency response: spills, cleanups, urgent containment jobs. A large spill doesn't book itself a quiet Thursday. It lands now, it takes priority over everything already booked, and it can demand the whole business reorganise around it within the hour. Crews get pulled off jobs, equipment gets redirected mid-task, and the week that was carefully planned is rebuilt in a phone call.

Crews finish early, a job overruns, a customer pulls work forward, a subcontractor cancels, plant breaks down. The schedule lives and dies on how quickly the people running it can see what changed, decide, and get the new plan in front of everyone who's working to it.

AAA's answer for years was a physical whiteboard. It was genuinely good: the whole week in one line of sight, anyone could walk up to it, and moving a card was a two-second decision. Its weakness was the same as every whiteboard's: it remembers nothing. Who moved what, why a job slipped from Wednesday to Thursday, whether the customer was told, what the crew was promised. All of that lived in memory and verbal handoff, and by Thursday's planning meeting the reasons behind the week's shape had already evaporated.

The confirmation problem ran underneath it. "Is this job confirmed?" means three different things to three different people at AAA. Sales means the customer has committed. Operations management means a date and a crew are allocated. The wider ops team means leadership has signed off and it's safe to load the truck. A single tick can't carry three meanings, and the failure modes are real: sales green-lights work operations isn't ready for, or the team goes to site without the sign-off they expected.

And once work reached the crews, the trail went quiet. Who clocked on, what the job actually took, whether the hours matched the quote, what was spent on plant and subcontractors against what was sold. The gap between the quote and reality is where the margin lives or dies, and on a whiteboard it's invisible.

The whiteboard is now software inside AAA's Dynamics 365, and it kept everything that made the physical board good: the whole week in one view, cards that move in seconds, the whole operation visible from a distance. Then it added the things a whiteboard can't do.

Every confirmation is layered. An order being won, a crew being scheduled, and a day being published to the team are three separate assertions by three separate people, and the board stores them separately. The publish step is per calendar day, because that's the rhythm operations actually runs on: end of day, tomorrow's plan is committed, the team plans around it. Publish a day again after a same-day edit and that's a normal action, not an exception.

Every card movement is written to a permanent log, inside the same transaction as the move itself. Who, what, from where to where, when, and a reason when a card crosses a month boundary, which is the moment deferrals quietly change revenue. The board's undo still snaps, but the history survives reloads, other users and other applications. When two people remember the week differently, the log settles it.

Emergency work is where that speed matters most. A spill response means tearing up the week: cards pulled off days to free the crew, other jobs pushed or re-staffed, a new urgent job created and crewed in minutes. The board absorbs the reorganisation as fast as the old whiteboard did, but now every displaced job carries the record of where it went and why, so the customers pushed aside on Tuesday for the emergency are tracked and re-booked rather than remembered.

Recurring work got its own model. A monthly pit clean for a meatworks isn't a card, it's a pattern: cadence, template, next due date. When the time comes, someone spawns the job and the system builds a properly quoted order from the template at current prices. If a cycle was missed, it's skipped explicitly with a reason and an audit row, never silently lost, so "why didn't we do the February clean?" has an answer years later.

The card grew into the working surface. Open a day and everything about it is there: the crew banner, the supervisor, times, the scope from the quote, crew and machines assigned from the yard. From that same card, operations can send the customer a branded booking confirmation and see on the card whether it went, raise a purchase order against what was sold, and pass a cost gate when reality costs more than the quote allowed. The gate has two named paths, absorb the overrun as a management decision or send it back to sales as a variation, and both are recorded with a name attached.

Publishing a day hands it to the team. After the hours come back, the card is checked and locks, but not with a hard freeze. AAA rejected that: "you always say that, then tell me to amend it after." The lock resists casual edits and allows a deliberate, permissioned amendment that's recorded.

The crews see their own jobs on their phones, clock on, and sign the safety pack individually. The job view is deliberately dollar-free: an operator sees the site, the crew, the work and the equipment, never a rate or a margin. And the two hour figures stay separate on purpose. Actual clocked hours drive wages, quoted hours drive invoicing, and the difference accumulates per resource type into an over/under position every manager can read.

The week is planned and re-planned at the speed of the old whiteboard, with none of the amnesia. A rearranged week is visible, undoable, and every change is attributable. That holds on the worst day as well as the normal one: an emergency spill can rebuild the entire board in minutes, and the jobs it displaced are still tracked, still promised, and still visible to re-book the moment the pressure passes.

Month-boundary deferrals stopped being folklore. A card pushed past month end needs a reason, and the reasons accumulate into a picture of what's really slipping and why.

The handoff to crews is explicit. A day is published, the team works to it, and republishing after a change is routine. Nothing reaches the yard on an implication.

Customers get confirmations from the card in one motion, and the card shows whether it went.

Every schedule change has an author. When the yard and the board disagree, the history says which one moved and who moved it.

And the money conversation happens with real numbers. Overruns surface at the day they happen, priced by what they cost AAA, with the absorb-or-variation decision recorded at the moment it's made.