define “done” first
before recording, write down:- the trigger
- required inputs and permissions
- the accepted result
- the process owner and reviewer
- sensitive information that must be excluded
- common exceptions worth capturing separately
step by step
1
perform one clean run
The process owner completes the task normally while screenpipe records the relevant screen and, if helpful, narration. pause when unrelated sensitive work appears.
2
mark the time window
Record the start and end. include a short statement of the trigger and result so the AI does not have to infer them from UI fragments.
3
generate a draft
Ask for prerequisites, numbered actions, decisions, exceptions, validation, rollback, and unresolved gaps. refer to UI labels rather than unstable screen coordinates.
4
review with the process owner
Remove accidental detours, add missing policy, and identify steps that reflected personal habit rather than an organizational requirement.
5
test with another person
Have a teammate follow the draft without coaching. capture where they hesitate or cannot verify success.
6
publish the approved version
Add an owner, review date, version, and change history. keep raw recording access narrower than the final SOP.
7
find the next improvement
After the SOP works, use workflow discovery to choose one stable step for automation.
SOP prompt
SOP or automation?
document first when the process contains policy, judgment, exceptions, or approvals. automate only the stable portion whose output can be checked. a reliable checklist is a valid result; not every workflow needs a bot.team administrators can standardize filters and pipe configuration with teams, but each participant still needs a clear recording policy and appropriate access.