Write the board down
Open a session when the car comes in, then log every card: the system, how bad it is, the time you book for it and the parts it needs.
The race is won at night.
The service log for the crew that starts work when the stage ends. Open a session when the car comes in, log every card, time the work instead of guessing it — and hand the next shift a board they can read.
No account. No analytics. Everything you write stays on the phone.
The app follows the way a service crew already works. Nothing here is invented at runtime — the vocabulary is the one on the awning wall.
Open a session when the car comes in, then log every card: the system, how bad it is, the time you book for it and the parts it needs.
Start a timer when the work starts. The app keeps your booked time against the real time, and later estimates carry that difference for you.
Repaired, temporary or partial — with the parts it used and a note in your own words. That is what the next shift reads in the morning.
The assistant reads your own board, your crew and your crate, and can look at a photo of a part. Everything it says is a suggestion to verify on the car.
8 of 12 likely failures covered
Flat surfaces, one accent, and colour used only where it carries meaning — because at three in the morning nobody reads a chart.
The event, the car, the conditions and the time it has to leave. Every card you log tonight files under that session, and closing it moves the whole thing to the log.
One tap starts the clock on a card. Booked minutes sit against real minutes all night, and the gap between them is what the next estimate is built from.
Repaired, temporary or partial, with the parts it consumed and a note in your own words — so the morning crew inherits the truth, not a tick.
Tell it what the next stage runs on and it checks your loadout against the failures that ground usually causes — with slots used and kilos carried.
Ask it to order the board, say what to defer, check the crate or write the handover. Say no to the network and the on-device chief still triages, with no signal at all.
Symptom, cause, the proper bivouac fix, the honest bodge and how far that bodge gets you — for two dozen failures every raid crew learns the hard way.
The middle button changes with the night: it opens the session when there isn't one, and reaches for the camera once the work is running.
Job cards carry a system, a severity, booked minutes, the parts they need and the crew on them. The header counts the window down against what you booked.
Sessions, job cards, free notes and photo inspections, all searchable, with an export that pastes straight into a report or an email.
An inventory of what the team owns, a loadout for the next stage, and a coverage figure that tells you which likely failures you cannot fix tonight.
The channel stays shut until you read the notice and agree. Decline it and the offline chief still orders the board — every part of the app works with the radio off.
Pick what tomorrow runs on and the app counts the failures that ground usually causes against what is actually in the truck.
0 of 0 of the common failures on this ground are covered by what is in the crate tonight.
Each one carries the symptom, the cause, the fix that holds, the bodge that does not — and how far the bodge gets you before it lets go.
There is no sign-up, no login and no profile. No analytics, no crash reporting, no advertising or attribution code — and it never asks for your contacts or your location.
Sessions, job cards, timers, notes, the parts inventory, the crew list and the photos you take live in the app's own private container on the device.
The Chief tab stays shut until you read the notice and agree. After that, your question and a briefing built from your own log go out — and nothing else.
We hold nothing, so there is nothing for us to delete. Settings wipes the log, the inventory, the photos and the threads in place; deleting the app takes the rest.
Bug reports, feature requests and notes from actual bivouacs are all welcome — especially the last one. Write below, or mail jasonlawrence168@gmail.com directly.
Never send us your log: we have no way to read it and no wish to hold it.
Open the session, log the board and let the clock do the arguing.