Start with one changed requirement
Imagine a UAE design-and-build project where a customer changes a material finish after the first design review. The design team updates its drawing and obtains approval, but purchasing still uses an earlier bill of materials and the site team receives a PDF saved before the change. Every department can show activity; the completed work can still be wrong.
This is an illustrative scenario, not a reported LETA client result. Select one real order, project or service where a requirement was clarified or changed. Begin with the customer source—contract, approved specification, meeting record or authorised message—and identify the person who accepted the change and the revision or date that makes it current.
Trace five handovers
At enquiry and contract review, ask how ambiguity was resolved and what the organisation agreed to deliver. At design or planning, check how the approved requirement became a drawing, work instruction or service plan. At purchasing, compare the purchase description and supplier communication with that current design output.
At execution, ask the person doing the work to show which instruction was available at the point of use. At inspection, release or customer acceptance, identify the evidence used to decide that the result met the approved requirement. A signature or system status has value only when it can be connected to the correct requirement and the actual output.
Use one short requirement trace
A practical trace can use six fields: requirement, source and revision, owner, downstream recipients, acceptance evidence, and change record. It may sit in the project system, ERP, controlled spreadsheet or other suitable tool. The aim is not to create a second database; it is to make the decision path visible enough to test.
If the customer change arrived through WhatsApp or email, capture it through the organisation's authorised review and change process before people act on it. The original message may support the evidence, but a private chat should not be the only place where purchasing, production or site personnel can discover the current requirement.
Treat the mismatch as process evidence
If the trace breaks, contain the affected work and evaluate the customer impact first. Then ask why the current requirement did not reach the next decision. A reminder to 'be careful' will not correct uncontrolled access, unclear approval authority, duplicate files or a missing purchasing handover.
This requirement trace is LETA's practical method, not a mandatory ISO form or copied clause text. ISO's public explanation confirms that customer focus, the process approach and continual improvement remain central to ISO 9001:2026, while the current edition strengthens areas including leadership, strategic alignment and informed action on risks and opportunities. Use an authorised copy of ISO 9001:2026 to assess exact requirements for your scope. LETA provides consultancy and readiness support; an independent certification body conducts the external assessment and decides certification.