P3 project agreements: how a bid team reviews the schedules, the output specifications and the payment mechanism, read on the Finch West LRT

A project agreement is the contract at the centre of an Ontario P3. The public sponsors sign it with Project Co, and it holds the obligations in its body and the detail in its schedules. This guide by Mirage Metrics reads one: the redacted Finch West LRT Project Agreement that Infrastructure Ontario published after financial close in May 2018. It is a design, build, finance and maintain (DBFM) contract, with five years of construction and 30 of maintenance and rehabilitation. Its 42 numbered schedules separate what must be built and maintained (Schedule 15, Output Specifications), how Project Co is paid during construction and after (Schedules 21 and 20), how deductions are made, how changes are priced (Schedule 22) and how disputes are settled (Schedule 27). When a bid team reviews it, the job is to tie each obligation to the schedule that defines it, the one that pays or deducts for it, and the clause that decides which prevails when they conflict (Section 1.2).

Published
Updated
Reading time
11 min
Written by
Jules Toussaint

Ontario P3 practice, read on one published agreement: the Finch West LRT Project Agreement (execution version, May 2018), its RFP (version 1.0, 2016) and Infrastructure Ontario's value for money report (May 2018). Where the published text is redacted, the page says so. Later agreements differ. Not legal advice.

Who wrote this, and why. Mirage Metrics builds AI agents that read construction documents, in English or French. Mirage has no published deployment on project agreements. Specification review and tender response are workflows the site presents as available. The published construction figures are John Cockerill's 80 to 90% less time on piping takeoff and OCBM's 3 agents in production with 100% of quantities tied to a source drawing. See specification review.

The agreement this guide reads

Everything on this page comes from one published contract, so start with what it covers. The Finch West LRT Project Agreement is made as of May 3, 2018 between Ontario Infrastructure and Lands Corporation, a Crown agent, and Metrolinx, together the "Contracting Authority", and Project Co (Project Agreement, parties). Its recitals describe the system: a maintenance and storage facility, about 10 kilometres of semi-exclusive at-grade guideway in the Finch Avenue West right of way, short below-grade sections, a tunnel of about 0.5 kilometres at Keele Street and an underground station there (Recital A). Financial close was May 7, 2018, 32 months after the request for qualifications. The term is five years of construction and 30 of maintenance and rehabilitation (IO value for money report).

Some provisions took effect at commercial close and the rest only at financial close (Section 2.1). The published version is redacted. Schedules 13 (Project Co Proposal Extracts), 14 (Commissioning) and 15 (Output Specifications) appear as cover pages marked [REDACTED], and so do the amounts and thresholds in Schedule 20 and the performance security requirements in Schedule 25. Even so, the structure, the payment formulas and the procedures are all there, and they are what a bid team reviews first. See how DBFM compares with other delivery methods.

The schedules, and what the bid team takes from each

The body runs to 64 articles, and the schedules hold the detail. The table keeps the ones a bid team works from, with the cross-references the agreement's own text makes between them. It does not say where the schedules conflict. It shows you where to check.

