Process vs Procedure: What Separates Them and How to Document Each

Process vs procedure sounds like a word choice until someone hands a new hire a 60-step “procedure” that runs through HR, IT, payroll, and the hiring manager. The new hire stalls at step 14 because steps 15 to 40 belong to other people.

A process describes the stages, owners, and handoffs that turn inputs into a result. A procedure tells one role how to complete one part of that process. Document each in the format that suits it, and your team can see both the big picture and the next step.

Key Takeaways

 

• A process is a chain of linked activities that turn inputs into a result and cross roles.
• A procedure is the specified way one role completes an activity inside that chain.
• You document a process with a map, a swimlane diagram, or a SIPOC table, and a procedure with numbered steps.
• A process owner answers for the result. A procedure owner answers for the accuracy of the steps.
• The FLOW test tells you which format a piece of work needs.

What Is a Process?

 

ISO 9000:2015 describes a process as a group of linked activities that transforms inputs into an intended result.

The NIST glossary reproduces that idea in the note to its entry for “procedure.” In plain terms, a process answers three questions: what goes in, what happens to it, and what comes out.

A process crosses roles. Hiring, purchasing, client intake, and month-end close each move through several people and often several departments. Since no single person performs the whole chain, a process needs a named process owner. That person answers for the result, tracks performance, and approves changes to the design.

You judge a process by its output. Time to hire, invoice accuracy, and days from referral to admission all measure the whole chain rather than one person’s work.

What Is a Procedure?

 

ISO 9000:2015 defines a procedure as a specified way to carry out an activity or a process. Note the direction in that definition: a procedure serves a process. It takes one activity inside the chain and spells out how a named role completes it.

A procedure has a defined start, a defined end, and numbered steps. It names the role, the system or form, and the record the role leaves behind. A standard operating procedure (SOP) is a procedure you have placed under document control, with a number, a version, and an owner. Our SOP guide covers that format in detail.

Process vs Procedure at a Glance

 

Use this comparison when you can’t tell which document you’re holding.

	Process	Procedure
Purpose	Shows the path from input to result	Tells one role how to complete one activity
Scope	End-to-end, across roles or departments	One activity, one role
Typical format	Process map, swimlane diagram, SIPOC	Numbered steps with a header block
Owner	Process owner, accountable for the result	Department lead or subject matter expert
Measure	Cycle time, error rate, cost, client outcome	Accuracy and completion of steps
Change trigger	New strategy, regulation, or bottleneck	New system, form, or tool
Audit evidence	Shows you designed and control the work	Shows staff follow a set method, through records

How Processes and Procedures Fit Together

 

A single process often contains several procedures. Purchasing, for example, might rely on separate procedures for raising a requisition, approving spend, receiving goods, and matching invoices.

Both sit inside a wider chain of documents:

1. Policy: the rule and the reason
2. Process: the stages and handoffs that deliver a result
3. Procedure: the steps one role follows for one activity
4. Work instruction: the detail for one step
5. Record: the evidence that the work happened

Each layer should point to the one above it. A procedure header that names its parent process tells the reader where the task fits and who to ask when a handoff fails. Our guide to policy vs procedure covers the top of this chain, and our post on SOP vs work instructions covers the bottom.

One Process, Several Procedures: A Worked Example

 

Take employee onboarding. The process map shows four stages.

Stage	Owner	Output
Offer accepted	HR coordinator	Signed offer and new hire file
Accounts and equipment	IT support	Active login, laptop, and access rights
First day	Hiring manager	Completed orientation checklist
Probation review	Hiring manager and HR	Signed 90-day review

The process owner, often the HR manager, tracks one result: new hires who work at full access from day one and pass review by day 90.

Each stage depends on procedures. The IT stage might use this one:

PRO-IT-007: Set Up a New User Account. Owner: IT Support Lead. Parent process: Employee Onboarding.

1. Open the new hire ticket from HR in the service desk queue.
2. Create the user account in the first-last naming format.
3. Assign the access group listed on the ticket for the new hire’s role.
4. Set a temporary password and turn on multi-factor authentication.
5. Record the laptop asset tag on the ticket and close it.

Notice the shift in detail. The process map fits on one page and tells the whole team who holds the work at each stage. The procedure gives IT the exact fields and settings, and HR has no reason to read it.

How to Document a Process

 

Process Maps and Flowcharts

 

A flowchart shows the stages in order, with decision points drawn as diamonds. The NIH Office of Research Services presents process mapping as a visual way to convey the essential details of a process. Its quality office lists uses such as finding bottlenecks at handoff points, spotting duplicate activities, and identifying steps you could automate.

Swimlane Diagrams

 

