SOP prerequisites: define the starting state

An SOP can describe every click correctly and still leave a reader unable to begin. The author may already be signed in, have the right workspace open or have prepared a sample record before recording. Those conditions belong in the guide. Writing the starting state makes clear where the procedure begins, what the reader needs and when they should stop rather than improvise.

Separate preparation from the first action

Before editing the step sequence, list what was already true when the capture started. Which application and page were open? Was a particular workspace selected? Did an earlier process create the item you are about to change? Turn the necessary conditions into a short preparation section, leaving unrelated details out.

A prerequisite describes a condition that must hold; a step tells the reader how to do something. If preparing a file requires several actions, link to the preparation procedure or document those actions separately. “Have the file ready” is useful only when readers know which file, where to obtain it and what ready means. Do not hide half the workflow inside one unexplained sentence.

Define access without including credentials

State the role or capability the task requires in the application being documented. A reader might need permission to edit a record rather than merely view it. Use the application's actual terminology and verify the path with the intended level of access. A successful capture from an administrator account does not establish that every other account can follow it.

Explain what to do if the required control is absent. Direct the reader to the appropriate owner or an existing access request process, rather than inventing a workaround. Never put passwords, tokens or recovery codes in the prerequisite section or its screenshots. Describe the required access, not the secret that provides it.

Name the environment and relevant starting data

Include environment details when they change the procedure. A demonstration workspace and a production workspace may look similar while carrying different consequences. Identify which one the instructions cover, and use an obvious example name that readers will not mistake for a real customer or operational record.

For input data, specify the properties that matter to the task. A sample import file might need a particular format and a known set of columns. A record being updated might need to be in a particular state. Avoid copying private content into the guide merely to make the example concrete. Say which values are examples and which requirements must be preserved.

Show a recognizable entry point

Choose a first screenshot that helps readers confirm where they are. Keep the relevant application heading or navigation landmark visible. If the guide begins halfway through a larger process, link to the preceding procedure and explain the handoff. An image of an open dialog does not explain how the reader arrived there.

Write a short entry check in plain language. For example, ask the reader to confirm that the intended workspace is open and the selected record has the expected status before making a change. Keep this check specific to the procedure you tested. It should identify a mismatch early, not suggest that one visible label guarantees the whole environment is safe.

Test the beginning as deliberately as the ending

Review the guide from a fresh starting point that matches its stated prerequisites. Look for preparation that you perform from memory but never describe. Check whether the linked setup guide opens, whether the sample material is available and whether the first instruction refers to a control the intended reader can actually see.

When the procedure changes, review the preparation section alongside the screenshots. An updated button label may be easy to notice, while a changed permission requirement or input format can remain hidden in an otherwise familiar workflow. Record unresolved conditions and obtain confirmation before presenting them as instructions.

StepShot for macOS 14 and later lets authors edit step titles and descriptions and insert notes or section headings. Use a note before the action sequence to explain preparation, then keep the numbered steps focused on the task. The capture guide explains choosing the material to record, and the editor guide covers arranging and explaining the resulting steps. Capturing the workflow supplies evidence; the author still defines the conditions under which readers should follow it.