Finch West LRT Project Agreement (May 2018): the schedules a bid team works from. Compiled by Mirage Metrics, November 2026
ScheduleWhat it governsWhat the bid team extractsOwner on the bid teamCross-references in the text
Body, Articles 1 to 64Obligations, risk events, payment, default, terminationDelay, compensation and relief events (Articles 40 to 43), Project Co default (45), limits on liability (57)Legal, bid managerRanked third in Section 1.2(a), after signed amendments and the higher-standard rule
1, Definitions and InterpretationEvery capitalized termThe terms the other schedules rely onLegal"Output Specifications" includes Schedules 15-1 to 15-3 (1.473)
6, Independent Certifier Agreement, with Articles 24 and 25The certifier and completionWho issues the Substantial Completion Certificate (25.3; Schedule 1, 1.648)Construction, commercialA dispute over that certificate goes to Schedule 27, Section 4
10, Review ProcedureReview of Project Co's submittalsDeliverables and review periods to carry in the scheduleDesign, planningItem (xiv) of Section 1.2(a)
11, Quality ManagementQuality plans and auditsBreaches designated as Quality FailuresConstruction, O&MQuality Failures can be designated here (Schedule 20, 1.39)
12, Works Scheduling RequirementsThe Works ScheduleMilestones and the scheduling standardPlanningArticle 22 pairs it with the Works Report of Schedule 33
13, Project Co Proposal ExtractsThe winning proposal's commitmentsWhat the proposal promised, now contractualBid managerRanked last (1.2(a)(xxii)); redacted in the published version
15, Output Specifications: 15-1 Technical Terms and Reference Documents, 15-2 Design and Construction Requirements, 15-3 Maintenance and Rehabilitation RequirementsWhat must be designed, built and maintained, and to what performanceRequirements, the quantities they imply once designed, interfaces, performance criteria with response and rectification timesDesign, estimating, O&M15-3 sets the Help Desk and the Daily Performance Report that Schedule 20 uses (1.15, 1.25); redacted in the published version
17, Environmental ObligationsEnvironmental requirementsEach obligation and its failure categoryEnvironment, O&MQuality and Service Failures can be designated here (Schedule 20, 1.37 to 1.41)
20, Payment MechanismMonthly Service Payments and Deductions in the maintenance termDeduction formulas, failure categories, Failure PointsFinance, O&MDeductions in a month capped at that month's Un-adjusted Service Payment (Part C, 1.2)
21, Construction Period PaymentsPayments during constructionEarned value payments and the substantial completion paymentFinance, estimatingA variation Estimate states its effect on these payments (Schedule 22, 1.6)
22, Variation ProcedureChangesWhat an Estimate must contain, and its 15 Business Day deadlineEstimating, commercialAn Estimate states any amendment it needs to Schedule 20 (1.6)
25, Insurance and Performance Security RequirementsInsurance and securityPolicies by period, insurance cost review, uninsurable risksFinance, riskThe insurance adjustment flows into the Monthly Service Payment (Schedule 25, 7.3; Schedule 20, 1.27)
27, Dispute Resolution ProcedureDisputesEscalation steps and who decides at eachLegalA dispute over a precedence determination is referred here (1.2(d))
34, Contracting Authority Permits, Licences and Approvals; 35, LandsPermits the authority obtains; the landsWhich permits stay with the authority; land accessDesign, planningRanked right after Schedule 1 in Section 1.2(a)
Finch West LRT Project Agreement (May 2018): the schedules a bid team works from. Compiled by Mirage Metrics, November 2026

Source: Finch West LRT Project Agreement, list of schedules, Sections 1.2 and 25.3, Schedules 1, 20, 22, 25 and 27. The owner column is a suggested split, not the agreement's.

Which schedule prevails: Section 1.2

When provisions are ambiguous or conflict, Section 1.2(a) sets the order in which they prevail. Signed amendments and Variation Confirmations come first, for the provisions they amend. Second, "any provision establishing a higher standard of safety, reliability, durability, performance or service shall take precedence over a provision establishing a lower standard". After those come the body, Schedule 1, Schedule 34 (permits), Schedule 35 (Lands), Schedule 27 (Dispute Resolution), Schedule 21 (Construction Period Payments), Schedule 20 (Payment Mechanism), Schedule 15 (Output Specifications), and so on down to Schedule 13, the proposal extracts, which ranks last (Section 1.2(a)).

A provision for a specific part of the project governs that part over a general one (1.2(b)). If the order does not settle the question, either party gives notice and the Contracting Authority Representative decides within 10 Business Days which provision governs, subject to the Dispute Resolution Procedure (1.2(c), (d)). The higher-standard rule is the one to price, because where two schedules set different standards for the same thing, the higher one prevails.

Output specifications, not prescriptive ones

