What belongs in an operations manual
An operations manual is the collection point for your SOPs, role definitions, tool logins reference, and team policies — not a new document to write from scratch. If you have already written individual SOPs, the manual is mostly an index and structure around them.
Include your five core systems (leads, database, transactions, listings, people), your communication policies, and your compliance file requirements. Leave out anything that is really a one-time project plan rather than a repeatable procedure.
Choosing where it lives
The manual needs to live where your team already works — inside your CRM's knowledge base, a shared drive, or a tool like Notion or Google Sites — not in a PDF emailed once and never opened again.
Avoid tools that require a separate login nobody remembers. If checking the manual means one more password, people will text a teammate instead, and the manual quietly becomes decorative.
Structuring it for search, not for reading
Nobody reads an operations manual cover to cover. Structure it so someone can search "how to submit an offer" and land on the exact procedure in two clicks, organized by the five core systems rather than by department or hire date.
Use consistent headings across every SOP inside the manual — trigger, steps, tools, owner — so once someone learns the format, every section is equally fast to scan.
Keeping it maintained
Assign one person as the manual owner, responsible for making sure updates to individual SOPs actually get folded back into the manual. Without this, the manual and the real process drift apart within a few months.
Add a version note or last-updated date to each section. When something changes — a new lender partner, a new lead source — update the manual as part of that rollout, not as a separate cleanup project later.
Where to start
If you already have SOPs scattered across documents and group chats, your first job is consolidation, not new writing.
- Gather every existing SOP into one shared location
- Organize them under the five core operations systems
- Pick the platform your team already checks daily
- Assign one person as manual owner
- Add a last-updated date to each section