Snapcraft Your Commissioning Process: 5 Modern Professional Oversights That Jeopardize Certification

Every commissioning project starts with a clear goal: deliver a system that performs as intended and meets certification standards. Yet, despite good intentions, many teams stumble into the same traps—missing documentation, misaligned expectations, and last-minute scrambles that threaten certification. These aren't failures of effort but of process. In this guide, we walk through five modern oversights that professionals commonly make and show how to correct them before they become costly problems.

1. Who Needs This and What Goes Wrong Without It

Commissioning is not a niche activity. It touches every major construction and retrofit project, from commercial HVAC systems to industrial control networks. The stakeholders who need a robust commissioning process include project owners, general contractors, commissioning agents, design engineers, and facility managers. Each group relies on accurate, timely information to verify that systems operate according to specifications. When the process breaks down, certification—whether from LEED, BREEAM, or local building authorities—becomes uncertain.

The Cost of Disorganized Information

Without a structured approach to commissioning, information becomes fragmented. Test reports get buried in email threads, submittal data lives in separate spreadsheets, and field observations are scribbled on paper. This fragmentation leads to missed requirements, duplicated work, and, ultimately, failed certification audits. A single missing signature or outdated calibration certificate can halt the entire process.

Who Is Most at Risk

Small to mid-sized engineering firms often feel the pain most acutely. They lack the dedicated document control teams of larger organizations, yet they face the same certification standards. Similarly, projects with compressed schedules—common in fast-track construction—are vulnerable because teams skip documentation steps to save time. The irony is that skipping those steps almost always costs more time later in rework and re-testing.

The Ripple Effect on Project Budget

When commissioning fails, the financial impact extends beyond re-testing. Delayed certification can trigger contractual penalties, hold up occupancy permits, and damage a firm's reputation. In one composite scenario, a mid-sized hospital project lost two months of schedule because the commissioning agent couldn't locate the original sequence-of-operations document. The resulting change orders added over $150,000 to the budget—a cost that could have been avoided with better information architecture from the start.

2. Prerequisites and Context Readers Should Settle First

Before diving into the five oversights, it helps to establish a baseline. Effective commissioning relies on three foundational elements: clear roles, a defined information flow, and a shared understanding of certification requirements. Without these, even the best-intentioned teams will struggle.

Define Roles and Responsibilities Early

Every project should have a commissioning authority (CxA) who owns the process. But the CxA cannot work in isolation. The design team, contractor, and facility operator all contribute data and decisions. A common mistake is assuming that the general contractor will handle documentation. In practice, the CxA must define who creates, reviews, and approves each deliverable—from the commissioning plan to the final report.

Establish a Central Information Repository

Modern commissioning generates a huge volume of documents: submittals, shop drawings, test procedures, checklists, and trend logs. Trying to manage these across email and shared drives invites chaos. Teams should agree on a single source of truth—preferably a cloud-based platform with version control and access permissions. This repository becomes the backbone of the commissioning process, ensuring that everyone works from the same data.

Map Certification Requirements to Commissioning Tasks

Certification bodies like the USGBC or BREEAM have specific prerequisites. For example, LEED v4 requires fundamental commissioning of building energy systems, including a commissioning plan, verification of installation, and a systems manual. Teams must map these requirements to specific tasks in their commissioning schedule. A simple spreadsheet that links each certification credit to a test procedure and responsible party can prevent oversights.

Understand the Timeline and Milestones

Commissioning is not a single event; it spans design, construction, and occupancy. The design review phase, for instance, is the best time to catch specification errors. Yet many teams treat commissioning as a post-installation activity. By the time they start, the building is already built, and changes are expensive. Shifting the mindset to early involvement is a prerequisite for success.

3. Core Workflow: Five Oversights and How to Avoid Them

With the foundation in place, we can now address the five specific oversights that jeopardize certification. Each oversight is paired with a corrective action that teams can implement immediately.

Oversight 1: Vague or Missing Commissioning Plan

The commissioning plan is the roadmap. Without it, teams lack direction. A common version of this oversight is a plan that lists general objectives but omits specific tests, acceptance criteria, or responsible parties. The fix is to write a plan that includes a detailed scope of work, a schedule of tests, and a clear chain of approval. Use a template from a recognized source, such as ASHRAE Guideline 0, but customize it for your project.

Oversight 2: Ignoring Information Architecture in Documentation

This is the core insight of our editorial angle. Many commissioning professionals focus on the physical systems—pumps, valves, sensors—but neglect the structure of the information that describes them. For example, naming conventions for points in a BAS (building automation system) are often inconsistent, making trend analysis nearly impossible. The solution is to adopt a standardized naming scheme early, such as the Project Haystack tagging system, and enforce it across all documents and databases.

Oversight 3: Relying on Manual Data Collection

Handwritten test forms and manual data entry introduce errors and delays. In one composite scenario, a team spent three weeks transcribing field measurements into a report, only to discover that the handwriting was illegible on half the forms. Modern tools like mobile data collection apps (e.g., commissioning-specific apps or general forms platforms) allow real-time entry with validation rules. Invest in training for field staff to use these tools effectively.

Oversight 4: Skipping the Systems Manual

Certification often requires a systems manual that describes how to operate and maintain the commissioned systems. Teams sometimes treat this as an afterthought, producing a binder of cut sheets and warranty cards. A useful systems manual includes sequences of operation, control diagrams, troubleshooting guides, and a preventive maintenance schedule. Allocate time during the project to draft and review this manual, not at the end.

Oversight 5: Failing to Close Out Issues

During commissioning, issues are logged and assigned. But without a disciplined close-out process, unresolved items linger. The oversight is not logging issues; it's failing to verify that fixes were implemented and re-testing was completed. Use a formal issue tracking system with status fields (open, in progress, resolved, verified) and assign a responsible party for each item. Hold a weekly review meeting to clear outstanding issues.

