You Don't Have Procedures. You Have Habits.

Ask any service company owner: "Do you have procedures?"

They'll say yes. They always say yes.

There's a binder somewhere. Or a Google Doc from 2022. Or a training video a former employee recorded. The procedures exist — in the sense that someone, at some point, wrote something down.

Now ask the person who actually does the work: "What do you do when you show up at a property?"

They'll describe something completely different.

Inferred vs. authored

Every service operation runs on six things: policies, procedures, assets, actors, triggers, and a ledger. The question is whether those exist as explicit, inspectable structures — or whether they live inside someone's head.

In most small service businesses, the answer is the latter. The policies are whatever the owner decided last time. The procedures are habits that veterans teach new hires by shadowing. The asset list is a spreadsheet that's three months out of date. The records are whatever someone remembered to write down.

That is an inferred system. It works — until the person doing the inferring gets sick, quits, or the business outgrows their memory.

An authored system is the same six things, made explicit. Written down, versioned, enforceable. The procedures have steps and gates. The assets are tracked. The actors are qualified and scoped. The ledger captures everything automatically.

How the habits form

A new hire starts. You pair them with your best person for two weeks. They shadow. They watch. They absorb the rhythm of the work — what to check first, what to skip, what to take seriously, what doesn't matter.

The problem is that your best person has been editing the procedure in their head for five years. They've dropped the steps that feel redundant. Added steps nobody else knows about. Developed shortcuts that work because they have context nobody else has.

The new hire doesn't learn the procedure. They learn one person's habits. And when that new hire eventually trains someone else, the habits mutate again. Each generation drifts further from whatever the binder said.

Three generations of shadowing. Three different versions of the same procedure. None match the documentation. No way to know which one is closest to right.

The cost you don't see

Habits don't show up on a balance sheet. They show up as:

• Inconsistency — two operators inspect the same property and produce different results. The customer notices. You can't explain why.
• Invisible failures — a step gets skipped. Nobody knows because nobody was checking whether it happened. The problem surfaces three months later as a customer complaint, a liability issue, or a repair bill.
• Unteachable expertise — your best operator can't explain what they do. They just do it. Training takes months instead of days because the knowledge transfer is oral tradition.
• Unearned blame — a new hire misses something the veteran always catches. But the procedure doesn't say to catch it. The new hire followed the process. The process was incomplete. The new hire gets the write-up.

Every service company owner has felt each of these. Most accept them as the cost of doing business with people. They are not a people cost. They are the cost of habits pretending to be procedures.

What a real procedure looks like

A procedure isn't a document. It's a system with four properties:

1. Steps — an ordered sequence. Not a checklist you can complete in any order. Step 3 depends on Step 2. The system knows the order.
2. Gates — decision points the system enforces. A gate might require a photo, a measurement, a confirmation that a value is within range. You can't skip the gate. The system won't let you.
3. Adaptation — the same procedure, different enforcement depending on who's running it. A veteran gets fewer gates — they've earned the trust. A new hire gets every gate. Same procedure, different experience. The policy knows who it's talking to.
4. A ledger — proof that every step happened, when, by whom, and what they found. Not a checkbox. A structured record you can query, audit, and learn from.

When a procedure has these four properties, the gap between what we say we do and what we actually do closes. Not because people try harder. Because the system doesn't allow the gap to open.

The veteran question

"My best people don't need a system telling them what to do."

Correct. Your best people don't need the system. Your business does.

The veteran's knowledge is the most valuable thing in your operation, and it's completely inaccessible. It lives in one person's head. It leaves when they leave. It can't be measured, audited, or transferred.

An authored procedure isn't a constraint on the veteran. It's a way to capture what the veteran knows so the next person doesn't start from zero. The veteran helps write the procedure. The system enforces it for everyone else. The veteran's gates are lighter — the policy adapts to their qualifications. They don't fill out the trainee's checklist.

But the ledger records their work the same way it records everyone's. Because the value isn't in controlling the veteran. It's in making their expertise survive them.

When the system is inferred, the operator gets blamed

An operator inspects a property. Misses a water heater showing early signs of failure. Two months later it floods the basement. The homeowner is furious. The service company asks the operator: "Why didn't you catch that?"

But there was no procedure that said to check the water heater. No checklist item. No photo requirement. No condition comparison against the last visit. The operator was doing what they were trained to do — follow a veteran around for two weeks and then figure it out.

In an inferred system, the operator absorbs the blame for gaps in a system that was never written down. "You should have known" is the mantra of an operation running on tribal knowledge.

With the same property and an authored procedure, the story changes. The procedure says: check the water heater. Compare today's photo to last visit's. If condition has degraded, flag it. The operator follows the procedure. The ledger proves they followed it. If the water heater still fails, the conversation turns into "the procedure needs an additional check" instead of "you messed up."

Screenshot placeholder: Mobile operator execution blocked by a required gate. Show a missing photo or pressure-reading requirement, the disabled/blocked close action, and the message explaining what must be completed.

For an operator making $18 an hour who is one bad review away from losing their route, that difference is the difference between a write-up and a process improvement. The authored system protects the person doing the work by making it possible to point at the rules and say exactly what was required, exactly what was done, and exactly where the gap was.

The first step

You do not need to author your entire operation in a week. Start with one procedure. Pick the one that varies the most between people — the one where you know two operators do it differently and you're not sure which way is right.

Sit down with your best operator. Ask them to walk you through exactly what they do, in order. Write it down as steps. Identify the gates — the moments where a decision gets made or a check gets performed. Then put it in a system that enforces those gates and records the results.

One procedure. Authored. With a ledger.

After a month, compare the records. You will learn more about your operation from one authored procedure than from a year of habits.

---

Runbook turns habits into authored procedures — steps, gates, and a ledger that proves the work happened. onrunbook.com

This perspective is grounded in the authored.systems framework — ten principles for building operational systems where humans author the rules and machines enforce them.