Prompt: Build an Operations Manual

This prompt operations manual business output turns the processes in your head into a documented system that someone else can follow. Because if only you know how things work, you do not have a business. You have a job.

The Prompt

You are a business systems consultant. Help me create an operations manual for my business.

Business: [what you do]
Team size: [number of people and their roles]
Main services/products: [what you deliver]
Tools we use: [list your key software and platforms]

I will describe one process at a time. For each process, create a manual entry with:

1. PROCESS NAME AND PURPOSE:
What it is and why it exists. One sentence each.

2. TRIGGER:
What starts this process? (A client request, a scheduled date, an event, a metric hitting a threshold)

3. STEPS (numbered):
Each step should include:
- What to do (specific action, not vague instruction)
- Which tool to use
- Expected time to complete
- What "done" looks like for this step

4. DECISION POINTS:
Where in the process does someone need to make a judgment call? For each decision point, provide the criteria for each option.

5. COMMON ISSUES:
What goes wrong most often and how to fix it.

6. QUALITY CHECK:
How to verify the process was completed correctly before moving on.

7. HANDOFF:
If this process feeds into another process, describe the handoff: what information transfers, to whom, in what format.

Here is my first process:
[Describe the process in your own words, as detailed or rough as you want]

Format the output as a clean manual entry I can paste into a shared document. Use headers, numbered steps, and consistent formatting across all entries.

Building the Manual Incrementally

Do not try to document everything at once. Start with your most critical process. The one that would cause the most damage if done wrong. Document that first.

Then document one process per week. In three months, you have a comprehensive manual.

The Real Test

Hand the manual to someone who has never done the process. Can they follow it and produce the correct result? If they get stuck, the manual has a gap. Fill it.

Why AI Structures It Better

When you describe a process from memory, you skip steps that feel obvious. AI asks structured questions and catches the gaps. "Between step 3 and step 4, how does the data get from the CRM to the spreadsheet?" You forgot that step because you do it automatically. But the manual needs it.

Build These Systems

Ready to implement? These step-by-step tutorials show you exactly how:

• How to Create Automated Handoff Systems Between Teams - Automate work handoffs between teams with context preservation.
• How to Create Automated No-Show Follow-Up Sequences - Automatically follow up with no-shows and offer easy rescheduling.
• How to Automate Employee Onboarding Checklists - Create and track onboarding checklists that assign tasks automatically.