Turn everyday business tasks into clear, repeatable instructions with 10 detailed, editable AI prompts. Create draft procedures for customer onboarding, order handling, staff training, inventory, invoicing, and more. Each prompt includes fill-in fields and specific instructions to help you document how your business works.

What this prompt pack does:

• Turns rough notes and business rules into structured procedures, checklists, and handover documents.
• Helps document 10 practical workflows, including customer service, daily operations, and staff training.
• Creates supporting materials such as message templates, trackers, approval records, and training exercises.

Tips for this prompt pack:

• Add real process details, including who does each task, which tools they use, and what counts as complete.
• Start with one workflow and check the draft against how your team actually performs the work.
• Use fictional examples or remove private information before sharing business records with an AI tool.

How to use the prompts:

• Choose a prompt and replace the bracketed fields with your business information.
• Paste the completed prompt into your preferred AI chat tool and answer any follow-up questions.
• Review the draft, test it with a realistic example, and approve the final instructions before sharing them with staff.

 10 AI Prompts for Small Business Process Manuals & SOPs

Replace the [bracketed text] with your business details. If something does not apply, write “Not applicable.” Each prompt works independently.

1. Turn rough notes into a step-by-step procedure

Act as a process documentation specialist for a small business. Turn my rough notes about one recurring task into a standard operating procedure (SOP): clear instructions that another person can follow without relying on the owner’s memory.

My business details:

• Business type: [e.g., bakery, cleaning company, online store]
• Process to document: [e.g., preparing a custom cake order]
• Person who normally handles it: [role]
• Person who may need to learn it: [role and experience level]
• Tools, forms, or equipment used: [list]
• What starts the process: [trigger]
• What a successful result looks like: [specific outcome]
• Current notes: [paste notes, bullet points, or a written explanation]
• Common mistakes: [list]
• Business rules that must be followed: [list]

First, check whether my notes explain who does the work, the correct sequence, and when the task is complete. If essential details are missing or contradictory, ask up to five focused questions before drafting.

Create:

1. A short overview explaining the purpose, owner, and when this procedure applies.
2. A preparation checklist covering everything needed before starting.
3. A procedure table with: step number, responsible role, exact action, tool used, and expected result.
4. Instructions for the three most likely problems, based on my notes.
5. A completion checklist that someone can use to check their work.
6. A short training exercise using a realistic example.
7. A document control box with owner, version, approval status, and review date.

Use simple language and one clear action per step. Replace vague instructions such as “check everything” with specific checks. Do not invent business rules; label unresolved details [OWNER TO CONFIRM]. Mark the document “Draft for owner review.”

2. Create daily opening and closing checklists

Write an opening and closing procedure for my small business so employees know how to prepare for the day and leave the business ready for the next shift.

My business details:

• Business type and location: [details]
• Opening and closing hours: [hours]
• Staff on each shift: [roles and number of people]
• Opening lead and closing lead: [roles]
• Areas to prepare or secure: [list]
• Equipment that needs attention: [list]
• Booking, order, or payment systems used: [list]
• Opening tasks we already perform: [list]
• Closing tasks we already perform: [list]
• Approved cash-handling rules, if applicable: [paste rules]
• Approved security and equipment shutdown instructions: [paste instructions]
• Problems that must be reported to the owner: [list]
• Available preparation and closing time: [minutes]

Ask up to five questions if missing information would affect safety, security, or task ownership. Do not invent alarm instructions, equipment settings, or cash-handling rules.

Create separate opening and closing checklists. For each task, include:

• The action.
• The responsible role.
• When it should happen relative to opening or closing.
• The visible evidence that it is complete.
• Who to contact if it cannot be completed.

Order tasks by their dependencies. For example, place system startup before checking new orders.

Also include a shift handover template, an exception log, and a final sign-off section. Explain what staff should record when a task is skipped or blocked.

