Ownsteps / Guides

Free SOP template: copy, edit and add screenshots

Reviewed 14 October 2026.

A useful SOP template helps you write a procedure that someone else can follow and verify. It needs a purpose, starting conditions, numbered actions, exceptions and an observable result. You can copy the template below into an existing editor without an account, paid download or documentation platform.

Use it for one repeatable task, such as preparing a draft invoice for review. Replace the placeholders with verified instructions for your application. This is a practical starting structure, not a certification template or evidence that your organization's approval requirements have been met.

Copyable Markdown SOP template

Select and copy the block. Paste it into a Markdown editor, or into Word as plain text and apply heading styles. Keep the sections that affect safe execution; shorten background material that the reader does not need at the point of work.

# SOP: [Verb + task + result]
Document ID: [identifier]
Version: [version]
Status: [draft / reviewed / approved under your process]
Owner: [responsible role]
Reviewed: [date]
Master location: [link or folder reference]

## 1. Purpose and scope
Purpose: [why this procedure exists]
Applies to: [audience, application and environment]
Starts when: [trigger and starting state]
Ends when: [observable final state]
Excluded: [actions handled elsewhere]

## 2. Responsibilities and access
Operator: [role]
Reviewer / approver: [role, if required]
Access needed: [permission; no credentials here]
Related policy or instruction: [master reference]

## 3. Before starting
- Confirm [correct account, environment or record].
- Obtain [required input] from [approved source].
- Check [authorization or prerequisite].
- Stop if [missing input, access or approval].

## 4. Procedure
1. [Action with exact control label].
   Expected result: [visible state].
   Input rule: [where values come from].
   Screenshot: [reviewed image and caption].
   If different: [safe next action or escalation].

2. [Next action].
   Expected result: [visible state].
   Warning before action: [condition, if needed].

## 5. Verification and completion
- Compare [saved result] with [approved source].
- Confirm [status or output].
- Record completion in [existing record, if required].
- Do not proceed to [excluded action] without [approval].

## 6. Exceptions and recovery
If [condition]: [stop, safe recovery or escalation].
Contact / route: [existing role or channel].
Related recovery procedure: [reference, if applicable].

## 7. Maintenance
Review when: [interface, role or rule changes]
Next review: [date set by your team, if applicable]
Change history:
- [version / date / what changed / review reference]

Fill the scope before adding screenshots

For a draft invoice procedure, the purpose might be ?prepare a saved draft for review.? State who can create drafts, which invoice application applies and where approved customer and amount details come from. Exclude sending the invoice if that belongs to a separate approval task.

Write the outcome in terms someone can check: the draft appears under the intended customer, contains the approved amount and has not been sent. Avoid ?the invoice is done,? which can mean different things to an operator and reviewer. If the saved result cannot be verified using the stated access, revise the procedure or its prerequisites.

Set the status honestly. A document copied from this template is a draft until your team completes its own review. Use roles and dates your team has actually assigned. Do not fill empty approval fields with guessed names or invent a review schedule to make the page look complete.

Turn the procedure section into actions and checks

Write one meaningful action at a time using the actual control label. In the invoice example, ?Select New invoice? locates the action; ?A draft form opens? describes the result. For form entry, specify the source and format of the input rather than embedding a real customer's data.

Add decision rules where the reader needs them. If the customer is absent from the approved list, say whether to stop and request a record rather than create a duplicate. Put warnings before actions that send, delete or change access. Link to a separate procedure when recovery requires a substantially different task.

Do not turn every click into a mandatory step. Opening an irrelevant tab or correcting the author's mistake does not belong in the final procedure. Conversely, a quick verification may deserve its own step even if it produced no click. The document should represent the intended method, including the checks a recorder cannot infer.

Add screenshots with the free guide maker

Take images using your existing screenshot tool. Capture the screen that helps readers find the next control and, when useful, a separate image showing the expected result. Keep enough application context to identify the right area. A picture of a Save button illustrates the action; it does not demonstrate that saving succeeded.

For a short image sequence, use the free screenshot guide maker. Add your reviewed screenshots, arrange their order, write a note for each step and download an editable Word guide or use the browser's Save as PDF option. No recorder purchase is required.

The guide maker assembles a numbered sequence; it does not supply the SOP's scope, authorization rules, exceptions or maintenance record. Add those sections in Word or your existing editor. It also does not redact images. Use safe captures and follow the redaction checklist before adding them.

Word tips for an editable SOP

• Apply heading styles. Use the title style for the document name and heading styles for sections. Remove Markdown hash marks after applying the corresponding Word styles.
• Use actual numbered lists. Keep action numbers consistent when inserting or removing a step. Avoid manually spacing text into columns.
• Place images inline. Put the screenshot after its instruction with a short caption. Check that text remains editable and the image is readable at normal page size.
• Keep headings with their content. Use paragraph pagination controls where appropriate, then review page breaks. Avoid a heading or warning stranded from the action it introduces.
• Review the output. Open the saved file in the recipient's editor when possible. Check images, links, numbering, comments and tracked changes before distribution.

Do not use a Word rectangle as the only way to hide sensitive screenshot content. Replace the image with one whose sensitive pixels have been removed. For a more detailed handoff workflow, see exporting a step-by-step guide to Word.

Test the SOP with a new reader

Have someone with the intended permissions follow the draft in an appropriate environment. Ask them to identify the starting record, perform the task and show the expected final state. Observe where they need verbal help or choose between options without a written rule. Correct those gaps where they occur.

Record the scope of the review. A successful test in a sample environment does not establish that every client system or production configuration behaves the same way. Keep the master in a known location, identify its responsible role and replace distributed copies when the method changes.

When a template needs a shorter companion

An experienced operator may only need a completion checklist, while a new colleague needs detailed work instructions. Keep the governing SOP and link to a short task guide rather than repeating every policy in both. See work instructions versus SOPs and checklists for the distinction and another copyable template.

For repeated Chrome procedures, Ownsteps can prepare an editable screenshot sequence from clicks. You still add the purpose, input rules, exceptions and final checks. A manual screenshot method remains useful for occasional work and tasks involving desktop applications.