Standard Operating Procedure Template

Document a repeatable process with clear steps, owners, and completion checks. Preview the four-page client onboarding SOP example, copy it into your workspace, or generate a procedure from your own process notes.

Customize your document

Client Onboarding SOP — From Signed Agreement to Project Kickoff — page 1: Purpose, scope, process ownership, and kickoff target — Purpose, scope, process ownership, and kickoff target
1 / 4

A fictional four-page procedure for a marketing agency, with six steps from confirming an engagement to running kickoff. The preview includes owners, timing, completion evidence, exceptions, and a final checklist. Its seven-business-day kickoff target depends on required inputs and participants being available. The example is marked as a draft with approval pending.

Make it your own

Generate a document from your brief, or copy the example into your workspace.

Your prompt

Create a standard operating procedure for [[process name]] at [[organization]]. Write it for [[team or role that will follow the procedure]].

Purpose and scope: [[why the process exists, what it covers, and what is excluded]].
Start and finish: [[event that triggers the process and what must be true when it is complete]].
Roles: [[process owner, step owners, approver, and escalation contact]].
Required inputs: [[information, materials, access, systems, and existing documents]].
Process notes: [[current sequence of actions, handoffs, timing, and decision points]].
Exceptions and checks: [[common problems, how to respond, when to escalate, and evidence of completion]].
Document control: [[SOP ID, version, approval status, effective date if approved, review date, and known revision history]].

Use my notes and any attached process documents. Ask about missing details that would prevent someone from following the procedure. Mark other unknowns as to confirm. Keep proposed improvements separate from the documented current process, and do not invent policies, approvals, deadlines, system features, or revision history. If no approval is supplied, label the SOP as a draft for review.

Include purpose, scope, start conditions, required inputs, roles, numbered instructions, exceptions, escalation, a completion checklist, and document control. For each step, state who acts, when to act, what to do, and what record or result confirms completion. Explain timing relative to its trigger, such as within one business day of receiving a complete handoff. Spell out unfamiliar abbreviations.

Use a simple revision log with version, date, change summary, and reviewer; leave unconfirmed entries clearly marked. Distinguish operating targets from guaranteed service commitments. Keep checklist boxes empty so the team can use them when performing the process.

Aim for four readable pages, adjusting the length to the actual process. Use concise instructions, clear headings, useful tables, and page numbers. Make the text, structure, and theme editable. Before finalizing, check that every handoff has a receiving owner, exceptions have a response, and the completion checklist matches the steps. Do not carry over the example's client onboarding scope or seven-business-day target unless my notes specify them.

Generate in ML Clever Copy to my workspace

Opens in Docs mode

Your generated document will reflect your brief and sources. The preview shows a completed example.

Format: Multi-pager
Example length: 4 pages
Category: Operations
Example process: Client onboarding

Standard operating proceduresProcess documentationClient onboardingSmall business

What to include in your document

Purpose, scope, and start conditions

Explain why the procedure exists, who should use it, and what starts the work. State what is included and excluded. The example begins after a marketing-services agreement is signed and covers the handoff through kickoff; proposals, billing, and ongoing campaign delivery fall outside its scope.

Roles and required inputs

Identify the process owner, the people responsible for individual steps, and the materials they need. The example assigns responsibilities to the Sales Lead, Account Manager, Project Manager, and Operations Lead. Inputs include the signed agreement, agreed scope, client contacts, goals, and supporting materials.

Numbered steps and handoffs

Give each step an action, owner, timing, and completion evidence. The example moves through confirming the engagement, completing and reviewing the handoff, welcoming the client, preparing the project, and running kickoff. Name the recipient of each handoff and explain when the next person can begin.

Exceptions and escalation

Explain how to handle missing information, conflicting scope, access problems, and delays. In the example, the Account Manager follows up on missing inputs, while unresolved blockers go to the Operations Lead. Record the impact, resolution owner, and due date so an exception has a clear next action.

Completion checks and records

Define what finished means using observable checks. The example's checklist covers accessible agreement and scope, a reviewed handoff, inputs or assigned outstanding items, project setup, kickoff, the written recap, and an Operations Lead review. Supporting records show that a step was performed.

Document control and revision history

Give your SOP an ID, version, process owner, approval status, and review date. Record subsequent changes with a date, summary, and reviewer so the team can identify the current procedure. The preview shows SOP ID CS-001 and an approval-pending label; add your own version details and revision log when adapting it.

Built for the decision ahead.

Start with a clear structure, then tailor the evidence and recommendation to the people in the room.

Ideal for

Small business owners documenting recurring work for their teams.
Operations leads clarifying responsibilities, handoffs, and completion checks.
Agencies and client services teams creating a consistent onboarding process.

Includes

A filled four-page client onboarding SOP example with a preview of every page.
A reusable SOP outline covering purpose, inputs, roles, steps, exceptions, checks, and document control.
An adaptable AI prompt and an option to copy the example into your ML Clever workspace.

What to prepare

Process name, intended users, purpose, scope, and exclusions.
The event that starts the work and the conditions that define completion.
Actual process notes, required materials, systems, and access.
Step owners, handoff recipients, timing, and evidence of completion.
Known exceptions, escalation contacts, and required checks.
Process owner, approver, SOP ID, version, review date, and existing change records.

How to use this template

01
Gather the process as it works today
Ask the people doing the work to describe the sequence, inputs, handoffs, and common exceptions. Replace the prompt placeholders with those details and attach relevant process notes in Docs mode. Identify open questions before presenting the draft as an agreed procedure.
02
Generate or copy your SOP
Choose Generate in ML Clever to draft a procedure from your notes, or Copy to my workspace to adapt the client onboarding example. Replace its roles, timings, steps, and escalation rules with your own. Add your document control details and adjust the layout and theme for your team.
03
Walk through it and review
Have a team member follow the draft using a representative case. Resolve unclear instructions, missing inputs, and incomplete handoffs. Confirm the checks and exceptions with the process owner, record the appropriate approval and version details, and set a review date before adopting the SOP.

Questions about this template

A standard operating procedure, or SOP, describes how to carry out a recurring task consistently. It tells the reader when to begin, what information is needed, who does each step, how to handle exceptions, and how to confirm the work is complete.

Include a title and document ID, purpose, scope, intended users, process owner, inputs, numbered steps, responsible roles, timing, exceptions, escalation, and completion checks. Add version, approval, review, and revision details so the team knows which procedure to use. The outline and prompt on this page cover these elements.

An SOP explains how to perform the work, including responsibilities, timing, decisions, and exceptions. A checklist helps someone confirm that required actions or conditions have been addressed. The example includes both procedural tables and a completion checklist so the checks can be used alongside the instructions.

Yes. Client onboarding is the filled example. Keep the overall structure and replace the trigger, inputs, roles, steps, checks, and escalation rules with the details of your own process. The example's seven-business-day kickoff target and role names are illustrative, not requirements for your business.

Yes. Use the prompt as an AI SOP generator brief in ML Clever, with your process notes and existing instructions as source material. It can organize those inputs into an editable draft. Have the people responsible for the process check the sequence, handoffs, exceptions, and completion criteria before adopting it.

The editable template is in ML Clever. You can preview all four pages and copy the prompt here before signing up, then generate a document or copy the example into your workspace. Edit the text, structure, and theme there. PDF export is available on eligible plans; this page does not provide a Word or Google Docs template download.

Create your next business document with AI.

Describe the document you want to generate

Docs mode

Standard Operating Procedure Template

Client Onboarding SOP — From Signed Agreement to Project Kickoff