Make the checklists easy to print and tick off. Use realistic timing estimates, clearly labeled as estimates, and flag if the listed work appears to exceed the available time.

3. Build a customer or client onboarding manual

Create a customer onboarding manual for my small business. Document what happens from the moment a customer agrees to buy until they are ready to receive our service.

My business details:

• Business and service offered: [details]
• Typical customer: [description]
• Event that starts onboarding: [e.g., accepted quote or confirmed booking]
• Person responsible for onboarding: [role]
• Information we need from the customer: [list]
• Documents or approvals required: [list]
• Deposit or payment requirements: [confirmed policy]
• Tools used for forms, scheduling, and communication: [list]
• Normal onboarding timeframe: [timeframe]
• What customers commonly misunderstand: [list]
• What marks onboarding as complete: [criteria]
• Escalation contact: [role]

If essential details are missing, ask up to five questions before writing. Use only the requirements and policies I provide.

Create:

1. A workflow showing each stage from confirmation to service handover.
2. A procedure table covering the responsible role, action, information to record, deadline, and completion check.
3. A customer information checklist explaining why each item is needed.
4. Three editable messages: welcome, missing-information reminder, and onboarding-complete confirmation.
5. Instructions for missing documents, unpaid deposits, delayed replies, and requests outside the agreed scope.
6. A handover checklist for the person delivering the service.
7. A sample completed onboarding record using fictional details.

For every exception, explain whether staff should proceed, pause, or ask for approval, using my stated policies. Mark any missing decision [OWNER TO CONFIRM].

Write for a new employee who has never handled onboarding before. Keep customer messages friendly and specific.

4. Document the order-to-delivery process

Create an order-handling manual that helps my team deliver the correct product or service, on time, with a clear record of what happened.

My business details:

• Business type: [details]
• Product or service being ordered: [description]
• Where orders arrive: [website, email, phone, marketplace, or other]
• Information every order must contain: [list]
• Payment or approval required before work starts: [confirmed rules]
• Roles involved: [list]
• Tools used to track orders: [list]
• Preparation or production steps: [describe]
• Delivery, collection, or service completion method: [details]
• Quality checks: [list]
• Promised turnaround time: [timeframe]
• Rules for changes, cancellations, and unavailable items: [paste policies]

Ask up to five questions if the handoffs, approval rules, or completion criteria are unclear.

Build the manual around these stages: receive, validate, approve, prepare, check, deliver, and close. Adapt the stages to fit my business.

For each stage, provide:

• The responsible role and exact steps.
• The order information that must be checked or updated.
• The condition that allows the order to move forward.
• The next person or team receiving the work.
• What to do when the stage is blocked.

Include a simple order status system with a definition for each status. Add a pre-delivery checklist, a completion checklist, and editable customer messages for confirmation, delay, and delivery or completion.

Cover duplicate orders, incomplete details, failed payment, unavailable stock or capacity, and last-minute changes. Apply only my supplied policies.

Finish with one fictional order moving through the entire process, showing the records and handoffs at each stage.

5. Write a customer service and complaint-handling manual

Create a practical customer service manual for my small business. Help staff respond consistently while staying within the authority and policies I give them.

My business details:

• Business type: [details]
• Support channels: [email, phone, social media, chat, or other]
• Support hours: [hours and time zone]
• Target first-response time: [target]
• Most common questions or complaints: [list five to ten]
• Refund, return, cancellation, or rework policy: [paste approved policy]
• What frontline staff can approve: [limits]
• What requires manager approval: [rules]
• Customer information staff may request: [list]
• Where support cases are recorded: [tool]
• Escalation contacts: [roles]

If the policies conflict or approval limits are missing, ask up to five questions before drafting. Do not create refund rights, compensation amounts, or promises.

Create:

