Functional test reports with clear measurements and follow-up

Write down the question the test is meant to answer. Identify the installation, component, area and function included, and state what is outside the test. A report headed "installation checked" is hard to interpret when several systems or phases are involved. A specific description lets the reviewer understand the boundary without guessing from the photos.

Keep functional testing apart from a visual inspection, an installation check and a defect list. They can support the same project, but they do not provide the same evidence. If your task is only to record a visual observation, say so. Do not use the label "functional test" for a measurement or operating test that was not performed.

Use the project requirements, the relevant instructions and the agreed test procedure to establish what the tester must do. The competent specialist should confirm the conditions, acceptance criteria and any prerequisites. This guide gives you a record structure, not a universal procedure for ventilation, electrical systems or other installations. Technical values must come from the applicable basis.

Reference the instruction and its revision in the report. If the procedure changes, record the change before using the new basis. When a requirement is unclear, get it clarified instead of copying a limit from another project. A well organised report is only useful when its results answer the right question.

Record the date, location, the person carrying out the test and the relevant operating conditions. Note whether the installation was ready for the agreed procedure and whether another activity limited the work. A reviewer should not have to work out from a photo that part of the system was isolated or unavailable.

Where measurements are required, include the value, unit and relevant instrument details under the agreed procedure, plus calibration information when the procedure requires it. Keep the observed result separate from the acceptance decision. A reading and the judgement that it is acceptable are related, but one should not silently replace the other.

Give each test item a clear reference, and record the planned action, the observed outcome and the supporting evidence. If the test has several steps, record each step's result rather than ticking a single box for the whole installation. A short description of what happened often explains more than a photo alone.

For example, a project might ask a competent tester to check an agreed operating sequence. The report would identify the installation, the procedure step, the observed response and the specialist's assessment. That is an example of how to document, not an instruction to carry out a particular test: the project supplies the actual method and criteria.

Take an overview photo that identifies the installation or area, and a detail photo when it adds information. Explain what each photo shows. A photo of an instrument display can be useful, but the value and unit should also be written in the report as readable text, so the photo is never the only way to recover a result.

Leave out unrelated pictures added only to make the report look complete, and follow the project's rules if a photo shows personal information or another company's restricted material. Our guide to photo documentation on site covers what makes a photo usable as evidence.

If the test was not completed, record the reason and the point reached. If it was completed with a result outside the agreed criterion, record that outcome accurately. These are different statuses and may need different decisions. Assign the follow-up to the person or company responsible rather than leaving a general note that somebody should fix it.

Link any corrective action and retest to the original item. Keep the earlier result and add the date, procedure and outcome of the retest. Do not remove a failed reading because the retest passed: the history shows the reviewer the sequence of events and the basis for closing the item.

Check the report against the agreed test list. Confirm that locations, references, units and results are clear, and list any open questions. Ask the appropriate reviewer to assess technical adequacy, and keep a draft awaiting assessment apart from an issued report. Record the issue date and the recipient so later changes can be traced.

A quick review before issue catches a wrong drawing revision, a missing attachment or a result recorded against the wrong item. Correct these without changing the original observation. If a substantive correction is needed, state what changed in the new issue.

A practical functional test report usually covers:

• Project details and installation identification
• The test basis: requirements, instructions and procedure revision
• Conditions on the day, and anything that limited the test
• Results per test item, with value and unit where measured
• Deviations, follow-up and the person responsible
• Retests, linked to the original item

Adapt the structure to the actual task. Keep entries short enough for the site team to record accurately, while preserving the detail the reviewer needs. Try the structure on one representative item before repeating it across a larger assignment.

In Lite Report, the project manager creates the report on the web and gives it a title and a description: for example "Functional test, basement ventilation", with a description of what is tested, where and on which basis. Each test item can then be set up as a structured checklist task with its room, scope, time and the acceptance criteria it must meet, or as a custom control point if you are not using the control plans for your trade.

The person on site carries out each task from their phone with photos, comments and markups. Every photo is stamped with the date, time and GPS position, and every action is recorded in the activity log. A photo of the instrument display or printout goes on the task as evidence, with the value and unit written in the comment. Project material such as the test procedure and the installation instructions is uploaded to the site's documents in the shared project storage, where every report on the site can use it. The registrations are compiled into one PDF report, and reports cannot be deleted.

Lite Report organises the records. It does not supply the test procedure or acceptance criteria, and choosing software does not establish the competence or authorisation the testing itself requires.