Provisional Go-Live Structuring – Use Now, Pay Later
Client needed system use, vendor needed time. Mid-program contract milestone introduced to start operations without transferring risk or releasing leverage.
- Operations commenced with zero commercial risk transfer
- Full leverage retained until formal go-live conditions were met
Use now, preserve leverage, keep the contract intact
The Situation
During a major automation rollout for a large trans-Tasman retail group, the program experienced schedule drift and formal go-live moved beyond the original plan. The system was functional enough to begin operational use, and the client needed throughput to support ramp-up and peak demand planning.
However, traditional go-live mechanisms are typically binary. If the client starts using the system, milestone triggers can activate, payment obligations can move, risk transfer can occur, and commercial leverage can be diluted before delivery is actually complete. Leaving the system idle would have carried its own operational and internal reputational cost. The program needed a structured middle position that allowed beneficial use without prematurely conceding commercial position
Our Role
As Superintendent, we identified that the standard go-live clause structure did not reflect the real operational need or the commercial reality on the ground. We designed and implemented a new contractual milestone: Provisional Go-Live
This milestone created a controlled interim state where the client could operate the system while formal completion mechanics remained protected. The structure was set up to:
- Enable operational use of the system for ramp-up requirements
- Defer formal risk transfer until defined completion conditions were met
- Prevent milestone-based payments from being triggered prematurely
- Preserve commercial leverage and remedies until formal go-live was achieved
- Give structured time for remaining rectification and completion activities without turning the program into an escalation event
The milestone was issued as a governed notice, aligned through the contract administration pathway, and accepted by both parties as a documented mechanism to separate beneficial use from commercial finality.
The Outcome
The client commenced operations without transferring commercial risk. Payment triggers and formal leverage remained tied to defined go-live conditions rather than early usage. The vendor gained the time required to complete remaining works under a controlled framework. Importantly, this was achieved without dispute momentum, without legal posturing, and without damaging the working relationship.
Governance Without Compromise
Provisional Go-Live was not a concession and it was not an informal workaround. It was a contract-led governance mechanism designed for real delivery conditions. It allowed operational progress while preserving commercial discipline, which is the difference between “making it work” and losing control.
Why It Mattered
Most delayed automation programs force one of two bad outcomes: either the client accepts risk early to keep operations moving, or the parties escalate because the contract provides no practical middle ground. This mechanism avoided both. With a defined interim milestone written in black and white, the project remained governable, leverage remained intact, and the program kept moving while completion was finished properly.