Business

Process vs procedure: the difference, with a worked example

Stefan Weiss, Co-Founder & CEO

Stefan Weiss

Process vs procedure: the difference, with a worked example

A process describes how related activities produce an outcome. A procedure describes an agreed way to carry out an activity or part of that process. The distinction helps you decide whether a team needs a clearer view of the whole workflow or more precise instructions for a particular job.

For example, handling a customer change request is a process: receive the request, assess its impact, make a decision, communicate it and keep the record current. Checking whether a submitted request contains enough information can be a procedure within that process.

Neither document replaces the other. Detailed instructions will not resolve an unclear decision owner. A process map will not teach a new colleague exactly how to check a request. Start with the question the reader needs to answer, then choose the level of detail.

Process vs procedure at a glance

Question

Process

Procedure

What does it explain?

How related work reaches an intended result

How to perform a defined activity consistently

Typical boundary

A trigger through to a useful outcome

A specific task, stage or recurring situation

What should the reader understand?

Inputs, activities, roles, decisions and handovers

Prerequisites, actions, checks, exceptions and expected results

Useful presentation

A short narrative, map or combination

Numbered steps with conditions and checks

Example

Handle a customer change request

Check a change request before assessment

Main failure to watch for

Work moves between roles without clear ownership

Readers follow steps without knowing what counts as correct

These are practical working distinctions, not a universal naming hierarchy. Some organisations use “procedure” for an entire cross-team workflow; others reserve it for a narrower task. Agree your vocabulary locally and make the document's purpose clear. A title alone does not establish what the document contains.

What makes something a process?

Look for an intended result and the activities needed to reach it. The ISO guidance on the process approach describes interacting activities that use inputs to deliver an intended result. Inputs and outputs can include information and knowledge, not only physical materials. That makes the idea relevant to office work as well as production. ISO: the process approach in ISO 9001:2015.

For a customer change request, useful process questions include:

  • What event starts the work?

  • Which information must be available?

  • Who assesses cost, timing and other consequences?

  • Who has authority to accept or reject the change?

  • How does the requester learn the outcome?

  • What record allows the next person to understand what was agreed?

Notice that these questions cross role boundaries. A request can be perfectly entered into a form and still wait indefinitely because nobody knows who should assess it. That is a process problem even if the form-entry instructions are excellent.

A process description also needs an end point. “Discuss the change” is an activity; “the requester has received the decision and the agreed scope is recorded” is a clearer intended result. Whether that result has actually occurred still needs evidence.

What makes something a procedure?

A procedure helps its intended reader carry out a bounded activity. It should explain what to do, what to check and what happens when the normal conditions do not hold.

In the change-request example, an intake procedure might tell a coordinator to check the requester, affected service, requested change, reason and required decision date. It would explain how to handle missing information and when a request is ready to pass to the assessor.

The useful detail is the detail needed to perform and verify the task. “Review the request” is too vague if readers do not know which fields matter. A long click-by-click account is also unhelpful when the reader already knows the system and the real uncertainty concerns an approval rule.

If you have already identified the activity and need to write its instructions, use our guide to writing a standard operating procedure. This article focuses on choosing the right boundary before writing more detail.

A worked example: one change request at three levels

The following example is fictional. The roles and rules illustrate a documentation choice; they are not a claim about an actual customer or a prescribed governance model.

Level 1: the process

A client asks a small service team to add a monthly report to an existing engagement. The process begins when the team receives the request and ends when the client knows the decision and the agreed work is recorded.

The account coordinator captures the request. A delivery lead assesses the effort and dependencies. The account owner decides how to respond within their authority, obtaining any additional approval the organisation requires. The coordinator communicates the decision and records the agreed scope or reason for declining.

The process description shows the important interfaces: who receives the request, who supplies an assessment, who decides and who closes the communication loop. It does not need to contain every instruction for using the request form.

Level 2: the intake procedure