1. A step-by-step procedure for receiving, recording, investigating, resolving, and closing a case.
2. A priority table based on the issue types I provide, with response targets and owners.
3. A decision table explaining when staff can resolve an issue and when they must escalate it.
4. Editable replies for a general question, delayed order, dissatisfied customer, refund request, and issue awaiting investigation.
5. A case-record template with issue summary, checks performed, decision, owner, next action, and follow-up date.
6. A checklist for confirming that the promised action was completed before closing the case.

Show staff how to acknowledge a customer’s concern without promising an outcome before checking the facts. Include a handover procedure for unresolved cases and a short fictional example of a complaint handled from start to finish.

6. Create a purchasing, stock receiving, and reordering manual

Write an inventory and purchasing manual for my small business. The manual should help staff know when to reorder, how to receive deliveries, and how to keep stock records accurate.

My business details:

• Business and products stocked: [details]
• Storage locations: [list]
• Inventory tracking tool: [tool or spreadsheet]
• Person responsible for checking stock: [role]
• Stock-check frequency: [schedule]
• Reorder point or minimum level for each item: [list or paste table]
• Rule for deciding order quantities: [approved rule]
• Supplier lead times and minimum order quantities: [details]
• Purchasing approval limits: [rules]
• Receiving and inspection requirements: [list]
• Rules for damaged, expired, missing, or incorrect items: [policies]
• Supplier contact and issue-recording process: [details]

Ask up to five questions if the reorder rules, approval limits, or receiving requirements are incomplete. Do not invent stock thresholds or supplier terms.

Create three connected procedures:

1. Check stock and prepare a purchase request.
2. Obtain approval and place the order.
3. Receive, inspect, record, and store the delivery.

For each procedure, specify the trigger, responsible role, actions, records, and completion checks.

Include:

• A reorder worksheet.
• A purchase approval record.
• A delivery inspection checklist.
• A stock discrepancy log.
• An editable supplier message for a missing or damaged item.
• Instructions for escalating urgent shortages.

Show one worked reorder example using my supplied rule. If I have not supplied a rule, mark the calculation [OWNER TO CONFIRM].

Explain how staff should handle a difference between physical stock and the recorded quantity, including who approves an adjustment.

7. Build an invoicing and payment follow-up manual

Create an administrative manual for issuing invoices, recording payments, and following up on overdue balances in my small business.

My business details:

• Business type: [details]
• Invoicing tool: [tool]
• Event that triggers an invoice: [e.g., completed job or approved milestone]
• Person who prepares invoices: [role]
• Person who checks or approves them: [role]
• Required invoice information: [list from our existing requirements]
• Payment terms and accepted payment methods: [confirmed details]
• Approved reminder schedule: [schedule]
• Rules for disputes, partial payments, and payment plans: [policies]
• Rules for credits, refunds, and write-offs: [policies and approval limits]
• Where payment records are maintained: [tool]
• Escalation contact: [role]

Ask up to five questions if the payment terms, reminder schedule, or approval responsibilities are unclear. Do not invent tax treatment, bank details, late fees, or collection policies.

Create:

1. A checklist for verifying invoice details before sending.
2. A procedure for preparing, approving, sending, and recording an invoice.
3. Instructions for matching a received payment to the correct invoice and flagging unmatched payments.
4. A follow-up workflow using my approved schedule.
5. Editable messages for sending an invoice, a friendly reminder, an overdue reminder, and acknowledging a disputed amount.
6. An outstanding-invoice tracker with owner, amount, due date, status, last contact, and next action.
7. An exception table for incorrect invoices, partial payments, disputes, and missing payment references.

Separate routine tasks from decisions requiring approval. Finish with a weekly review checklist so unresolved balances have a clear owner and next step.

8. Create a new employee onboarding and training manual

Create a role-specific onboarding and training manual for a new employee joining my small business. Focus on the work they need to learn and how we will confirm they can do it.

My business details:

