---
title: 'Deferred commissioning: price the return visit before the team demobilizes'
url: 'https://piper-ai.com/resources/deferred-seasonal-commissioning-bid-scope'
description: 'Level subcontractor bids for condition-dependent commissioning returns, including attendance, access, evidence and distinct retest obligations.'
contentTypes: [guide]
publishedAt: '2026-11-22T17:58:22.325Z'
updatedAt: '2026-11-22T17:58:22.334Z'
author: 'Ido Gedanken, CEO'
readingTime: 6
---

# Deferred commissioning: price the return visit before the team demobilizes

A winter turnover date does not tell a chief estimator what it will cost to complete a cooling test when suitable conditions arrive. Before carrying a subcontractor's number, identify the unperformed original test, the condition that permits it, who must return, and what the proposal actually buys. Price a stated return scenario and keep unresolved access and repeat-visit assumptions visible.

That is different from pricing a callback after a failed test or a warranty complaint. The same technician may appear in all three cases, but the reason for the visit and the applicable documents can differ. The goal is a defensible carry, not a declaration of who ultimately owes every future cost.

## A completion date can leave an unperformed test

A schedule may show startup, initial testing and turnover in winter, while the commissioning plan identifies cooling verification that needs a later condition. The condition may concern weather, actual load, occupancy, a prerequisite, or a combination. A calendar date is useful for planning, but it does not establish that the specified condition will exist or that every participant can attend.

The [GSA Commissioning Guide, September 2020](https://www.wbdg.org/FFC/GSA/gsa_commissioning_guide_2020.pdf), page 33, describes deferred and seasonal testing in its federal-facility process and calls for clear construction-document requirements because contractor personnel may need to return. This is a public-owner example, not a rule allocating cost on every project. Read the actual commissioning plan, specifications, contracts and proposal qualifications for the job.

For the broader contractor-side participation picture, see [data center commissioning scope in subcontractor bids](https://piper-ai.com/resources/data-center-commissioning-scope-sub-bids). The particular decision here is what happens after the original team has left and the trigger is outside a fixed mobilization date.

## An illustrative winter-turnover comparison

Consider a fictional office project turning over in January. Its fictional commissioning plan says cooling verification remains open until the commissioning provider confirms a suitable operating condition. The mechanical scope calls for the installing contractor and controls technician to support that verification; the equipment supplier's participation is subject to its separate proposal. The engineer and equipment manufacturer establish the actual acceptance criteria and any permitted test conditions.

The fictional mechanical proposal carries $12,000 for one return mobilization, including its technician and travel. It excludes controls attendance. A separate controls proposal carries $3,000 for one scheduled visit. The supplier includes remote startup support in its existing price but quotes $4,000 for one on-site representative visit if required. Neither proposal defines the cost of returning after a cancelled or unsuccessful visit. Facility access is available only during an agreed window, which has not yet been reserved.

If the team confirms that an on-site supplier representative is required, an illustrative base carry for the first return is $19,000: $12,000 mechanical plus $3,000 controls plus $4,000 supplier. This is a scenario, not a market rate. Do not add a second allowance for the supplier's remote support already included in its price. If the approved test needs only that remote support, the $4,000 on-site item is not part of this scenario; confirm coverage and access before removing it.

The consequential qualification is the single mobilization. The documents describe a condition-triggered event, but the quotes buy one attendance window. A suitable day can arrive when the controls technician is unavailable, the facility cannot grant access, or a prerequisite remains open. The team should ask whether the one visit covers a reschedule before travel, an aborted visit after arrival, and another mobilization. Until priced or agreed, those are separate unresolved exposures, not automatically included in the $19,000.

A useful bid clarification gives every bidder the same basis: expected notice, site location, anticipated working window, required participants and equipment, and the treatment of a cancelled or additional visit. Ask for first-visit coverage and separately stated rates or pricing for additional attendance. If the trigger or attendance requirement is unsettled, record an explicit assumption and carry a priced scenario or unresolved allowance according to the estimate's rules. Do not disguise uncertainty as an arbitrary commissioning percentage.

## Separate three reasons for returning

**Deferred original testing** is work in the original testing plan that could not be performed under the necessary conditions. Identify the open test and the agreed trigger. A return for that test may already be included in the original price, excluded, limited to one visit, or otherwise qualified.

**Correction and retest** follows an identified issue or an unsuccessful test. The cost depends on the issue, responsible scope, retest requirements and applicable agreements. An allowance for one deferred test should not silently stand in for an unlimited number of correction and retest cycles. Conversely, do not presume a retest is an extra merely because a second trip is needed.

**Warranty response** addresses a reported problem under the applicable warranty and contract terms. The reported issue may arise during the same season as deferred testing, but timing alone does not turn an unperformed original test into a warranty call. Record warranty dates and obligations from the actual documents rather than assuming when they begin or end.

Keep these categories on separate rows even if one visit serves two purposes. Assign the shared travel only once in the estimate, and retain the basis for splitting or revising it. The team can then discuss responsibility with the relevant parties without losing the practical cost of getting people to site.

## Price the trigger and the return team

The estimator needs more than a list of names. For each party, identify the work window, duration, travel, notice and whether attendance is remote or on site. Confirm whether the quote covers test equipment, consumables, setup and any necessary support from the building operator. If temporary equipment is needed, name its assumed duration and supplier instead of burying it in a generic line.

The trigger and access are linked. If the test needs an operating condition that may occur at short notice but site access requires advance coordination, a single fixed appointment may not be a workable basis. Ask the commissioning provider and operations representative how the opportunity will be identified and communicated, and ask each bidder how its availability and cancellation terms fit that plan. This is a planning question, not a substitute for the engineer's or manufacturer's technical direction.

Check the procurement boundary as well. A supplier may include a remote session but exclude site attendance; the installing trade may include its own labor but exclude controls. Compare the current proposal and its attachments to each required role before deciding which amount is a gap. Obtain a clarification when the documents are silent rather than treating silence as either inclusion or exclusion.

## Track completion evidence across the handoff

Use one register for every outstanding condition-dependent activity. A practical row can contain:

- **Trigger and status:** open test, reason deferred, required condition, prerequisites and who confirms readiness.
- **Party and commitment:** commissioning provider, installing trade, controls, supplier and operator as applicable; proposal revision, included visits and notice terms.
- **Access:** site contact, operating window, permissions and any constraints on occupied space.
- **Evidence:** test identifier, applicable document revision, record to be delivered, recipient and acceptance or issue status.
- **Pricing:** included amount, travel and equipment assumptions, extra-visit rate or unresolved quote, and estimate owner.

At turnover, transfer the register with the open issues and current contacts to the person arranging the return. When conditions are forecast, confirm readiness, access and all attendance together. After the visit, attach the actual record and any open issue; a scheduled visit alone is not evidence that the test was completed or accepted. Update the carry if the approved scope or priced assumptions change, and preserve the earlier basis for reconciliation.

## Compare the return scope before carry

[Piper bid leveling](https://piper-ai.com/use-cases/bid-leveling) compares subcontractor bids with project scope and presents source-linked findings. The estimating team can review the plan and proposal evidence for the return roles, decide which clarifications are needed, and approve the carry. The commissioning team still determines the test requirements and completion evidence for the project.
