Process vs procedure comes down to scope: a process is the sequence of activities that turns an input into a result, usually across several people or teams, while a procedure is the agreed, step-by-step way to carry out one task inside that process. A policy sits above both: it states the rule the work must follow and why, with no steps. This guide compares all three using one running example, shows where SOPs, work instructions and job aids fit, and helps you pick which to write first.
What is the difference between a process and a procedure?
A process describes what happens to reach a result and in what order, often across several roles: employee onboarding, order to cash, incident response. A procedure describes how one task inside that process is done, step by step, so that anyone trained does it the same way. The process is the route map; a procedure is the turn-by-turn directions for one stretch of it.
ISO 9000:2015, the vocabulary standard whose defined terms ISO 9001:2015 uses, draws the same line. It defines a process as a “set of interrelated or interacting activities that use inputs to deliver an intended result” and a procedure as a “specified way to carry out an activity or a process”, as NIST's glossary entries for process and procedure reproduce them (all three pages read on 15 November 2026). ISO published a new edition of ISO 9000 in 2026, so check its wording if you are working to the current standards. Put simply, a procedure exists to carry out part of a process.
| Aspect | Process | Procedure |
|---|---|---|
| Answers | What happens, in what order, and who hands off to whom? | How exactly is this one task done? |
| Scope | End to end, often across teams | One task, usually done by one role |
| Level of detail | Stages, inputs, outputs, decisions and handoffs | Numbered actions, checks and exceptions |
| Typical format | Flowchart, swimlane map or a table of stages | Numbered list, checklist, SOP document or video |
| Judged by | How long the whole thing takes and where it stalls | Whether each run is done the same correct way |
| Changes when | The business, the team structure or the customer journey changes | A tool, screen, form or rule inside the task changes |
| Example | Employee onboarding | Set up a new hire's accounts |
The two also break in different ways. A broken process shows up as work that stalls between teams: the laptop arrives on day one, but the accounts do not. A broken procedure shows up as the same task done two ways by two people, with two results. Fixing the first means redesigning the handoffs. Fixing the second means agreeing on the steps and writing them down.
What is the difference between a policy and a procedure?
A policy is a rule or principle that says what the organization requires or forbids, and why. A procedure is the sequence of steps people follow to meet that requirement. The policy is decided by someone with authority and changes rarely; the procedure changes whenever the task, the tool or the team does.
| Aspect | Policy | Procedure |
|---|---|---|
| Answers | What must or must not happen, and why? | How do I do it, step by step? |
| Language | “Must”, “may”, “is not permitted”; principles and limits | Verbs in order: “Open”, “Enter”, “Approve” |
| Audience | Everyone it applies to | The people who perform the task |
| Approved by | Leadership, HR, legal or a board | The process owner or the team lead |
| How often it changes | Rarely, through formal approval | Whenever the task, tool or team changes |
| Room for judgment | None on the rule itself; exceptions need sign-off | Some, at the decision points the procedure names |
| Example | Access control policy | Set up a new hire's accounts |
How do policies and procedures work together?
Each policy is carried out through one or more procedures, and each procedure should name the policy it serves. A policy with no procedure behind it gets applied a different way by every person who reads it. A procedure with no policy above it has no stated reason, so people cannot tell which steps are safe to skip and which ones protect the company.
Keep them in separate documents and link them. Policies usually pass through leadership, HR or legal, while procedures belong to the team that does the work. When the steps live inside the policy, every change to a screen needs a policy sign-off, and in practice the steps stop being updated. One line in the policy, such as “see the new hire account setup procedure”, and one line at the top of the procedure naming the policy, keep the two connected.
Policy vs process vs procedure: how do they fit together?
They nest from broad to narrow. A policy sets the rule, a process carries the work from start to finish within that rule, a procedure fixes the method for one task in the process, a work instruction gives the exact actions for one step on one system, and a job aid reminds a trained person of the essentials at the moment of work. Here is one business task followed through every level.
| Level | Answers | Usually owned by | Example: giving a new hire system access |
|---|---|---|---|
| Policy | What must be true, and why? | Leadership, HR, security or legal | Access control policy: each employee gets only the access their role needs, approved by their manager, and all access ends on their last day. |
| Process | What happens, in what order, and who hands off to whom? | A process owner, here HR operations | Employee onboarding: offer signed, HR record created, accounts and laptop set up, first week planned, first-month check-in. |
| Procedure (often an SOP) | How is this one task done, by whom, and with what exceptions? | The team that does the task, here IT | Set up a new hire's accounts: start from the HR ticket, create the email account, add the role's groups, get the manager's approval for anything extra; contractors and rehires follow a variant. |
| Work instruction | Exactly what do I click and type on this system? | The person who does the step most reliably | Create a user in the admin console: Users, Add user, enter the name and work email, pick the role group, Create, then check the status reads Active. |
| Job aid | What do I need to remember right now? | The procedure's owner | A one-page table of which groups each role gets. |
Not every task needs all five. A small team may have the policy and one procedure and nothing else, and that is fine. The levels start to matter when one document tries to do two jobs. For the levels below the procedure, the work instruction template guide compares work instructions with SOPs, and the job aid guide compares a job aid with an SOP and a training manual.
Is a procedure the same as an SOP?
Almost. An SOP, or standard operating procedure, is a procedure the organization has written down, standardized and put under control: it has an owner, a version, an approval and a review date. Every SOP is a procedure, but not every procedure is an SOP. The note to ISO's definition says procedures “can be documented or not”, and plenty still live only in someone's head.
So when a colleague says “we have a process for that” and then lists steps, they usually mean a procedure. When an auditor asks for your SOPs, they mean the written, approved versions. What is an SOP covers what an SOP contains and the formats it comes in, and how to write an SOP covers the writing, from the scope line to the test on a new reader.
How can you tell whether a document is a policy, a process or a procedure?
Read the verbs and ask which question the document answers. Rules with reasons and no steps make a policy. Stages and handoffs between roles make a process. Numbered actions that one role can follow make a procedure.
- It says “must”, “may” or “is not permitted” and explains why. Policy. If it also lists clicks, those steps belong in a separate procedure.
- It shows boxes, arrows or swimlanes for several roles. Process. Each box that people keep getting wrong is a candidate for its own procedure.
- It numbers actions for one role, with checks and exceptions. Procedure, or an SOP if it is formally controlled.
- It names exact buttons, fields and screens on one system. Work instruction.
- It fits on one page and is used during the task by someone already trained. Job aid.
A document that fits two of those lines is the usual source of trouble. The common case is a policy with steps buried in the middle: the rule stays right for years, the steps go stale within months, and nobody owns the update. Split it in two and link the halves.
When should you write a policy, a process map or a procedure?
Write a policy when a decision has to be made the same way every time and someone with authority needs to stand behind it. Map a process when work crosses teams and keeps stalling or getting lost between them. Write a procedure when one task is frequent, shared, error-prone or known by only one person.
| Document | Write one when | You can skip it when |
|---|---|---|
| Policy | Money, data, safety, legal risk or fairness to staff is involved, and people keep asking “are we allowed to?” | An existing policy already covers the decision, or the choice is low-stakes and can be left to judgment |
| Process map | Work passes between teams, handoffs get dropped, or you want to shorten the time from request to result | One person does the whole job from start to finish |
| Procedure or SOP | A task is done often, by several people, mistakes are costly, or only one person knows how | The task happens once, or is so simple nobody gets it wrong |
| Work instruction | People follow the procedure in principle but get the clicks or settings wrong | The procedure's steps are already clear enough to follow on the system |
| Job aid | Trained people forget a detail at the moment of work | Nobody does the task often enough to remember it exists |
If you are starting from nothing, start with the procedure people ask about most. It gives the quickest relief, and writing it shows whether a policy decision is missing: when two people disagree about a step because nobody has ever decided the rule, that is a policy gap, and it needs an owner who can settle it. For the mapping side, see our guide on how to document a process.
What do process and procedure mean in everyday English?
Outside business documents the two words overlap more. A process is any series of actions or changes that leads to a result, including ones nobody planned, such as the aging process or the process of learning a language; as a verb, you process a payment or an application. A procedure is a fixed, established way of doing something, and it sounds more formal: a medical procedure, legal procedure, an emergency procedure.
So you would say “the hiring process takes three weeks” but “follow the fire evacuation procedure”. If you could swap in “the official steps”, the word you want is procedure. If you mean everything that happens from start to end, waiting included, the word is process.
Which of these documents does a screen recording help with?
Procedures and work instructions, when the task happens on a screen. A policy is a rule and a process map is a flow, and a recording adds little to either. A procedure is a sequence of actions, and for software tasks, watching those actions once answers questions a page of text struggles with, such as where a button sits or what the screen should show afterwards.
That is the job stepvideo.io does. You record the task once with the Chrome extension, which records a browser tab, a window or your whole screen; click-accurate editing comes from tab capture with the extension. From that one recording it builds an edited how-to video with AI voiceover and captions, a written step-by-step guide with a screenshot for each step, which downloads as a PDF, and a share page that plays the video. You fix the steps rather than a timeline: rename, reorder, merge or delete them, rewrite a step's narration, and re-render. How it works shows each stage.
In the running example, that covers the work instruction: record yourself creating a user in the admin console with a test account, and you have the steps as a video and as a written guide. Put the share link or the PDF in the account setup procedure, your wiki or your intranet page. The policy, the process map, the procedure's roles and exceptions, and the approvals stay in your own documents. Plans are on the pricing page.
The short version
A policy says what must happen and why. A process says what happens, in what order, across which people. A procedure says how to do one task, step by step. Write each at its own level, keep them in separate documents that link to each other, and give every one an owner who will change it when the work changes.
Frequently asked questions
What comes first, a policy or a procedure?
The policy comes first in authority: it sets the rule, and procedures carry it out. In practice, teams often write a procedure for a task they already do and only then find a rule nobody decided. That is normal, but the missing decision belongs to someone with the authority to make it, written as policy, not settled inside the steps.
Is a procedure part of a process?
Yes. A process is a set of activities that together deliver a result, and a procedure is the specified way to carry out one of those activities. A single process such as employee onboarding usually has several procedures, one for each task that needs a standard method, while simple activities in the same process may need none.
How does ISO 9001 define a process and a procedure?
ISO 9001:2015 uses the vocabulary in ISO 9000:2015, which defines a process as a “set of interrelated or interacting activities that use inputs to deliver an intended result” and a procedure as a “specified way to carry out an activity or a process”. Its note adds that procedures can be documented or not, so a written procedure is a choice. ISO 9000 has a 2026 edition, so check the current wording before an audit.
Where do standards and guidelines fit with policies and procedures?
Many organizations, especially in IT and security, use four levels. A policy states the rule, a standard sets the specific mandatory requirements that support it, such as minimum password settings, a procedure gives the steps to comply, and a guideline offers recommended practice that people may adapt. Standards are mandatory; guidelines are advice.
What does “policies and procedures” mean?
Policies and procedures is the usual name for an organization's set of rules and the step-by-step instructions for following them. Policies state what is required and why, such as how expenses are approved; procedures say how to do the work, such as how to submit an expense claim. Together they are often kept as a policies and procedures manual.
Can a policy and its procedure live in one document?
For a small team, yes, as long as the rule and the steps sit in clearly separate sections. Split them once different people approve each part or the steps change often. Otherwise every update to a screen or form needs a policy sign-off, the steps stop being updated, and readers stop trusting the whole document.
Is an SOP a process or a procedure?
An SOP is a procedure: a standard operating procedure gives the agreed steps for one routine task, with roles, checks and exceptions. Some companies also call broader process documents SOPs, which blurs the line. Check what the document answers: if it tells one role how to do one task, it is a procedure, whatever its title says.
Who should own policies, processes and procedures?
A policy needs an owner with authority over its subject, such as the head of HR, finance, security or legal. A process needs a process owner who answers for the end result across teams. A procedure is best owned by the lead of the team that does the task and drafted by the person who does it most reliably.

