Engineering and architecture
Commissioning reports and functional test records from MEP firms
By SourceX Editorial · Updated
Short answer
A commissioning report documents whether building systems were verified against the owner's requirements, backed by functional performance tests and a Cx issues log that trace each deficiency to its fix and retest. For MEP firms these are structured problem-to-resolution records, but ownership depends on the firm's contract role, and owner-sensitive facilities should be excluded.
Key takeaways
- The Cx issues log and functional test records are the most structured part of a commissioning record set.
- A useful record links a test step, the observed result, the deficiency, the responsible party, the fix and the retest.
- Ownership depends on the contract role: owner-hired commissioning authority, engineer of record or contractor-side commissioning.
- Trend data and building automation exports often belong to the owner, even when the firm collected them.
- Data centers, secure sites, laboratories and patient-care areas are usually excluded from any external use.
What is in a commissioning report?#
A commissioning report is the record that building systems were checked against what the owner asked for, and of what happened when they fell short. It typically draws together the owner's project requirements, the basis of design, the commissioning plan, pre-functional checklists, functional performance tests, the issues log, training records and recommendations for ongoing operation.
For an MEP firm, the report itself is often the least distinctive part. The value sits underneath it, in the test procedures, the trend logs reviewed, the deficiencies found and the retests that closed them. Those records show how systems actually behaved at startup, not how they were drawn. Owners often receive the summary report and systems manual, while the firm keeps the working files that produced them.
The anatomy of a functional test record#
A functional test record follows a sequence from test to resolution. Each element is useful on its own; linked together, they form a complete problem-to-resolution chain that shows expert diagnosis from start to finish.
| Record element | What it contains | Why it is useful |
|---|---|---|
| Test procedure | System, sequence step, test conditions and method | Shows how an expert designs a check |
| Acceptance criteria | Expected response, setpoints and tolerances | Defines what correct operation looks like |
| Observed result | What happened, with readings or trend excerpts | Real system behavior, not design intent |
| Deficiency entry | Description, location, system and severity | A labeled fault example |
| Responsible party and fix | Who was assigned and what they changed | Links the fault to its cause and correction |
| Retest | Repeat of the failed step and the new result | Confirms whether the fix worked |
| Closure | Acceptance by the commissioning authority or owner | Marks the end of the chain |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Why the Cx issues log is the core record#
The Cx issues log is the core record because it is already structured as problem, owner, action and status. Each entry links a symptom, such as a valve hunting or an economizer that will not modulate, to a diagnosis, a responsible trade and a verified resolution.
That structure is what AI developers working on building operations, fault detection and diagnostics, or maintenance support look for. It records expert diagnosis in plain language, tied to a specific system and to a confirmed outcome.
Logs are only as good as their closure discipline. Entries closed without describing the fix, or left open after turnover, lose most of their value. Requiring a resolution note and a retest reference on every closed item produces records that are far more usable later, for the firm's own lessons learned as much as for anyone else.
Where commissioning records live inside an MEP firm#
Commissioning records at an MEP firm are usually spread across several places, and the first job is finding which ones hold linked chains rather than isolated forms.
Scanned forms with handwritten readings are the hardest to use, because the readings must be transcribed before they connect to anything. Platform records with status history are usually the easiest place to start.
- Commissioning software platforms: issues logs, checklists and test forms with status history.
- Spreadsheets on the file server: issues logs and test matrices from older or smaller projects.
- Scanned PDFs: field-completed functional test forms with handwritten readings.
- Building automation exports: trend data and alarm histories pulled during testing.
- Email and meeting minutes: commissioning meetings where deficiencies were assigned and debated.
- Final commissioning reports and systems manuals delivered at turnover.
Who owns commissioning records depends on the contract role#
Who owns commissioning records depends on who hired the firm and for what. The same test sheet can be the owner's deliverable on one project and part of the contractor's record on another.
| Contract role | Typical arrangement | Ownership and use position | Check |
|---|---|---|---|
| Independent commissioning authority hired by the owner | Direct owner agreement | Deliverables usually owner-controlled; working records depend on the agreement | Ownership and confidentiality clauses |
| MEP engineer of record providing commissioning | Added service under the design agreement | Follows the design agreement's ownership clause | Whether the added service changed the terms |
| Commissioning under the contractor | Subcontract to the general or MEP contractor | Often follows the subcontract and the prime contract | Flow-down clauses |
| Retro or ongoing commissioning | Service agreement with the building owner | Trend data and findings often owner-controlled | Data use and confidentiality terms |
| Building automation exports | Collected from the owner's system | Usually the owner's data | Treat as owner data unless the contract says otherwise |
Facilities to exclude or handle with extra care#
Some facilities are best kept out of any external use of commissioning records, even where the contract would allow it, because the records describe how sensitive buildings work and fail.
Exclusion is the simpler and safer choice for these projects. For the remaining projects, remove owner names, addresses, equipment tags that identify a site and the names of field staff before any record leaves the firm.
- Data centers and other mission-critical facilities, where system layouts and failure modes are security-sensitive.
- Government, defense and other secure facilities.
- Hospitals and patient-care areas, where records can touch clinical operations.
- Laboratories and pharmaceutical facilities with confidential processes.
- Any project covered by a nondisclosure agreement or a client security requirement.
- Buildings where trend data could reveal occupancy or operating patterns of identifiable tenants.
Illustrative: an MEP firm reviews its commissioning archive#
Illustrative: a fictional MEP engineering firm provides commissioning on its own designs and as an owner-hired commissioning authority on others. Issues logs for recent projects live in a commissioning software platform; older ones sit in spreadsheets on a file server, and functional test forms are scanned PDFs with handwritten readings.
The CEO asks which records could ever be used outside the firm. The review finds that platform-based logs carry full closure notes and retest links, while the spreadsheet logs often stop at the assignment step. Owner-hired projects for a university and a data center operator are excluded on contract and security grounds. Engineer-of-record commissioning on private office projects, under the firm's standard agreement, moves to a rights review.
The firm also changes its procedure so that every closed issue needs a resolution note and a retest reference, starting with current projects.
How SourceX approaches commissioning records#
SourceX approaches commissioning records as operational problem-to-resolution data. Under the SourceX Enterprise Data Value Framework, linked test and issue records rate well on human-generated signal, domain expertise and AI utility, while owner identifiers and site details add privacy burden and preparation cost.
A package follows the SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, with the firm approving each step. The SourceX Evidence Packet records the contract role and rights basis for every project included, and nothing is shared during the initial fit check.
Frequently asked questions
Are building automation trend logs part of the commissioning record?
Trend logs reviewed during commissioning are often attached to test results, but the underlying data usually comes from the owner's building automation system. Treat raw trend data as the owner's unless the contract says otherwise, and keep only the excerpts and findings the firm itself produced.
Do retro-commissioning projects count?
Yes, and they often produce the richest issues logs, because existing buildings accumulate faults over time. Ownership usually follows the service agreement with the building owner, and trend data is typically owner data, so the rights review matters as much as it does for new construction.
Should equipment manufacturer and model names be removed?
Not necessarily. Manufacturer and model information often makes a fault record more useful, because it ties a symptom to a type of equipment. Remove anything that identifies a site, such as unique equipment tags tied to a building, and check client confidentiality terms.
Do we need owner consent to use commissioning records?
Sometimes. Where the owner controls the deliverables or the contract restricts project information, consent may be the only route. Where the firm's working records are its own and confidentiality terms allow de-identified use, consent may not be required. Counsel should decide project by project.
Are pre-functional checklists worth keeping in a package?
They add context but less signal than functional tests and issues logs, because most items are simple confirmations. Keep them where they explain a later deficiency, such as a missed installation step that caused a failed test, and leave routine pages out.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.