How Do I Know If a Process Is Actually Being Followed?

You asked, they said yes, and you still do not know

A 16-person plumbing company at about $3.2M in revenue has 11 written procedures. The owner asks his service manager whether they are being followed, and the answer is yes.

He asks two techs the same question. Also yes, and both are telling the truth as they understand it.

To know whether employees are following a process, read the evidence the process leaves rather than asking about it. Any procedure worth keeping produces a trace, a filled field, a photo, a signature, a timestamp, and reading 10 of those takes two minutes and does not depend on anyone's memory or willingness.

Nine of the 11 procedures at that company left no trace at all. There was no dishonesty anywhere in the building and no way to know anything.

Three instruments, ranked by how much they lie

They are not equally good, and the cheapest one is the worst.

The middle one deserves a word, because owners default to it when asking stops satisfying them. Two hours riding along produces one very compliant day and no information about Tuesday.

In high-consequence operations the rule is blunter: a step with no recorded evidence is treated as a step that did not happen. That is a design rule about the procedure, not a suspicion about the person.

Asking measures intention. Watching measures capability. Only the trace measures behavior.

Design the trace into the procedure

The move is to make the evidence something the next person in the chain already needs. Then it gets created because the work requires it, not because anybody is being checked.

The plumbing company's closeout procedure was already traceable and nobody had noticed. The invoice cannot go out without the parts list, so a same-day invoice is evidence the closeout ran.

Its safety-check procedure was not. It had no output at all, so a tech doing it perfectly and a tech skipping it produced identical records.

The fix was a single field on the job ticket the dispatcher already reviews. That took ten minutes to add and turned an unverifiable rule into a countable one.

Ask one question of every procedure you have: if this ran correctly, what would exist afterward that would not exist otherwise. If the answer is nothing, the procedure is not finished yet.

The writing standard matters here too. A procedure vague enough to be followed several different ways will not produce a consistent trace, and what a new hire can actually run is the bar to hold.

The two-minute weekly read

You do not audit everything. You read one procedure a week, in rotation.

1. Pick one procedure. Rotate through the list, so an 11-procedure business comes back around roughly quarterly.
2. Pull the last 10 instances. Ten is enough to see a pattern and few enough to read standing up.
3. Count, do not interpret. How many have the trace, how many do not.
4. Read the misses, not the hits. Three misses out of 10 is a question about those three jobs, and the answer is usually one condition the procedure does not cover.

That is the whole thing, and it fits inside a weekly review you already run. Two minutes a week beats a quarterly audit that takes an afternoon and gets rescheduled twice.

The misses are the useful half, and they are usually not about people. A recurring miss is a rule that stopped matching the work, which is how procedures actually die rather than through neglect.

Read the misses, not the hits. The hits tell you nothing you did not hope.

Whether the procedure was ever adopted in the first place is a separate question with a human answer. Setting a standard that sticks is what happens before there is anything to verify.

When there is no trace, that is the finding

An unverifiable procedure is not a compliance problem. It is a design defect, and it is the more useful finding of the two.

It means the procedure was written as a description of good behavior rather than as a step in a chain of work. Descriptions of good behavior are what get ignored, precisely because nothing downstream depends on them.

The repair is usually small. Add one field, one photo, one signature, one timestamp, attached to something somebody else already reads.

Do that and adherence often rises without any conversation about adherence. A step whose output somebody is waiting for gets done, because skipping it now blocks somebody else.

There is an exit-value reason to care beyond the operations one. A business where the owner is the only verification mechanism is a business that runs on a person, and on a $300,000-SDE business the gap between that and an owner-light operation is $555,000 on identical earnings.

The wider frame is running the business as a system, and verification is the part most owners skip. A system you cannot read is a system you are personally holding up.

Some traces already exist and are worth reading for reasons beyond adherence. Customer records are the clearest case, and reading them tells you how concentrated your revenue really is as well as whether the account procedure ran.

Take your written procedures and ask each one what would exist afterward if it ran. The ones with no answer are this month's work.

The free Keystone diagnostic is 18 questions and about four minutes. It returns three scores and an estimated sale price, calibrated against 10 years of BizBuySell Insight Reports and 1.6M+ SBA 7(a) loan records, so you can see how much of the business is still verified by you personally.

Get your three scores and an estimated sale price, free, at https://app.trykeystone.io.

Adding a trace field is a ten-minute change. Rebuilding a set of procedures so each one produces evidence somebody downstream needs is the operating layer, and it is months of work.

A Full Operations Modernization installs that layer in a live system your team runs. The Full Operations Modernization page is where scoping begins.

FAQ

How do I know if my employees are following a process?

Read the evidence the process leaves rather than asking about it. Pull the last 10 instances of one procedure and count how many produced the expected trace, which takes about two minutes and does not depend on anybody's memory.

Why do employees say they follow SOPs when they do not?

Because they are reporting intention rather than behavior, and most people do follow the procedure most of the time. Asking is the cheapest instrument available and the least reliable, and watching is worse because a crew being observed complies that day.

How do I audit a small business process?

Do not run audits, run a two-minute weekly read of one procedure in rotation. Count the last 10 instances, read only the misses, and treat a recurring miss as a rule that stopped matching the work rather than a discipline problem.

What if a procedure leaves no evidence at all?

That is the finding. An unverifiable procedure is a design defect, and the repair is to add one field, photo, signature or timestamp attached to something somebody downstream already needs.