Article
Principal-Arranged vs Contractor-Arranged Insurance: PAI, PCIP & OCIP Explained
Topic
Commercial InsuranceAuthor
Shane StewartAn Australian guide to principal-arranged vs contractor-arranged insurance — PAI, PCIP and OCIP structures, when each makes sense, and CFO decision factors.
On every Australian construction or infrastructure project above modest size, the same structural question lands on the desk of the principal's project commercial team and each major contractor's CFO: who arranges the insurance, the principal or the contractors? The answer shapes premium economics, claims management, cross-claim friction between parties on site, and the tail liability that runs years after practical completion.
This guide is the decision-stage companion to BCS Broking's broader commercial insurance for Australian construction and mining coverage. It explains the three principal-side terms in current Australian usage (PAI, PCIP, OCIP), when each structure makes sense, what coverages are typically inside and outside, and the five factors that drive the choice for a CFO at a $20M+ operator.
PAI, PCIP, OCIP — three names for two structures
Australian usage mixes three labels for what is, in practice, two structures.
- Principal-Arranged Insurance (PAI) is the Australian native term. The principal arranges and pays the premium for a project insurance program that names itself, the head contractor, sub-contractors and consultants as insureds for defined coverages on a specified project.
- Principal-Controlled Insurance Program (PCIP) is functionally the same as PAI, used more often by Australian government infrastructure agencies and large private developers. The "controlled" framing emphasises that the principal manages the program and claims, even where the contractors fund part of the cost via priced deductions from their tender prices.
- Owner-Controlled Insurance Program (OCIP) is North American terminology that has bled into Australian usage on internationally backed projects, particularly mining and energy infrastructure. Treat it as synonymous with PCIP.
The opposite arrangement — contractor-arranged insurance — is each contractor procuring its own cover for its own scope of work. The principal still carries certain exposures (typically property in care/custody/control, liability arising from the principal's own activities, professional indemnity for principal-engaged consultants), but each contractor is responsible for its own contract works, public liability and other operational covers under its contract.
In this guide, "PAI" is used for the principal-arranged structure and "contractor-arranged" for the alternative. PCIP and OCIP are interchangeable with PAI in practice.
What PAI typically covers
Where a principal arranges the project insurance, the program normally bundles four to six coverages:
| Coverage | Inside PAI typically | Outside PAI (contractor still arranges) |
|---|---|---|
| Construction All Risks / Contract Works | Yes — covers physical loss or damage to the works during construction | — |
| Public & Products Liability | Yes — covers third-party injury or property damage during the works | Some contractors maintain a separate corporate PL policy for non-project work |
| Marine Cargo (if relevant) | Often — covers materials in transit to site | — |
| Delay in Start-Up (DSU) | Sometimes — covers the principal's loss of revenue from late project completion | Rarely contractor-arranged |
| Professional Indemnity (PI) | Sometimes for principal-engaged consultants; less commonly contractor-side | Each contractor's PI for its own scope |
| Workers' Compensation | No — statutory in each state, always contractor-arranged | Yes, mandatory under each state's WHS scheme |
| Plant & Equipment | No, generally | Yes — each contractor's own |
Workers' compensation is statutorily controlled in each Australian state and cannot be wrapped into a project insurance program. Plant and equipment policies typically stay with the contractor that owns the equipment.
When PAI makes sense
Three structural conditions tend to make a PAI structure efficient on Australian projects:
Project size above $250M contract value. Below that threshold, the brokerage and program-management overhead of arranging principal-side cover for multiple contractors usually exceeds the savings from premium aggregation. Major infrastructure projects, mining capital expansions and large commercial developments typically clear the threshold; mid-sized commercial works do not.
Multiple contractors and complex cross-claim risk. When five, ten or more contractors and consultants share a site, the risk of cross-claims between insureds (one contractor's negligence damaging another's works) is high. A single principal-arranged Construction All Risks and Public Liability program eliminates the cross-claim friction by naming all parties as joint insureds with cross-liability cover. On simpler projects with a single head contractor, this benefit is small.
Principal preference for claims control. PAI gives the principal direct control of the claims process — the principal's broker manages the response, the principal's interests drive the settlement, and information about losses flows to the principal first. Government infrastructure agencies and large developers typically value this control highly. Tier 1 contractors with mature in-house insurance programs sometimes resist it.
Australian government infrastructure programs at scale — major road projects led by Transport for NSW or Major Road Projects Victoria, water infrastructure, large hospital and education builds — commonly use PAI/PCIP. Mining majors (BHP, Rio Tinto, Fortescue and equivalents) frequently use principal-controlled programs on capital expansion projects.
When contractor-arranged makes sense
The contractor-arranged structure is the default for most Australian construction and engineering work below the PAI threshold, and remains common above it where the principal lacks insurance management capability or where head-contractor preferences dominate.
It tends to suit:
- Smaller projects (typically under $250M contract value) where the program-management overhead of PAI is not justified by premium savings
- Single-contractor or simple-structure projects with limited cross-claim risk between parties on site
- Projects where the principal lacks insurance program management capability — many mid-tier private developers default to contractor-arranged because they do not have an in-house insurance team
- Tier 1 contractors with established corporate insurance programs that price project work efficiently within their existing capacity, often more cheaply than a project-specific PAI structure
In Australian practice, the contractor-arranged model is the dominant structure on commercial construction works under ~$250M contract value, on most engineering services contracts, and on many Tier 1-led design-and-construct contracts where the head contractor's own program is at least as efficient as the principal could arrange.
The CFO decision frame — five factors
For an Australian construction or mining operator with $20M+ revenue evaluating which structure is right for a specific project, five factors matter most:
- Project value and complexity. Above ~$250M with multiple contractors, PAI usually wins on premium economics and cross-claim simplicity. Below that, contractor-arranged wins on overhead.
- Contractor count and contract structure. Many contractors and consultants on one site favour PAI; single head-contractor projects favour contractor-arranged.
- Existing insurance program strength. A contractor with a well-priced corporate program may be able to insure a project more efficiently within its own program than a principal-arranged structure can. The opposite is true for contractors without scale or with weaker loss histories.
- Tail liability allocation. PAI programs typically include defined run-off cover for completed-operations exposure and latent defect risk. Contractor-arranged programs allocate that tail to each contractor's policy, which can introduce gaps if contractors restructure or leave the market before the tail expires.
- Claims management preference. Where the principal wants direct control of the claims process — common on government and large private infrastructure — PAI delivers that. Where the contractor needs control to protect its corporate claims experience and renewal terms, contractor-arranged is preferable.
For mid-sized contractors regularly tendering on a mix of PAI and contractor-arranged projects, the practical answer is to maintain a corporate insurance program that is competitive on the contractor-arranged side and well-understood on the PAI side — with clear deduction provisions in tender pricing where PAI applies.
Common pitfalls
- Double insurance and premium duplication. Where contractors also carry their own corporate PL policy, claims can trigger arguments between insurers about which policy responds. Clear "PAI primary, corporate excess only" wording in the principal's project schedule and in each contractor's policy avoids this.
- Coverage gaps at handover. PAI programs end at practical completion or expiry of the defects liability period; contractor-arranged programs continue for that contractor's other work. Mismatched expiries leave gaps for completed-operations claims.
- Statutory coverages assumed inside PAI. Workers' compensation cannot be wrapped into PAI; each contractor must hold its own state-scheme cover. Some PAI deduction structures wrongly assume otherwise.
- Principal's existing relationship constraints. Some principals require a specific broker, underwriter or program structure that does not match the contractor's existing arrangements — adding underwriting friction and sometimes claims-handling friction. Worth checking at tender stage, not afterward.
For broader context on insurance requirements that often interact with PAI structures, see insurance requirements for government construction contracts. For the surety-bond side of project security (which is separate from project insurance but often arranged in parallel), see surety bonds for Australian construction and mining and the performance bonds guide.
FAQ
What is the difference between PAI, PCIP and OCIP?
In Australian usage, PAI (Principal-Arranged Insurance) is the native term. PCIP (Principal-Controlled Insurance Program) is more common in government infrastructure procurement and emphasises the principal's program-management role. OCIP (Owner-Controlled Insurance Program) is North American terminology used on internationally backed projects. All three describe the same basic structure — the principal arranges and manages a project insurance program covering itself and the contractors.
What contract value typically justifies a PAI structure?
Most Australian PAI programs sit above $50–100M contract value. Below that, the program-management overhead and brokerage cost typically exceed the premium savings from aggregation. Government infrastructure projects above $200M almost always use PAI; mid-sized private commercial works usually do not.
Does PAI cover workers' compensation?
No. Workers' compensation is statutorily controlled in each Australian state and territory and is always arranged by the employer of record (each contractor or subcontractor). PAI cannot wrap workers' compensation. Tender deduction structures should not assume otherwise.
Who controls the claims process under PAI?
The principal does, typically through the principal's broker. The principal's interests drive the response and settlement. Contractors are notified of claims affecting their works but do not have primary control. This is one of the principal's main reasons for choosing PAI on infrastructure works.
Can a contractor still need its own corporate PL policy under PAI?
Yes. Most contractors maintain a corporate Public Liability policy for non-project activities, off-site operations and bidding work. Where PAI applies, the corporate PL typically operates excess of the project program (or is suspended for the project scope). Coordination between the corporate policy and the project program is important to avoid coverage gaps or double-insurance disputes.
How is PAI premium typically funded?
Two main models. In the first, the principal pays the full premium and absorbs the cost. In the second, the principal arranges the program and deducts a defined cost from each contractor's tender price (or from progress claims) to fund the contractor's share of the cost. The deduction model is most common on Australian government infrastructure projects.
What happens to PAI cover at the end of the project?
PAI programs typically include cover during construction plus a defined run-off period for the defects liability period (commonly 12–24 months post-completion) and, where included, longer-tenor latent defect cover. After the run-off expires, completed-operations claims fall back on each contractor's then-current corporate program, or on whatever bespoke completed-operations cover the principal has arranged.
Where to next
PAI vs contractor-arranged is one of several structural choices a CFO faces on a major Australian construction or mining project. To explore further:
- The commercial insurance for Australian construction and mining pillar covers the broader program design context
- The insurance requirements for government construction contracts guide covers the statutory and contractual requirements that interact with PAI
- The construction & infrastructure insurance sector page and mining & resources sector page cover BCS Broking's sector-specific program design approach
- For the surety-bond side of project security (separate from project insurance but typically arranged together), see surety bonds for Australian construction and mining
If you would like to discuss whether PAI or a contractor-arranged structure is the right fit for a specific project, contact BCS Broking.
This information is general in nature and does not consider any specific objectives, financial situation or needs. Consider whether the information is appropriate before acting on it. BCS Broking Pty Ltd is an authorised insurance broker (AFSL details on the Financial Services Guide).



