What’s the Difference Between Processes and Procedures?
A process shows the breadth of work needed to turn an input into an output. A procedure adds depth by defining how a specific part of that process should be carried out, by whom, and with what controls.
The Revenue Process makes the distinction practical. It may cross sales, the warehouse, and accounting, while separate procedures cover sales orders, pulling inventory, shipping, collections, and cash deposits. That relationship is the key to understanding processes and procedures.
Difference Between Processes and Procedures
The difference between processes and procedures can be summed up as breadth and depth. A process captures the overall flow from input to output. A procedure captures the detailed method for completing part of that flow consistently.
ISO quality-management terminology defines a process as interrelated activities that use inputs to deliver an intended result, while a procedure is a specified way to carry out an activity or process. The practical distinction below applies those definitions to everyday business documentation. See the ISO terminology listing.
| Question | Process | Procedure |
|---|---|---|
| What does it explain? | The end-to-end flow and intended output | The specified way to complete a defined part of the flow |
| How broad is it? | May cross functions and department lines | Usually focuses on a role, task, handoff, or control point |
| What does it contain? | Inputs, activities, outputs, owners, measures, and interactions | Responsibilities, sequence, methods, records, and exceptions |
| Revenue example | Order received through cash collected | Sales order entry, inventory pull, shipping, collection, or cash-deposit steps |
What Is a Process?
A process is a set of interrelated steps followed to convert an input into an output. It encapsulates the overall picture and highlights the most important aspects of your company. A process typically operates at a higher level, may cross department lines, and may contain one or more procedures. It may also refer to procedures from other processes.
A process map depicts the activities, handoffs, inputs, and outputs that make up the process. For example, a Vendor Process may begin with business requirements and selection criteria, move through vendor qualification and approval, and produce an approved vendor record, purchase relationship, and performance review. That input-to-output view keeps the map focused on the whole process rather than the instructions for one task.
Business requirements and selection criteria
Qualify, select, approve, and monitor vendors
Approved records and performance reviews
The Revenue Process
The Revenue Process is one of the core business processes. It starts when sales takes an order. Inventory is pulled, the order is shipped, collections follow, and the merchandise is converted into cash. The process is not complete merely because one department finished its part.
Notice how the Revenue Process crosses department boundaries from sales to the warehouse to accounting. It may intersect with the sales process, inventory process, cash process, and manufacturing process. The related revenue cycle provides additional context for those handoffs.
- Sales orders
- Pulling inventory
- Shipping
- Collections
- Cash deposits
Process Controls and Measures
To manage a process, define the intended output, assign responsibilities, choose measures, and decide what action to take when results do not meet the objective. Clearly defined responsibilities, measures, actions, and operating time frames help establish control. ISO process-approach guidance describes the same management cycle: identify inputs and outputs, monitor performance, compare results with objectives or requirements, and act when correction is needed. See the ISO process-approach guidance.
What Is a Procedure?
A procedure defines the specified way to carry out an activity or part of a process. In business use, a documented procedure normally states who is responsible, what sequence to follow, which method or form to use, what record to retain, and how to handle an exception. A procedure may be written as a Standard Operating Procedure, or SOP, but the label matters less than the clarity of the method.
Procedures support consistent execution, employee training, retained organizational knowledge, and defined control points. A simple process may be described by a single procedure. A more complex process, such as the Revenue Process, may require several procedures because responsibilities change across functions. See what a procedure is before choosing a format or procedure manual template.
From One Process to Five Procedures
The Revenue Process may use one procedure or five individual procedures. The right number depends on functional boundaries, the size of the organization, the type of business, and where critical control points should be placed.
| Process stage | Likely responsibility | Procedure detail |
|---|---|---|
| Sales orders | Sales or customer service | Validate the order, customer, terms, and requested delivery |
| Pulling inventory | Warehouse | Locate, pick, verify, and stage the ordered items |
| Shipping | Warehouse or logistics | Pack, document, dispatch, and confirm shipment |
| Collections | Accounts receivable | Issue invoices, monitor due dates, and follow escalation rules |
| Cash deposits | Accounting | Record receipts, make deposits, and reconcile records |
How Do Processes, Procedures, and Work Instructions Fit Together?
Think of the documentation layers as an organization chart. The process sits at the higher level and shows the connected flow. Procedures add more information about functional responsibilities, objectives, methods, controls, and records. Work Instructions provide even more detail for a specific task within a procedure.
Processes, procedures, and Work Instructions therefore expand in depth as the work becomes more specific. They are related, but procedures and Work Instructions are not the same thing.
Which Should You Document First?
Map the end-to-end process first so the inputs, outputs, owners, and department handoffs are visible. Then write procedures where consistency, responsibility, risk, or a critical control point requires more depth. This sequence helps prevent a detailed procedure from optimizing one task while overlooking the larger business process.
The practical rule is simple: use a process to define the big picture and use a procedure to define how a specific part of that picture should work. When the map is clear, the next step is to document processes and procedures at the level your organization needs.
