Blog

Guide · November 2026

How to document undocumented processes from screen activity

Why processes stay undocumented

A standard operating procedure, or SOP, is “the set of step-by-step instructions that document how” a task is done. Many tasks have no SOP, or have one that no longer matches the work.

The knowledge is in the heads of the people who do the work. Part of it is tacit knowledge: knowledge that is “difficult to extract or articulate”. An experienced person knows which screen to check and which case needs a different path, but rarely writes it down.

Where the usual methods stop

  • Interviews and workshops describe how people remember the process. They miss the exceptions and the small workarounds.
  • Shadowing one person shows one way to do the task, on the cases of that day.
  • A screen recording of one walkthrough shows the usual path. It does not show the cases that go wrong.
  • A document written once goes out of date when a system or a rule changes.

How to build an SOP from screen activity

  • Agree the scope with the team: which people, which applications, and what is left out. Tell everyone in scope what is recorded and why.
  • Record the real work in the background for some weeks, so the recordings hold many cases of each task.
  • Group the recordings by task, so you can compare the same task done by different people.
  • Find the common path, then the variants and the exceptions, and how often each one occurs.
  • Write the SOP from that evidence, and link each step to recorded examples.
  • Ask the people who do the work to review it. They can explain why a step is done, which a recording cannot always show.

Recording real work is the method of task mining. Privacy needs care from the start: task mining privacy.

What a good SOP holds

  • The purpose of the task, and the event that starts it.
  • The inputs, and where they come from.
  • The applications used, in the order they are used.
  • The steps of the common path.
  • The exceptions, how to identify each one, and what to do.
  • The output, and how to check that it is correct.

An SOP with its exceptions is also the start of an automation. An automation must handle the same cases that the team handles.

How Subliminal documents processes

A small desktop app runs in the background while your teams work. Nobody writes the process down: Subliminal maps each recurring workflow from the work itself, with its steps, tools, inputs, outputs and exceptions. The documentation shows the exceptions that are not in your process documents, and your team can review the recorded examples behind each workflow.

At Fella Health, models read the recordings and wrote a wiki of how the work is actually done. Every claim in the wiki links back to the recordings it was drawn from. The full account: the Fella Health case study.

Sources