Turn everyday business tasks into clear, repeatable procedures with 10 detailed, editable ChatGPT prompts. Create SOP drafts for onboarding, customer support, content publishing, order fulfillment, invoicing, reporting, file management, and more. Each prompt includes customizable fields and specific instructions for steps, responsibilities, checks, and exceptions.

What this prompt pack does

• Turns process notes and business details into structured, step-by-step SOP drafts.
• Defines task owners, handoffs, quality checks, and responses to common exceptions.
• Helps review existing SOPs and identify missing information before team testing and approval.

Tips for this prompt pack

• Choose the prompt closest to your workflow and replace every bracketed field with specific details; use “not sure” when needed.
• Provide approved policies, real process notes, and exact tool names. Remove passwords and unnecessary personal or customer information.
• Have the process owner review the draft, then ask a team member to try it and record any unclear or missing steps.

How to use the prompts

• Copy one complete prompt into ChatGPT and fill in the editable fields.
• Submit it, answer any follow-up questions, and request revisions using your actual workflow.
• Copy the finished draft into your document editor, confirm unresolved details, test it, and obtain approval before team use.

 10 ChatGPT Prompts for Creating SOP Documents

SOP stands for standard operating procedure: written instructions for completing a task consistently.

Replace the [BRACKETED FIELDS] with your details, then paste one complete prompt into ChatGPT. If you don’t know an answer, write “not sure.”

1. Turn rough notes into a complete SOP

Act as an operations documentation specialist. Turn my process notes into a standard operating procedure (SOP) that a new team member can follow without guessing.

My details:

• Business and industry: [BUSINESS / INDUSTRY]
• Process to document: [PROCESS NAME]
• Who will use this SOP: [ROLE / EXPERIENCE LEVEL]
• Starting trigger and finished result: [START] → [FINISH]
• Tools and responsible people: [TOOLS / ROLES]
• Rules that must be followed: [APPROVED POLICIES / LIMITS]
• Existing notes: [PASTE NOTES, A TRANSCRIPT, OR BULLET POINTS]

Ask up to five essential questions in one message if missing information would change the procedure. After my answers, draft the SOP. If no questions are needed, draft it now. Mark unresolved details [TO CONFIRM]; do not invent policies, deadlines, permissions, or software menu labels.

Include:

1. Document details: title, SOP ID, version, draft status, owner, approver, and review date. Leave unknown fields editable.
2. Purpose, scope, starting trigger, and definition of completion.
3. Required access, materials, and checks before starting.
4. A numbered procedure table: step, responsible role, action, tool/input, and expected result.
5. If/then instructions for the likely exceptions supported by my notes, including when to stop and who to contact.
6. A final quality checklist and a list of unresolved decisions.

Use plain English and one action per step. Replace vague instructions such as “check everything” with specific checks. Label any suggested improvement separately from the documented process.

2. Create a client onboarding SOP

Create a client onboarding SOP for my [BUSINESS TYPE] business. The procedure should take a client from [STARTING EVENT, SUCH AS ACCEPTING A PROPOSAL] to [ONBOARDING COMPLETE, SUCH AS AN APPROVED KICKOFF BRIEF].

My details:

• Service being purchased: [SERVICE]
• Team roles and onboarding owner: [ROLES / OWNER]
• Agreement and payment requirements: [EXISTING REQUIREMENTS]
• Information or files the client must provide: [INTAKE REQUIREMENTS]
• Tools for forms, project management, meetings, and file sharing: [TOOLS]
• Target timeline and communication channel: [TIMELINE / CHANNEL]
• Person approving the start of delivery: [APPROVER]

Ask up to five essential questions before drafting if a missing detail affects the workflow. After my answers, create the SOP; otherwise draft now. Keep unknowns as [TO CONFIRM]. Use only the contract and payment terms I provide.

Cover checking the agreed scope, confirming required approvals and payments, sending the welcome message, collecting intake information, arranging approved access, creating the project workspace, scheduling kickoff, and handing the project to the delivery team.

Provide:

1. A document header with owner, approver, editable version/review fields, and “Draft for review” status.
2. A stage table showing the trigger, responsible role, action, deadline, and evidence of completion.
3. Clear handling for missing intake information, delayed payment, unavailable access, and a changed start date.
4. Two editable messages: a client welcome and a reminder for missing information.
5. An onboarding completion checklist and the conditions that must be met before delivery begins.

