Build Operate Transfer Agreement Template and Key Clauses (2026)

What is a build-operate-transfer agreement, and when do you need one? A build-operate-transfer (BOT) agreement is a contract in which a private party finances and builds an infrastructure asset, operates it for a fixed period to recover its investment and earn a return, and then transfers the asset back to the public authority at the end. The name is the lifecycle: build, then operate, then transfer. It is one of the most common ways governments deliver roads, bridges, power plants, ports and water systems without paying the full capital cost up front. You need a BOT agreement when an authority wants a new asset built with private money and run by a private operator for years, but wants to own the asset outright again once the operator has been repaid through usage. The defining feature that sets BOT apart from other arrangements is the transfer phase: the deal is written from day one around the moment the operator hands the asset back, and around the condition it must be in when that happens. BOT is a model within the wider family of public-private partnerships, and it is usually documented through a concession agreement. Its close variants change one letter of the lifecycle: BOOT (build-own-operate-transfer) gives the operator ownership during the term, and DBFOT (design-build-finance-operate-transfer) adds design and financing explicitly. This page focuses on the BOT agreement and its three phases. (Last verified October 2026.) This article is general guidance, not legal advice. BOT projects engage public-procurement, fiscal and sector-regulatory rules that vary by jurisdiction, so have qualified counsel review any agreement before you rely on it. ## The three phases a BOT agreement must get right - Build. The operator finances and constructs the asset to specification by the appointed timeline, with independent certification before it can start earning. Construction risk sits with the operator.

• Operate. The operator runs and maintains the asset for the operation period, earning revenue by tolls or user charges (the user pays) or by annuity or availability payments (the authority pays). Demand risk depends on which revenue model you choose.
• Transfer. At the end of the period, the operator hands the asset back to the authority in a defined condition, free of debt and liens, usually at no cost. The handback standard is what protects the authority from receiving a worn-out asset. ## Build-operate-transfer agreement template Copy the block below and fill the bracketed fields. A real BOT agreement runs to hundreds of pages with technical schedules; this captures the core clauses. ``` BUILD-OPERATE-TRANSFER AGREEMENT This Build-Operate-Transfer Agreement ("Agreement") is made on [DATE] BETWEEN: [AUTHORITY NAME], [address] (the "Authority") AND [CONCESSIONAIRE / OPERATOR NAME], [address] (the "Concessionaire") 1. SCOPE AND STRUCTURE On a build-operate-transfer basis, the Concessionaire will finance, construct, operate and maintain [Project] at [site], and transfer it to the Authority at the end of the Concession Period. 2. CONCESSION PERIOD AND KEY DATES The Concession Period is [N] years from the Appointed Date, comprising a Construction Period ending on the Commercial Operations Date (COD) and an Operation Period to the Transfer Date. 3. BUILD PHASE The Concessionaire will design and construct the Project to Schedule [A] by [date], obtain all approvals, and achieve COD only after the independent engineer certifies completion. 4. FINANCING The Concessionaire is responsible for arranging finance; [any grant / viability gap funding / equity support] from the Authority is set out in Schedule [B]. 5. OPERATE PHASE AND REVENUE During the Operation Period the Concessionaire will operate and maintain the Project to the service levels in Schedule [C] and earn revenue by [collecting tolls / user charges / receiving annuity or availability payments], with the tariff or payment adjustment in Schedule [D]. 6. MAINTENANCE AND MAJOR MAINTENANCE RESERVE The Concessionaire will maintain the asset to the standards in Schedule [C] and fund a major maintenance reserve so the asset meets the Transfer condition at the end. 7. RISK ALLOCATION Construction and operation risk sit with the Concessionaire; demand risk follows the revenue model; change-in-law and force majeure are shared per Schedule [E]. 8. TRANSFER PHASE AND HANDBACK On the Transfer Date the Concessionaire will transfer the Project to the Authority free of cost and free of encumbrances, in the condition and to the divestment requirements in Schedule [F], with residual life of at least [N] years. A handback inspection and defect-rectification period apply before transfer is accepted. 9. PERFORMANCE SECURITY AND PENALTIES The Concessionaire provides performance security of [AMOUNT]; failure to meet service or handback standards triggers penalties or deductions. 10. LENDERS' RIGHTS AND STEP-IN The Authority will enter a direct agreement giving lenders step-in or substitution rights on default (Schedule [G]). 11. CHANGE IN LAW AND FORCE MAJEURE Material change in law or force majeure triggers relief and compensation per clause [X], which may extend the period or adjust revenue. 12. TERMINATION AND COMPENSATION Termination events and payments differ for Authority default, Concessionaire default and force majeure (Schedule [H]). 13. DISPUTE RESOLUTION AND GOVERNING LAW Disputes follow [escalation then arbitration at [seat] under [rules]]. This Agreement is governed by the laws of [jurisdiction]. Signed for the Authority: __________ Signed for the Concessionaire: _____ Name / title / date Name / title / date

- **Build phase (clause 3).** Put construction risk and the obligation to reach COD on the operator, and require independent-engineer certification before revenue starts. This is what protects the authority from paying for an unfinished asset.
- **Operate phase and revenue (clause 5).** Choose the revenue model deliberately. Toll-based BOT puts demand risk on the operator; annuity or availability-based BOT shifts it to the authority. Set out how tariffs or payments adjust over the operation period.
- **Maintenance reserve and handback (clauses 6 and 8).** This is the clause unique to BOT. Require a major maintenance reserve during operation so the asset is not run into the ground, and define the handback condition, divestment requirements and minimum residual life precisely. A handback inspection and defect-rectification period stop the operator from walking away from a degraded asset.
- **Lenders' step-in and termination (clauses 10 and 12).** Lenders fund BOT projects against future revenue, so they need step-in rights and clear termination-payment formulas that differ by cause. Without them the project cannot raise finance. ## Common mistakes to avoid - Vague key dates, so the start of revenue and the transfer obligation become disputed.
- No major maintenance reserve, so the asset is neglected in the final years and handed back worn out.
- Weak handback and residual-life standards, leaving the authority with an asset that needs immediate rebuilding.
- Choosing a toll model where demand is uncertain, putting unbearable demand risk on the operator.
- No lenders' direct agreement or step-in rights, so the project is not financeable. ## A note on jurisdiction BOT frameworks vary by jurisdiction. In India, BOT is a core model used for highways and other infrastructure, documented through Model Concession Agreements maintained by NITI Aayog and line ministries, alongside the hybrid annuity model and viability gap funding, with central projects appraised through Ministry of Finance bodies; there is no single BOT statute. Other jurisdictions run BOT within their own procurement and PPP regimes: the EU under the Concessions Directive and national law, and Singapore, Australia and many US states under their own P3 frameworks. Because the model documents, revenue mechanisms and procurement rules differ so much, the safe approach is to start from the applicable national model concession agreement and procurement regime and say "varies by jurisdiction" rather than assume one template fits all. (Last verified October 2026.) ## Where a contract workspace helps A BOT agreement lives for decades across a main document and many schedules, so the build, operate and transfer terms have to stay aligned, a thin handback standard has to be caught before signing, and the appointed date, COD and transfer obligations have to be tracked throughout. Drafting, reviewing, tracking and governing a build operate transfer agreement can live in one AI workspace tuned to your revenue model and sector, with the clauses linked so phase dependencies and per-clause risk show and the key dates stay in view. [Adira](https://adiralaw.com) is one tool built around that idea of a single workspace for infrastructure contracts like a BOT deal. This template alone is enough to frame a BOT agreement.