4. Tools, Setup, and Environment Realities

Choosing the right tools and setting up the project environment can make or break the commissioning process. Here we discuss practical considerations for selecting software, configuring data standards, and managing team collaboration.

Software Platforms for Commissioning Management

Several commercial platforms are designed specifically for commissioning, such as Commissioning Manager, eCommission, and CxAlloy. These tools centralize checklists, test results, and reports. However, they require upfront setup and training. For smaller projects, a well-structured spreadsheet with conditional formatting and data validation can suffice. The key is to choose a tool that the entire team will actually use—not the most feature-rich option that collects dust.

Data Standards and Naming Conventions

Information architecture is not just about software; it's about how you name and organize data. Adopt a standard like the aforementioned Project Haystack or the Brick Schema for semantic tagging of building data. This ensures that data from different sources (BAS, metering, commissioning tests) can be correlated. Even if you don't use a formal ontology, establish a naming convention for points (e.g., AHU-1.SA-TEMP) and document it in the commissioning plan.

Setting Up the Digital Workspace

Create a shared folder structure that mirrors the commissioning plan. For example, have top-level folders for Design, Submittals, Test Procedures, Field Reports, and Close-out. Within each, use consistent naming: '01_CommissioningPlan_v2.docx' rather than 'final_plan.docx'. Set permissions so that only authorized team members can edit, but everyone can view. Version control is critical; use a platform that tracks changes and allows rollback.

Environmental Considerations for Field Work

Field conditions vary widely. A commissioning agent working on a rooftop in winter needs a rugged tablet, not a laptop. Consider the physical environment when choosing data collection devices. Also, ensure that the digital tools work offline, as many construction sites have limited internet connectivity. Sync data when back online to avoid duplication.

5. Variations for Different Constraints

Not every project has the same budget, timeline, or complexity. The five oversights apply universally, but the corrective actions can be adapted. Here we explore variations for small projects, fast-track schedules, and existing building retrofits.

Small Projects with Limited Budget

On a small project, hiring a dedicated commissioning authority may not be feasible. In that case, the design team or contractor can take on commissioning duties, but they must allocate time for it. Use free or low-cost tools: Google Sheets for checklists, a shared drive for documents, and free tagging standards. Focus on the most critical systems—typically HVAC and lighting controls—and accept that certification may be limited to a subset of credits.

Fast-Track or Accelerated Schedules

When the schedule is compressed, the risk of oversight increases. The solution is to parallelize tasks. For example, start writing the systems manual during construction, not after. Use prefabricated test procedures from previous projects (with modifications) to save time. Hold daily stand-up meetings to track issues rather than weekly reviews. The trade-off is that some documentation may be less polished, but completeness is more important than formatting.

Existing Building Retrofits and Recommissioning

Retrofit projects face unique challenges: existing documentation may be incomplete, and the building is often occupied. Prioritize systems that are being replaced or upgraded. Use the existing BAS trend data to establish baseline performance before changes. For recommissioning, focus on functional testing rather than full documentation, but still log issues and verify fixes. Information architecture is especially valuable here because it helps correlate old and new data.

Large, Complex Projects with Multiple Certifications

For projects pursuing multiple certifications (e.g., LEED and WELL), the commissioning scope expands. Create a matrix that maps each certification requirement to a commissioning task. Use a centralized platform that can generate reports for each certification body separately. The biggest risk is duplication of effort; ensure that one test satisfies multiple requirements where possible. Assign a single point of contact for each certification to avoid confusion.

6. Pitfalls, Debugging, and What to Check When It Fails

Even with careful planning, things go wrong. This section covers common pitfalls in the commissioning process and how to diagnose and fix them.

Pitfall: Incomplete or Inconsistent Test Results

When test results are missing or contradictory, the first step is to check the data collection method. Were the tests performed according to the approved procedure? Was the equipment calibrated? Often, the issue is that different technicians used different criteria for pass/fail. Standardize the acceptance criteria in the commissioning plan and train all field staff on it. If results are still inconsistent, consider re-testing a sample of points to validate the process.

Pitfall: Certification Audit Failures

If a certification audit finds non-conformances, don't panic. Review the audit findings carefully. Common issues include missing signatures on forms, outdated submittals, or insufficient evidence of training. Create a corrective action plan that assigns each finding to a responsible person with a deadline. Use the issue tracking system from the commissioning process to manage these corrections. Most certification bodies allow a grace period to fix minor issues.

Pitfall: Data Silos and Integration Problems

When different systems (BAS, metering, commissioning software) don't talk to each other, data reconciliation becomes a nightmare. Debug by mapping the data flow from sensor to report. Identify where data is lost or transformed incorrectly. The root cause is often a mismatch in data formats or naming conventions. Invest time in aligning these at the start of the project. If the problem emerges later, consider using middleware or APIs to bridge the gap.

Pitfall: Team Turnover and Knowledge Loss

When key personnel leave mid-project, institutional knowledge walks out the door. Mitigate this by documenting decisions and rationale in a shared log. Use a knowledge management tool like a wiki or a shared document that captures design intent, test results, and lessons learned. When a new team member joins, assign a mentor and provide access to the central repository. The goal is to make the process resilient to personnel changes.

What to Check When Certification Is Denied

If certification is denied outright, the first thing to check is the commissioning plan itself. Did it meet the certification body's requirements? Often, the plan was too vague or didn't cover all required systems. Next, review the test reports for completeness. Were all tests performed? Were the results signed off? Finally, check the systems manual—it's a common source of rejection. Engage the certification body early in the process to get feedback on the plan and deliverables before final submission.