Start with a precise requirement
Quality depends on understanding requirements and translating them into daily activities. A set of documents cannot replace evidence that a process works.
Choose a customer requirement or applicable obligation. Identify the activities that satisfy it, the owners and the acceptance criteria. Check whether resources suit the expected outcome.
Look for observable evidence
Evidence may be a measurement, an inspection record or an accepted result. It must match the scope and remain understandable to a reviewer. Distinguish a written procedure from its actual application.
Address the cause and review effectiveness
When a gap appears, consider its consequences, investigate the cause and check the effectiveness of the action. Closing a line in a spreadsheet does not resolve a recurring problem.
Use the tool below for one priority requirement. The ISO reference describes quality management systems; this article makes no claim of NASCIELIS certification. Discover our quality and performance service.
A tool to use
Requirement–evidence–action sheet: requirement or obligation; process and owner; observable acceptance criterion; available evidence and location; gap and consequence; action, owner and effectiveness check.
A worked example
Before accepting an order, a process checks the need and acceptance criteria. Evidence may be a recorded review followed by a relevant delivery check. If information is missing, the team completes the enquiry before accepting it. The review checks how the process works.
Illustrative situation, unrelated to any client.
A decision question
What observable evidence demonstrates that your priority requirement is actually met today?