Explain how to request access through approved invitations or sharing features without asking clients to send passwords.

3. Create a new employee onboarding SOP

Act as a practical people operations manager. Write an employee onboarding SOP for someone joining as [JOB TITLE] at [BUSINESS].

Use these details:

• Start date and work arrangement: [DATE / REMOTE, HYBRID, OR ONSITE]
• Manager, onboarding coordinator, and IT contact: [ROLES / NAMES]
• Equipment and approved access needed: [EQUIPMENT / SYSTEMS / PERMISSION LEVELS]
• Documents and policies to provide: [APPROVED DOCUMENT LIST]
• Required training: [TRAINING TOPICS]
• First-week responsibilities: [TASKS]
• Expected 30-day outcomes: [OUTCOMES]
• Check-in schedule: [SCHEDULE]

If essential details are missing, ask up to five questions together and draft after I answer. Otherwise draft now. Mark remaining gaps [TO CONFIRM]. Do not create employment policies or legal requirements.

Organize the SOP into before the start date, first day, first week, and first 30 days.

For every task, show the owner, timing, action, completion evidence, and who receives the handoff. Include equipment preparation, approved account creation, introductions, policy acknowledgments, job training, supervised practice, and manager check-ins. Have the new employee test their own access; never include passwords in the document.

Add an exception table for delayed equipment, unavailable accounts, a missing manager, and incomplete training. Identify who resolves each issue and which tasks must wait.

Finish with separate manager and employee checklists, a training sign-off table, and document controls: owner, approver, editable version/review fields, and draft status. Define onboarding completion using my supplied outcomes.

4. Create a customer support SOP

Write a customer support SOP for handling [TICKET TYPES, SUCH AS DELIVERY QUESTIONS, LOGIN ISSUES, OR BILLING QUESTIONS] at [BUSINESS].

My support setup:

• Channels and support hours: [CHANNELS / HOURS / TIME ZONE]
• Help desk and reference materials: [TOOLS / APPROVED KNOWLEDGE SOURCES]
• Existing response and resolution targets: [TARGETS, OR “NOT YET SET”]
• Common customer issues: [ISSUES]
• Support agent permissions: [WHAT AGENTS MAY APPROVE OR CHANGE]
• Escalation contacts: [ISSUE TYPE → RESPONSIBLE ROLE]
• Refund, replacement, or account-change policies: [PASTE APPROVED RULES]

Ask up to five essential questions if needed, then draft after my answers. Otherwise draft now. Flag missing rules [TO CONFIRM]. If targets are not set, list them as decisions for the owner; do not invent customer commitments.

Document the complete ticket lifecycle: record the request, categorize it, set priority, check relevant records, investigate, respond, escalate when required, follow up, confirm resolution, and close the ticket.

Include:

1. Draft document controls, scope, owner, and review fields.
2. A numbered workflow with the responsible role and what must be recorded at each step.
3. A decision table for routine issues, repeat contacts, disputed charges, and issues outside the agent’s authority.
4. Two editable replies: an initial acknowledgment and a resolution follow-up.
5. A closure checklist covering the solution, customer notification, final status, and internal notes.

Use only the identity checks and customer information required by our approved process. Explain when an agent should pause a change and escalate it.

5. Create a social media content publishing SOP

Create a social media production and publishing SOP for [BRAND / CREATOR NAME]. A team member should be able to move a post from an approved idea to publication and follow-up.

My setup:

• Audience and content goals: [AUDIENCE / GOALS]
• Platforms and formats: [PLATFORMS / REELS, CAROUSELS, POSTS, ETC.]
• Posting schedule and time zone: [SCHEDULE / TIME ZONE]
• Brand voice and content rules: [GUIDELINES]
• Creation, storage, and scheduling tools: [TOOLS]
• Writer, designer/editor, reviewer, publisher, and backup: [ROLES]
• Approval method and deadline: [METHOD / DEADLINE]
• Comment response and escalation rules: [RULES]
• Metrics and reporting window: [METRICS / WINDOW]

Ask up to five essential questions if needed and draft after I answer. Otherwise draft now. Mark gaps [TO CONFIRM]. Do not assume software features or platform menu names.