• Business type: [details]
• New employee’s role: [role]
• Expected starting experience: [description]
• Manager and trainer: [roles]
• Working schedule: [details]
• Main responsibilities: [list]
• Tools and equipment used: [list]
• Existing procedures they must learn: [paste or summarize]
• Access and equipment approval process: [details]
• Customer service and quality expectations: [standards]
• Tasks requiring supervision: [list]
• Training time available: [hours or days]
• Approved workplace policies to include: [paste policies]

Ask up to five questions if the role, training priorities, or supervision requirements are unclear. Do not invent employment terms or workplace policies.

Create:

1. A pre-arrival checklist with an owner for each item.
2. A first-day schedule.
3. A training plan for the first [number] weeks, fitted to the available training time.
4. A skills checklist showing what the employee must observe, practice, and demonstrate.
5. Three realistic practice tasks based on this role.
6. An assessment sheet with observable pass criteria and a place to record additional training.
7. A manager check-in template for discussing progress and questions.

For each training activity, identify the trainer, materials needed, expected outcome, and evidence of completion.

Distinguish completing training from being approved to work independently. Use approval criteria I provide; mark missing criteria [MANAGER TO CONFIRM]. Refer to approved access procedures without requesting or recording passwords.

9. Write a staff absence and task handover manual

Create a handover and absence-cover manual so essential work continues when someone is away, changes roles, or leaves a task unfinished at the end of a shift.

My business details:

• Business type: [details]
• Role being covered: [role]
• Planned absence or handover situation: [details]
• Dates or shifts affected: [details]
• Tasks that must continue: [list]
• Tasks that can wait: [list]
• Deadlines and customer commitments: [details]
• Backup staff and their skills: [list]
• Tools and records needed: [list]
• Existing access approval process: [details]
• Decisions backup staff can make: [limits]
• Escalation contact and availability: [details]

Ask up to five questions if essential work has no owner, the backup lacks required skills, or decision limits are unclear. Do not assume a backup has access or authority.

Create:

1. A handover checklist for the outgoing employee.
2. A coverage table with task, frequency, deadline, primary backup, second backup, and required information.
3. A handover record for each active order, project, or customer issue.
4. A first-day checklist for the person providing cover.
5. A procedure for unexpected absence when no handover was prepared.
6. A return-to-work summary template covering completed work, open issues, and decisions made.

For every active item, record its current status, next action, due date, owner, and location of supporting records.

Flag uncovered responsibilities and conflicting deadlines. If backup capacity is insufficient, identify the decisions the owner needs to make rather than silently assigning extra work.

Include a fictional completed handover example. Refer to approved access arrangements without including passwords or other credentials.

10. Review, test, and maintain an existing process manual

Act as an editor and process reviewer for my small business. Review our existing process manual and help us make it accurate, usable, and easier to maintain.

My business details:

• Business type: [details]
• Intended users and experience level: [description]
• Existing manual or selected procedure: [paste text]
• Current tools and team roles: [list]
• Changes since the manual was written: [describe]
• Recent mistakes, delays, or staff questions: [list]
• Current document owner: [role]
• Person authorized to approve changes: [role]
• Where the approved manual is stored: [location]
• Preferred review frequency: [schedule]

Use only the material I provide. If you cannot verify a statement, mark it [REQUIRES VERIFICATION]. Ask up to five questions if missing information prevents a reliable review.

Produce:

1. An issue table showing the original wording, the problem, its practical consequence, and a suggested correction.
2. A priority list identifying which problems should be resolved first and why.
3. A revised draft that preserves confirmed business rules.
4. A separate list of proposed policy changes requiring owner approval.
5. A practical walkthrough test that a staff member can run using a fictional case.
6. A test record for noting where the tester became confused, needed help, or could not complete a step.
7. A maintenance procedure covering ownership, review dates, change requests, approval, staff notification, and archiving older versions.
8. An editable change log.

Check specifically for missing owners, unclear triggers, broken handoffs, unexplained terminology, conflicting instructions, and missing completion checks.

Do not describe the manual as tested or approved. Clearly distinguish your suggested edits from changes that still require a business decision.