Functional Checkout Record
A blank record for documenting an agreed controls test, its expected and observed results, and any open follow-up.
Blank example record. Agree test steps and acceptance criteria for the specific system before use. No completed test or client result is shown.
The Commission & Verify step checks sequences, data, alarms, trends, integrations, graphics, and operator workflows against the intended result and the submittal. Use one record for each agreed test so the equipment, expected behavior, observations, and open exceptions can travel with the handoff records.
Blank checkout record
Use your browser's Print command for a blank writing sheet. Complete the record only after the test steps, acceptance criteria, and responsibility for the test have been agreed for the specific system.
- Equipment / point ID
- Blank; complete for the agreed test.
- Agreed test
- Blank; complete for the agreed test.
- Expected result
- Blank; complete for the agreed test.
- Observed result
- Blank; complete for the agreed test.
- Date
- Blank; complete for the agreed test.
- Reviewer
- Blank; complete for the agreed test.
- Pass / fail / not tested
- PassFailNot testedBlank; complete for the agreed test.
- Open exception / follow-up
- Blank; complete for the agreed test.
Using the record
- Identify the equipment or point using the same ID as the current project records.
- Write the agreed test and expected result before testing. Reference the applicable sequence or submittal where needed.
- Record what was actually observed, the date, and the reviewer. Leave an unperformed test marked Not tested.
- Record an open exception and its follow-up when an expected result is not met or further work is needed. Keep the completed record with the project handoff.
Energy & Sequence Optimization
Tune sequences, schedules, setpoints, alarms, and trends around actual building operation.
How does this apply to your building?
Tell us about your system and we can discuss how this resource applies.