The tool, in your browser
The job debrief log
One row per job. Put in the job and the day you rolled off, the biggest thing that went right, the biggest thing that went wrong, and the one fix that came out of it — with one name on it and one date. This flags any fix past its date and keeps the count: open, overdue, done, and how many debriefs you’ve actually logged. One glance tells you which jobs left a loose end nobody closed.
Free, and it asks for nothing. No email, no account, no sign-up. What you type stays in this browser on this device.
Read this first
The fix doesn’t walk over to the promise list by itself. The play says every fix gets one name and one date and then goes on the promise list, because that’s the list that gets read out loud every week. This page keeps the record job by job; it does not put anything on that list for you. You type it in both, exactly as you would with the two spreadsheets. A fix that only lives here is a fix nobody chases.
And this log only knows about this browser — nothing is sent to us and nothing syncs, so your foreman and your office manager don’t get it, though anyone who opens this page on this computer can read it. When you want it where they can, put the-job-debrief-log.xlsx on the shared drive and work from there.
The log fills in right here in your browser. If this line stays put, JavaScript is off — the spreadsheet below does the same job.
How it gets used
- Run the debrief at the truck first, roof still in sight, then write it down here. The meeting is the play; this is the record.
- Walk the roof before anybody talks. Valleys, penetrations, flashing, and the ground cleanup on the way down. You can’t debrief what you never looked at.
- Biggest win first, by name. Always. A debrief that’s only about what broke teaches the crew to dread it and hide the misses.
- Biggest miss — the thing, not the man. The near-miss counts too: the course that almost got skipped, the ladder that slid.
- What the homeowner said rides in the win or the miss line — “nails left in the flowerbed, homeowner found them.” There’s no homeowner column on purpose: the log is a fast scan, not a transcript. His exact words belong on the printable card at the truck.
- One fix, one name, one date. Then put that same fix on the promise list, or it dies in the parking lot. Set its Status to Open while you’re there: Open fixes and Done fixes count that column and nothing else, exactly like the spreadsheet, so a fix with no status sits in neither number. Plenty of jobs come off the roof with nothing to fix — those rows keep no status at all, and they still count as debriefs logged.
- At your weekly review, read the box. Anything showing OVERDUE is a job fix that blew its date and still isn’t Done — chase those first. Nothing gets marked Done until the fix is actually made.
Want it in a spreadsheet?
The same log as a spreadsheet
the-job-debrief-log.xlsx is this log as a spreadsheet — same columns, same formulas — for the computer at the shop. Two differences in the page’s favour: it has no twenty-row ceiling (the file’s box counts rows 5 to 24, and a debrief typed under row 24 is in none of the counts and never flags), and the example row is placeholder text here so there’s nothing to delete before your first real job. Three smaller ones: this page says so when a date you typed isn’t a date, it tells you when you’ve written a fix and left its Status alone, and where the file’s Flag column is simply blank until a fix is late, the same line here counts down to the date first. Two the other way: the file can sit on a shared drive where everyone sees it, and it opens on any computer you send it to. The sheets ask for your email once; this page never does.
The play behind it — M3-01 Ten Minutes at the Tailgate, Every Job — is the ten minutes at the tailgate that fills a row in, and the sheet notes spell out every column and formula. The play also carries the printable debrief card, in English and in Spanish, for the truck.