An NEC4 Engineering and Construction Contract Project Manager is a role defined by that contract. It is not simply another title for a general project coordinator or a traditional JCT contract administrator. The NEC4 ECC also identifies a Supervisor with distinct functions. This guide helps a client compare the appointments through their decisions, information and records. It does not select a contract for an individual project or claim that experience with one form proves competence to administer another.
Start with the precise contract family
Traditional JCT forms such as Minor Works, Intermediate and Standard use an architect or contract administrator. JCT Design and Build has a different employer-side arrangement, commonly supported by an Employer's Agent. NEC4 is also a family of contracts: this comparison concerns the Engineering and Construction Contract, usually shortened to ECC. Do not transfer ECC role descriptions automatically into every other NEC form.
Write the proposed form, edition, options and amendments at the top of the appointment brief. Ask the adviser to identify the roles named in those documents and the functions each performs. Keep a general project-management service distinguishable from a named contractual role. Our construction-role comparison explains that broader separation before you compare the contract-specific mechanisms.
Distinguish the NEC Project Manager from the Supervisor
NEC's publisher guidance separates the ECC Supervisor's testing and defect functions from the Project Manager's other contract-management responsibilities. For example, the Project Manager administers changes to the Scope and certifies Completion; the Supervisor has a distinct Defects Certificate. These are contractual functions, so a client's organisation chart should identify who holds each role and any properly notified delegation.
Ask how inspection information reaches the person making the corresponding contractual decision. Identify specialist input, absence cover and the method for recording observations. Do not assume the Supervisor has authority to change the Scope because they are present on site, or that a Project Manager's appointment automatically supplies continuous inspection. Define any additional reporting or site-attendance service explicitly in the appointment.
Compare change procedures by their required actions
NEC's guidance describes instructions changing Scope and the separate compensation-event process. JCT administration uses the procedures and documents of its own selected form, including instructions and the applicable valuation and time provisions. A client should compare those actions rather than treating a change register as proof that either contract has been administered correctly.
For the proposed arrangement, ask the team to map how a change is raised, assessed, authorised, communicated and recorded. Identify the difference between a client request and an instruction that the contract recognises. Ask what further notification or assessment follows the instruction. Keep the commercial approval route clear without allowing an internal approval workflow to obscure the contractual responsibilities of the named role.
Keep early warnings distinct from compensation events
NEC's published guidance distinguishes an early warning about a matter that could affect the project from the compensation-event mechanism. A warning can prompt discussion and action without itself establishing entitlement to additional money or time. The publisher's compensation-event questions and answers likewise emphasise that the two processes are separate. The specific contract and amendments must be read for the applicable requirements.
Ask for separate status fields in the project record. Show what was warned about, what action was discussed and whether a compensation event was separately notified or assessed. Record the owner of each next step. Avoid marking a matter fully resolved merely because it was discussed at a meeting; identify which decision or communication is still required under the contract being used.
Establish how the programme supports decisions
NEC's explanation of its processes connects programme submissions and acceptance with compensation-event assessment. The programme therefore needs a controlled record of revisions and responses, rather than a single chart filed at the start. The relevant form and Contract Data should be checked for the project requirements; this guide does not provide a universal update interval or assessment deadline.
Ask the team to explain how it will distinguish the accepted programme, proposed revisions, actual progress and forecasts. Identify who supplies information about client decisions and other parties' activities. For a JCT appointment, make the equivalent information and assessment responsibilities explicit under that form. Do not compare software dashboards alone: ask how the records will support the decisions that the contract actually requires.
Prepare payment and completion records for the selected form
Request a document schedule for applications, assessments, notices and payment, with each sender and recipient identified. Have the adviser confirm the actual timescales before creating reminders. Do not copy a JCT interim certificate into an NEC workflow merely because both contracts involve payments during construction. Equally, a shared accounting spreadsheet should not hide the differences between the documents issued under each arrangement.
Repeat that exercise for Completion and defects. Establish who makes each decision, which supporting information is needed and what record is issued. Avoid translating an NEC term into a familiar JCT label without checking whether it has the same contractual effect. A practical handover checklist can sit alongside both systems, but it should preserve their respective formal decisions and any separate regulatory requirements.
Check competence and resource against the real brief
Ask a prospective consultant to describe relevant experience with the proposed form and the functions you need performed. Request a clear explanation of the decision process, reporting arrangements and staff cover. Where examples are offered, clarify the person's actual role and the contract used. Do not infer competence across an entire contract family from a professional title or a general project-management description.
Compare the proposed time commitment with the submission, meeting and inspection arrangements in the brief. Identify dependencies on designers, cost consultants and specialist advisers. If design-and-build procurement is being considered, read the separately scoped Employer's Agent service. The appointment must describe the role being commissioned; one service label should not be used to imply that every associated professional duty is included.
Turn the comparison into an appointment schedule
Before committing, ask for a short schedule pairing each contractual function with its appointed person, required information, communication route and output. Put unresolved questions beside the relevant function rather than leaving them in general meeting notes. Check the schedule against the final contract documents and consultancy terms, especially if options or amendments change during negotiation.
See HCS contract administration to discuss the proposed project and professional scope. HCS cannot act as independent contract administrator where HCS is the contractor. Form-specific experience should be confirmed for the person proposed to act; this guide does not attribute NEC or any particular JCT form to an individual team member. Keep the agreed responsibility schedule with the executed documents and revisit it when appointments change.