Guide

Test records: the paperwork that is actually the product

The test report is the deliverable, not an afterthought: what a defensible record contains, how field notes become submitted reports, why retention is a professional habit, and how sloppy paperwork loses routes.

Ask a new tester what they sell and they will say testing. Ask a water authority what they receive and the answer is a report. Nobody at the cross-connection program watched you bleed the hoses, sequence the valves, or read the gauge. The only artifact of your work that leaves the property is the record you file, and everything downstream, the property's compliance status, the authority's inventory, your own defense if anything is ever questioned, runs on that document. In a very real sense, the test is how you manufacture the report, and the report is the product.

That framing sounds cynical until you follow the consequences. If the report is the product, then report quality is product quality, and a tester with flawless gauge technique and sloppy paperwork is shipping a defective product from a clean factory. This article covers the discipline end to end: why the report carries the value, what a defensible test record actually contains, the chain of custody from field notes to submitted report, retention as a professional habit rather than a chore, and the specific ways bad records cost testers the routes they spent years building.

Why the report is the deliverable

Consider what each party in the transaction actually needs. The property owner needs proof of compliance: a document that says the assembly at their address was tested by a certified tester on a date, and passed. The water authority needs an inventory update: a record that closes the compliance requirement for that assembly for this cycle, in a format their program can file, search, and audit. Neither party needs the test itself, exactly. They need the trustworthy record that the test produces. Your fieldwork is what makes the record trustworthy; the record is what makes the fieldwork worth paying for.

This is why authorities regulate the paperwork as heavily as the procedure. Certification requirements, approved tester lists, and required report forms all exist to make the filed record credible without anyone re-witnessing the work. When an authority requires your credential number on the form, they are attaching your professional standing to the document. When they require gauge identification, they are attaching the instrument's documented accuracy. The form is engineered so that the record can stand alone, and a tester who fills it out casually is undermining the very mechanism that gives their signature value.

It also explains a pattern every experienced tester recognizes: the customers who keep you for years almost never compliment your test technique. They compliment the fact that the paperwork was handled, the deadline never crossed their desk, and the one time an inspector asked for records, everything was there in one email. The gauge work is assumed. The record-keeping is noticed.

What a defensible test record contains

A defensible record is one that answers every question a skeptical reader could ask, years later, without you in the room. Authorities' required forms vary, and their form is always the minimum, but the standard you should hold yourself to is consistent everywhere. A complete record identifies the device, places it in the world, shows the evidence, states the verdict, documents what was done about failure, and identifies the people and instruments involved, with dates on everything.

• Assembly identification: manufacturer, model, type, size, and serial number, exactly as found on the device, not from memory or a prior report
• Location: the service address plus the physical location of the assembly on the property, specific enough that a stranger could walk to it
• Orientation and installation notes where relevant: vault, pit, above grade, interior mechanical room, and anything unusual about the installation
• The service it protects: domestic, irrigation, fire, or process, and whether the assembly serves containment or an internal hazard where the form asks
• Test readings: the actual measured values for each check valve, relief valve, or air inlet the procedure covers, recorded as read, not rounded to what passing usually looks like
• Pass or fail: an explicit determination for the assembly, consistent with the recorded readings
• Repairs: what failed, what was replaced or cleaned, and the retest readings after repair, recorded as a distinct event from the initial test
• Tester identification: your name, certification type and number, and where required your registration with that authority
• Gauge identification: the test kit's make, model, and serial number, with its documented accuracy record, which is commonly required, confirm locally what your authorities expect
• Dates: the test date, any repair and retest dates, and the submission date, each recorded distinctly

Two items on that list deserve extra attention because they are where shortcuts concentrate. The first is readings recorded as read. There is a temptation, on a device that clearly passed, to write down tidy expected numbers rather than the actual gauge values. Resist it completely. Actual readings trend over cycles: a check valve that passed at a strong margin last cycle and a thin margin this cycle is telling you something, and a record full of identical tidy numbers tells a reviewer something too, none of it good. The second is serial numbers read from the device every visit. Assemblies get swapped by other contractors between your visits more often than you would expect, and a report that carries forward last cycle's serial number onto a replaced device is a false record you signed.

The pass or fail determination must also be internally consistent. A report whose recorded readings fail the criteria but whose verdict box says pass is worse than no report: it is documentary evidence of either carelessness or dishonesty, and it is the first thing any auditor, opposing expert, or program manager will look for. Before any report leaves your hands, the numbers and the verdict must agree.

From field notes to submitted report: the chain

Errors in test records rarely happen at the gauge. They happen in transcription: between the device and the notebook, between the notebook and the form, between the form and the portal. Every handoff is a chance for a digit to flip, a serial to migrate from the previous stop, or a reading to land on the wrong line. Professional record-keeping is mostly the discipline of shortening and hardening that chain.

The strongest practice is to capture data once, at the assembly, in the format it will be submitted in. If your authority takes electronic submissions, entering readings directly into the submission tool while standing at the device eliminates the transcription step entirely. If you work on paper in the field, the rule is to complete the record at the assembly, before the hoses are packed: serial read off the plate and written down, readings recorded as the gauge shows them, pass or fail marked while the evidence is in front of you. A record reconstructed in the truck is a record partly invented, and a record reconstructed at the kitchen table that night is fiction with confidence.

