Architect, Contractor or PMC: Who Actually Does What on Your Project

Clients commissioning their first significant building usually discover the roles in the wrong order, by finding out, mid-project, that nobody owned something.

The three roles are genuinely distinct. The confusion is not about what each is called. It is about where accountability sits when two of them touch the same problem.

The architect: decides what gets built

The architect's product is intent, made precise enough to execute. Concept, spatial planning, statutory compliance, coordination of structural and services design, material and detail specification, and the full drawing set that a contractor prices and builds from.

What the architect is accountable for: that the building works, that it is compliant, and that the drawing is complete and unambiguous enough that it can be built without invention on site.

What the architect is not accountable for, in the traditional arrangement: the contractor's labour productivity, their procurement, or their programme.

The contractor: builds what was decided

The contractor's product is the physical building, delivered against the drawings, at the agreed price and programme. Labour, plant, procurement, sequencing, site safety, quality of workmanship.

What the contractor is accountable for: building to the drawing, to the specification, on time, safely.

Where trouble starts: an incomplete drawing set. A contractor confronted with a gap will fill it, with whatever is cheapest and fastest. That is not bad faith; it is the rational response to ambiguity. Most disputes we have seen trace back to a drawing that left a decision unmade.

The project management consultant: makes sure it actually happens

The PMC's product is delivery. Programme, cost control, quality assurance, contractor procurement and evaluation, bill certification, site supervision, and the coordination between every party who has an opinion.

What the PMC is accountable for: that cost, quality and time hold. That the drawing becomes the building without drift.

This is the role most frequently skipped on Indian projects, and it is the one whose absence is most expensive. Without it, cost control tends to default to the client's finance team, who can see that a number has risen but not why, and by the time it is visible in a bill, the decision that caused it was taken six weeks earlier on site.

The three arrangements

Architect + contractor, client manages. Lowest fee, highest client burden. Works for small, simple, single-building projects where the client has genuine construction literacy and time. Fails when the client is a busy principal treating it as a side responsibility.

Architect + contractor + independent PMC. Three parties, clean separation of interest. The PMC has no incentive to protect either the design or the contractor, which is exactly the point. Standard on institutional and large commercial work.

Integrated, architecture and project management under one roof. Fewer interfaces, single accountability, no gap between the drawing and its enforcement. The person who specified the detail is the person checking it on site. This is how Vastukriti has worked since 1987, and it is why we describe project management as a discipline rather than a service line.

Each arrangement is legitimate. The failure mode is not choosing one, it is assuming a role is covered when no one has been appointed to it.

The four questions to ask before you commission anyone

1. Who is accountable for the programme? If the answer is "the contractor," ask who checks the contractor.
2. Who certifies bills, and are they independent of the party being paid?
3. Who resolves a conflict between the structural drawing and the services drawing? If it is resolved on site by a foreman, it will be resolved badly.
4. Who tells you when a decision is about to cost money, before it does?

If any of these has no name attached, that is your gap, and it will surface. Projects rarely fail on the things everyone is watching.