A swimlane diagram splits the map into horizontal lanes, one per role or department. Each lane holds the work that role owns, and each arrow that crosses a lane marks a handoff. Since NIH names handoff points as places to look for bottlenecks, the lane crossings tell you where to start.

SIPOC Summaries

 

SIPOC stands for suppliers, inputs, process, outputs, and customers. It fits in one table and gives leaders a one-page view of a process before anyone draws the detailed map. Use it to agree on the start point, end point, and result before mapping begins.

How to Document a Procedure

 

A procedure needs less design and more precision. Use a consistent structure:

• A header with the procedure number, title, owner, version, and parent process
• A scope line stating the start and end points
• The role that performs the steps
• Numbered steps, one action each, starting with a verb
• References to forms, systems, and records

Test the draft by handing it to someone who has not done the task and watching them follow it. Our procedure writing guide covers step-writing technique and the anchor sections in depth.

The FLOW Test: Process Map or Written Procedure?

 

Run any piece of work you plan to document through four questions.

F: Finish Line

 

Is the end point a business result or a finished task? “A new hire works at full access from day one” is a result, so map it as a process. “The user account exists” is a finished task, so write it as a procedure.

L: Lanes

 

Does the work pass between roles or departments? If it crosses two or more lanes, you need a process view to show the handoffs. If it stays in one lane, a procedure covers it.

O: Operator

 

Can one person complete the work from start to finish without waiting on anyone? If yes, write a procedure for that person. If they must hand off and wait, the work belongs on a process map, with procedures for each stage.

W: Wording

 

Look at the verbs in your draft. Stage verbs such as “review,” “approve,” “route,” and “escalate” describe a process. Action verbs such as “click,” “enter,” “attach,” and “scan” describe a procedure. A draft that mixes both kinds needs splitting into two documents.

Common Mistakes When Documenting Processes and Procedures

 

• Writing a process as one long procedure. A 60-step document that crosses four departments hides the handoffs and loses its readers. Map the process and split the steps into role-level procedures.
• Writing procedures with no parent process. Staff can follow the steps but can’t see the downstream effect of skipping one.
• Leaving the process without an owner. Each department maintains its own procedure, and no one manages the gaps between them.
• Mapping without measuring. A process map with no cycle time or error measure gives you a picture and no way to improve it.
• Copying the same steps into several documents. Two copies drift apart after the first update. Keep each step in one controlled document and reference it elsewhere; our guide to document control procedures shows how.

If your documents show these problems, The Write Direction’s procedure manual writers can map the process and rebuild the procedures under it.

From Our Client Work

 

Our team documents operations for licensed care providers in Canada and the US. Clients include Ontario children’s residential operators, New Hampshire providers that serve people with intellectual and developmental disabilities under He-M rules, and Georgia child care institutions.

Licensing reviewers in these sectors look at the design of the work and at the evidence that staff follow it. The Write Direction writes the policies, procedures, and forms these clients use to show reviewers both.

Frequently Asked Questions

 

What is the difference between a process and a procedure?

 

A process is a chain of linked activities that turns inputs into a result, and it often crosses several roles.

A procedure is the specified way one role completes one activity in that chain. In the process vs. procedure split, the process shows who holds the work at each stage, and the procedure shows the exact steps.

What is an example of a process and a procedure?

 

Employee onboarding is a process. HR, IT, and the hiring manager each own a stage, and the result is a new hire working with full access.

Setting up the new hire’s user account is a procedure inside it. One IT role follows numbered steps to create the account, assign access, and record the laptop.

Can a process exist without procedures?

 

Yes, for simple or low-risk work. A small team can follow a process map and rely on experience for each stage.

Procedures become necessary once a stage carries compliance risk, involves new staff, or produces errors when people vary the method. Regulated organizations tend to need written procedures for the stages their auditors review.

Should you document the process or the procedure first?

 

Map the process first. The map shows the stages, owners, and handoffs, which tells you which procedures you need and where each one starts and ends.

Writing procedures first tends to leave gaps and overlaps between them. Settle the process vs. procedure split early, then write one procedure per stage that needs one.

Does ISO 9001 require documented procedures?

 

ISO 9001:2015 uses the term “documented information” and leaves much of the decision to you.

ISO’s guidance on the requirement describes it as a documented quality management system rather than a large set of documents, and says each organization decides how much documentation it needs. Check the clauses that apply to your scope.

Get Your Processes and Procedures Documented Right

 

A clear process map shows your team how work moves. Clear procedures show each person how to do their part.

Build both, link them, and you can train new staff faster, find bottlenecks sooner, and pass audits with records that trace back to a design. Our policies and procedures guide shows how the full set fits together.

At The Write Direction, we document your processes and write the procedures, SOPs, and forms that sit under them for organizations in healthcare, residential care, and other regulated sectors across Canada and the US. Book a consultation or email us at [email protected] to get started.