TapGuide / Blog / 29 October 2026

How to write an SOP with screenshots (and keep it current)

Two colleagues smiling at a phone in a warehouse, with shelves of cardboard boxes behind them and a clipboard on the counter.

A good SOP with screenshots covers one task, with numbered steps. Each step has one action and one screenshot, and the button to press is marked on it. Around the steps you add a short header: the purpose, who does the task and when, what to have ready, and how to check it worked. Give every SOP an owner and a "last updated" date, and redo the screenshots whenever the app changes. Otherwise the pictures stop matching the screen and people stop trusting the document.

Here's how to do each part, with the steps for capturing and marking up screenshots on Android.

What goes in an SOP with screenshots?

Keep the structure the same in every SOP, so readers always know where to look. This one works for most tasks done in an app:

  1. Title. The result, written the way staff would say it: "Receive a delivery in the scanner app", not "Inbound goods process v2".
  2. Purpose. One sentence on why the procedure exists.
  3. Who and when. The role that does it and what triggers it ("Shift lead, at the end of every shift").
  4. Before you start. The device, the login, and anything to have ready.
  5. Steps. Numbered, with one screenshot each.
  6. Check. What the reader should see when it's done, so they know it worked.
  7. Owner and last updated. A name and a date, plus a short change log.

One SOP, one task. If a procedure branches ("if the item is damaged, do this instead"), write the branch as its own SOP and link to it. Long documents with many paths are the ones nobody follows.

How do you take screenshots on Android?

The button combination is the same on most Android phones, including Samsung Galaxy phones:

  1. Open the screen you want to capture.
  2. Press Power and Volume down at the same time.
  3. A preview appears at the bottom of the screen. Tap it to edit or share, or ignore it to keep going.

If the buttons don't work, Google's Android help says to press and hold Power, then tap Screenshot. On Android 12 and later, tap Capture more in the preview to capture a page that scrolls.

On Samsung phones, you can also turn on Palm swipe to capture in Settings > Advanced features > Motions and gestures, then swipe the edge of your hand across the screen. The exact names vary between One UI versions, so if you can't find a setting, use the search bar at the top of Settings.

Screenshots land in the Screenshots folder: in Google Photos under Collections > On this device, or in Samsung's Gallery app. Menu names differ between phone makers and Android versions, so check them on the phone your team actually uses.

One step, one action, one screenshot

This is the rule that makes an SOP easy to follow. Each step tells the reader to do one thing, and the screenshot shows the screen at that moment.

Take the screenshot right before the action, with the button visible. A screenshot taken after the tap shows the next screen, and the reader has to guess what you pressed.

Mark up the screenshots so the button is obvious

A full phone screenshot has a lot on it. The reader needs to find one thing in a second or two.

Most phones have a built-in editor for this. Tap the preview after a capture, or open the screenshot in Google Photos or Samsung's Gallery app and tap Edit. The tools differ by phone maker and Android version, so open the editor on the phone your team uses and see what it offers. Built-in editors don't always have a proper blur tool, so check before you rely on one.

The faster way: record the steps instead

Doing all of this by hand is where most SOPs stall: screenshot, paste, type, crop, mark up, twenty times over.

TapGuide is an Android app that does the capture and the writing for you. Press Record, do the task once the way it should be done, and press Stop. Each tap becomes a step with its screenshot, and the step text is written from the button's label, such as "Tap Receive". You can then edit the wording, reorder or delete steps, highlight buttons and blur private data.

When it's ready, export it as PDF to print or pin in a team chat, or as Markdown or HTML to paste into your wiki or help center. You add the title, purpose and check sections around the steps there. It runs on Android 8.0 and later, has no account and no internet permission, so screenshots of internal apps stay on the phone until you share them. It records on Android only, but the exported guide opens on any device. There's more on this use in SOPs and work instructions, made on the phone.

How do you keep an SOP with screenshots current?

Screenshots go out of date faster than text does. A renamed button or a moved menu makes the whole step look wrong, even if the process hasn't changed. A few habits keep that in check:

  1. Name an owner. One person per SOP, who gets told when the app or the process changes.
  2. Date it. Put "Last updated" at the top, and a short change log at the bottom: date, who, what changed.
  3. Review on triggers, not just on a calendar. An app update, a new device, a changed policy, or a staff question that the SOP should have answered.
  4. Redo whole SOPs, not single images. Mixing old and new screenshots confuses people. If you recorded the SOP, recording it again is usually quicker than patching it.
  5. Keep one copy. Link to the SOP from chats and onboarding material instead of attaching files, so there's never an old version going around.

Test it before you publish

Give the SOP to someone who has never done the task. Ask them to follow it on their own while you watch, and don't help. Every place they hesitate or ask a question is a step to fix: a missing action, a vague label, a screenshot that doesn't match their screen.

The same test works for family, too: see how to write phone instructions your parents can follow on their own.

A quick checklist

For the general method behind step-by-step guides on a phone, see how to make a step-by-step guide on Android.

Make your next guide in one take

Press Record, do the task once, and TapGuide turns every tap into a step with a screenshot. Free on Android 8.0 and later. No account, no internet access.

Get it on Google Play