Pre-construction services agreement (PCSA): key contractor obligations
By Roman Bazelchuk | NEC Accredited Project Manager | APMG Project Planning and Control
Founder, NEC Planning Solutions Ltd
A pre-construction services agreement (PCSA) is the contract that pays a contractor for defined services before the main construction contract is awarded, usually in a two-stage tender. It binds the contractor to those services, not to build, and the programme it produces has no standing under the main contract until that contract adopts it.
Two-stage tendering lets a client appoint a contractor before the design is finished. The contractor is chosen first, on terms that can be fixed early, such as preliminaries, overheads and profit, and the fee for the pre-construction services. The PCSA then pays it to work with the design team, price the work packages and build up the construction price, which becomes the price of the construction contract if both parties agree it.
Much of what is written about PCSAs comes from law firms, and it covers what a lawyer has to cover: the scope of services, fees, termination, intellectual property and liability. This guide is written from the planner's desk. Its subject is the contractor's obligations under the agreement, the programme produced under it, and what happens to that programme on the day the construction contract is signed.
If the question is what to plan before mobilising rather than what the agreement says, the practical guide to pre-construction planning is the better starting point. Where the construction contract will be an NEC4 ECC, the choice of main Option matters too, and the comparison of NEC4 Option A and Option C explains what it does to the programme.
PCSA in construction: where it sits in a two-stage tender
A PCSA is a contract for services, not for works. It appoints the contractor to carry out defined pre-construction services before any construction contract exists, typically design input and buildability review, programming and logistics, cost planning, risk identification and the procurement of work packages on an open-book basis. It does not authorise the construction works themselves, although some PCSAs let the client instruct early preparatory works or long-lead orders. It usually creates no obligation on either party to enter the construction contract, although some agreements give the contractor exclusivity or preferred bidder status for a period.
Guides number the stages differently. Some call the period a PCSA covers the second stage, because the first stage was the selection. Others, and NEC4's Option X22, call it stage one. This guide follows X22: stage one is the pre-construction services, and stage two the construction works.
The trade-off is well known on the client side. The client gets the contractor's knowledge while the design can still change, and gives up bargaining power: once the contractor is part of the team, the stage two price is negotiated rather than tendered against competitors. That is why the pricing rules agreed when the contractor is chosen, such as the preliminaries, the fee percentage and the rates, carry so much weight later. On public work, the Construction Playbook says that public works projects and programmes should contract for early supply chain involvement, and it points to guidance on two stage open book as one collaborative model.
A PCSA is also not a letter of intent. A letter of intent is a temporary measure that lets work start while the terms of the construction contract are settled, and not every letter of intent creates a binding contract. A PCSA is a stand-alone agreement for a defined scope of services, with its own fee. A document called a PCSA that is vague about what the contractor delivers leaves the contractor in much the same position as a loose letter of intent when somebody later asks who owed what.
The standard forms: JCT, NEC4 and bespoke agreements
JCT publishes two: the Pre-Construction Services Agreement (General Contractor) and the Pre-Construction Services Agreement (Specialist). Both were reissued as 2024 editions on 4 September 2024. JCT describes the 2024 General Contractor edition as designed for appointing a contractor to carry out pre-construction services under a two-stage tender, for use with its Standard Building, Design and Build, Major Project and Intermediate contracts. The Specialist form appoints a specialist for either the employer or the main contractor, so what follows it may be a sub-contract rather than a building contract. JCT withdrew its 2016 Edition on 31 March 2026, with a transitional period until 31 December 2026 for projects already started or tendered on the 2016 forms.
NEC4 has no form called a PCSA. An article on NEC's website describes two routes. In the first, the pre-construction services are let under a separate agreement, for example an NEC4 Professional Service Contract, and the works under a separate Engineering and Construction Contract. In the second, one ECC carries secondary Option X22, early contractor involvement, which splits the contract into Stage One, in which the scope, programme and prices are developed and agreed, and Stage Two, construction. X22 is used only with main Options C and E, the target contract with activity schedule and the cost reimbursable contract.
Under X22 the Client states a budget, with an incentive paid to the Contractor if the final project cost comes in below it, and the Project Manager issues a notice to proceed to Stage Two. The Client can decide not to proceed. Since the January 2023 amendments, the Project Manager then notifies the Contractor and changes the Completion Date to the date Stage One was completed.
Clients also write their own PCSAs or amend the standard forms, so the agreement on the desk is the one to read, whatever its title says. The table sets the three standard routes side by side.
Route | Contract for stage one | Moving to stage two | The programme at the switch |
|---|---|---|---|
JCT PCSA, then a JCT building contract | JCT PCSA (General Contractor) | A separate building contract, if the parties agree one | Under SBC 2016 the master programme is provided after execution if not provided before (2.9.1.2), and imposes no obligation beyond the contract documents (2.9.3) |
A services agreement, then an NEC4 ECC | A separate agreement, for example an NEC4 Professional Service Contract | A separate ECC, if the parties agree one | The Accepted Programme from the Contract Date if identified in the Contract Data (11.2(1)); otherwise submitted for acceptance (31.1) |
NEC4 ECC with Option X22 | Stage One of the same ECC, with Option C or E | The Project Manager's notice to proceed to Stage Two | One contract throughout, so no handover between contracts |
Key contractor obligations under a PCSA
The agreement binds the contractor to the services in its schedule, delivered to the standard and timetable it sets, for the fee it states. It does not bind the contractor to build, and it does not turn the dates on the programme the contractor produces into construction obligations. Those dates bind only if a construction contract adopts the programme, and then only in the way that contract provides.
Much of the schedule describes inputs to the stage two price: design development and buildability, cost planning, package enquiries and returns, risk registers and logistics. The programme sits underneath all of them. The package tenders need its dates, the cost plan its durations and the stage two price its sequence, yet the programme lines can be the least defined in the schedule: "programming", with no number of revisions, no format and no statement of what the programme has to show.
Some obligations can outlast the agreement. Confidentiality is one. The licence the client takes over the contractor's documents is another, and it matters because the client may want to use the programme whether or not the contractor builds the job. Design input raises a third question, whether the contractor takes on design liability, and the agreement should answer it in terms. Liability for the services can outlast it too. In Belong (Construction) Ltd v Seddon Construction Ltd [2026] EWHC 1275 (TCC), decided on 28 May 2026, a clause subsuming a bespoke PCSA into a JCT Standard Building Contract did not wipe out liabilities for breaches committed during the PCSA period.
The programme the contractor produces under a PCSA
During stage one the contractor builds the programme that supports the stage two price. It carries the sequence, the procurement lead times, the design release dates and the interfaces between packages. It is examined closely, because the price rests on it.
It also carries a trap of the contractor's own making. A programme built to win stage two tends to be optimistic, and the optimism is priced. The client may set the completion date, but the durations and sequence that make it look achievable are the contractor's own.
The discipline is the same as for any tender submission: a programme the contractor would defend after award, not one that reads well before it. The argument is set out at length in what makes a tender programme credible. The PCSA version is harder, because the contractor is being paid to produce the programme and the client has watched it being built.
COMMERCIAL CONSEQUENCE Every week cut from the programme to sharpen the stage two price takes a week of time-related preliminaries out of it: at £25,000 a week, six weeks is £150,000. If the work then takes the time it needed, a lump sum leaves that cost with the contractor, and NEC4 Option C shares the overrun at its Contract Data percentages. |
What happens to the programme when the contract is signed
When the construction contract is signed, the PCSA usually ends or is subsumed into it, and the stage one programme is a document produced under that agreement. What it becomes depends on the construction contract, and on whether anyone acts on the day of award.
Under an NEC4 ECC there are three routes. If the programme is identified in the Contract Data, it is the Accepted Programme from the Contract Date, because clause 11.2(1) defines the Accepted Programme as the programme identified in the Contract Data until the Project Manager accepts a later one. If it is not identified, clause 31.1 has the Contractor submit a first programme for acceptance within the period the Contract Data states, and clause 31.3 gives the Project Manager two weeks to accept it or give reasons, a step the guide to clause 31 programme acceptance walks through.
If neither happens, there is no Accepted Programme. Where no programme is identified in the Contract Data, clause 50.5 retains a quarter of the Price for Work Done to Date until a first programme showing the information the contract requires is submitted. When a compensation event arrives, clause 64 has the Project Manager assess it, using its own assessment of the programme for the remaining work. The guide to compensation events without an Accepted Programme covers how to recover from that position.
Under the JCT Standard Building Contract 2016, still in use on projects tendered on the 2016 forms, the contractor provides its master programme as soon as possible after the contract is executed, if it has not already been provided (clause 2.9.1.2), and clause 2.9.3 says nothing in it imposes any obligation beyond the contract documents. A programme handed over during stage one may count as already provided, so the building contract should say which version is the master programme. The 2011 and 2016 JCT Design and Build contracts have no express programme clause, so there the programme's standing comes from what the contract documents say about it. The guide to the JCT master programme covers what it is asked to show.
Under X22 there is no handover between contracts. Stage Two runs under the same contract, so the Accepted Programme carries on. It does not cross unchanged, though: by the notice to proceed it should have been revised to show the Stage Two work in full, with its access dates, Key Dates and Completion Date.
On the two-contract routes there is a handover moment, and it is easy to miss. Everyone worked on the stage one programme and everyone remembers it, so it is treated as the baseline. Nobody identifies it in the new contract or submits it under it. Months later the project is measuring progress against a document with no standing and, under an NEC4 ECC, the first compensation event is assessed on the Project Manager's view of the programme rather than the contractor's.
PLANNER'S TAKEAWAY Under an NEC4 ECC, name the programme in Contract Data part two of the stage two offer, updated to the expected award date. It is then the Accepted Programme from the Contract Date: no submission, no two-week wait, no clause 50.5 retention. Failing that, submit it as the first programme on the day the contract is signed. |
Writing the programme into the services schedule
The services schedule decides much of what a PCSA is worth commercially, so the programme lines need the same precision as the fee. Name the deliverables: how many programme revisions the fee includes, whether the programme is resource-loaded or cost-loaded, whether a procurement schedule and a design information schedule are separate deliverables, and whether the stage two programme carries a risk-adjusted completion date or a single deterministic one.
Then name what costs extra. Design changes during stage one are normal, and each can take programme time to absorb. If the schedule does not make reprogramming after a design change an additional service, with a way of instructing it, the fee absorbs it, and over a long stage one that adds up.
Finally, say who owns the output and on what licence. The programme, its logic and the procurement analysis are the contractor's work. If the client can take them to another contractor after termination without paying their full value, the contractor has subsidised a competitor's tender, part of the wider question of what a specialist or smaller contractor gives away at bid stage.
The exit, and what the contractor keeps
A PCSA that ends without a construction contract is not a failure. It is one of the outcomes the agreement exists to allow. What matters is whether the contractor was paid for what it produced, and whether it keeps the benefit.
Three things are worth checking before signing. That the fee reflects the real workload, not a token sum treated as an investment in winning stage two. That termination pays for services performed to that date, including work in progress. And that the licence over the contractor's documents is limited to the project the client is procuring and tied to payment of the fee due, rather than a general assignment. Under X22, the January 2023 amendments added a clause setting out the amounts due if the contract is terminated during Stage One.
A contractor that accepts a thin PCSA fee is counting on the construction contract to follow. Sometimes it does not, and the exit terms then decide whether stage one was paid work or an unusually expensive tender.
NEC Planning Solutions builds the stage one programme to the standard the construction contract will judge it by: logic-linked, carrying the package procurement and design release dates, and ready to be named in the Contract Data at award. Pre-construction planning starts from £2,000 plus VAT for a smaller scope and £4,000 plus VAT for a standard one.
See how pre-construction planning support works.
The author's view
The PCSA is the best chance a contractor gets to influence a project, and one of the most often wasted. The planner is in the room while the design is still moving, when planning can still change an outcome rather than record one.
My position is that the stage one programme should be built as if it were already the Accepted Programme: the same logic discipline, the same evidence for durations, the same treatment of risk allowances. Not because the PCSA requires it, since it usually does not, but because that programme will be re-read by people looking for the difference between what was promised and what was delivered, and the fact that it was produced under a different agreement will not help.
And I would treat the day of award as a gate, not an administrative step. It is the moment months of paid work either becomes the contract's programme or stays a file on a shared drive, and it is the cheapest protection available on a two-stage job.
Summary
A PCSA in construction is a pre-construction services agreement: a contract for defined services before the main construction contract, usually in a two-stage tender. It binds the contractor to the services, timetable and fee in its schedule, not to build, and it usually commits neither party to the construction contract. JCT publishes General Contractor and Specialist forms, reissued in 2024. Under NEC4 the services can be let under a Professional Service Contract followed by an ECC, or the two stages joined in one ECC with Option X22 under main Option C or E.
The programme built under a PCSA underpins the stage two price, and its standing depends on the construction contract. Under NEC4 it is the Accepted Programme from the Contract Date if the Contract Data identifies it. Otherwise it has to be submitted and accepted, and until a first programme showing the information the contract requires is submitted, a quarter of the Price for Work Done to Date is retained. Name the programme deliverables in the services schedule, price the reprogramming that design change causes, and protect the exit.
Download the PCSA checklist
Two pages of checks for before signing, during stage one and on the day of award: reading the services schedule, pricing the programme work, building stage one to the standard it will be judged by, protecting the exit and the gate at award. Direct download, no sign-up.
Pre-construction services agreement: frequently asked questions
What is a PCSA in construction?
A PCSA, or pre-construction services agreement, is a contract that appoints a contractor to provide defined services before the main construction contract is awarded, usually in a two-stage tender. Typical services are design input and buildability review, programming, cost planning, package procurement on an open-book basis and building up the stage two price. It does not authorise the construction works, and usually obliges neither party to enter the construction contract.
Is a PCSA the same as a letter of intent?
No. A letter of intent is a temporary measure that lets work start while the terms of the construction contract are settled, and not every letter of intent creates a binding contract. A PCSA is a stand-alone agreement for a defined scope of pre-construction services, with its own fee. A document called a PCSA that is vague about deliverables protects the contractor little better than a loose letter of intent.
Does a PCSA oblige the client to award the construction contract?
Usually not. A PCSA normally creates no obligation on either party to enter the construction contract, and some give the contractor exclusivity or preferred bidder status for a period. That is why the fee and the exit terms matter: termination should pay for services performed to date, including work in progress, and the licence over the contractor's programme and analysis should be limited to the project and tied to payment.
Does the PCSA programme become the Accepted Programme under NEC4?
Only if the construction contract makes it so. If it is identified in the Contract Data, clause 11.2(1) makes it the Accepted Programme from the Contract Date. If not, clause 31.1 has the Contractor submit a first programme for acceptance, and until one showing the information the contract requires is submitted, clause 50.5 retains a quarter of the Price for Work Done to Date.
What is the difference between a PCSA and NEC4 Option X22?
A PCSA is a separate agreement for the pre-construction services, followed, if the parties agree, by a separate construction contract. Option X22 keeps both stages in one NEC4 ECC: Stage One develops the scope, programme and prices, and the Project Manager's notice to proceed starts Stage Two, construction. X22 is used only with main Options C and E, and the Client can decide not to proceed.
Which standard forms of PCSA are there?
JCT publishes the Pre-Construction Services Agreement (General Contractor) and the Pre-Construction Services Agreement (Specialist), both reissued as 2024 editions on 4 September 2024; the superseded 2016 forms remain usable until 31 December 2026 on projects already started or tendered on them. NEC4 has no form of that name: pre-construction services can be let under its Professional Service Contract, or both stages joined in one ECC with Option X22.
About the author
Roman Bazelchuk is the Founder of NEC Planning Solutions Ltd, a UK project planning and controls consultancy supporting contractors with NEC programme compliance, compensation event assessments and live project controls. He is an NEC Accredited Project Manager and holds the APMG Project Planning and Control qualification, with a BEng in Mechanical Engineering and postgraduate training in Planning and Control.
NEC Planning Solutions provides contract-aware planning support through a QA-governed delivery model, helping project teams keep programmes accepted, current and commercially useful from tender through to live delivery.
Appointed under a PCSA and building the stage one programme?
NEC Planning Solutions builds the stage one programme to the standard it will be judged by later, prices the reprogramming that design change causes, and handles its naming in the Contract Data or its submission at award, so the work the client paid for carries contractual weight. See how the pre-construction planning service works.
