Capture only the interface detail a reader needs, remove sensitive information, and connect every image to a written action.
Created by the First Role Skills Editorial Team. This lesson uses a fictional workplace scenario and links to primary product documentation where the interface or feature matters.
A realistic scenario
You need to explain a recurring task. The screen contains names, email addresses, browser tabs, and account details that must not appear in a training document.
DeliverableA short SOP with focused, accessible screenshots created from a fictional practice environment.
Three beginner mistakes
- Capturing the full desktop when only one control matters
- Blurring data lightly enough that it can still be read
- Using a screenshot instead of writing the instruction
Complete it in six controlled steps
Prepare a safe environment
Use fictional records and close unrelated tabs, notifications, chats, and password tools before capturing. Prevention is safer than relying on redaction later.
Write the instruction first
State the action, expected result, and decision rule in text. The screenshot should confirm location or appearance, not carry the entire explanation.
Capture the smallest useful area
Include enough interface context to orient the reader, then crop tightly. Keep cursor placement and zoom consistent across a sequence.
Annotate sparingly
Use one numbered callout or outline for the relevant control. Do not cover labels or rely on red and green alone to convey meaning.
Redact and inspect
Remove email addresses, phone numbers, tokens, filenames, and personal browser details. Zoom in after export and ask another person to inspect the image.
Name and describe the asset
Use a useful filename, concise alt text, and a caption that explains why the image matters. Record the application and review date in the SOP.
Before and after
Before:
Full desktop screenshot showing inbox names, open tabs, profile photo, and a tiny highlighted button.
After:
Cropped fictional interface with one numbered callout, alt text, caption, and no personal or account data.
Complete the exercise
Create a three-step SOP using a fictional browser form or spreadsheet. Run the privacy checklist, export images, and ask a reviewer to identify any remaining sensitive details.
Download the SOP and privacy template — An editable SOP outline with a pre-publication privacy review. — Download file
Use only fictional or fully anonymized data. Never upload an employer’s confidential information to a portfolio.
Turn the exercise into credible evidence
Keep the original safe practice screen, the cropped annotated image, and the completed privacy checklist. In your explanation, identify what you excluded from the frame, why one callout was enough, and how the alt text supports a reader who cannot see the image. Record the second-person review result. Never use a real inbox, customer record, token, or employer interface simply to make a portfolio sample look more authentic.
Check your own work
- Fictional environment
- Instruction written first
- Tight crop
- Sensitive data removed
- Alt text provided
Primary reference: Microsoft Support: capture and redact with Snipping Tool
Why this matters in your first job
Documenting processes is one of the most useful things a new employee can do. You see the process with fresh eyes, notice confusing steps and can write instructions the next new hire will appreciate. Screenshots make instructions much clearer, but careless screenshots can expose customer data, passwords or internal information. Learning to capture only what is needed is a professional skill that protects everyone.
Common questions
What should never appear in a screenshot? Personal data, passwords, access tokens, financial details, internal URLs that should not be shared and anything confidential. When in doubt, crop or blur it, or use test data.
How many screenshots does an SOP need? Only enough to make each step clear. One screenshot per meaningful step is usually plenty.
How do I keep SOPs up to date? Add a “last reviewed” date and an owner, and check them when software changes. See how to take notes in your first weeks and how to build a professional portfolio for ways to reuse your documentation safely.