← IndexEntry № 209·productivity

Draft a Step-by-Step SOP from a Rough Process

Converts an informal process description into a structured, new-hire-ready SOP.

Optimized for

§ When to use this

The knowledge of how to do things lives in people's heads, which is great until that person is on vacation, leaves, or simply gets tired of being the only one who knows. This prompt turns your informal, in-your-head process into a real standard operating procedure that someone else can actually follow. You describe how you do something in plain, rambling terms, and it returns a structured doc: purpose, owner, trigger, prerequisites, and numbered imperative steps. The detail that makes SOPs usable rather than ornamental is that each step names the tool and the expected result, so the reader can confirm they did it right before moving on. It also adds a troubleshooting section for the two most common failure points, because every process has spots where people predictably get stuck, and a 'definition of done' checklist so there's no ambiguity about completion. Tune the audience level so the steps match who's reading. Use it to onboard new hires, hand off recurring work, or finally document the thing only you know how to do.

§ The Prompt— fill in the fields, then copy or open in a tool

§ Customize0/3 fields filled

Process[PROCESS]The task you want documented, e.g. 'onboarding a new client into our project tool'.

Process description[PROCESS DESCRIPTION]Your informal explanation of how you do it, e.g. 'I make a workspace, invite them, copy the kickoff template, set their billing in Stripe, then send a welcome email'.

Audience level[AUDIENCE LEVEL]Who will follow the SOP and their familiarity, e.g. 'a brand-new hire who has never used our tools'.

your prompt — fill the fields above

You are a process documentation specialist. Turn my rough description of how I do [PROCESS] into a clean standard operating procedure. Output: a one-line purpose, who owns it, when it's triggered, prerequisites or access needed, then numbered steps in plain imperative language. For each step note the tool used and the expected result so a reader knows it worked. Add a short troubleshooting section for the two most common failure points, and a 'definition of done' checklist. Write it so a new hire could follow it without asking questions. My rough description: [PROCESS DESCRIPTION]. Audience skill level: [AUDIENCE LEVEL].

Open with your prompt →ChatGPT ↗Claude ↗Sends your filled-in prompt straight into a new chat.

§ Example Output

What you can expect back

Purpose: Get a new client fully set up so work can start on day one.
Owner: Account Manager. Triggered when: a signed contract lands.
Prerequisites: Asana admin access, Stripe access, shared inbox login, client's email and plan tier.
Steps:
1. In Asana, create a new project named '[Client] - [Year]'. Result: project appears in the Clients portfolio.
2. Invite the client via email in Asana. Result: they show as a pending member.
3. Copy the 'Kickoff Template' project into the new one. Result: all kickoff tasks populate.
4. In Stripe, create a customer and attach their plan. Result: subscription shows 'active'.
5. Send the welcome email from the shared inbox using the saved template. Result: appears in Sent.
Troubleshooting: Client didn't get the invite - check spam and resend; Stripe plan won't attach - confirm a payment method exists first.
Done when: project live, client invited, billing active, welcome email sent.

Illustrative example — your results will vary by tool and inputs.

§ Pro Tips

Get sharper results

01Talk it through as if explaining to a friend; the messier and more complete your description, the better the SOP. Don't pre-structure it.
02Match the audience level honestly; an SOP written for an expert will leave a new hire stuck on the steps you think are obvious.
03Have the actual new person run the SOP once and flag every spot they hesitated; feed those back in to tighten it.
04Ask it to add a 'time estimate' and 'frequency' line so readers know how long it takes and how often it's done.

§ Variations

Adapt it for your case

Checklist-only

Add 'output as a single repeatable checklist with no prose' for a process people run often and just need to tick through.

With screenshots placeholder

Add 'mark where a screenshot should go with [SCREENSHOT: description]' to prep a visual SOP for a wiki.

Escalation-aware

Add 'include who to escalate to and when' for processes where steps can fail in ways the reader can't fix alone.

Best For — Roles

Use For — Tasks

Writing Status Updates

Tags#sop#documentation#process

§ FAQ

Common questions

My process changes often. Is an SOP worth it?

Yes, but keep it lean and date it. Ask for the shortest version that still works, and rerun when the process shifts. A slightly outdated SOP still beats undocumented tribal knowledge.

How do I know if it's detailed enough?

The test is whether someone unfamiliar can complete it without asking you a question. If your real new hire gets stuck anywhere, that step needs more detail or a screenshot.

Can it document a process I do partly by intuition?

Describe what you'd check or how you'd decide at the judgment points, and ask it to write those as 'decision rules.' It turns instinct into something teachable.

§ Related Entries