Follow the result across organisational boundaries
An equipment hire company has separate sales, workshop, transport and accounts teams. Each team meets its local target, yet customers sometimes receive machines without the correct accessories. Sales confirms the booking, the workshop prepares a machine and transport delivers what is waiting. The failure occurs in the connection between those activities.
QMS processes are about how work produces results and how those results connect. Clause 4.4 is the familiar reference used for this subject. Exact 2026 subclause text and documentation duties must be checked in the official standard. The requirements overview explains the wider system; this article offers a practical process analysis method.
Define the intended result before drawing boxes
For the hire company, a useful result is an available, suitable machine with agreed accessories, delivered when needed and ready for the customer’s intended use. That is more informative than complete the dispatch form. A form may support the result, but it is not the whole purpose of the work.
Identify the information and resources needed to achieve that result. These may include the customer’s application, equipment capability, availability, inspection status, accessory compatibility and delivery arrangements. Missing or unreliable inputs can undermine the outcome even where employees perform their assigned tasks correctly.
Choose a boundary that lets the organisation manage the relevant decisions. A booking to handover process might cross several departments. A maintenance process might provide a dependable machine to that flow. There is no need to make every clause heading a separate business process.
Examine handovers as working agreements
At a handover, one activity produces something another activity depends on. Sales provides an agreed booking. The workshop needs enough information to select and prepare the correct equipment. Transport needs a complete, identifiable load and usable delivery instructions.
Ask what the recipient considers acceptable. A booking marked confirmed can still omit a critical accessory. A machine marked ready can still lack evidence of a completed check. Clarifying these criteria helps prevent teams interpreting the same status differently.
Then examine exceptions. What happens when the requested machine is unavailable, an accessory is returned damaged or the customer changes the delivery address? A process should make the required decision and responsible authority clear before work proceeds on an unsupported assumption.
Assign ownership that matches the process
A process owner needs to understand the intended result and the interfaces affecting it. This does not necessarily mean supervising every employee involved. It does mean having a workable route to resolve obstacles and escalate decisions beyond local authority.
In the hire company, an operations manager might coordinate booking to handover performance while sales and workshop managers retain direct responsibilities. The arrangement should explain who can change a control and who decides when a customer commitment exceeds current capability.
Test ownership with a recent problem. Who identified the incomplete load, who could stop dispatch, and who ensured the booking information was corrected? If each team points to another, the responsibility arrangement needs attention even if the organisation chart looks complete.
Select controls according to what can fail
A control should address a credible failure mechanism. Scanning accessories against the agreed booking may reduce selection errors, but it will not correct an incomplete original booking. The process may also need a clearer needs assessment and a way to approve substitutions.
Consider people, information, equipment and external contributions together. A transport provider may deliver accurately while the company’s load identification remains ambiguous. Requiring another supplier certificate would not necessarily address the problem.
The support article examines the conditions people need to work reliably. Process controls and supporting resources should reinforce one another rather than become separate lists maintained by different departments.
Use information that describes the whole result
Local measures can encourage undesirable tradeoffs. Sales might maximise confirmed bookings while the workshop struggles with unrealistic turnaround promises. Transport might report punctual departures while customers receive incomplete equipment. Select information that helps management see the complete service.
A useful review could compare complete first deliveries, substitution frequency, readiness delays and customer reports. Define the measures carefully and investigate conflicts. A single overall percentage can conceal a recurring problem in one type of equipment or one delivery arrangement.
The APG Processes paper offers historical guidance on examining interactions and performance through a process approach. It belongs to the 2015 collection and is advisory. Its examples can inspire questions but should not be converted into a compulsory 2026 process map format.
Make the description useful to the people involved
A map, workflow, short description or existing software view can support understanding. Choose a form that exposes the decisions and interfaces that matter. A diagram with dozens of symbols may be less useful than a concise explanation that employees can apply under pressure.
Walk a representative booking through the description with sales, workshop and transport staff. Then choose a changed booking and check whether the same description explains the exception. Revise the description where it hides an important decision or implies a control that does not exist.
A useful process model helps the company see why an incomplete accessory set reached the customer and where a proportionate improvement belongs. Its value lies in better control and clearer decisions, supported by the official requirements rather than by the appearance of a particular diagram.