The Project Team & Consultants

Ask a first-year student who designs a building and they will say 'the architect'. Ask a principal who has delivered fifty and they will laugh, because they know a building is designed and built by a small society of people, each holding a piece of the truth. At the centre is the client - the party who commissions, pays for and ultimately owns the project, and whose brief and decisions set the boundaries for everyone else. Around the client sit the design consultants: the architect, who leads and shapes the whole; the structural engineer, who makes it stand up; the MEP engineers (mechanical, electrical and public-health/plumbing), who make it habitable; and, depending on the project, a widening circle of specialists - facade, geotechnical, fire, acoustics, lighting, landscape, vertical transportation, sustainability, kitchen, security and more.

Alongside the designers sit the commercial and management roles: a cost consultant or quantity surveyor (QS), who prices and controls the money; sometimes a project management consultant (PMC) or client's project manager, who runs the programme and the process on the client's behalf; and, once construction begins, the contractor, who actually builds, usually through a chain of subcontractors and suppliers. On public and large projects there may also be statutory and third-party players - proof consultants, a resident engineer, third-party inspectors, and the local authority whose sanction gives the whole enterprise legal life. Understanding this cast, and who answers to whom, is the first competence of anyone who wants to manage a project rather than merely draw one.

In the traditional arrangement, the architect is the lead consultant - the conductor of the orchestra, not the loudest instrument. That role carries duties that go well beyond producing beautiful drawings. The lead consultant holds the design vision and makes sure every specialist's work serves it; convenes and chairs design meetings; distributes and coordinates information so the structural grid, the ductwork, the drainage and the architecture actually fit together; advises the client on which consultants are needed and when; and, in many appointments, administers the building contract during construction. The architect is, in effect, the single point where the design comes together and speaks to the client and the builder with one voice.

This leadership is a matter of both convention and duty. The Council of Architecture and professional bodies worldwide frame the architect as the coordinator of the design team; the AIA and RIBA models of practice, and India's own tradition of the architect-led project, all place the architect at the hub of information flow. But leadership is earned in the doing, not assumed by title. A lead consultant who cannot run a meeting, cannot get a late engineer to deliver, or cannot hold the ring when the cost consultant and the client are at war, quickly finds the project leaking authority to whoever will fill the vacuum - often a PMC or the contractor. The craft of this module is precisely the craft of leading well: coordinating, sequencing, adjudicating and keeping everyone honest, so that the many hands produce one building rather than a committee's compromise.

The two consultants present on almost every project of any size are the structural engineer and the MEP engineers. The structural engineer sizes the frame, foundations, slabs and lateral system, working to the National Building Code and the relevant IS codes, and takes professional responsibility for the building standing safely under gravity, wind and, in much of India, seismic load. The MEP engineers design the arteries and nerves of the building: mechanical (air-conditioning, ventilation), electrical (power, lighting, low-voltage systems) and public health or plumbing (water supply, drainage, firefighting). Their services fill the ceiling voids, shafts and plant rooms, and their coordination with the architecture is where most on-site clashes are born.

Beyond this core, the circle widens with the ambition and complexity of the project. A tall tower needs a facade consultant and a vertical-transportation (lift) consultant; a hospital needs medical-planning and infection-control specialists; a concert hall needs an acoustician; a landmark needs a geotechnical engineer for the ground and a fire/life-safety consultant for compliance and insurance. A hallmark of professional maturity is knowing which specialists a given project truly needs, advising the client to appoint them early rather than as expensive afterthoughts, and defining each one's scope so nothing falls in the gaps between them. The most dangerous words on a project are 'I thought they were doing that' - and preventing them is the lead consultant's daily work.

Three roles govern whether a good design becomes a real building. The cost consultant or quantity surveyor is the keeper of the money: preparing cost estimates and the bill of quantities, advising on procurement, running the tender, valuing work done and controlling variations and the final account. In India the QS discipline is less universally engaged than in the UK, and on smaller projects the architect or PMC absorbs the role - but on any project of scale, an independent cost brain is worth many times its fee, because it turns 'we hope it is affordable' into a number that can be managed.

The project management consultant (PMC) - or the client's in-house project manager - runs the process on the client's behalf: the programme, the meetings, the risk register, the approvals, the payments and the reporting. On large or corporate projects the PMC has become common in India, sometimes sitting above the architect in the client's chain of command. This can help a stretched client enormously, but it also shifts authority, and a wise architect defines early, in writing, how the lead-consultant role and the PMC role divide - who coordinates the design, who chairs which meeting, who instructs whom. Finally, the contractor builds the project, usually as a main contractor who subcontracts trades and manages a supply chain. In the traditional route the contractor arrives after design; in design-and-build they may lead the design too. Their relationship to the architect - collaborator, counterpart, or adversary - is set by the procurement route, which is the subject of Lesson 7.3.

Consultants join a project through appointments - agreements that define each one's scope of services, deliverables, fee, programme and liability. Two models dominate. In a directly-appointed structure, the client contracts separately with each consultant, and the architect coordinates them without holding their contracts - clean lines of liability, but the architect must lead by influence and process rather than authority. In a sub-consultant structure, the architect (or a lead firm) holds the appointments and the specialists sit beneath them - more control, but the lead firm carries their liability and cashflow. On design-and-build projects, consultants first appointed by the client are often novated to the contractor, transferring their contract mid-project; understanding novation, and its effect on who the consultant now serves, matters greatly to the architect's independence.

Whatever the structure, the lead consultant's job is to make the appointments add up to a whole. That means writing scopes that interlock without gaps or overlaps; agreeing a shared programme so structural and MEP information arrives when the architecture needs it, not after; setting up the information protocols (Lesson 7.2 covers these) so everyone draws on the same current data; and confirming, in writing, who is responsible for each element - the perennial ambiguities of who sizes the plinth beam, who coordinates the toilet, who takes the facade waterproofing. A responsibility matrix, agreed at the start, is the cheapest insurance a project can buy. In India, remember too that each professional signs and stamps their own work under their own registration and liability - the structural engineer owns the structure, the architect the architecture - so coordination never means taking on another discipline's professional responsibility.

The simplest, most powerful tool for turning a crowd into a team is the RACI matrix - a grid that, for every task or deliverable on a project, names who is Responsible (does the work), who is Accountable (owns the outcome and signs off - and there should be exactly one per task), who is Consulted (gives input before it is done), and who is Informed (told once it is done). Laid across the project team, RACI makes the invisible visible: it exposes tasks with no accountable owner, tasks with two people both assuming the other will act, and consultants who are being left out of decisions that affect them.

Building a RACI for even a modest project is a revealing exercise. Take a task like 'coordinate services within the false ceiling'. Who is accountable - the architect, the MEP engineer, the contractor? Take 'obtain the building sanction' - the architect prepares and signs the drawings, but the client or a liaison agent may lodge them, and the local authority decides. Take 'value the work done each month' - the cost consultant, informed by the architect's certification. Working through the matrix with the whole team present surfaces the disagreements early, on paper, when they cost nothing to resolve, rather than late, on site, when they cost weeks and relationships. The matrix is not bureaucracy for its own sake; it is the written answer to the question that sinks more projects than any technical failure - 'whose job was that?' Keep it visible, revisit it when the team or scope changes, and let it be the quiet backbone of a team that trusts each other because everyone knows exactly what they own.