Short answer: 3 to 6 months for a complete multi-location manual, assuming the business is actively participating. A single role-based playbook takes 4 to 8 weeks. The real variable isn't writing speed — it's how much of the business lives in people's heads versus how much is already documented somewhere.
The numbers that actually predict the timeline
Two estimates we use with every client:
- ◆~5 hours per page to document a new procedure from scratch — interviews, drafting, screenshots, review, revision
- ◆~2 hours per page to revise or restructure content that already exists in some form
That ratio matters because most brands have fragments. A closing checklist in a Google Doc. A training video from 2022. A GM's personal notes. None of it is wrong — none of it is stitched together either.
If half your content exists in fragments and half lives in someone's head, expect a 100-page manual to take roughly 350 hours of focused work. Split across a 4-month engagement, that's a real schedule — not a side project.
The manual isn't the finish line. It's the baseline — something concrete enough to refine against.
What drives the timeline up
Decision bottlenecks. Every procedure has a call to make — which way do we actually do this? If that call has to wait two weeks for a founder to weigh in, every procedure stalls. Brands that assign a single internal owner with decision rights ship twice as fast.
Too many cooks on the first draft. Writing by committee produces mush. One person drafts. Two or three review. Everyone else waits for the validation phase.
Scope creep mid-project. New section, new role, new location type added halfway through. Each addition resets the timeline for that module. Lock scope before starting. Add new modules in a follow-up phase.
What shortens it
Start with the role that's hurting most. If new GMs are ramping too slowly, build the GM playbook first. If franchisees are calling HQ for every decision, start with the franchisee operations guide. Don't try to build the whole manual at once — build the part that earns its keep in month one.
Interview the best operator, not the founder. The founder knows why. The best operator knows how. How is what needs documenting.
Validate in parallel, not sequentially. Put draft procedures in front of one or two locations while you're still writing the rest. Fix what breaks in real time instead of holding everything for a big reveal.
A realistic project shape
For a multi-location brand at 10 to 30 units building a complete manual from scratch, a realistic shape looks like this:
Weeks 1–2·audit what exists, interview key operators, lock scope
Weeks 3–10·draft core playbooks, role by role
Weeks 11–14·validation period — run drafts at two locations
Weeks 15–16·final revisions, rollout plan, LMS load
That's a 4-month project if the business participates actively. Stretch it to 6 months if review cycles are slow or decisions take time.