Every small business has a person everyone asks.
“Which supplier do we use for this?” “What do we tell a customer when the crew runs late?” “Has this equipment failed before?” That person may be the owner, the office manager, or the technician who has been around longest.
The business works because that person remembers. It also slows down when every answer waits for them.
Capture decisions, not transcripts
Start with the questions people ask twice a month. Ask the subject-matter expert to answer each one in plain language and include the condition that changes the answer.
Weak note: “Use Northside for filters.”
Useful note: “Use Northside for standard 16-by-25 filters when the customer has an account. For same-day pickup, call the counter before promising availability. The current account contact is in the vendor directory.”
The second note gives the team a decision, a boundary, and a next action.
Use a repeatable page
Give every playbook entry the same fields:
- Question: what someone is trying to decide
- Answer: the approved action in one or two sentences
- When it changes: exceptions and limits
- Evidence: policy, rate sheet, photo, or person who confirmed it
- Owner: who keeps the entry current
- Reviewed: date of the last check
This structure matters more than the platform. You can store the pages in a shared drive, a wiki, or a document system while you learn what the team needs.
Separate facts from judgment
Mark the difference between a rule and an experienced opinion.
“The warranty covers parts for one year” is a policy fact. “I prefer this supplier because their driver arrives early” is useful context, but it should not become a promise to a customer.
An AI assistant can summarize both. It should label the source and avoid turning a preference into company policy.
Make search answerable
People do not search for your folder structure. They search for a situation:
- “Customer says the unit is still noisy after service.”
- “Which jobs need a photo before closeout?”
- “What should I ask before quoting a driveway repair?”
Write page titles and headings in the language your team uses. Put alternate terms in the page when they help search. “AC,” “air conditioner,” and “HVAC” may describe the same work to different people.
If you add AI search, require the answer to show its sources. A short answer with a link to the approved procedure beats a long answer that sounds certain but cannot show where it came from.
Start with 20 entries
Do not try to document the whole company. Pick one area where the owner gets interrupted often:
- List the 20 questions that cause the most interruptions.
- Interview the person who answers them.
- Draft the entries while they watch.
- Have a second employee try to use the entries without asking the expert.
- Fix the pages that caused confusion.
That second employee is your test. A document is useful when a capable person can act from it, not when the author says it looks complete.
Review the shelf life
Some knowledge changes every year. Some changes every week. Put a review date on both. Route an entry back to its owner when a price, supplier, policy, or service area changes.
Archive old entries instead of deleting them when the history matters. Label them clearly so search does not present an old policy as current.
The goal is not to remove experience from the business. It is to make good judgment easier to share, check, and improve.
If your team keeps interrupting the same person for the same answers, book a free Opportunity Scan. We can help you choose the first 20 entries.