Process vs Procedure
A process is the high-level sequence of stages that turns an input into an outcome and describes what happens and in what order. A procedure is the detailed, step-by-step set of instructions for carrying out a specific task within that process — the exact how. In short, the process is the map; the procedure is the turn-by-turn directions.
What is a process vs procedure?
"Process" and "procedure" get used interchangeably, but they operate at different altitudes, and the distinction is genuinely useful once you see it. A process is the big-picture view: the ordered stages that move work from a trigger to a result, often crossing several people or teams. It answers "what happens, and in what order," without getting into the mechanics of each stage.
A procedure zooms all the way in. It's the exact, step-by-step instructions for performing one task within the process — specific enough that anyone following it produces the same result. Where a process might say "the request is approved," the procedure spells out who opens which screen, which fields they check, which button they click, and what they do if something's off.
The practical value: you document them differently and for different reasons. A process is best captured as a flow or map so everyone shares a mental model of the whole; a procedure is best captured as a numbered, often screenshot-backed guide so the work gets done consistently. Confusing the two is why some documentation is too vague to follow and other documentation buries the big picture in click-by-click detail.
Key characteristics
Different altitudes
A process is the zoomed-out view of the whole workflow; a procedure is the zoomed-in view of one task inside it. One shows the forest, the other a single tree.
What vs how
A process answers what happens and in what order. A procedure answers how to actually do a given step — the specific, repeatable actions.
Scope of ownership
A process often spans multiple people or teams handing work off; a procedure usually lives with one role performing one task.
How each is documented
Processes are captured as flows or maps; procedures are captured as numbered, step-by-step instructions — frequently with screenshots for software tasks.
They nest together
A single process contains many procedures. Documenting a workflow well usually means mapping the process once, then writing a procedure for each task inside it.
Process vs procedure at a glance
Both describe how work gets done, but at different levels of detail. The clearest way to keep them straight: a process is the map, a procedure is the turn-by-turn directions.
| Process | Procedure | |
|---|---|---|
| Question it answers | What happens, and in what order? | How do I actually do this task? |
| Altitude | High-level — the whole workflow end to end | Detailed — one task within the workflow |
| Scope | Often spans multiple people, roles, or teams | Usually a single role performing a single task |
| Best documented as | A flow or process map showing stages and handoffs | Numbered, step-by-step instructions, often with screenshots |
| Level of detail | Stages and decision points, not individual clicks | Every specific action, in order, with no ambiguity |
| Example | "Employee onboarding" — from offer accepted to fully ramped | "Create the new hire's email account in the admin console" |
| Changes how often | Rarely — the shape of the work is fairly stable | More often — tools and screens change underneath it |
Where policy fits: policy vs procedure
People often line up a third term with these two — policy — and it sits above both. A policy is a rule or principle that governs decisions: what the organization requires or forbids and why. It states intent, not mechanics. "All customer refunds over $500 require manager approval" is a policy; it tells you the rule without telling you how to carry it out.
The procedure is how you comply with the policy. Given that refund rule, the procedure spells out the actual steps: where to log the request, how to route it for approval, and how to process it once approved. The policy is the "what must be true"; the procedure is the "here's how we make it true." A process, meanwhile, is the broader flow the procedure lives inside — the end-to-end refund handling from request to resolution.
A simple way to hold all three: policy sets the rules, the process describes the overall flow, and procedures give the step-by-step actions. Strong operations documentation usually needs all three — policies so people know the boundaries, a process map so they see the whole, and procedures so the work gets done the same way every time.
Where Glyde fits
Glyde lives at the procedure level — the step-by-step how. You perform a task once while recording (or upload an existing screen recording), and Glyde writes a structured procedure: purpose, scope, prerequisites, and annotated, numbered steps that anyone can follow to get the same result. Because it reads the actual on-screen actions and page context, each step reflects what really happened, not a vague paraphrase.
That makes Glyde the fast way to fill in the procedures a mapped-out process implies. Once you've sketched a workflow's stages, each stage that happens on a screen becomes a Glyde recording and, minutes later, a finished procedure — the click-by-click detail that a process map deliberately leaves out. It's the difference between having a diagram of how work should flow and having the concrete instructions that let a new person actually do each part of it.
Process vs Procedure, answered
What's the difference between a process and a procedure?
What's the difference between a policy and a procedure?
How do process, procedure, and policy relate?
Should I document a process or a procedure?
Related terms
Standard Operating Procedure (SOP)
A documented, repeatable set of steps for doing a task the same way every time — what goes in one, formats, and how to build them.
Process Documentation
Recording how a process is performed so it can be followed, improved, and scaled — what it includes and the fastest way to do it.
Turn your next recording into a real SOP
Record once, get documentation your team can follow on day one. Free plan, no credit card required.
Try Glyde Free