Standard vs Judgment Call: When to Write a Rule

Why this matters

Some shops have a rule for everything and a binder so thick nobody follows it. Others have no rules and every job is improvised, so quality swings wildly with whoever showed up. Both extremes hurt. The skill is knowing when a situation deserves a hard standard and when it should stay a judgment call. Write a rule for the wrong thing and you frustrate good people and create loopholes; leave a rule unwritten where you needed one and you get inconsistent, sometimes dangerous, results. This is how to decide.

Start here: what kind of thing are you trying to control?

Before writing any rule, ask: does this need to be the same every time, or does it need to fit the situation? That single question sorts most cases. Safety, legal, and money-handling almost always need to be the same every time. Customer interactions and field problem-solving usually need to fit the situation. Most mistakes come from forcing one type into the other.

If getting it wrong is dangerous or illegal: write a hard rule

This is the clearest branch. If a wrong call risks injury, a code violation, or breaking the law, do not leave it to judgment. Write the standard, make it non-negotiable, and train to it.

• Lockout before working on energized or pressurized systems.
• Permit and code requirements.
• How money is handled and recorded.
• The safety steps that keep someone alive.

There is no "use your judgment" on whether to verify a circuit is dead. That is a rule, full stop. Judgment is for gray areas, not for the steps that prevent a funeral.

If it must be consistent for the customer or the books: write a standard

If inconsistency between people would confuse customers, hurt the brand, or break your numbers, standardize it. Pricing from the price book, how warranties are honored, what gets documented on every job, how invoices go out. Customers should get the same answer no matter which person they reach. Your records should look the same no matter who entered them. These do not require deep judgment; they require everyone doing it the same way.

If it depends on reading the situation: keep it a judgment call, but give guardrails

If the right answer genuinely changes with the circumstances, do not write a rigid rule. You cannot script every customer conversation or every weird field condition. A rule that says "always do X" will be wrong the moment reality does not match X, and your people will either follow it into a bad outcome or ignore it and learn that rules are optional.

Instead of a rigid rule, give principles and boundaries:

• State the goal ("leave the customer confident the problem is solved").
• Give the limits (what they can decide alone, where to escalate).
• Trust trained judgment inside those limits.

This is how you handle complaints, unexpected site conditions, and pricing edge cases. Teach the thinking, set the guardrails, let the person decide.

The diagnostic question when you are unsure

When you cannot tell whether something needs a rule, ask: how much does the right answer vary, and how bad is a wrong one?

• Low variation, high cost of error: hard rule. Same every time, mistakes are expensive or dangerous.
• Low variation, low cost of error: a standard or a checklist is plenty.
• High variation, high cost of error: judgment plus strong guardrails and training. The stakes are real but no rule fits every case.
• High variation, low cost of error: leave it to judgment, do not bother writing anything.

Signs you wrote a rule you should not have

• People constantly ask for exceptions. If a rule needs frequent overrides, the situation was a judgment call.
• The rule produces obviously wrong outcomes in cases you did not anticipate. Reality outran the rule.
• Good employees feel insulted or boxed in. You scripted something that needed their brain.

When you see these, convert the rigid rule into a principle with guardrails.

Signs you needed a rule and did not write one

• Two people handle the same situation in opposite ways and both think they are right.
• Quality or safety depends on who happened to do the job.
• The same argument about "how do we handle this" keeps coming up.

When you see these, stop debating case by case and set the standard.

What to do this week

Find one thing your team keeps debating. Decide which branch it belongs in: hard rule, standard, or judgment with guardrails. Then either write the rule once or write the principle once, and stop relitigating it on every job.

References

• See related: Checklist vs SOP vs Training: A Decision Matrix
• See related: Decision Authority Mapping: Who Owns What
• See related: Document a Process at the Right Level of Detail
• OSHA standards for required safety procedures
• Trade-standard practice for shop policy and field judgment