← backOps & AutomationFounding · Free forever

Turn messy notes into an SOP

Force a 'checks' section — SOPs without validation steps fail silently.

by @whitney · recommended tool Claude · 0 unlocks

You'll need

CLAUDE SKILLS

docx

CONNECTORS

Google Drive

EXAMPLES · WHAT THIS PROMPT PRODUCES

Sample output

**SOP: Onboarding a New Client to the Project Management Workspace**

**Purpose**
Get a new client fully set up in Asana within one business day of contract signature, so the kickoff call can happen on a live workspace.

**Inputs / tools**
Signed contract, client contact list (name + email + role), Asana admin access, the "Client Template" project, welcome-email template in HubSpot.

**Steps**
1. In Asana, duplicate the "Client Template" project. Rename it `[Client Name] — Engagement`.
2. Open the project's Members panel. Invite each client contact by email; set role to Commenter (not Editor).
3. In the template's first task, replace the placeholder client name in the project brief.
4. Set the project due date to the contract end date.
5. Assign the internal PM as project owner in the project settings.
6. In HubSpot, send the welcome email using the "Client Onboarding" template; attach the workspace link.
7. Post the kickoff date in the project's Messages tab.

**Checks (how do I know it's done right)**
- Every client contact shows "Invited" or "Active" in Members.
- The welcome email shows "Sent" in HubSpot.
- The project brief shows the real client name, no placeholders.

**Troubleshooting**
- Invite bounces → confirm email spelling, resend.
- Client can edit tasks → recheck role is Commenter, not Editor.

**Owner:** Account Coordinator.

PRICE HISTORY0 cr · current

PROMPT TEMPLATE · v1.0.0

Turn these messy notes into a clean SOP.
Structure: purpose → inputs/tools → step-by-step (numbered, one action per step) → checks (how do I know it's done right) → troubleshooting → owner.
Write so a new hire can follow it unsupervised.