Most construction disputes don’t start on site. They start in a document, usually one signed months earlier, before anyone has lifted a tool or poured a foundation.
Pre-Construction Services Agreements (PCSAs) can be one of the most commercially significant documents in a project’s lifecycle, and one of the most frequently underestimated. Get one right and you set the project up with clarity, shared expectations, and a contractor who is genuinely invested in making it work. Get it wrong and you can lock in cost exposure, blurred responsibilities, and the conditions for a dispute before the main contract is even signed.
What a PCSA actually does
A PCSA brings a contractor into the project during the pre-construction phase, before the main building contract is executed. During this period the contractor carries out design reviews, buildability assessments, risk identification, programming and planning support. The idea is straightforward: early contractor involvement surfaces problems while they are still cheap to solve.
Used well, a PCSA gives developers genuine commercial advantage. You get a contractor who understands the project’s risks before pricing the main works, a more realistic programme, and a stronger foundation for the relationship that will carry the project through to completion.
Both JCT and NEC provide for this arrangement. The JCT publishes two versions of the PCSA. NEC4 addresses it through Option X22, building on the early contractor involvement provisions introduced in NEC3.
Where it goes wrong
The commercial risks in a PCSA are real, and they are not always obvious at the point of signing.
Scope creep is a common problem. If the services the contractor is expected to provide are not defined with precision, obligations expand and costs follow. The case of Almacantar (Centre Point) Ltd v Sir Robert McAlpine is a useful reminder of what happens when scope and fee arrangements are left ambiguous: what should have been a straightforward pre-construction arrangement became a dispute about what had actually been agreed.
Pricing is another pressure point. The pre-construction process is designed to surface risk, and it does. But that means contractors often reprice the main works upward once the full picture emerges. That is not necessarily unreasonable, but it can catch developers off guard if they have not modelled for it.
There is also no guarantee that the contractor completing pre-construction services will win the main contract. If negotiations break down or competitive tendering continues in parallel, the early work may not convert, leaving the contractor out of pocket and the developer behind schedule.
None of these risks are reasons to avoid PCSAs. They are reasons to go into them with proper commercial and contractual advice.
What good looks like
A well-drafted PCSA is clear about what it covers and what it does not. It defines the scope of services precisely, sets out the fee structure without ambiguity, and includes proportionate termination provisions so both parties know where they stand if the arrangement does not proceed to a main contract.
Obligations should be balanced. An agreement that is heavily weighted toward the employer’s interests may appear protective on paper but often creates friction that costs more to manage than it saves.
Early advice, not afterthought
The pre-construction stage is where commercial positions are established. It is also where they are most vulnerable if the paperwork has not kept pace with the conversations.
DRS works with developers, contractors and project teams to review and advise on PCSAs before they are signed, not after a problem has already taken hold. If you are heading into a pre-construction arrangement and want to be confident in what you are signing, speak to the team before the ink is dry.