12 AI Prompts for Operations and Admin (SOPs, Reports, Checklists)

Admin is the tax every small business pays for existing. The SOPs nobody wrote, the report nobody enjoys compiling, the inbox that eats the first hour of every day.

It's also the best place to point AI, because most admin work follows patterns, and patterns are the one thing these tools handle reliably. Below are 12 AI prompts for operations and admin, grouped by the job they do, each with a note on what to feed it and what good output looks like.

Every prompt follows the same four-part shape we teach in how to brief AI like a contractor. Swap the [BRACKETS] for your specifics and they run on ChatGPT, Claude, Gemini, or Copilot as-is.

The AI prompts for operations, by job

Documentation prompts

1. Turn a voice memo into an SOP. Record yourself doing the task, transcribe, paste.

You are an operations manager who writes procedures a new hire can
follow without asking questions. Below is a rough transcript of me
explaining how I do a task. Turn it into a numbered SOP, one action
per step, under 400 words. Flag anything ambiguous or missing as an
open question at the end. [PASTE TRANSCRIPT]

Good output has short imperative steps and at least one open question. If it found nothing to question, you explained unusually well or it's flattering you. The SOP writer is the full version with formats per task type.

2. Update an SOP that's drifted.

Here is our written procedure, and here is how the task actually
gets done today, in my words. List every difference, tell me which
version seems safer or faster for each, then rewrite the SOP to
match what we decide. Procedure: [PASTE]. Reality: [DESCRIBE].

The comparison step is the point. Skipping straight to "rewrite it" loses the moment where you notice the checklist said two people should count the till.

3. Build an onboarding checklist from your own chaos.

I'm hiring a [ROLE]. Below is an unsorted list of everything I can
think of that they'll need: accounts, tools, intros, tasks,
things to read. Organize it into a day 1 / week 1 / month 1
checklist, each item one line with an owner (me, them, or other).
Ask me about anything obviously missing for a role like this.
[PASTE LIST]

4. Write the "if I'm hit by a bus" doc.

Interview me about how [CRITICAL PROCESS] works in my business.
Ask one question at a time, up to 15 questions, favouring the
questions whose answers only exist in my head. Then write it up
as a continuity document someone could follow cold.

Letting the AI interview you beats writing from scratch, because it asks about the parts you'd skip as obvious. They're only obvious to you.

Reporting prompts

5. Compile the weekly report from scraps.

Below are my raw inputs for this week: sales numbers, a few Slack
updates, my own notes. Compile a weekly report: five bullet
highlights, then Numbers / Risks / Next week, under one page.
Where two inputs disagree, flag it rather than averaging them.
[PASTE EVERYTHING]

"Flag it rather than averaging" earns its place. Models default to smoothing conflicts over, and the conflict is usually the most useful line in the report. The weekly report automator turns this into a repeatable template.

6. Make a number legible to the team.

Explain this metric to my team in three sentences: what moved,
the most likely why, and what we'll watch next week. No jargon.
Metric: [NAME, THIS PERIOD vs LAST]. Context: [ONE SENTENCE].

7. Turn meeting notes into owners and deadlines.

Extract every commitment from these meeting notes. For each:
action, owner, due date. Where the owner or date isn't stated,
say so instead of guessing. Separate decisions made from open
questions. Attendees: [NAMES]. [PASTE NOTES]

We wrote up the full workflow around this one, same-day sending and open questions on top, in turning meeting notes into action items.

Inbox prompts

8. Triage a full inbox.

Here are the subject lines and first lines of [N] emails. Sort
into: needs my reply today, can wait, delegate to [NAME], ignore.
One line of reasoning per "today" item only. [PASTE LIST]

Paste subjects and first lines, and leave the bodies out. The triage decision rarely needs them, and your inbox contains things an AI tool doesn't need to read. The inbox triage system covers the full setup including reply drafting.

9. Draft the reply you keep rewriting.

Draft a reply to the email below. We will say yes to [X] but not
[Y]. Keep it under 120 words, warm but unambiguous, and don't
apologize for the boundary. [PASTE EMAIL]

10. Write the recurring announcement once.

Write a reusable template for [RECURRING MESSAGE: holiday hours,
price update, schedule change] with placeholders I fill in each
time. Friendly, under 100 words, no exclamation marks.

Decision prompts

11. Compare vendor quotes on facts.

Below are [N] quotes for [PURCHASE]. Build a comparison: total
first-year cost, what's included, what's extra, contract terms,
and the questions I should ask each vendor before deciding. Note
where a quote is vague; vague is information. [PASTE QUOTES]

The vendor comparison matrix adds scoring weights if the decision is big enough to justify them.

12. Find what to automate next.

Interview me about a typical week in my business, one question at
a time, up to 10 questions. Then list the 5 tasks most worth
systematizing, ranked by hours saved times how much I dislike
them, with the simplest first step for each.

Run this quarterly. The answer changes as the business does, and the ops automation planner picks up where the list ends.

Where these break

Two honest limits, one general and one specific.

The general one: every prompt here produces a draft, and admin drafts look deceptively finished. A confident SOP with a wrong step is worse than no SOP, because someone will follow it. The filed version of anything (procedures, reports, replies that make commitments) carries a human sign-off.

The specific one: several of these ask you to paste internal material into an AI tool. Emails and meeting notes contain customer names, salaries, and things said in confidence. Strip what shouldn't leave the room first; our guide to protecting customer data when using AI covers where the lines are.

Where to start

Don't install all 12. Pick the one that names the task you did most recently while resenting it. For most owners that's the weekly report or the inbox. Run it three times this week until the prompt is tuned to your business.

The rest of the recurring admin jobs, and the order to hand them over in, are in our operations and admin playbook.