Photographs are cheap insurance across the whole chain. A photo of the assembly's data plate, a photo of the installation, and a photo of the gauge at the deciding reading cost seconds each and resolve almost every later dispute: which device, which location, what the instrument actually showed. They also protect you in the specific scenario every tester eventually meets, where a device fails, the owner disputes it, and someone suggests the tester made it up to sell a repair. A timestamped photo of a relief valve opening outside its limit ends that conversation.

Then close the loop the same day. Whatever your submission path, portal, email, or paper, the report should be filed before the day ends and the customer told it was filed. Same-day filing is not perfectionism; it is queue management. A tester with forty unfiled reports has forty chances to miss a deadline, lose a page, or misremember a detail, and the backlog always grows fastest exactly when you are busiest and least able to reconstruct anything. The reports you file the same day are the reports that never become problems.

A workable field-to-filed routine looks like this:

• At the device: read and record the serial from the plate, capture readings as shown, photograph the plate, the installation, and the deciding reading
• Before leaving the stop: verify the record is complete, the verdict matches the numbers, and location notes would guide a stranger
• Same day: submit to the authority in its required format, and archive your own copy with the photos
• Same day: confirm to the customer that the test is done and the report is filed, with the pass or fail result and next steps if it failed
• Weekly: reconcile submissions against your schedule, so anything that bounced or stalled at a portal gets caught in days, not at renewal

Retention: keeping records is a professional habit, not a chore

Submitting the report satisfies the authority. Keeping your own copy, permanently organized, is what makes you a professional rather than a vendor. Authorities and jurisdictions have their own retention expectations, and you should ask each one what they require, but your private standard should be simpler: keep everything, forever, organized by property and by date. Storage is effectively free. The situations where old records matter are not.

Your archive earns its keep in at least four ways. First, history is diagnostic: a device's readings across cycles show drift that a single test cannot, and walking into a mechanical room already knowing this assembly's tendencies is the kind of competence customers can feel. Second, history is protective: if a contamination event, an insurance claim, or a dispute ever touches a property you tested, your dated records and photos are the difference between a documented professional and a name in someone's filing. Third, history is commercial: your archive is your customer database, your due-date engine, and your route map, and every operational system described anywhere in this trade runs on it. Fourth, history is the asset: a testing book with complete records is transferable and auditable, and one without them is just a phone that rings.

Organize the archive around the assembly, not the invoice. Accounting systems file by customer and payment; your professional records should file by property and device, so that the question you will actually be asked, what is the history of this assembly, has a one-folder answer. However you store it, on paper, in spreadsheets, or in software built for testers, apply the same three rules: every record findable by address, every record backed up somewhere a truck fire cannot reach, and nothing ever deleted.

How sloppy records lose routes

Routes are lost through paperwork far more often than through fieldwork, and it is worth being concrete about the mechanisms, because every one of them is preventable.

The report that never arrived is the classic. The test happened, the tester got paid, and the report died in a truck cab, a spam filter, or a portal error nobody checked. The owner finds out when the authority's violation notice arrives, and from their chair the sequence is simple: I hired a tester and I got a violation. No amount of explaining the portal outage restores that relationship, and the property manager who oversees thirty properties does not move one account when this happens. They move thirty.

The record that could not stand inspection is quieter but worse. An authority audits filings, or a new program manager reviews the inventory, and a tester's reports show carried-forward serials, identical readings across dozens of devices, or verdicts that contradict numbers. Authorities talk to certifying bodies, and they control the approved lists that are the trade's marketing channel. A tester removed from a list, or merely known to a program as the one whose paperwork needs checking, has lost the channel that fed the route, and that reputation does not reset quickly.

The unanswerable customer question costs accounts one at a time. A facilities manager asks for three years of test history on a building before a sale, an insurer asks for the fire line assembly's records, a new owner asks what was done about last cycle's failure, and the tester has nothing organized to send. The customer learns, at the exact moment they are evaluating vendors, that their compliance history exists only in your memory. The next tester they hire will be asked about record-keeping first.

And the succession failure ends businesses. A tester retires or gets hurt, and the route, which was real revenue serving real customers, turns out to live in a memory and a box of unsorted carbons. There is nothing to sell and nothing to hand off. The customers scatter to whoever answers the phone next. The difference between that outcome and a book a buyer pays for is not the fieldwork, which was identical. It is the records.

The through-line of all four failures is the same: in this trade, the paperwork is not administrative overhead on the real work. It is the real work, in the only form that outlives the visit. Testers who internalize that, who record at the device, file the same day, keep everything, and treat every report as a document their name has to survive, do not just avoid the failure modes. They become the tester that authorities trust, customers keep, and competitors cannot dislodge, because the thing they are competing against is not a person with a gauge. It is a decade of clean records.

Get the tester's business toolkit

The instrument this trade runs on

Mid-West 845-5 5-Valve Test KitArbiter Mako MK5 Digital 5-Valve KitAcugauge TK Plus 3-Valve KitBAC-FLO-5 Test Kit

Confirm what your jurisdiction's test procedures require before choosing a kit.The kit guide.

Certification facts sourced from ASSE International's published requirements. The full 5000-series reference.