Test report (protocol): required contents and how to stop filling it by hand

In a testing laboratory, a noticeable share of working time goes not to the tests themselves, but to documentation. The test report (protocol) is the central document of that work. Any engineer who has copied research results from working notes into a blank form knows the cost of a mistake: an inaccurate value — and a finding from the assessor, negotiation with the client, lost time.

This article covers what matters for the test report: how it differs from an act and a conclusion, and concrete ways to automate drafting. It is written so a newcomer can understand the structure, and an experienced engineer can take away a checklist of required sections and a review of typical form mistakes.

Test report, act, and conclusion — the difference

These documents have different purposes, and mixing them costs labs time and audit findings. The test report, act, and conclusion are often treated as interchangeable. In practice each records different information and carries different legal weight. For conformity assessment against Customs Union technical regulations, that distinction is essential.

Test report: the primary document

A test report contains the results of specific tests performed against a specific method. It includes laboratory details, sample description, test conditions, measurement methods, obtained values, and an uncertainty evaluation. The report answers: “What was tested, how, and what was obtained?”

Its key property is traceability of every value back to a primary record. Unique number, test date, product name, measuring-instrument details, responsible signatures — all required elements. General drafting requirements come from ISO/IEC 17025 (GOST ISO/IEC 17025 in Russia), and competence of the testing laboratory is assessed against it for accreditation. The official standard text is available from the national standards body.

When an assessor visits, they take the report and cross-check it with records. Not the conclusion, not the act — the report, because it is the primary document the whole conformity system rests on.

Act of testing: fact without detail

An act records the fact: tests happened, samples were received, work was done. It usually contains neither methods nor measurement results. An act may record handover of construction materials, without strength values.

Using an act instead of a report fails when organizations try to use it for product certification. Certification bodies do not accept it: they need a full test report.

Conclusion: expert opinion

A conclusion is the next level. It states conformity: whether the product passed. It relies on the report but adds expert interpretation. Certificates of conformity may be issued on that basis.

That is why hierarchy matters: the report is primary. Without a correct test report, the conclusion has no foundation, and certification loses its evidence base.

Required elements of a test report

What must a test report contain to survive scrutiny? The ISO/IEC 17025 baseline is the same for accredited laboratories. Drafting rules apply to testing centres of any profile — chemical to construction.

Laboratory details

Organisation name, legal address, accreditation certificate number and validity, contacts, phone, legal-entity tax ID. Without these the document cannot be checked in the accreditation register, so it is unfit for conformity assessment. Optionally: scope of accreditation and approval date.

Client information

Who ordered the tests: company name, details, contacts. A report without the client’s stated purpose cannot support conformity assessment against Customs Union technical regulations. Where needed, also the client’s application for work.

Object of testing

Full sample information: product, batch or unit, marking, sampling date, condition on receipt. For submitted samples — delivery method and conditions. The more precise the sample description, the more reliable the results.

Reference to the test method

The report must identify the normative documents used. “By the standard method” is not enough — exact number and year are required. ISO/IEC 17025 demands unambiguous method identification.

Test conditions

Temperature, humidity, pressure, specific measuring instruments — everything that affects results. A report without this block will not survive expert review.

Measurement results

The core. Results in the units required by the method, with appropriate precision. A conformity statement is included only when the client or the normative document requires it.

Measurement uncertainty

ISO/IEC 17025 requires an uncertainty evaluation — or a justification why it does not apply. Uncertainty is required for conformity decisions and certification in most cases.

Dates and signatures

Start and end dates, unique report number, signatures of the performer and laboratory head. Without signatures nobody bears responsibility, and the document has no legal force.

What auditors check: data and sources

Full traceability — where a value in the report came from, who entered it, when, from which record — is an ISO/IEC 17025 requirement. The laboratory must produce primary records for any issued report. In practice that is not always possible.

The assessor’s path is simple: take the finished report, look at results, then ask for records. They check values, date, sample number, method name. If any link is broken — a nonconformity is logged.

Where problems appear

Typical case: a technician records results, and two days later an engineer copies them into a report template — and writes 0.034 instead of 0.043. The assessor treats the mismatch as a serious finding, up to suspension of accreditation.

Another case: the template was updated, but staff used an old blank. Worse — changes were made to a finished report with no history kept.