The coordinator needs a repeatable way to decide whether a request is ready for assessment:

  1. Confirm the requester and the engagement affected by the change.

  2. Check that the request describes the proposed outcome and the reason for it.

  3. Identify the requested decision date and distinguish it from a promised delivery date.

  4. Check whether an existing request already covers the same change.

  5. Ask for missing information before describing the request as ready for assessment.

  6. Pass the complete request to the named assessor and record that handover.

The expected result is a request that can be assessed, with a clear next owner. It is not an approved change. The coordinator must not turn an acknowledgement into an acceptance or invent an assessor where the process leaves that role unresolved.

Level 3: the work instruction

One task inside the procedure may need more precise help. For example, a new coordinator might need instructions for checking whether a duplicate request exists in the team's actual system.

A useful work instruction would identify the search location, the relevant identifiers, the match to look for and what to do with a possible duplicate. It might include approved screenshots of that system. It would not require the entire change process to be repeated on every page.

The labels matter less than the relationship. A reader should be able to move from the process to the relevant procedure and then to task-level guidance where they need it. Do not create three documents merely to satisfy a hierarchy if one short, clear document meets the need.


Two separate cream cloth trays with an apricot cloth sheet suspended between them, representing a handover between roles.

When the problem is a handover, more detail may not help

Suppose complete requests are entering the queue, but nobody knows whether the delivery lead or the account owner should make the next move. Adding more form-entry steps will not answer that question.

Inspect the handover itself. Name the input, the receiving role, the condition that makes the work ready and the way receipt is confirmed. Check whether the next owner has the authority and information needed to act. If a decision is unresolved, keep it visible rather than hiding it inside plausible instructions.

A process map can make these interfaces easier to discuss. ASQ describes flowcharts as a way to represent a sequence and recommends involving people who do the work when defining and reviewing it. A map is useful when it exposes a decision or gap; decoration alone adds little. ASQ: flowcharts.

How to choose what to document next

Use the current uncertainty as the starting point:

  • “We do not know where this work starts or ends.” Define the process boundary and outcome.

  • “Work keeps waiting between teams.” Examine roles, decisions and handovers across the process.

  • “People perform the same activity differently.” Check whether a procedure needs a shared method and verification point.

  • “A newcomer cannot perform this particular task.” Add the task-level instruction they need, using the actual tools and prerequisites.

  • “The written steps do not match what people do.” Compare current practice with the document and resolve the discrepancy with its owner.

These symptoms can coexist. You may need a short process view plus a few focused procedures. Avoid deciding in advance that every activity needs a separate document or that every difference in practice is an error; some variation may be intentional.


Weeve source reader showing the approved synthetic Pilot planning transcript with speaker names and timestamps.

Use recorded walkthroughs as evidence, then check the work

A recorded explanation can preserve the sequence, reasoning and exceptions an experienced colleague describes. It remains an account of the work. It may omit screen actions, tacit checks or a workaround the speaker considers obvious.

If you use Weeve, select the relevant saved conversation and review the source passage before turning it into a proposed process description. Compare explanations from different roles when the handover is the question. Keep current practice, proposed improvements and unresolved decisions separate. Chat with saved recordings describes the supported source-review workflow.

A useful request is: “From the selected walkthrough, identify the trigger, intended outcome, roles, handovers and exceptions. Cite the supporting passages. Label missing information and proposals instead of filling the gaps.”

Check the result against the source and an authorised walkthrough of the real task. A generated draft does not establish approval, compliance or successful execution. Local chat and optional external providers also have different processing boundaries; choose a suitable mode for the material you are authorised to use.

Keep the levels connected as work changes

Choose an owner for the documentation and a way to recognise the current version. When a role, system or decision rule changes, review the affected process view and the procedures linked to it. Updating one without the other can leave a reader following a valid local step towards an obsolete handover.

Finish by asking someone from the intended audience to explain where they would start, what they would do next and how they would know the task was complete. If they cannot answer, identify the missing decision or instruction before adding more prose.

The next useful action is small: choose one recurring workflow, name its intended outcome and inspect its most troublesome handover. Then decide whether you need a better process view, a clearer procedure or a more precise instruction for one task.