Infrastructure Ontario's value for money method assumes lower costs in a P3 partly because "the use of performance-based specifications in AFP projects allow contractors to consider innovative and alternative ways to deliver a project", compared with traditional delivery "which uses more prescriptive specifications". For DBFM projects, the report adds that the private partner must "meet specifications which ensures the asset is well maintained over the project term" (IO value for money report).

In the Finch West agreement those specifications are Schedule 15, which includes 15-1 (Technical Terms and Reference Documents), 15-2 (Design and Construction Requirements) and 15-3 (Maintenance and Rehabilitation Requirements) (Schedule 1, 1.473). For the estimating team, the consequence is practical: a requirement stated as an outcome carries no quantity. The quantities come from the proponent's own design, so the takeoff follows design development. Each requirement in 15-2 then needs a line saying which design element answers it. The maintenance requirements in 15-3 carry two costs: the work itself, in the maintenance and life-cycle plan, and the deduction risk under Schedule 20.

The payment mechanism and its deductions

This is where an obligation turns into money. During construction, Project Co receives monthly construction period payments based on an earned value method, and a substantial completion payment. During the 30-year term, monthly payments cover the capital and service portions, life-cycle, volume and energy gainshare and painshare, "minus any performance deductions" (IO value for money report). Schedule 20 builds each Monthly Service Payment from the Annual Service Payment, a Service Payment Adjustment and a Lifecycle Payment, less the sum of Deductions, among other terms (Schedule 20, Part B, 1.1).

  • Availability Failures (Part D): vehicle kilometres, passenger facilities (a station or stop that does not meet the Station and Stop Access Standard, 1.52) and rooms, each with its own deduction formula.
  • Quality and Service Failures (Part E): fixed amounts by severity (minor, medium or major), index-linked, with the amounts redacted. Failures are designated in Schedules 11, 15-3, 17 and 20 itself (1.37 to 1.41).
  • Energy Failures (Part E, Section 3), which earn no Failure Points (1.23).

An event is classified when it is reported to the Help Desk (Part C, 2.1). Deductions in a month cannot exceed that month's Un-adjusted Service Payment (Part C, 1.2). Failures also earn Failure Points (Part G), which carry consequences of their own. The agreement provides for warning notices at thresholds that are redacted (Sections 31.3, 31.4). It also provides for replacing a non-performing maintenance and rehabilitation contractor when points over any six rolling Payment Periods exceed further redacted thresholds (Section 45.5).

Illustrative example, invented figures: one obligation traced to its deduction, with invented values

A requirement in Schedule 15-3 carries a performance criterion with a rectification time, invented here as 24 hours, and the event is classified as a minor Service Failure when it is reported to the Help Desk (Schedule 20, Part C, 2.1). Under Part E, 2.2, the Service Failure occurs only if the event is not rectified within that time. Under 2.3, Project Co then gets a further 24 hours. If it misses that too, a further Deduction is made and another period of equal length begins, until the failure is remedied.

The event is reported at hour 0 and rectified at hour 70. Deduction one falls at hour 24, deduction two at hour 48, and the fix lands within the third period, which ends at hour 72, so there is no third. With a minor Service Failure deduction invented at $500 (the real amount is redacted, index-linked under Part B, 5.1), the month carries 2 × $500 = $1,000, plus the Failure Points that Part G attaches to it.

Variations, certification, disputes and insurance

Four more procedures shape a bid: how changes are priced, who certifies completion, how disputes escalate and how insurance works.

Variations (Schedule 22). The Contracting Authority issues a Variation Enquiry (1.3). Project Co answers within 15 Business Days with an Estimate (1.4(a)) and may refuse only on listed grounds (1.5). The Estimate sets out the steps and any effect on the Construction Period Payments or the Scheduled Substantial Completion Date, on the Project Operations and on utilities. It also states any amendment needed to the agreement, Schedule 20 included, and the direct cost to Project Co and each subcontractor (1.6). A Variation Confirmation follows (1.8), or a Variation Directive comes first: a signed instruction to proceed at once, pending the Confirmation (1.1) (Schedule 22).

