ISO/IEC 17025 clause 7: control the work from request to report
Clause 7 connects the laboratory's technical decisions from accepting a request through to issuing and, when necessary, correcting a report. It includes eleven main topics. Read them as one workflow: confidence in a final result depends on the request, method, item, records, monitoring and reporting decisions that came before it.
What clause 7 requires in practice
Clause 7 is the operating core of the standard. It follows a job from the moment a customer asks for something to the point where a result is issued, and it continues into the situations where things go wrong. Its eleven topics describe decisions the laboratory has to make and keep evidence of: whether it can and should accept the work, which method is used and how its suitability is shown, how items are sampled and kept intact, how observations are recorded, how uncertainty and result validity are handled, and how results are reported.
It also covers what happens afterwards: complaints, work that does not meet requirements, and the data systems that carry everything. In practice the clause requires connected arrangements. A weak contract review shows up later as an unsuitable method; an untracked spreadsheet change shows up as a wrong report. The outputs are controlled procedures, technical records for each job and reports that a customer can interpret correctly.
7.1: establish what the customer needs before accepting work
Review the request, capability, resources, method and any use of external providers. Resolve differences before work starts and retain the required review records. Tell customers when a requested method is unsuitable or outdated. Changes after work begins need renewed review and communication to affected personnel.
Where a statement of conformity is requested, establish the relevant specification and decision rule. Unless the rule is inherent in the requested specification or standard, communicate and agree it with the customer. This is especially important near specification limits: a numerical result and a defensible pass-or-fail conclusion are not the same thing.
7.2: distinguish selecting, verifying and validating a method
Select methods suitable for the intended activity. Under 7.2.1, verify the laboratory can perform a method to the required performance before introducing it; consider necessary re-verification when it changes. Plan method development and justify, authorise and agree applicable deviations.
Under 7.2.2, validation addresses whether methods are fit for the intended use, including laboratory-developed or non-standard methods and standard methods used outside their intended scope or otherwise modified. Keep the relevant validation evidence. Copying a published method into a procedure does not demonstrate local capability or validate a changed application.
7.3 and 7.4: protect sampling and item integrity
When the laboratory performs sampling for subsequent testing or calibration, it needs a suitable sampling plan, method and records. Decisions about sample selection, location, preparation and conditions can affect the eventual result. Do not treat sampling as an administrative prelude to the technical work.
Items also need unambiguous identification and appropriate transport, receipt, protection, storage and disposition. Record unsuitable conditions at receipt and consult the customer where needed before proceeding. If the customer asks to continue despite a relevant deviation, the report needs appropriate qualification of affected results. Customer agreement does not make an unsuitable item technically sound.
7.5: create records that allow the work to be understood
Technical records need the observations, calculations, identities and other information necessary to understand the activity and factors affecting the result. Record original data when generated and connect it to the task. Changes must remain traceable to earlier data, with the required history retained.
A practical check is to ask a competent colleague to reconstruct a selected job using the records. Missing units, undocumented spreadsheet changes or unexplained overwritten values can prevent reconstruction even when a final report appears complete.
7.6: evaluate measurement uncertainty
Identify significant uncertainty contributions, including sampling where relevant. Calibration laboratories evaluate uncertainty for their calibrations, including those of their own equipment. Testing laboratories also evaluate uncertainty; where rigorous evaluation is precluded by the test method, an appropriate estimation based on method understanding or experience is needed.
This does not mean every result always needs an entirely new calculation. The standard recognises circumstances where established uncertainty and controlled critical factors can support the work. The technical basis must fit the method and use; generic figures copied from another laboratory do not establish that basis.
7.7: monitor whether results remain valid
Plan, record and review monitoring capable of showing trends and concerns. Appropriate internal checks might include reference materials, checks, replicate work or other technically suitable approaches. Comparison with other laboratories, where available and appropriate, includes proficiency testing or other interlaboratory comparisons.
Monitoring needs action criteria and an effective response. Participation alone is not enough if an unsatisfactory outcome is filed without investigating its significance. Use the data to control the activity and prevent incorrect results from being reported.
7.8: report results in a way the customer can use correctly
Review and authorise results before release. Clause 7.8.1 addresses general reporting responsibilities; 7.8.2 covers information common to reports. The following sections address additional needs for tests, calibration certificates and sampling, then conformity statements, opinions and interpretations, and report amendments.
For 7.8.3–7.8.5, check the particular information needed for the service. Calibration certificates include measurement uncertainty and traceability information; test reporting needs relevant conditions and uncertainty where applicable to interpretation or conformity. Sampling information must support correct interpretation where the laboratory is responsible for that activity.
For 7.8.6, document and apply the decision rule behind a conformity statement, addressing relevant decision risk except where the prescribed-rule provisions apply. Clearly identify what the conclusion relates to. Under 7.8.7, distinguish authorised opinions and interpretations from measured results and record their basis. Under 7.8.8, preserve clear links and identification when reports are amended or replaced. Silently overwriting an issued report can undermine its history.
7.9 and 7.10: handle complaints and unsuitable work
Complaints need an accessible, documented handling process, investigation and appropriate communication. Outcomes communicated to a complainant must be made or reviewed and approved by someone not involved in the original activities. That can require an external competent person in a small laboratory.
Nonconforming work needs defined responsibilities and risk-based action. Consider whether work or reporting should stop, the significance of the issue, effects on previous results, notification or recall where necessary, and who may authorise resumption. Where recurrence or wider management-system concerns are indicated, corrective action is needed. Fixing the immediate job and removing an underlying cause are different decisions.
7.11: protect data and information systems
Information systems must support reliable collection, processing, recording, reporting and retention of data. Validate functionality and interfaces before introduction as applicable; authorise, document and validate relevant changes. Protect access and integrity, address failures and check calculations and transfers systematically. Responsibilities remain when systems are managed externally.
The requirement is not a command to buy a particular laboratory information management system. Paper and electronic arrangements both need effective controls suited to their use. A familiar spreadsheet can still create risk when a formula, unit conversion or data transfer changes without checking.
Why clause 7 matters to the laboratory
Clause 7 is where customers actually experience the laboratory. Delays, disputes, disputed pass-or-fail conclusions and reissued reports usually trace back to a decision taken early in the workflow and not recorded. A laboratory that runs the clause as one connected process spends less time on rework and more time on work that is correct the first time. It can also answer a hard question from a regulator or customer by showing the chain of decisions for a single job. For laboratories seeking accreditation, this clause is where assessors spend most of their time, so weaknesses here are the most likely to delay recognition or to attract follow-up.
How to implement clause 7
Map the workflow before improving any single clause, because the value lies in the handovers.
- Draw the path of a typical job on one page, from enquiry to issued report, marking who decides what at each stage.
- Mark the points where a decision could change the validity of the result, such as method choice, item condition or calculation.
- Compare each marked point with the matching topic in clause 7 and note where the laboratory has a clear arrangement, a partial one or none.
- Fix the gaps that sit at handovers first, for example between sales and technical review, or between bench and report approval.
- Pick two or three recent jobs, including one with a problem, and trace them through every stage as a trial.
- Agree who owns the workflow as a whole so changes to one stage are checked against the others.
- Repeat the trace whenever a new service, method or system is introduced.
Illustrative example: one wrong unit travels into a report
A fictional testing laboratory updates a worksheet for a revised method. Raw data are recorded correctly, but a reporting calculation still uses the earlier unit conversion. A quality-control review identifies an unexpected pattern after several jobs have been completed.
The response should look beyond correcting the spreadsheet. The laboratory assesses affected work, determines whether reports need action, checks the change and authorisation arrangements, and considers whether the same issue exists elsewhere. The example connects 7.5, 7.7, 7.8, 7.10 and 7.11. It illustrates why a checklist that treats each clause as an isolated document can miss the real failure.
Evidence to follow during a readiness review
Trace a job end to end and select exceptions as well as routine work. Examine contract review, method evidence, sampling and receipt records, original observations, calculations, uncertainty, validity monitoring and report approval. Then follow a complaint, an amended report and a nonconforming activity to check whether decisions and consequences were addressed.
BPO and software example: a handover that changes a result
An outsourced reporting team transfers laboratory results into a customer format. An automation update changes the treatment of decimal separators, producing a different number in one export. The laboratory checks the data interface, examines affected reports and applies its nonconforming-work arrangements. The provider's role, software validation and transfer checks need to support the laboratory's responsibilities. This fictional example shows a relevant support dependency, not a claim that ordinary BPO operations require laboratory accreditation.
Go deeper into this clause
Explore each numbered part
7.1 · review customer requests before accepting work
Agree what the customer needs, confirm laboratory capability and resolve differences before work starts. This guide covers all contract-review provisions, including external services, unsuitable methods, conformity decision rules, changes and retained discussions. Examples show how an apparently simple quotation can conceal technical requirements that affect the usefulness of the final result.
7.2 · verification versus validation
Distinguish method selection, verification and validation before introducing or changing laboratory work. This guide explains how to establish required performance, assess intended use, control development and deviations, and retain useful evidence. Examples show why a published method, a supplier's claim or a modified calculation needs the right technical evaluation.
7.3 · plan sampling and preserve its evidence
Control sampling performed for later testing or calibration so the result has a defensible starting point. This guide covers the sampling plan and method, selection and preparation decisions, on-site availability and required records. Examples show how sampling responsibility and conditions affect what the laboratory can conclude about an item or wider population.
7.4 · protect test and calibration items
Protect items from transport and receipt through storage, preparation, retention and return or disposal. This guide explains identification, receipt deviations, customer consultation and controlled environmental conditions, with examples showing how item integrity affects the meaning of results and why acknowledging a problem does not remove the need for accurate reporting.
7.5 · make laboratory technical records traceable
Create technical records that explain what was done, by whom and under which conditions, while preserving the history of later changes. This overview connects original observations and calculations with reports and amendment controls, helping laboratory teams build a usable evidence trail rather than retain only the final number sent to the customer.
7.6 · explain measurement uncertainty
Evaluate measurement uncertainty in a way that reflects the laboratory's actual work and significant influences. This guide distinguishes calibration and testing requirements, explains the role of sampling and controlled factors, and connects uncertainty with reporting and conformity decisions. Practical examples help teams build an understandable evaluation instead of copying another laboratory's numbers.
7.7 · monitor whether laboratory results remain valid
Build a planned system for monitoring result validity, combining suitable internal checks with external comparisons where available and appropriate. This overview explains trend detection, review and action when criteria are not met, helping laboratories use monitoring data to control work instead of collecting charts or proficiency-testing certificates without follow-up.
7.8 · issue clear and reliable reports
Issue laboratory reports that customers can interpret and use correctly. This overview connects general reporting controls with service-specific information, uncertainty, conformity statements, opinions and amendments. It explains customer-supplied information and external results, then links to focused guides for each reporting requirement and the evidence behind an authorised release.
7.9 · handle laboratory complaints impartially
Receive, investigate and decide complaints through a documented process that preserves appropriate independence. This guide explains validation, records, communication and review of outcomes by people not involved in the original activities. Examples show how a laboratory can respond constructively without promising that every complaint will lead to a changed technical result.
7.10 · control nonconforming laboratory work
Respond when laboratory activities or results depart from procedures or agreed customer requirements. This guide explains risk-based containment, evaluation of earlier results, acceptability decisions, customer notification or recall where necessary and authority to resume work. It also identifies when the problem must progress into corrective action rather than end with an immediate correction.
7.11 · protect laboratory data and information
Control the data and systems that support laboratory work, whether electronic or paper-based. This guide explains access, functionality, protection, system failures, external hosting, user instructions and systematic checking of calculations and transfers. Examples show why a purchased LIMS or a cloud provider does not remove the laboratory's responsibility for reliable information.
Common nonconformities with clause 7
Findings against clause 7 are often symptoms of a handover that nobody owns.
- Work is accepted by sales staff without any technical review of method or capability.
- A method change is made at the bench with no assessment of its effect on earlier approvals.
- Reports are corrected in one place while the technical record still carries the old values.
- Monitoring results show a trend but nothing links them to report release decisions.
- Complaints and nonconforming work are handled one by one with no look at wider causes.
Frequently asked questions
Is method verification the same as validation?
No. Verification checks the laboratory's ability to achieve required method performance; validation establishes fitness for the intended use where required. The correct approach depends on the method and its application.
Does the customer decide whether a technically invalid result can be issued?
Customer instructions do not remove the laboratory's responsibility for valid work and accurate reporting. Clarify limitations and applicable requirements rather than treating acceptance of a deviation as permission for misleading reporting.
Does clause 7 apply only after a sample reaches the laboratory?
No. It begins with review of the customer request and covers the full technical service, including sampling where performed, reporting, complaints and information management.
Make technical evidence easier to manage
Sterling can help identify gaps across this workflow, develop laboratory-specific arrangements and prepare the team for assessment. Effivity ISO & GRC automation software can support agreed evidence and action workflows; specialist laboratory data-system needs should be scoped separately. Discuss your methods and accreditation scope or build shared understanding with ISO/IEC 17025 awareness training.