How to Use the HVAC Test Report Generator
Fill in project name, address, equipment tested, test date, and the technician and company responsible for the work.
Add a card for every reading taken, categorized as airflow, pressure, temperature, or electrical, with the specific value and unit recorded.
Include any additional context, testing conditions, or observations that belong in the formal record.
Click Generate Report to see a formatted preview organized by category, then export as a PDF to attach to your project file.
Understanding HVAC Test Report Documentation
A pile of readings scrawled on a work order doesn't hold up well as a record months or years later. A formatted test report, organized clearly by category with specific values and units, turns a day's worth of field measurements into something that actually holds value as documentation, whether that's for the client, for a warranty claim, or for your own future reference on a return visit.
What Belongs in a Field Test Report
Beyond project identification, a useful test report organizes readings by category rather than dumping everything into one undifferentiated list. Airflow readings from tools like the airflow measurement calculator or pitot traverse calculator belong together. Pressure readings from a duct blaster test or pressure decay test form their own section. Temperature readings, whether from refrigerant charge verification or coil performance testing, group naturally together, as do electrical readings from motor and circuit checks. The service report generator is a natural companion for the narrative of what was done on the visit.
Detailed vs. Vague Documentation
A note that simply says "airflow good" or "pressure normal" provides almost no value if a question comes up later, since it captures a subjective impression rather than an actual measurement. Specific numbers with units, like "612 L/s measured supply airflow" or "42.5 kPa test pressure held for 10 minutes," give a future reader, including your future self on a callback visit, something concrete to compare against. Write each value with its unit and a space between them, as the NIST guide to the SI recommends (30.2 °C rather than 30.2°C), so a reader never has to guess whether a figure means litres per second or cubic feet per minute. The extra 10 seconds it takes to write down an actual number pays off considerably if the equipment ever needs troubleshooting again.
This Tool vs. the Commissioning Report Generator
The commissioning report generator is built around pass or fail test results for a project handover summary, useful when you need a clean document showing a system passed its required checks. This test report generator instead focuses on compiling raw field readings organized by category, which suits detailed service documentation, troubleshooting records, or as supporting backup data behind a commissioning summary. Many projects benefit from both: a commissioning report for the client-facing summary, and a detailed test report as the underlying record. For the checklist side of a handover, see the commissioning checklist calculator in compliance and codes.
Building a Documentation Habit
The technicians who benefit most from tools like this are the ones who use them consistently, not just on the occasional complicated job. A simple, formatted record of readings taken during a routine service call builds a performance history over time that makes diagnosing a future problem considerably faster, since you have a documented baseline to compare against rather than starting from scratch. The U.S. Department of Energy's Operations and Maintenance Best Practices Guide makes the same case, recommending that equipment be baselined and its diagnostic data trended over time.
Frequently Asked Questions
The commissioning report generator focuses on pass or fail test results for a project handover summary. This test report generator is built for compiling raw field readings organized by category, such as airflow, pressure, temperature, and electrical data, making it better suited for detailed service documentation or supporting data behind a commissioning summary.
A documented test report with specific readings, dates, and technician information provides useful supporting evidence for a warranty claim, though the manufacturer or warranty provider ultimately determines what documentation they require. Keeping detailed field records is good practice regardless of whether a warranty claim ever becomes necessary.
Enough detail that someone unfamiliar with the job could understand what was tested, what was found, and what condition the equipment was in at the time. Vague notes like good or normal without actual readings provide little value if a question comes up months later, while specific numbers with units and context hold up much better over time.
Yes. Add as many readings as needed across any of the 4 categories, whether they came from a single test type or a combination of airflow, pressure, temperature, and electrical checks performed during the same visit.
Related HVAC Tools
Pass/fail summary document
Document TAB results
Field airflow methods
Motor and circuit checks
Superheat and subcooling checks
Verify system performance
Sensible and total capacity
Browse all 20 tools