ISO/IEC 17025 clause 7.7.1: design useful internal validity checks
Clause 7.7.1 requires a procedure for monitoring result validity. The data must be recorded so trends can be detected, with statistical review where practicable. Monitoring must be planned and reviewed, using techniques appropriate to the activities. A check is useful when it can reveal a relevant weakness in the process.
What clause 7.7.1 requires in practice
Clause 7.7.1 is about the laboratory's own internal checks. A procedure must exist for monitoring the validity of results. The data it produces must be recorded so trends can be detected, and where practicable statistical techniques are used to review them. The monitoring is planned, reviewed and covers, where appropriate, a range of techniques.
The standard names examples: reference or quality control materials, alternative instruments with traceable calibration, functional checks of equipment, check or working standards with control charts, intermediate checks, repeat tests or calibrations with the same or different methods, retesting of retained items, correlation between characteristics of an item, review of reported results, comparisons between staff or instruments within the laboratory, and blind samples. These are options, not a compulsory set. The laboratory should be able to explain why its chosen checks suit its methods.
Select techniques for the technical question
The standard's examples include reference or quality-control materials, suitable alternative instruments, functional and intermediate checks, check standards and control charts, repeat work, retained-item retesting, correlations between characteristics, report review, intralaboratory comparisons and blind samples. These are options to consider where appropriate, not an instruction to apply all of them to every method.
Identify what each check demonstrates and what it cannot detect. Repeating a measurement with the same setup may reveal poor repeatability but not a systematic error common to both measurements. A report review may catch unit or transcription errors without proving the underlying measurement was technically correct.
Plan frequency, criteria and ownership
Use method knowledge, scope, workload and performance history to plan monitoring. Establish appropriate acceptance or investigation criteria and identify who reviews the data. The standard does not prescribe a universal daily, weekly or monthly frequency for every technique.
Record enough context to interpret changes, including relevant method, equipment or personnel differences. Use a format that makes trends visible rather than keeping isolated pass/fail entries with no history. Statistical techniques should be applied where practicable and technically meaningful, not added as decoration.
Review the programme as well as the results
Ask whether the selected checks still address current risks. A new method, changed matrix or automated calculation may introduce a failure mode that the previous programme cannot reveal. Review monitoring effectiveness and adjust the programme where necessary.
Connect outcomes with clause 7.7.3. Data outside predefined criteria require action to prevent incorrect reporting. A competent review should consider the affected work and appropriate investigation, not simply repeat the check until a passing value appears.
Why clause 7.7.1 matters to the laboratory
Internal checks are the laboratory's daily proof that things are still working. Between calibrations and external schemes there are many weeks in which an equipment fault, a reagent problem or a changed habit could slip into customer results. Well-chosen checks catch these early, often before any customer is affected, and keep the cost of correction small. They also build a history that helps decide whether a worrying value is a one-off or part of a drift. Poorly chosen checks, such as repeating a measurement on the same setup, give comfort without evidence, so careful design pays off quickly. They also give staff confidence that their work is being supported by data.
How to implement clause 7.7.1
Choose checks for what they can detect, and write down what they cannot. Keep the design visible to the people running the checks, so they understand what each one is meant to catch.
- For each method, list the failures that matter: drift, contamination, calculation slips, operator differences or equipment faults.
- Match each failure to a technique that could expose it, for example control materials for bias or blind samples for operator effects.
- Set a frequency from workload and past performance, and define acceptance and investigation limits before collecting data.
- Plot or tabulate results so changes over time are visible, applying statistical rules where they make technical sense.
- Name a reviewer and a review point, and record what was concluded and what was done.
- Define what happens on an out-of-limit result, including how the original reading is kept and what earlier work is examined.
- Review the check set at least when scope or methods change, and drop or replace checks that never find anything useful.
Two illustrative internal checks
A materials laboratory uses a control material alongside routine work. It retains the results in a form that reveals gradual drift and reviews the possible cause. A sequence approaching a limit can be informative even before a formal failure occurs, depending on the programme's criteria.
A calibration laboratory compares work by two authorised operators under defined conditions. It examines the comparison against a technical expectation and relevant uncertainty rather than declaring agreement because the rounded numbers look similar. The exercise informs competence and process control without replacing other required evidence.
Evidence and common weaknesses
The monitoring procedure, recorded data, planned reviews and resulting actions should form a coherent record. A commercial quality-control software licence is optional. What matters is whether the programme detects meaningful changes and prompts appropriate decisions.
Avoid checks chosen only because they are easy, undocumented changes to limits, discarded failed readings and reviews delayed until the accreditation visit. Also distinguish an internal comparison from proficiency testing; terminology should accurately describe the activity and evidence provided.
Frequently asked questions
Is a control chart mandatory for every laboratory method?
No. Use appropriate monitoring techniques and statistical review where practicable. A chart is useful when it suits the data and technical question, not as a universal formality.
Can we repeat a failed check until it passes?
Repeating work may be part of an investigation, but it must not erase the original result or replace evaluation and appropriate action to prevent incorrect reporting.
Can internal monitoring also inform personnel competence?
Yes, where the check is designed and interpreted appropriately. It can contribute evidence, but does not automatically replace the full competence and authorisation requirements.
Turn this requirement into reliable laboratory practice
Ask Sterling to help review whether your internal checks address the failures that could affect customer results. A laboratory consultation can connect monitoring design, technical review and staff learning within the agreed consulting and documentation work scope.
Build the team's understanding through Method Validation and Verification (ISO/IEC 17025:2017). Discuss the relevant scope, employee learning and agreed access to Effivity ISO & GRC automation software with Sterling; laboratory technical decisions remain with competent, authorised personnel.
ISO/IEC 17025 requirements hub · Result-validity overview · Competence · External comparisons