An operations manual should be the instruction manual for running your agency. In practice, most operations manuals are bloated documents that nobody reads, nobody updates, and nobody references after the first week.
The agencies that get operations manuals right treat them as living products, not one-time documents. They are searchable, concise, current, and integrated into daily workflows. When someone has a question about how to do something, the answer is in the manual—and finding it takes less than sixty seconds.
What Goes In (and What Does Not)
Include
How-to procedures: Step-by-step instructions for recurring tasks. These are the core of the manual.
Examples:
- How to onboard a new client
- How to set up a project in your PM tool
- How to submit an invoice
- How to request access to a client's systems
- How to handle a client escalation
- How to conduct a sprint demo
Templates and checklists: Ready-to-use documents that team members copy and fill out.
Tool guides: How to use each tool in your stack, including configuration, access, and key workflows.
Policies: Security, data handling, communication, time off, expense reimbursement.
Contact directory: Who to contact for what, with escalation paths.
Exclude
- Strategic plans (those belong in separate planning documents)
- Client-specific information (that belongs in project documentation)
- Technical reference material (that belongs in your knowledge base)
- Meeting notes or decisions (those belong in your project management tool)
- Anything that changes more frequently than monthly (it will be outdated immediately)
Structure and Organization
The Three-Tier Structure
Tier 1: Quick Reference (the most-accessed content)
- New hire first-day checklist
- Tool access and setup guide
- Key contacts and escalation paths
- Common procedures quick reference
Tier 2: Detailed Procedures (referenced as needed)
- Client onboarding process
- Project delivery workflow
- Quality assurance procedures
- Invoicing and billing procedures
- Security and data handling protocols
Tier 3: Policies and Reference (consulted occasionally)
- Company policies (time off, expenses, remote work)
- Brand guidelines
- Contract templates and legal notes
- Vendor and tool agreements
Naming and Navigation
- Use descriptive titles: "How to Onboard a New Client" not "Client Process v3"
- Organize by function (Delivery, Sales, Operations, Admin) not by date
- Create a clear table of contents with links
- Tag pages with relevant keywords for search
Writing Usable Procedures
The Procedure Template
Every procedure should follow this format:
Title: Clear, action-oriented (How to...) Purpose: One sentence explaining why this procedure exists When to use: What triggers this procedure Steps: Numbered, sequential steps Tools needed: What tools or access is required Templates: Links to relevant templates Owner: Who is responsible for this procedure Last updated: Date of last review
Writing Rules
- Write in second person ("You should..." not "The team member shall...")
- Use short sentences and bullet points
- Include screenshots for tool-specific steps
- Link to templates instead of describing their contents
- Note exceptions and edge cases separately (do not clutter the main flow)
- Test the procedure by having someone unfamiliar with the task follow it
Keeping the Manual Alive
Ownership
Assign an owner for each section. The owner is responsible for:
- Keeping content current
- Reviewing their section quarterly
- Updating procedures when processes change
- Responding to feedback and questions about their section
Update Triggers
The manual should be updated when:
- A process changes
- A new tool is adopted
- A new team member asks a question the manual should answer
- A project retrospective identifies a gap in documentation
- A quarterly review finds outdated content
The Quarterly Review
Every quarter, each section owner spends thirty minutes reviewing their content:
- Is everything still accurate?
- Are there new procedures that need documenting?
- Can anything be simplified or removed?
- Has the team provided feedback that should be incorporated?
Making Updates Easy
If updating the manual takes more than five minutes for a small change, the platform or process is wrong. Choose a platform where editing is as easy as typing in a document.
Integrating the Manual Into Daily Work
New Hire Onboarding
The operations manual should be the backbone of onboarding:
- Day 1: New hire works through the "Getting Started" section
- Week 1: New hire references procedures for their first tasks
- Week 2+: New hire uses the manual independently and flags anything confusing or missing
Process Enforcement
When someone does something incorrectly, the response should be: "Check the manual for the correct procedure." If the manual does not cover the situation, update it.
Team Meetings
Reference the manual in team meetings when discussing processes. "The procedure for this is documented in the ops manual here: [link]." This normalizes using the manual as a reference.
Common Ops Manual Mistakes
- Writing a novel: If your manual is 200 pages, nobody will read it. Keep it concise and scannable.
- Writing it all at once: Build the manual incrementally, starting with the most critical procedures.
- No ownership: A manual without assigned owners becomes outdated within months.
- Platform friction: If the manual lives in a PDF or a locked-down system, it will not be updated.
- Perfection paralysis: A rough procedure that exists is infinitely more valuable than a perfect procedure that does not.
Your operations manual is the operating system of your agency. Build it incrementally, maintain it consistently, and make it part of how your team works every day.