The decisive difference is contractual authority. An Employer's Agent is appointed under a design and build contract to administer it: issuing instructions, assessing payments and certifying practical completion. A project manager provides broader strategic oversight of procurement, the design team, risk and reporting, but has no standing under the building contract unless also appointed as contract administrator.
Two distinct but complementary roles
The terms Employer's Agent and Project Manager are often used interchangeably but they are distinct roles with different contractual responsibilities.
The Employer's Agent role
An EA is appointed under design and build contracts to administer the building contract: issuing instructions, reviewing proposals, assessing payments, monitoring progress and certifying practical completion.
The Project Manager role
A PM provides broader strategic oversight: procurement strategy, design team management, risk management, client reporting and ensuring delivery on time and budget.
When each is needed
An EA is needed with design and build contracts. A PM is valuable on complex projects. On many projects both are needed. On simpler projects one person may fulfil both.
How they work together
On larger projects the PM manages programme, budget and stakeholders while the EA handles contractual administration. Clear delineation avoids duplication or gaps.
Where the two roles overlap and where they diverge
In day-to-day delivery an Employer's Agent (EA) and a project manager (PM) can look similar - both protect the client's interest, both chair meetings, both track programme and cost. The decisive difference is contractual authority. The EA is a named role under a JCT Design and Build contract with powers to issue instructions, certify payment and agree the final account. A PM, unless also appointed as contract administrator, has no such standing under the building contract.
This matters most when something goes wrong. If a contractor submits a loss-and-expense claim, the EA assesses and certifies it under the contract; a PM without a contractual role can only advise. Clients sometimes appoint both - a PM for overall delivery strategy and an EA for contract administration - but on smaller schemes one suitably qualified person commonly covers both functions under clearly separated appointments.
Which to appoint, by project type
For a design-and-build residential or commercial scheme where the client wants single-point contractor responsibility, an Employer's Agent is usually the right core appointment. For a complex multi-stakeholder programme - phased works, multiple contracts, funder reporting - a project manager coordinating the wider team, with an EA or contract administrator beneath them on each contract, is the more robust structure.
On Section 20 leaseholder major works the distinction is practical: leaseholders are entitled to clear information and a defensible cost position, so the contract-administration function (EA or CA) must be genuinely independent and well-documented regardless of whatever delivery-management label sits above it.
Frequently asked questions
Can one person be both?
Yes on simpler projects. On complex projects, separating the roles provides better oversight.
EA same as Contract Administrator?
Similar but not identical. CA for traditional contracts, EA for design and build.
Do I need a PM for a small project?
Not always. For straightforward projects the CA or EA may suffice.
Who appoints the EA?
The employer (client). The EA acts in the employer's interest.
Ross Alinari
Director, Construction and Project Delivery.
Writes on Construction delivery, Refurbishment, Remedial works, Procurement, Project oversight. See the full team profile.