A process connects related activities to an intended result. A procedure specifies the method for carrying out an activity or a process. The distinction helps you decide whether to change the way work is organized, the instructions people follow, or both.
Consider an equipment service request. The process connects intake, assignment, resolution, verification, and closure. A procedure explains how a coordinator checks an incoming request before assigning it. The example below shows how to keep these two descriptions connected when a team changes its work.
Process vs Procedure at a Glance
| Question | Process | Procedure |
|---|---|---|
| What does it explain? | How related activities produce a defined result | The method to use when carrying out the work |
| What should be clear? | Inputs, outputs, responsibilities, and connections between activities | Required information, actions, checks, completion criteria, and exceptions |
| What might represent it? | A process map supported by an agreed scope and ownership | Instructions, a checklist, a diagram, or guidance within a task |
| Who maintains it? | An owner accountable for the process and its interactions | A designated owner of the method, working with the people who use it |
| What shows it worked? | The intended output meets the agreed acceptance criteria | The activity produces an acceptable result using the applicable method |
These are practical distinctions, rather than a rule that a process must always be a large diagram or a procedure must always be a separate document. A procedure can cover an entire process. A process can also be described at several levels of detail.
Define the Process by Its Result and Boundary
Start by naming the result the work must produce and the event that starts it. Then identify the activities, responsible roles, and information needed to reach an acceptable finish. Include connections to other teams rather than stopping the description at a department boundary.
In the illustrative service-request process, the trigger is a submitted request. The result is a resolved request whose outcome has been checked and recorded. Closing a task without checking that outcome would not satisfy the stated boundary.
To set the boundary, list the information needed at intake and the evidence expected at closure. A team should be able to check whether an individual request has reached the intended result, including when it follows an exception path.
Define the Procedure by the Method People Need
A useful procedure gives a suitably qualified person enough information to carry out the activity consistently. Describe the starting information, the required actions and checks, the expected output, and what to do when the normal method cannot be completed.
For example, “check the request” names an activity but leaves its method unclear. Specify which information must be present, where it is recorded, what makes the submission usable, and how an incomplete request is returned.
Oracle’s guide to policies, processes, and procedures also distinguishes the broader activities from the instructions for carrying them out. Agree on your team’s terminology so people can find the guidance they need.
Example: One Process and Its Intake Procedure
Illustrative example: the following service-request design is fictional. It is not a customer case or a product configuration.
The process has five activities: receive the request, check and assign it, perform the appropriate service, verify the outcome, and close the record. An incomplete submission returns to its requester. Unresolved work goes to a designated exception owner.
The coordinator’s intake procedure could be:
- Open the submitted request and confirm that its location, equipment identifier, and problem description are present.
- Check whether the identifier matches the equipment record available to the coordinator. Record a discrepancy rather than guessing which item was intended.
- If information is missing or inconsistent, record the specific question and return the request for clarification.
- If the submission is usable, record the request category and send it to the responsible service role under the agreed assignment rules.
- Confirm that the record contains the intake result and the next responsible role. If no role can be resolved, use the documented exception route.
The process explains how the request reaches a verified outcome. The intake procedure explains one method used along the way. It does not provide equipment repair instructions or establish who has authority to approve expenditure.
Where Policies, SOPs, and Workflows Fit
A policy can set a requirement that the work must satisfy. In the example, a policy might require an equipment identifier before assignment. The procedure explains how the coordinator checks it and handles a missing identifier.
A standard operating procedure, or SOP, documents an agreed method for recurring work. A work instruction may give further detail for a particular tool or activity. The useful level of detail depends on the task and its users; naming a document an SOP does not establish that its method is correct.
A workflow describes the route of tasks, decisions, and handoffs. The intake instructions can appear within a workflow task, while the workflow controls where the request goes next. See workflow vs process for the separate question of task flow and broader process scope.
Decide What Must Change Together
| Proposed change | Review | Acceptance check |
|---|---|---|
| A form field gets a new name | Instructions and references that use the old name | A user can locate the correct field |
| A new team receives some requests | Assignment rules, responsibilities, and intake instructions | Each affected request has an accountable next owner |
| Verification is required before closure | The process route, completion criteria, and verification method | An unresolved request cannot silently count as completed |
| A new instruction version takes effect | Applicable records, guidance, training, and open-work treatment | Users can identify which method applies to their request |
Do not assume that a change is isolated because it edits only a paragraph. A new instruction can require different information or a different decision. Conversely, a changed route can make otherwise accurate instructions point to the wrong team.
Keep the Map, Instructions, and Working System Aligned
Give the process and its supporting instructions stable references and named owners. Link the applicable guidance to the activity where it is used. Record the version and effective date when the method changes, and decide explicitly how open requests will be handled.
Test one normal request and one incomplete request using the revised map and instructions. Ask a person who uses the procedure to explain the next action without help from its author. Check the resulting record against the acceptance criteria. This tests whether the descriptions connect in practice.
For the visual overview, start with business process mapping. For the controlled lifecycle of the instructions themselves, see the guide to DMS workflows.
CMW Lab’s visual workflow builder describes modeling workflow steps with forms, data, and business rules. Evaluate those capabilities against an agreed process and procedure, including the exception tests. Software configuration does not establish that the underlying method is appropriate.
Frequently Asked Questions
Can a process exist without a written procedure?
Yes. Work can happen without a documented method. Decide where documented guidance is needed based on the work, its users, and the consequences of inconsistent execution.
Can one procedure cover a whole process?
Yes. The distinction concerns activities and their method, rather than a fixed number of steps. State the scope so users know whether the procedure covers one activity or the full route.
Should a process map contain every instruction?
Include enough detail to understand the route and decisions. Link to detailed instructions where needed so the overview and task guidance remain usable and can be maintained together.
Bring one real request, its process map, and its instructions to an evaluation of CMW workflow management software.