If the lab runs an electronic system where results are pulled from a database and actions are logged, assessors have far fewer questions. If everything rests on manual entry, the audit becomes unpredictable.

Typical mistakes when drafting reports

These mistakes show up often — and can delay assessment or call a whole sample series into question.

Values in the report do not match records. Copying into a template introduces typos; the assessor finds the mismatch.

Outdated document template. The method was revised; drafting still uses the old blank with a withdrawn normative reference or a missing new field.

Missing required fields. No method name, no lab conditions, no sample number, empty instrument fields — ready-made findings.

Unit confusion. The method requires one unit; the report shows another. Conformity assessment becomes impossible.

No change history. Someone edited a finished report; when, why, and on what basis is unknown. For an accredited lab that is a serious nonconformity.

What unites these errors is manual data entry. At a flow of dozens of documents a month, manual checking consumes hours needed for testing itself.

Why manual result entry is a systemic problem

The engineer runs tests and records results. Opens a template, enters data. Uses a calculator. Enters values again. Formats the document. Sends it for signature. Six stages; at each one information passes through human hands.

Drafting one report often takes two to four hours. At dozens of reports a month, drafting consumes a noticeable share of a specialist’s time — time that could go to testing and analysis.

The problem is not people. With manual transfer, errors are statistically inevitable. Double-checking raises labour without removing them. Data live in one place; the report is built in another — with manual copying in between.

How automatic report generation works

Replacing the manual process is what a laboratory information management system (LIMS) is for. Data enter the database, the system calculates by configured methods, and the finished document is assembled automatically.

Where data come from

It starts with a LIMS. Results arrive directly: from instruments via integration, or from electronic sample registration. Each record is tied to a sample, method, date, and responsible person.

Calculations without human transfer

Method formulas live in the system. The LIMS recalculates units, evaluates uncertainty, and forms a conformity statement when that is in scope. People do not re-key formulas. Mistakes are possible mainly at configuration — and can be checked once.

Template chosen by method

Each method has its own layout. The system picks the template and builds the document. When a method updates, the template updates. Old reports stay tied to the previous version; new tests use the current one.

Action logging without extra effort

Who entered data, when, which results entered the calculation — all logged. You can raise the full history of any report from primary data to the finished document. That approach is how WAPP builds laboratory systems, for example.

Before and after: how lab work changes

Drafting time. Manual work often stretches to tens of minutes or hours. After automation the system pulls data, calculates, and builds the document in minutes.

Error count. Data enter the document from the electronic record. Errors do not vanish, but they drop substantially.

Audit readiness. Reports formed in a LIMS are structured and searchable. Prep takes days, not weeks.

Engineer load. Automation removes routine that does not need deep skill but eats hours. Engineers spend time on tests and analysis.

For a live example, see the Spektrokhim project. If you are considering similar changes, the lab automation starting guide walks from process audit to module choice.

Frequently asked questions about test reports

Is there a single approved report form?

No. Content and layout depend on accreditation scope and the method used. ISO/IEC 17025 sets the required elements: unique number, date, laboratory name, sample details, methods, results, responsible persons. The application rules are shared across Russia’s national accreditation system.

Can you correct an issued report?

Yes. The laboratory issues an amendment stating what changed, why, and who decided. The old report is not destroyed — it stays for traceability. With an electronic system, change history is logged automatically.

Must measurement uncertainty be stated?

For an accredited laboratory — yes. It is a direct ISO/IEC 17025 requirement when uncertainty affects conformity assessment. In practice that is almost always.

Can the report be issued electronically?

Yes. An electronic test report has legal force with a qualified electronic signature. Many testing centres already issue a signed PDF; paper is printed only on request. Electronic form is regulated at federal level under the established procedure.

Conclusions

A test report is a document where every value, date, and method reference matters. Three takeaways.

First. Report content is tightly defined by ISO/IEC 17025 and national accreditation rules. Laboratory, client, samples, methods, conditions, results with uncertainty, signatures — all required. Missing a block is an audit finding.

Second. Main errors — typos on entry, mismatch with primary records, outdated blanks, no change history — are a systemic problem of manual drafting, not specialist competence.

Third. Automating report generation removes manual re-entry, cuts labour, and logs the full chain from primary measurement to finished document. See WAPP’s where to start with lab automation and the LIMS section for how report workflows look in practice.