Certification. The Independent Certifier, appointed under the Independent Certifier Agreement of Schedule 6, issues the Substantial Completion Certificate under Section 25.3 (Schedule 1, 1.648).

Disputes (Schedule 27). A dispute goes first to the party representatives (Section 2), then to senior officers (3). Depending on the dispute, it then goes to the Independent Certifier for certain disputes about the Works and the completion certificate (4), to expert determination (5) or to adjudication under the Construction Industry Council's Model Adjudication Procedure, Fourth Edition (6.3). The last steps are arbitration, on mutual written consent, or litigation (7, 8).

Insurance and security (Schedule 25). The schedule covers insurance from execution through construction and after the Substantial Completion Date (Articles 1 and 2). It also sets a periodic insurance cost review that adjusts the Monthly Service Payment (7.2, 7.3), and a regime for uninsurable risks (Article 8). The performance security requirements are redacted.

How the bid phase ran on the Finch West procurement

Metrolinx and Infrastructure Ontario issued the request for qualifications on September 8, 2015 and prequalified three teams. The request for proposals followed on February 19, 2016, and proposals closed on December 13, 2017 (IO value for money report). The RFP itself sets the mechanics (RFP No. 15-382):

  • Two deadlines. The RFP sets a Technical Submission Deadline and a Financial Submission Deadline (3.1). Technical submissions are scored first and must reach minimum scores, and the financial ones are scored after them (6.3.3, 6.3.5).
  • Addenda. Only an addendum amends the RFP documents, for technical matters until the technical deadline and for all others until the financial one. Addenda go into the data room with an email notice, and each proponent must make sure it has them all (3.7). The data room carries the documents "black-lined" against each addendum (2.4(1)(a)).
  • Commercially confidential meetings. The RFP provides for bilateral meetings on the project agreement and the proponent's suggested amendments, and on design issues, including the proponent's own design (3.4.2). CCM-Design Presentation Meetings are among them. Requests for information (RFIs) can also be commercially confidential (3.2.2).
  • Security. Within three Business Days of being named preferred proponent, the proponent provides an irrevocable standby letter of credit in the amount set in the RFP Data Sheet (9.1(2)).

Where AI helps on a project agreement, and where it stops

The work is narrower than general contract review, and the agreement's structure shows where software can carry it:

  • An obligations register tied to clauses: each requirement with its schedule and section, its owner on the bid team, and the clauses it refers to.
  • A cross-reference check: every reference from one schedule to another, such as Schedule 20's to sections of Schedule 15-3, resolved to the text it names.
  • An addendum-to-addendum change list: what each addendum changed in the agreement and the specifications, read against the black-lines.
  • A list of quantity-bearing requirements: the requirements in 15-2 that become quantities once designed, so takeoff can follow each design submission.

A person decides everything that costs money or carries risk: what a clause means, the price of deduction exposure, the comments to raise in a commercially confidential meeting, and whether to accept a schedule as drafted. AI does not give legal interpretation or price risk. See the tender response workflow, and see the research on AI in P3 preconstruction.

Limits: when this page is not enough

  • One agreement, of 2018. Later agreements by Infrastructure Ontario and Metrolinx, and those of other agencies, use their own forms, schedule numbers and payment terms.
  • Redactions. The output specifications, deduction amounts, Failure Point thresholds and performance security are not in the published text. A bid team reads them in its own procurement documents.
  • Not legal or financial advice. Risk allocation, deductions and disputes need counsel and the lenders' advisers on the signed documents.

For unit price work governed by provincial standards, see the OPSS guide and the BC standard specifications guide.

