Free SOP Template

By Nikhil Gupta

Free SOP Template

Short answer: A good SOP template has eight sections:

1. Header (ID, title, owner, version, dates)

2. Purpose

3. Scope

4. Roles and responsibilities

5. Process map

6. Procedure steps, with decisions and exceptions

7. Related documents and systems

8. Revision history

Copy the template below, or generate a filled-in draft from your process in Vevos.

Part of the Process Documentation Guide. New to SOPs? Read how to write an SOP first.

The template

SOP ID:            [e.g. HR-003]
Title:             [Verb + object, e.g. "Onboard a New Employee"]
Process owner:     [Role, not just a name]
Version:           [1.0]
Effective date:    [DD Mon YYYY]
Next review date:  [DD Mon YYYY]
Approved by:       [Role / name, date]

1. PURPOSE
   [One or two sentences: why this procedure exists and what outcome it ensures.]

2. SCOPE
   Starts when:  [trigger event]
   Ends when:    [end state]
   Applies to:   [teams, locations, systems]
   Excludes:     [what this SOP does NOT cover]

3. ROLES AND RESPONSIBILITIES
   [Role]  – [what they do in this process]
   [Role]  – [what they do in this process]
   (For approvals, note who is Responsible, Accountable, Consulted, Informed. See RACI.)

4. PROCESS MAP
   [Insert a BPMN or swimlane diagram, or link to it.]

5. PROCEDURE
   Step 1. [Role]: [Verb + action.]
   Step 2. [Role]: [Verb + action.]
           IF [condition] → [action / go to step X]
           ELSE → [action]
   Step 3. [Role]: [Verb + action.]
   ...

   EXCEPTIONS
   - [What can go wrong] → [what to do]
   ESCALATION
   - If [condition, e.g. not completed in X days] → escalate to [role]

6. INPUTS, OUTPUTS AND SYSTEMS
   Inputs:   [forms, data, documents needed]
   Outputs:  [what the process produces]
   Systems:  [tools used, with links to work instructions]

7. CONTROLS AND MEASURES (optional)
   Key controls:  [approvals, checks, segregation of duties]
   KPIs:          [e.g. cycle time, error rate, on-time %]

8. RELATED DOCUMENTS
   [Policies, work instructions, forms, other SOPs]

9. REVISION HISTORY
   Version | Date | Change | Author | Approved by

Filled-in example: employee onboarding

SOP ID:            HR-003
Title:             Onboard a New Employee
Process owner:     HR Operations Manager
Version:           2.0      Effective: 1 Nov 2026    Next review: 1 Nov 2027
Approved by:       Head of People, 20 Oct 2026

1. PURPOSE
   Ensure every new hire has a contract, equipment, system access and a
   first-week plan before day one.

2. SCOPE
   Starts when: candidate accepts the offer
   Ends when:   new hire completes day-one orientation
   Excludes:    contractors (see HR-009)

3. ROLES
   HR Coordinator   – contract, documents, orientation
   IT Support       – laptop, email, system access
   Hiring Manager   – first-week plan, introductions

4. PROCESS MAP
   [Employee onboarding BPMN: vevos.ai/templates/employee-onboarding]

5. PROCEDURE
   1. HR Coordinator: Send contract and document checklist within 1 business day.
   2. HR Coordinator: Confirm documents received.
      IF incomplete 5 days before start → follow up and notify Hiring Manager.
   3. In parallel:
      3a. IT Support: Provision laptop, email and role-based access by day -2.
      3b. Hiring Manager: Prepare first-week plan and buddy assignment.
   4. HR Coordinator: Run day-one orientation.
   5. Hiring Manager: Introductions and first assignments.

   EXCEPTIONS
   - Start date moves → HR updates IT and Hiring Manager the same day.
   ESCALATION
   - Access not ready by day -1 → IT Support escalates to IT Manager.

6. SYSTEMS
   HRIS, ticketing system (IT access request form), e-signature tool.

7. MEASURES
   % of hires with full access on day one (target 100%).

9. REVISION HISTORY
   2.0 | 20 Oct 2026 | Added parallel IT/manager steps | HR Ops | Head of People

Generate this from your process instead

Typing an SOP from scratch is slow. In Vevos:

1. Describe the process, upload existing notes, or record a walkthrough.

2. Vevos builds the BPMN process map (section 4).

3. Generate the documentation from the map and edit it.

4. Export it as Word, PDF, Markdown, or HTML, or publish it to your knowledge base.

When the process changes, update the map and regenerate the documentation, so the map and the SOP never drift apart.

Try it free →

FAQ

What format should an SOP be in?

Whatever your team will actually open: a shared document, a wiki page, or a knowledge base. Keep the structure consistent across SOPs so people know where to look.

Should an SOP include a flowchart?

Yes, for any process with decisions or more than one role. A diagram shows hand-offs and exceptions far faster than text.

How often should SOPs be reviewed?

At least annually, and whenever a system, regulation, or team structure changes. See keeping process documentation current.