The Standing Question Log SOP

Purpose

To keep a running, permanent record of every question that reaches the owner, so that recurring questions get retired into written answers instead of being answered again, and so that the shop can tell the difference between a documentation gap, a training gap and a genuine judgment call.

A one-off audit tells you where you are today. This log is the standing version: it stays on, it feeds a short weekly review, and it is the mechanism that stops the same fifteen questions from quietly coming back six months after you published the answers.

Scope

Covers every inbound question directed at the owner or at whoever currently holds the answers, from technicians, office staff, subcontractors and helpers, across all channels: calls, texts, radio, walk-ups and in-person interruptions on a job.

Excludes customer questions, which belong in the customer communication path. Excludes approval requests, which need authority limits rather than answers and are handled separately. Excludes emergencies and safety questions, which get answered immediately and logged after the fact, never delayed for the sake of the log.

Roles and responsibilities

That last row is load-bearing. The moment a question log becomes evidence in a review, people stop asking, the log goes quiet, and you lose the only instrument that showed you where the gaps were. State this out loud when you start.

Procedure

1. Set up the log with five fields and no more

Time and asker, channel, the question in the asker's own words, minutes spent answering, and minutes until you were back into what you were doing.

Keep the asker's wording verbatim. When you eventually publish an answer, it has to be findable by the words people actually use, and your own summary of their question is already translated into your vocabulary. Six fields is where logs die: keep it at five, on a phone note or a single sheet, and capture within the hour or you will reconstruct from memory and undercount.

2. Log continuously, review weekly, in a fixed slot

The review is short. Fifteen to twenty minutes, in the same slot every week, tied to a meeting you already hold so it does not need its own defense. Do not batch four weeks of log into a monthly session: by then you no longer remember which questions came in a rush and which were considered, and that context is what separates a training gap from a documentation gap.

3. Classify each entry: Lookup, Rule, or Judgment

• Lookup: a fixed fact that already exists somewhere. Publish it.
• Rule: the answer is consistent but has never been written. Write the rule.
• Judgment: the answer legitimately changes with the job. Coach, do not publish.

The test is one sentence: if the same question on a different job next month would get a different answer, it is Judgment.

4. Apply the retire trigger

A distinct question is retired when it has appeared three or more times within the trailing four weeks of the log, counted across all askers rather than per person, AND its answer does not change with the job. Both gates, joined by AND. A question that hits three occurrences with a moving answer is a Judgment entry and gets a coaching plan instead.

Three occurrences in four weeks is the point where you are looking at a pattern rather than a bad week for one person. Shops that set the trigger at two spend the review writing pages for coincidences; shops that set it at five carry the same interruption for a month longer than they needed to.

5. Write the answer against a fixed standard

Every published answer carries four things or it comes back as a question:

1. The unit of analysis. Per job, per customer, per truck, per week.
2. The Boolean, stated explicitly, whenever two conditions are joined.
3. The step size, if the rule changes a number. "Add hours when a job type runs long" is not usable; "add 1.0 hour to the quoted time for that job type once three consecutive jobs have run over" is.
4. The exception, in the same sentence as the rule rather than a paragraph below it. Readers extract rules and skip context.

Then run one real recent job through your own written rule before publishing. If your own last decision does not survive your own rule, fix the rule.

6. Confirm the answer is placed, not just written

The office lead confirms placement in the surface the crew opens daily. Written and unplaced is the most common way this SOP fails, because the work feels done.

7. Mark the entry retired with a review date

Retired means published and placed, not answered once. Set a check date four weeks out.

8. Run the reappearance test at the check date

If a retired question reappears three or more times in the following four weeks, the answer is not findable, and the fix is to move it, not to rewrite it. Owners reflexively rewrite: more detail, more structure, a longer page. The page was rarely the problem.

Rewrite only when the reappearing question is worded differently from the one you published. Different words mean a comprehension miss, and that is fixed by matching the crew's language.