Build the workflow around briefing, drafting, checking factual claims and asset permissions, creating visuals, reviewing, approving, scheduling, publishing, checking the live post, monitoring responses, and recording results.

Provide an SOP header with draft status and editable owner/version/review fields; a numbered procedure table with owners, required inputs, and completion evidence; and a pre-publication checklist for captions, links, tags, accessibility, asset specifications, and approval.

Add if/then instructions for missed approval, incorrect links, an error discovered after publishing, and comments that need escalation. State who may approve corrections or removal.

Finish with a content tracking template containing the post ID, platform, asset link, approver, scheduled time, live URL, and agreed metrics.

6. Create an e-commerce order fulfillment SOP

Write an order fulfillment SOP for my [STORE TYPE] business, from [STARTING EVENT] to [ENDPOINT, SUCH AS CONFIRMED CARRIER HANDOFF].

My details:

• Store platform and order tools: [PLATFORM / TOOLS]
• Products and special packing requirements: [PRODUCTS / REQUIREMENTS]
• Payment verification method: [APPROVED METHOD]
• Inventory source and stock rules: [SOURCE / RULES]
• Processing schedule and cutoff time: [SCHEDULE / TIME ZONE]
• Approved shipping services and delivery promises: [SERVICES / EXISTING PROMISES]
• Staff roles and approval limits: [ROLES / LIMITS]
• Cancellation, address-change, and refund policies: [APPROVED POLICIES]

Ask up to five essential questions if important details are missing; draft after I answer. Otherwise draft now. Use [TO CONFIRM] for gaps. Do not invent shipping promises, payment rules, or platform automation.

Cover verifying the order and payment status, checking stock, picking the correct item and variant, inspecting condition, packing, verifying the shipping address, creating the shipment, handing it to the carrier, updating records, and notifying the customer.

Include:

1. Draft document controls and a clear definition of the endpoint.
2. A step table showing the owner, action, required check, and evidence.
3. A status/handoff table using my platform’s confirmed labels; leave unknown labels as placeholders.
4. Exception instructions for unpaid orders, stock shortages, incomplete addresses, damaged items, and cancellation requests.
5. A pack-and-ship checklist and an order record template with order ID, items, checks, carrier, tracking reference, and handoff evidence.

Distinguish shipment handoff from confirmed delivery. Show when fulfillment must pause for approval.

7. Create an invoicing and payment follow-up SOP

Create an invoicing and payment follow-up SOP for my [BUSINESS TYPE] business. The process starts when [BILLING TRIGGER] and ends when [PAYMENT IS MATCHED AND THE RECORD IS CLOSED].

My details:

• Billing arrangement: [PROJECT / HOURLY / SUBSCRIPTION / OTHER]
• Approved pricing and billing records: [SOURCE OF PRICES / TIME / DELIVERABLES]
• Invoice and accounting tools: [TOOLS]
• Required invoice fields and numbering rule: [FIELDS / RULE]
• Currency and supplied tax treatment: [CURRENCY / APPROVED TAX DETAILS]
• Payment terms and accepted methods: [AGREED TERMS / METHODS]
• Preparation, approval, and follow-up owners: [ROLES]
• Reminder schedule and escalation rules: [APPROVED SCHEDULE / RULES]

Ask up to five essential questions if needed, then draft after I answer. Otherwise draft now. Mark missing rules [TO CONFIRM]. Do not decide tax rates, invent late fees, or change agreed payment terms.

Document how to verify billable work and customer details, check for duplicate invoices, prepare line items, verify totals against approved records, obtain approval, send the invoice, record delivery, track the due date, send permitted reminders, match payment, and close the record.

Provide a draft SOP header; a numbered table with owners, checks, and completion evidence; an exception table for disputed invoices, incorrect details, partial payments, and overdue payments; and two editable reminder messages based on my approved schedule.

Finish with a pre-send accuracy checklist and a payment-matching checklist. Identify changes that require approval, including credits, write-offs, and amended invoices.

8. Create a weekly reporting SOP

Write a weekly reporting SOP for [TEAM / BUSINESS] so a team member can produce a consistent [REPORT NAME] without guessing how metrics are calculated.

My details:

• Audience and decisions the report supports: [AUDIENCE / DECISIONS]
• Reporting period and time zone: [PERIOD / TIME ZONE]
• Metrics and approved definitions: [METRICS / DEFINITIONS]
• Data sources and access owners: [SOURCES / OWNERS]
• Existing calculation rules: [FORMULAS / FILTERS / EXCLUSIONS]
• Comparison period and alert thresholds: [COMPARISON / APPROVED THRESHOLDS]
• Report template and reporting tool: [TEMPLATE / TOOL]
• Preparer, reviewer, deadline, and distribution channel: [ROLES / DEADLINE / CHANNEL]

Ask up to five essential questions if needed and draft after I answer. Otherwise draft now. Flag missing definitions [TO CONFIRM]. Never fabricate numbers, thresholds, or explanations for changes.

Document collecting source data, checking freshness and date filters, removing duplicates according to supplied rules, calculating metrics, comparing periods, documenting exceptions, reviewing the report, distributing the approved version, and archiving it.

Include a draft document header; a metric dictionary showing each definition, source, formula, and owner; and a numbered procedure table with checks and completion evidence.

Explain how to handle a missing source, late data, mismatched totals, a changed metric definition, and a zero denominator. Keep “no data” separate from zero. Label explanations as confirmed facts or hypotheses.

Finish with a reviewer checklist and a reusable report outline using [VALUE] placeholders wherever data has not been provided.

9. Create a file organization, access, and backup SOP

Create a file management SOP for [BUSINESS / TEAM]. The goal is to make current files easy to find, control access, and document how approved backups are checked.

My details:

• File types and storage tools: [FILE TYPES / TOOLS]
• Current folder structure: [PASTE STRUCTURE]
• Naming and version rules: [EXISTING RULES, OR “PLEASE PROPOSE”]
• File owners and access approvers: [ROLES]
• Internal and external sharing rules: [APPROVED RULES]
• Retention and archive policy: [APPROVED POLICY]
• Backup method, frequency, and responsible person: [METHOD / FREQUENCY / OWNER]
• Restore-test schedule and approved test location: [SCHEDULE / LOCATION]

Ask up to five essential questions if needed and draft after I answer. Otherwise draft now. Keep unknown policies [TO CONFIRM]. If proposing a naming or folder convention, label it “Proposed for approval.”

Include:

1. Draft document controls and the authoritative location for current files.
2. A folder map and naming examples using clearly fictional filenames.
3. Steps for creating, naming, reviewing, sharing, revising, archiving, and retrieving files.
4. An access request and removal workflow with owners and approval evidence.
5. Backup checks, failure escalation, and a non-destructive restore test using a copy in the approved test location.
6. Instructions for duplicate versions, incorrect permissions, accidental overwrites, storage limits, and failed backups.

Do not assume that syncing alone provides a recoverable backup. Mark unverified recovery capabilities [TO VERIFY]. Do not authorize deletion without a supplied policy and approval. Finish with a recurring review checklist and evidence log.

10. Audit and rewrite an outdated SOP

Act as an SOP editor and process reviewer. Review my existing procedure and produce a clearer draft based on the current workflow.

My inputs:

• Existing SOP: [PASTE DOCUMENT]
• Current workflow and approved policies: [PASTE NOTES / RULES]
• Known changes to tools, roles, or requirements: [CHANGES]
• Common mistakes and complaints: [EXAMPLES]
• Intended users and experience level: [USERS]
• Process owner and approver: [ROLES]
• Target review date: [DATE]

Ask up to five essential questions where missing or conflicting information affects the procedure. After I answer, complete the review; otherwise begin now. Do not silently choose between conflicting sources. List unresolved issues and mark affected steps [TO CONFIRM].

Deliver:

1. An audit table: original section, specific problem, operational impact, and proposed correction.
2. A revised SOP marked “Draft for review,” with editable document controls, purpose, scope, prerequisites, numbered steps with owners and expected results, exception handling, and a completion checklist.
3. A change log showing what changed and why, linked to the supplied information. Label any new process suggestions separately.
4. A written walkthrough of three scenarios: normal completion, a missing required input, and a likely exception. Show which steps handle each scenario and where ambiguity remains.
5. A practical test checklist for an actual team member, including what evidence to capture and who approves the result.

Explain that the written walkthrough checks the document’s logic; actual operation still needs a user trial. Finish with the steps for approval, version update, communicating changes, and archiving the superseded SOP after approval.