juxt-a-position: A 2,000-Bed Hospital Is a Programme, Not a Building

A 2,000-bed hospital is not one building problem. It is a network of clinical, logistical and infrastructure systems that must be governed before the design is fixed.

Why clinical assumptions need ownership, dependencies and evidence before they become architecture.

The West Bengal announcement prompted a design-management question: when a healthcare campus reaches this scale, what exactly are we trying to make deliverable?

The announcement is significant because the scale changes the management problem

On 24 September 2026, the foundation stone was laid for the 2,000-bed Adani Arogya Mandir at New Town, Kolkata. The public numbers are striking: more than ₹4,000 crore of investment, 51.75 acres, more than 200,000 inpatients and 2 million outpatients annually, a medical college, nursing and allied-health education, research, step-down care, transitional care and accommodation for patients’ relatives. International clinical and academic advisers have also been named.

Those facts are enough to trigger an important design-management question. At this scale, the project is not simply a large hospital building. It is a healthcare delivery programme in which clinical services, education, research, digital systems, logistics, utilities, accommodation and long-term operations have to converge into one functioning campus.

I am not commenting here on the Adani project’s design or its internal delivery arrangements. From this point onward I use a notional 2,000-bed academic medical centre as the working example. The point is to examine the governance problem that any programme of comparable complexity has to solve.

A bed count is not a brief

“2,000 beds” sounds like a definition. It is really only a scale marker. Two hospitals with the same bed count can have entirely different clinical missions, acuity profiles, emergency demand, theatre utilisation, diagnostic load, teaching requirements, research programmes, staffing models and infrastructure demands.

A 2,000-bed project therefore becomes credible only when the bed number is translated into an operating model: what services are being delivered, to whom, at what activity level, through which clinical pathways, with what staffing and equipment, and with what level of resilience.

That translation matters commercially as well as clinically. If the operating model moves after the architecture has hardened, the consequences can appear as changed room mixes, enlarged plant, altered risers, new equipment loads, revised vertical transport, reworked digital systems and delayed procurement. The earlier the dependencies are visible, the less expensive they are to resolve.

The hospital should be governed as a programme of interdependent systems

At this scale, familiar departmental labels are necessary but insufficient. Emergency, critical care, inpatient wards, surgery, imaging, laboratories, pharmacy, sterile services and outpatients do not operate as separate boxes. Patients cross them. Staff cross them. Specimens, drugs, clean supplies, sterile goods, linen, food, waste, beds and mobile equipment cross them. Engineering and digital systems connect them all.

The design-management problem is therefore not only whether each department is well planned. It is whether the interfaces between departments, services and project stages are visible early enough to be governed.

The Facility Guidelines Institute reinforces the importance of owner-driven functional programming and safety risk assessment involving clinicians, infection preventionists and other care providers. NHS guidance similarly treats infection prevention as something to be designed in from concept, not checked into the project at the end. The lesson for design management is simple: the brief is an operating proposition, not a schedule of rooms.

Seven flows should be visible before the architecture becomes difficult to change

For a campus of this scale, I would expect at least seven movement systems to be visible at concept stage: patients, staff, visitors, clean supplies, sterile supplies, dirty/waste returns and equipment/material logistics.

The purpose is not to produce attractive diagrams. It is to expose decisions. Where do public and clinical movements cross? How does a bed transfer interact with service traffic? How does a specimen move from theatre to laboratory? How does sterile supply reach operating rooms without crossing contaminated returns? Which routes remain available during an emergency or a maintenance shutdown?

When those questions are unresolved, the risk does not disappear. It is simply transferred downstream to detailed design, procurement or construction, where the options are fewer and the cost of change is higher.

Scale requires nested design governance, not one project status

One of the most misleading statements on a large project can be: “Design is 80% complete.” The percentage may be useful for a programme report, but it can conceal very different states of maturity.

In our notional hospital, inpatient units may be well resolved while operating theatres are waiting for equipment decisions. Imaging may depend on vendor data. Clinical ICT may lag architectural planning. Medical gases may be technically advanced but still depend on confirmed clinical policy. Central plant may be designed while phased activation remains unresolved.

The solution is to govern the programme at several levels: programme, building, department, room type and specialist system. A department that has met its evidence threshold can progress. A specialist package that has not should remain visible as a controlled exception rather than being hidden inside an overall percentage.

Stage gates should test readiness, not calendar compliance

This is where the Design Manager’s Manual sits quietly behind the argument. A stage gate should not be the date on which the programme says concept design ends. It should be the point at which the client can see enough evidence to accept that the design is ready to move forward.

For the notional 2,000-bed hospital, an early gate would test whether the clinical service model is defined sufficiently for design; whether capacity and activity assumptions are recorded; whether departmental adjacencies and major flows are credible; whether critical infrastructure assumptions are visible; whether key clinical equipment strategies are known; and whether unresolved decisions have named owners and clear next-stage consequences.

If the evidence is missing, the design may still be visually persuasive. It is simply not ready.

This is fundamentally an owner-side delivery issue

The larger the programme, the more design risk migrates from individual disciplines into the spaces between organisations, packages and stages. I have seen the same pattern across large mixed-use and hospitality programmes and again from the contractor side of design management: the difficulty is rarely that a competent consultant does not know how to design their own discipline. It is that one team’s assumption arrives late, changes form or loses ownership as it passes to another team.

Healthcare multiplies those hand-offs. That makes design governance an owner-side delivery capability: someone has to maintain the line of sight from strategic brief to clinical planning, from planning to coordinated design, from design to procurement, and from procurement into construction and commissioning.

The design manager does not replace the clinician, health planner, architect, engineer, project manager, contractor or specialist vendor. The role is to make their dependencies visible, clarify decision rights, protect information as it moves between them and ensure that important risks do not travel silently into the next stage.

The question behind the 2,000-bed number

The public announcement in West Bengal is impressive because of its ambition. But the design-management question behind any project of this scale is more useful than the number itself: can the organisation create a governance system strong enough to convert ambition into a coordinated, buildable, commissionable and operable healthcare environment?

That is the question I would use to judge design maturity — not whether every drawing exists, but whether the decisions represented by those drawings are mature enough to support the next commitment.

Part 2 moves to the point where major hospital projects become hardest to control: the interfaces between clinical planning, room data, equipment, engineering, digital systems, procurement and construction.

At programme scale, the biggest delivery risk increasingly sits not inside the individual disciplines, but in the spaces between them.

Background framework: The Design Manager’s Manual — Design Management & Governance