9. Reclassify upward every quarter

Once a quarter, read the Judgment entries for anything that has stopped moving. A call that needed real experience two years ago often has a stable answer now because the shop's mix narrowed. Those become Rules. This is the only step that shrinks the Judgment pile, and without it the log slowly stops paying.

10. Route the question nobody in the shop can answer

Some entries are not gaps in documentation or training, they are gaps in the shop's knowledge: an unfamiliar system, an inspector's requirement nobody has met before, a code question. These jam a log because they have no obvious disposition.

Give them their own disposition, External, and a time box: 20 minutes of looking before the question goes to a named outside source, whether that is a manufacturer support line, a supply house counter, an inspector, or a peer. Twenty minutes because past that you are usually not converging, you are circling.

Then log the answer, not just the fact that you called someone. An External entry that is closed without a written answer will be asked again the next time the same system shows up, and this time nobody will remember who was called. Externals are the highest value entries in the whole log precisely because the answer is hardest to re-obtain.

11. Hand off a class when it is stable

When a category has been published, has passed its reappearance test, and the field lead has answered it correctly for four consecutive weeks, move the log ownership for that category to them. The owner stops receiving those questions. That transfer is the actual point of the log.

What a live log looks like after a quarter

A shop with three techs and one office person ran the log for thirteen weeks. Trailing four week counts, taken at the end of each month:

Month one retired 11 distinct questions, all Lookup. Those 11 accounted for 26 of that month's 34 lookup occurrences, so a little over three quarters of the lookup load sat in 11 questions.

Month two retired 6 more, this time mostly Rules, and caught its first reappearance: a pricing question published in month one came back four times. It had been written into a document nobody opened. Moved to the app the crew already used every morning, unchanged in wording, and it did not return in month three.

Read the Judgment column across the three months: 11, 13, 14. It rose while everything else fell, and the total still went from 63 to 29 across the same four week window. That is the pattern to expect. The easy questions leave, the hard ones surface because there is finally room for them, and the owner's remaining load is the part that actually needs the owner.

At month three, 29 questions in four weeks against 63 in month one is a reduction of 34 questions per four week window, a little over half. The owner's own recovery-time column had averaged 11 minutes, so the remaining load was still costing about 5 hours across that four week window before any further handoff.

Two reads the log gives you that nothing else does

Beyond the retire list, the log carries two diagnostic signals that no other instrument in a small shop produces.

Asker concentration. Sort a four week window by who asked. In the shop above, month three's 29 questions split 13 from one tech, 6 and 5 from the other two, and 5 from the office person. One person accounting for 13 of 29, a little under half the month's questions, against a shop where the load should sit near a quarter each, is not a documentation finding. Publishing another page will not move it. That is a training conversation with one person, and the log is the only place that number was ever visible, because in the moment every question feels like it came from everywhere.

Channel concentration. Sort the same window by how the question arrived. Questions that arrive as calls interrupt harder than questions that arrive as messages, and a shop where the ratio is heavily weighted toward calls usually has an unstated norm that messages get ignored. If your own reply time on messages is slow, people will call, and no amount of asking them to text instead will change it. Fix your own reply latency first and the channel mix moves on its own.

When to pause the log rather than push through

Pause it during a genuine surge week, a storm response, or the first week of a new hire's onboarding. In all three, question volume spikes for reasons that have nothing to do with a documentation gap, and logging through it produces a set of retire triggers that will send you off writing pages for a situation that will not recur. Resume the following week and note the gap.

Do not pause it because it is quiet. A quiet log is data, and it is usually the first sign a handoff has actually held.

References

• See related: Universal - How to Stop Being the Answer to Every Question (the initial audit and classification method this log makes permanent)
• See related: The Owner Bottleneck: When Everything Needs My Approval
• See related: The Checklist That Grows Every Time Something Goes Wrong
• U.S. Small Business Administration, guidance on documenting standard operating procedures for small businesses