Questions readers ask

  • A project agreement in a P3 is the contract between the public sponsors and Project Co, the company that designs, builds, finances and, in a DBFM, maintains the asset. On the Finch West LRT it is signed by Infrastructure Ontario and Metrolinx, together the Contracting Authority. It holds the obligations in Articles 1 to 64 and the detail in 42 numbered schedules.

  • Output specifications are requirements stated as what the asset must achieve rather than how to build it. In the Finch West agreement they are Schedule 15, which includes the technical terms and reference documents (15-1), the design and construction requirements (15-2) and the maintenance and rehabilitation requirements (15-3). Infrastructure Ontario's value for money method credits such performance-based specifications with leaving room for alternative ways to deliver the project.

  • On the Finch West LRT, deductions are taken from the Monthly Service Payment that Schedule 20 pays during the maintenance term, for Availability, Quality, Service and Energy Failures. A Service Failure with a rectification time is deducted only once that time has passed, and again for each further period of equal length until it is fixed. Failures also earn Failure Points, which lead to warning notices and remedies.

  • The project agreement itself sets which schedule governs, in an order of precedence. In the Finch West agreement, Section 1.2(a) ranks signed amendments and Variation Confirmations first, then any provision setting a higher standard of safety, reliability, durability, performance or service, then the body, Schedule 1, the permits schedule, Lands, Dispute Resolution, Construction Period Payments, Payment Mechanism and Output Specifications, with the proposal extracts last.

  • On the Finch West RFP, addenda are the only way to change the RFP documents: for technical matters until the technical submission deadline, and for everything else until the financial one. Addenda are posted in the data room with an email notice, and each proponent must make sure it has them all (RFP 3.7). The data room also carries the documents black-lined against each addendum (2.4).

Sources and scope

Checked on . All three documents were read on 9 November 2026, as PDFs downloaded from Infrastructure Ontario's site.

  • Infrastructure Ontario, Finch West LRT Project Agreement, execution version (redacted), dated as of May 3, 2018: parties and Recital A; list of schedules; Sections 1.2, 1.3 and 2.1; Articles 22, 24, 31.3, 31.4, 39, 45.5 and Section 25.3; Schedule 1, 1.15, 1.473 and 1.648; Schedule 20, Parts A to H (1.15, 1.16, 1.23, 1.25, 1.27, 1.37, 1.39, 1.41, 1.52; Part B 1.1; Part C 1.1, 1.2 and 2.1; Part D 2.1 to 2.3; Part E 1.1 to 1.3 and 2.1 to 2.5; Part G); Schedule 22, 1.3 to 1.10; Schedule 25, Articles 1, 2, 7 and 8; Schedule 27, Sections 2 to 8; Schedules 13, 14, 15 and the performance security requirements of Schedule 25 redacted in the published version
  • Infrastructure Ontario and Metrolinx, Finch West LRT Project Request for Proposals, RFP No. 15-382, version 1.0, 2016: 2.4(1)(a) data room and black-lined documents; 3.1 technical and financial submission deadlines; 3.2.2 commercially confidential RFIs; 3.4.2 commercially confidential meetings; 3.7 addenda; 6.3.3 and 6.3.5 scoring and minimum scores; 9.1(2) letter of credit; CCM-Design Presentation Meetings (definition 23)
  • Infrastructure Ontario, Value for Money Assessment, Finch West Light Rail Transit, May 2018: DBFM over 35 years (5 years construction, 30 years maintenance and rehabilitation); performance-based versus prescriptive specifications in IO's method; RFQ September 8, 2015, three teams prequalified; RFP February 19, 2016; proposals December 13, 2017; financial close May 7, 2018, 32 months after the RFQ; earned value construction payments, a substantial completion payment, monthly service payments minus performance deductions

This guide describes the published text of one project agreement for educational purposes. It is not legal or financial advice and does not replace a reading of the documents of your procurement by qualified advisers.

Show us how your bid team reads P3 documents

Leave your work email, then pick a time for a 30-minute call on the documents your bid team reads by hand, from output specifications to addenda. You leave with a written plan: what an agent could prepare, a register, a cross-reference check or a change list, and what stays with your team. No commitment.

We use your email to reply to you and, now and then, to tell you about Mirage. You can opt out at any time. Privacy policy