Write down how your store works before the founder steps back

The founder knows which vendor's dispatch estimate needs another phone call, which deep sofa needs an extra access check, and which leather order needs a manager's approval. The team knows to ask. The answer rarely reaches the next order.

Start documenting the store while the founder can explain the decisions behind the routine. Follow a real order, capture the rule and its exceptions, then put each rule where staff will use it. OrderPilot's status map, product templates, vendor settings, and roles can carry the supported parts of that process.

Interview the decisions, not just the steps

Walk an order from the first showroom conversation through delivery and a later service question. At every step, ask what the founder checks, why it matters, what evidence settles it, and what happens when the normal answer does not fit.

Write the exception beside the rule. “Ask about access” is less useful than identifying which product dimensions prompt a detailed access conversation and who can assess an unusual delivery. Keep actual measurements in the relevant product information; do not turn a remembered doorway rule into a universal furniture dimension.

Ask a long-serving colleague to describe the same journey independently. Differences are evidence to discuss. The written procedure should reflect a sound way of working the team can follow, not a polished account of what the founder assumes happens.

A founder's memory can be remarkably well organized. It is simply difficult to put a second keyboard on it.

Turn a repeatable decision into a clear process step

Use the status map for meaningful stages and connections on Professional. A step deserves a status when it changes the work, the owner, or what the customer can reasonably understand.

Where a check uses facts the map supports, express it as an Only if condition. Where the decision needs judgment, use a staff step and explain the evidence the employee must read. Next status can then show the available move and what other moves are waiting for. Then actions can add a note or tag and notify the next responsible person. They should carry a handoff the store actually needs. Avoid building a connection for every sentence in the interview; the map should remain readable during work.

Put product and vendor knowledge where it belongs

Different kinds of knowledge need different homes. Use this sorting table while reviewing the founder's notes.

Vendor settings can hold supported details such as contacts, minimum quantities or values, and whether SKUs appear on POs. Keep interpretive knowledge, such as how to clarify a vendor's dispatch wording, in a shared operating note rather than forcing it into an unrelated field. The day-one mapping guide helps turn the organized notes into an initial process. For several locations, decide which rules are shared before setting up one way of working across showrooms.

Keep a short manual alongside the software

Write a short manual for the reasons, exceptions, contacts, and escalation boundaries the software cannot explain on its own. The app should carry the current order and supported rules. The manual should help a person make the judgment those records require.

There is no dependable universal duration for this work. Start with one order path and expand as you encounter meaningful exceptions. As a suggested exercise, run the written process alongside the founder for a month, with a colleague performing the work and the founder observing where explanation is still needed.

Test proposed map changes against orders before publishing them. Keep a record of why a rule changed. Version history preserves published maps, so the next responsible person can inspect the process's evolution rather than inherit an unexplained collection of conditions.

Make the business understandable to someone taking it over

A successor or prospective buyer should be able to understand how sales become vendor commitments, how customer money and delivery promises are followed, who approves exceptions, and how service finds the original sale. Show the current instructions and sample records, with appropriate access and customer information protected.

Documentation supports that understanding; it does not guarantee a sale price or a successful handover. Test the practical question first: can someone other than the founder run the next ordinary order and recognize when they need help?

Use the succession-planning guide to place this work in a wider handover plan, and the store-sale preparation guide when a sale is the intended route. Begin with the next decision only the founder currently knows how to make.