Acceptance

How deployment closes and ongoing service begins

Acceptance is not a single meeting. It is the point where the customer, ClimaMind, and any agreed M&V partner confirm that the system is operating inside the approved boundary, that comfort and reliability evidence is reviewable, and that the cadence for ongoing optimization is defined.

This stage assumes on-site deployment has produced a handoff package: validated point map, current operating mode, issue log, and any agreed M&V plan fields. If those inputs are missing, acceptance should wait rather than sign off on assumptions.

Responsibility

Who participates in acceptance

The exact sign-off model varies by contract, but the roles and evidence owners should be explicit before the review window starts.

Customer

Owns business approval, operating constraints, comfort expectations, and the decision to accept deployment or keep it in staged operation.

  • Approve acceptance criteria, comfort and reliability rules, and any savings or M&V thresholds before the review window.
  • Review operator feedback, overrides, issue logs, and excluded operating periods with facility and energy stakeholders.
  • Sign off on go-live acceptance, open items, and the cadence for ongoing optimization review.

ClimaMind

Prepares the acceptance evidence package, leads the technical review, and defines the post-go-live optimization and reporting cadence.

  • Summarize operating mode, control actions, telemetry quality, fallback events, and unresolved items inside the agreed boundary.
  • Present comfort, reliability, and savings evidence against the agreed M&V method when savings claims are part of acceptance.
  • Document sign-off status, excluded periods, and the ongoing service scope after initial acceptance.

Optional M&V Partner

Provides independent review when the commercial arrangement requires third-party confirmation of baseline, savings, or acceptance logic.

  • Review baseline method, measurement boundary, adjustments, exclusions, and uncertainty treatment.
  • Check savings calculations and comfort or reliability pass/fail status against the site-specific M&V plan.
  • Provide independent input for sign-off when the contract or incentive program requires it.

Sequence

How to start acceptance

Acceptance should begin only after the on-site phase has enough operating evidence. The review window can overlap with early supervised operation, but the criteria must be agreed before results are judged.

01

Confirm prerequisites

Verify that the on-site handoff package, operating mode, and any M&V plan fields are complete enough to start a structured review.

  • 01Review the validated point map, current operating mode, commissioning record, and issue log from on-site deployment.
  • 02Confirm that comfort, reliability, and savings criteria were agreed before the reporting or review window.
  • 03Identify open items that must stay excluded from acceptance until they are resolved.

02

Run the acceptance review window

Collect enough operating evidence inside the approved boundary to judge comfort, reliability, control behavior, and savings when applicable.

  • 01Review zone conditions, equipment constraints, uptime, control actions, operator overrides, and rejected writes.
  • 02Track fallback events, stale telemetry, BAS alarms, and maintenance windows that should be excluded.
  • 03Hold periodic review meetings with the customer and SI while the system remains inside the approved operating plan.

03

Evaluate savings and M&V evidence

When savings claims are part of acceptance, judge results against the agreed measurement boundary and site-specific M&V plan.

  • 01Compare reporting-period performance to the approved baseline model and documented independent variables.
  • 02Apply exclusion rules for non-routine events, comfort failures, reliability failures, and incomplete attribution evidence.
  • 03Separate accepted measured savings from directional or site-level observed results when evidence is incomplete.

04

Close sign-off and define ongoing service

Document what passed, what remains open, and how ClimaMind will continue optimization after initial acceptance.

  • 01Issue an acceptance memo with pass/fail status, excluded periods, open items, and approved operating mode.
  • 02Confirm reporting cadence, escalation contacts, and change-control rules for model or boundary updates.
  • 03Transition from commissioning-focused review to ongoing optimization, M&V reporting, and performance accountability.

Criteria

Acceptance criteria we review

The exact thresholds come from the contract and site-specific M&V plan when they exist. These are the default review dimensions ClimaMind uses before sign-off.

Operating boundary

The live system matches the approved deployment package: measurement boundary, write list, limits, fallback behavior, and operator override path.

Comfort

Occupied spaces remain within the owner-approved comfort rule for the review window. Critical spaces such as labs, healthcare, and data centers use site-specific criteria.

Reliability

Equipment trips, safety alarms, BAS communication loss, sensor failures, and unapproved overrides are tracked and excluded when they materially affect the boundary.

Control traceability

Operating mode, commands, BAS acceptance, guardrails, fallback events, and operator actions can be reviewed for the periods under evaluation.

Savings and M&V

When savings claims apply, baseline model acceptance, measurement boundary, exclusions, and uncertainty review are completed before savings are labeled accepted.

Operator readiness

Facility operators know how to pause optimization, override actions, read status, escalate issues, and distinguish advisory from supervised operation.

Long-term service

What continues after acceptance

ClimaMind is designed for ongoing optimization, not a one-time commissioning visit. Initial acceptance closes the deployment phase and starts the operating service cadence.

  • Regular performance review against comfort, reliability, equipment constraints, and agreed savings metrics.
  • Ongoing model and strategy calibration as weather, occupancy, tariffs, equipment changes, or operating modes shift.
  • M&V or customer-readable operating reports on the cadence defined in the site plan, with exclusions and attribution status documented.
  • Issue response for telemetry gaps, fallback events, rejected writes, and operator escalation paths.
  • Change control for point mapping updates, boundary changes, model revisions, and report corrections.
  • Quarterly or agreed optimization review to retire underperforming strategies and expand only where evidence supports it.

Deliverables

What acceptance should produce

The output is a sign-off record and a clear handoff into ongoing service, not a generic completion certificate.

  • Acceptance memo with pass/fail status, approved operating mode, excluded periods, and open items.
  • Comfort, reliability, and control evidence for the reviewed window inside the measurement boundary.
  • Savings summary or directional result when M&V is in scope, with uncertainty and exclusion notes.
  • Agreed cadence for ongoing optimization review, reporting, escalation, and change control.

Related

Related deployment topics

Acceptance intersects with on-site deployment, M&V planning, operator workflows, and fallback behavior.

On-site Deployment

See the handoff package and operating evidence that should exist before acceptance starts.

Measurement & Verification

Review baseline method, measurement boundary, and savings evidence requirements before sign-off.

Operator Change Management

Confirm operators are prepared to review, override, and escalate before acceptance closes.

Fallback & Manual Override

Understand how fallback events and manual overrides are treated during acceptance review.

Long-term Support

See the optional data custody, model optimization, dashboard, partnership, and technical collaboration available after sign-off.

Readiness Blockers

Check common gaps that delay baseline approval, M&V planning, or sign-off.

Back to deployment overview