SCREENSHOT SOP TEMPLATE
Bundlepix | Version 1.0 | 17 September 2026
Guide: https://bundlepix.com/turn-screenshots-into-documentation

HOW TO USE
Save a copy and replace the bracketed prompts in your document editor.
Duplicate the STEP block for each meaningful action. Insert reviewed screenshots
in your working document at the corresponding capture references.
This is an original planning worksheet, not an exported Bundlepix document.
You may adapt it for your team's work with any capture tool. No account required.
Use sample data; keep completed company records in approved internal systems.

PROCESS BRIEF
Process: [One repeatable task]
Purpose: [Business outcome]
Audience: [Authorised role; no personal details]
Owner / reviewer: [Responsible roles]
Version / review date: [Version and date]
Environment: [Application version and approved test environment]
Prerequisites: [Required access, inputs and knowledge; never credentials]
Start condition: [What must be true before step one]
Completion condition: [Observable result]
Storage and access: [Approved internal location and authorised roles]

STEP [NUMBER]
Action: [One clear action]
Capture reference: [Sanitised image identifier]
Expected visible result: [What the reader should check]
Why this capture matters: [Decision, changed state or completion evidence]
Exception: [When to stop and which role to contact]

FICTIONAL EXAMPLE - NOT A CUSTOMER RESULT
Action: Submit a sample equipment request in the test system.
Capture reference: STEP-04-confirmation
Expected result: A submission confirmation is visible.
Why it matters: It confirms handoff to the next role.
Exception: If confirmation is absent, stop and ask the process owner.
Boundary: Submitted does not mean approved.

RELEASE CHECKLIST
[ ] Another authorised colleague followed the instructions in a test environment.
[ ] Each screenshot explains an action, decision or result; redundant images removed.
[ ] Instructions and screen labels match the current application.
[ ] Sensitive details removed; final output inspected.
[ ] Exceptions, completion check and next owner are clear.
[ ] Owner, version, approval and next review trigger recorded.
[ ] Editable source and approved output stored under company controls.

NEXT REVIEW
Review when: [System change, process change or agreed review date]
What changed: [Instruction and matching screenshot]

Bundlepix compiles reviewed screenshot evidence into documents. Your team writes
and approves the instructions. Screen recording is a separate workflow.