Volume 04, Chapter 4
Operational Records
Definition
Imagine a customer insists a repair was never actually done, even though they were charged for it. The mechanic remembers doing the work. Memory against memory settles nothing. What settles it is a signed log filled out the moment the job was finished. An SOP (a written step-by-step procedure) tells someone how to do a task; a record proves it actually happened.
document how a business operates day to day: the instructions for doing the work, and the evidence that it was done.
If Volume 02 taught how to write a system, this drawer is where systems live once written, SOPs, schedules, logs, and the records they generate every day. An SOP that exists but is never filed anywhere findable is barely better than no SOP at all.
What Belongs in Drawer Three
| Record | What It Captures |
|---|---|
| Standard operating procedures (SOPs) | How each recurring task is done, see Volume 02, Ch. 3 |
| Production schedules | What's being made, in what order, by when |
| Machine maintenance logs | Every service, oil change, and repair, see Volume 02's generator story |
| Pattern registers | Which pattern, which version, used on which order, full treatment: Volume 05 |
| Supplier information | Who supplies what, at what price and how long delivery takes, full treatment: Volume 12 |
| Delivery records | What left the business, to whom, when |
| Quality control reports | What was inspected, what passed, what didn't, full treatment: Volume 14 |
| Inventory records | What's in stock, where, full treatment: Volume 13 |
Several of these are big enough to earn their own entire volume later in this manual. This chapter's job is simpler: these records exist, they belong in this drawer, and they are generally maintained by supervisors or department managers, not the owner personally.
Volume 02 teaches how to write a system. Drawer three is the proof that the system was actually followed: which SOP was used, by whom, and when.
Why This Drawer Is Where Systems Prove Themselves
An SOP without records only shows what is supposed to happen. An SOP with records shows what actually happened. Volume 02, Chapter 2's sixth question, "how is success measured?", can only be answered from this drawer. A maintenance log either shows the monthly service happened, or it doesn't; there's no argument once the record exists.
This is also the drawer an insurance claim, a warranty dispute, or a quality complaint will ask for first. "We definitely serviced that machine" is worth nothing without the log that proves it.
Example Story: The Log That Won the Argument
A customer of Rapid Auto Works claimed a repair had never actually been performed, despite being charged. The shop's job intake and completion log, filled in the same day, signed by both the mechanic and the customer at drop-off, settled the dispute in one look. No log, no argument won, regardless of the truth.
Common Mistakes
A card that exists on someone's phone but not at the point of use might as well not exist. See Volume 02, Chapter 3's storage rule.
A maintenance log completed a week after the fact, from memory, is barely more reliable than no log, record it the moment the work happens.
If it's "everyone's job" to file operational records, it's no one's. Every log needs a named owner, per Volume 02's Six Questions.
Quiz Yourself
Practice Exercise
- List every SOP your business has written (Volume 02, Chapter 3).
- For each, confirm: is it filed at the point of use? Is there a log capturing that it's being followed? Who owns that log?
- Pick one operational record with no owner and assign one this week.
Quick Summary
Quick Summary
- Operational records are where systems from Volume 02 prove they're actually being followed, SOPs, schedules, maintenance logs, and quality reports.
- They're the evidence behind "how is success measured?", Volume 02's sixth question.
- Typically maintained by supervisors and department managers closest to the work.
- Several deserve, and get, full volumes of their own later: Volume 05, 12, 13, 14.