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

Sources and reference context

• Adani Group — West Bengal CM lays foundation stone for 2,000-bed Adani Arogya Mandir, 24 September 2026

• Reuters — Adani Group investment and 2,000-bed hospital announcement, 24 September 2026

• Facility Guidelines Institute — Application Guidance: functional programme and safety risk assessment

• NHS England — HBN 00-09: Infection control in the built environment

Tender Readiness Is a Condition, Not a Date

 

A tender package can be issued on time and still be unready for tender.

That sounds contradictory only if tender readiness is defined as the act of issuing documents.

In practice, the market does not price a drawing issue. It prices the design information, assumptions, exclusions and unresolved risks contained within it.

If those inputs are immature, the uncertainty does not disappear when the package is uploaded. It simply moves into qualifications, provisional sums, RFIs, contingency, inconsistent bids, post-tender clarification and eventual variation.

Tender readiness is therefore a condition, not a date.

The date still matters

Projects need tender dates. Commercial programmes need procurement milestones. Contractors need time to price. Developers need cost certainty. Lenders, operators and boards may depend on the result.

The problem is not scheduling the tender.

The problem is treating the scheduled issue date as proof that the information is suitable for pricing and procurement.

A package may contain hundreds of drawings and still leave the market to interpret major decisions.

The more sophisticated the project, the more dangerous that can become.

What the market is actually being asked to price

A tenderer is not only reading dimensions and details.

The tenderer is trying to understand scope, quality, performance, interfaces, risk allocation, quantities, exclusions, sequencing, specialist design responsibilities, authority requirements, temporary conditions, procurement lead times and the degree to which the documentation can be trusted.

If the design team has not aligned those matters, the tenderer must make assumptions.

Different tenderers make different assumptions.

The bids then become difficult to compare, because the apparent price difference may actually be a difference in interpretation.

The cheapest bid may simply carry the greatest unpriced uncertainty.

Drawings, specifications and schedules need to tell one story

One of the first tests of tender readiness is alignment across the information set.

Does the specification describe the same system that appears on the drawings?

Do the room or space schedules match the plans?

Do the door, finish, equipment and hardware schedules reflect the current design?

Have value-engineering decisions been incorporated consistently?

Are provisional items clearly identified rather than hidden inside incomplete detail?

Are consultant drawings based on aligned grids, levels, room names, equipment assumptions and revision status?

Tender uncertainty often begins in the gaps between documents rather than inside a single drawing.

A well-detailed elevation cannot rescue a specification based on an earlier design. A coordinated model cannot help if the tender drawings exported from it are not the documents the market has been instructed to rely upon.

Unresolved decisions need to be visible

No tender package is perfect.

The question is whether unresolved matters are controlled.

A client decision may still be pending. A specialist system may depend on contractor design. An authority matter may remain conditional. A long-lead item may need early release before the whole project is complete.

These conditions can be manageable if they are explicit.

They become dangerous when the market is asked to discover them independently.

A tender-readiness review should therefore identify what is unresolved, who owns it, what bidders should assume, what commercial mechanism will apply and when the matter must be closed.

Again, uncertainty is not the same as failure.

Invisible uncertainty is the bigger problem.

Operator and client comments must be incorporated, not merely answered

Projects with operators, tenants, brands or complex client stakeholders often accumulate large comment logs.

A comment can be responded to without being fully incorporated.

"Accepted" is not the same as "transferred into the tender information."

If a decision changes a room standard, equipment requirement, material, operational flow, access requirement or maintenance expectation, the tender package should reflect the consequence across all relevant documents.

Otherwise the project may tender one design while believing it has approved another.

The same applies to internal client decisions. A decision log is useful only if the decision reaches the drawings, specifications, schedules, BIM data and cost information that depend upon it.

Value engineering needs a closure loop

Value engineering is another major source of tender drift.

A project may agree to change a facade build-up, reduce a finish standard, alter equipment, remove redundancy or modify a room type. The commercial saving may be recorded immediately.

But has the design response caught up?

Has the specification changed?

Have details been revised?

Has the operator accepted the operational consequence?

Has statutory compliance been checked?

Have maintenance and warranty implications been considered?

Has the cost plan removed the original scope and added the revised one consistently?

A value-engineering decision that has not moved through the information set is not ready for tender. It is a future clarification waiting to happen.

Authority conditions belong inside the package

Consent and statutory requirements are often treated as a parallel workstream.

That can be misleading.

If an authority condition affects the design, it belongs inside the design information.

Fire requirements, accessibility, planning conditions, acoustic requirements, service connections, environmental controls, staging constraints or other statutory matters can all affect what the contractor must price and build.

A tender-readiness review should therefore ask whether known authority requirements are visible in the package and whether outstanding conditions are clearly identified.

It is not enough for the approval team to know them if the pricing team cannot see them.

Long-lead items change the sequence

Tender readiness is also tied to procurement strategy.

Some items cannot wait for a conventional sequence of design completion followed by tender followed by procurement.

Lifts, facade systems, major plant, specialist kitchen equipment, switchgear, generators, bespoke joinery, certain finishes and technology systems may require early decisions.

That creates a governance problem: what information must be sufficiently mature before an early package is released?

The answer is not "everything."

It is the information necessary to make that specific procurement decision reliable.

An early package therefore needs its own evidence threshold: performance criteria, interfaces, dimensions, access, maintenance, authority implications, commercial assumptions and downstream design responsibility.

Early procurement can be intelligent. Premature procurement simply freezes uncertainty into the project.

Scope responsibility must be legible

Tender packages also fail when design responsibility is implied rather than stated. A detail may appear partly developed in the consultant documentation while the specification expects contractor design. A specialist supplier may be expected to complete engineering without clear performance criteria. Interfaces between base build, fit-out, landlord works, tenant works or operator-supplied equipment may sit between packages.

The market will price those ambiguities differently. Some bidders will include them, some will qualify them and some will assume another party carries the responsibility.

A tender-readiness review should therefore ask whether the responsibility matrix and package boundaries match the drawings and specifications. Contractor design can be entirely appropriate, but the performance requirement, design inputs, review process and interface responsibility still need to be clear.

Buildability should be tested before the market prices ambiguity

Tender readiness should also include a practical buildability lens.

Can the design be constructed in the sequence implied by the documentation?

Can major equipment reach its final location?

Are access, temporary works, tolerances and interfaces plausible?

Do details depend on impossible installation sequences?

Are waterproofing, facade, fire-stopping and service penetrations coordinated at the level needed for pricing?

Has the project considered what will require shop drawings or specialist design later?

A tender package does not need to solve the contractor's methodology. It does need to avoid transferring unresolved design coordination to the contractor without acknowledging the responsibility and risk.

A useful tender gate asks what can be relied upon

The most important tender-readiness question is similar to the question at every design stage:

Can the next participant safely rely on this information for the decision they are being asked to make?

In tender, that decision is commercial as well as technical.

The bidder is deciding price, risk allowance, resources, programme, subcontract strategy and sometimes whether to bid at all.

If the information is unreliable, the commercial response will reflect that - whether through contingency, qualification, exclusion or post-award pressure.

Proceed, proceed with declared risk, or hold

Tender readiness does not have to be binary.

A project may decide to proceed with identified residual risks. That may be commercially sensible when programme pressure is real and the consequences are understood.

But the risk should be declared.

A useful gate can distinguish:

PROCEED - the package is sufficiently coordinated and complete for the intended procurement decision.

PROCEED WITH DECLARED RISK - specific unresolved matters remain, but assumptions, ownership and commercial treatment are explicit.

HOLD - the information is too immature for the market to price reliably without creating unacceptable downstream risk.

This is more honest than allowing the programme to force an unconditional issue.

Tender comparison depends on information quality

The quality of the tender package also determines the quality of the tender comparison. If bidders are pricing different interpretations, the post-tender process can become an exercise in normalising assumptions rather than comparing genuine market value. Clarifications multiply. Qualifications have to be negotiated. The preferred bidder may change once exclusions are understood.

This creates a false sense of cost certainty at exactly the point when the project is seeking greater certainty. Better design readiness does not guarantee a low price, but it improves the chances that the prices received describe the same scope.

That matters to developers, cost consultants and contractors alike. A transparent risk is easier to price and negotiate than an uncertainty hidden inside incomplete design information.

Tender readiness leaves evidence

A strong tender-readiness decision should be supported by evidence appropriate to the project.

That may include a coordinated drawing and model review, specification alignment, room-data or schedule freeze, operator-comment closure, authority-condition review, value-engineering incorporation, long-lead register, procurement-risk review and a list of accepted residual risks.

The point is not to create another ceremonial report.

The point is to know why the team believes the package can be priced.

Tender readiness is also a governance decision

The final decision to release a package should therefore not belong only to the person responsible for document issue. It is a project governance decision. The design leads understand technical maturity. The cost consultant understands pricing risk. The project manager understands programme consequence. The client understands commercial appetite. The contractor or procurement adviser may understand market capacity and sequencing.

Bringing those perspectives together does not mean everyone gets a veto. It means the decision to tender is made with a clearer understanding of what the market is being asked to absorb.

Do not transfer confusion to the market and call it procurement

Tendering is often described as the moment when the market tests the design.

That is partly true. Contractors and subcontractors bring valuable buildability, supply-chain and commercial knowledge.

But the market should not be asked to resolve basic design-management uncertainty simply because the project reached the tender date.

The price of that uncertainty will return later - in qualifications, claims, redesign, procurement pressure, site RFIs or compromised outcomes.

A tender package should communicate a controlled proposition: this is the design, these are the known assumptions, these are the responsibilities, these are the unresolved risks, and this is what the bidder is being asked to price.

That is tender readiness.

Not the date the upload button was pressed.

A Stage Gate Is Not a Date: Why Design Readiness Needs Evidence

Projects need dates.

Concept Design needs an end date. Schematic Design needs a milestone. Developed Design needs a point at which cost planning, approvals, tender preparation or procurement can move forward. Consultant programmes cannot operate without these boundaries.

But a date is not the same thing as readiness.

A project can arrive at the end of a design stage with drawings issued, presentations approved and consultant deliverables uploaded, while still carrying unresolved decisions that the next stage is about to inherit.

That is the difference between programme completion and design maturity.

A stage gate should test the second.

Why stage dates become dangerous

The programme itself is not the problem. The problem begins when the project starts using the date as evidence that the design is ready.

A concept package may look coherent while the services zones have not been protected. A room or tenancy module may be approved while structure and MEP implications remain untested. A fire strategy may exist but may not yet be reflected consistently across disciplines. An authority pathway may be assumed rather than confirmed. An operator comment may have been acknowledged but not incorporated. A cost plan may be based on information that is still moving.

None of these conditions automatically means the project should stop.

They do mean the project should know what it is carrying forward.

The project has moved. The risk has moved with it.

What an evidence-based stage gate is actually testing

A useful stage gate is not a ceremonial approval meeting. Nor is it an attempt to freeze every detail too early.

It is a decision about whether the information produced at one stage is sufficiently mature for the next stage to rely upon it.

That requires a different set of questions from "Have the drawings been issued?" or "Has the client signed off the presentation?"

Has the purpose of the stage actually been achieved?

Are the major decisions visible?

Have the critical multidisciplinary interfaces been tested to the level required at this point?

Are approval assumptions clear?

Has cost advice been based on information that genuinely represents the current design?

Are unresolved matters classified and owned?

Can the next team understand what it may rely upon and what remains conditional?

These questions do not demand perfection. They demand honesty about maturity.

Different stages need different evidence

The evidence required at Concept Design is not the same as the evidence required before tender or construction.

At concept stage, the project may need confidence that the basic asset logic works: access, massing, room or tenancy modules, vertical circulation, broad structural logic, service zones, fire principles, operator or client requirements and likely approval constraints.

At schematic design, the technical systems should be becoming credible. Plant space, major risers, MEP zones, structural interfaces, room data, BIM deliverables, cost assumptions and approval risks should be visible at an appropriate level.

At developed design, the project should be testing whether the consultants, authority requirements, operator/client decisions and cost decisions are genuinely coordinated.

Before tender or construction, the threshold becomes much higher. Drawings, specifications, schedules, room data, long-lead decisions, authority conditions, value-engineering changes and procurement assumptions need to tell a consistent story.

The gate therefore changes with the stage.

The principle remains the same: what is the next stage entitled to rely upon?

Not every uncertainty has to disappear

No complex project reaches a stage gate with every future question answered.

Some information is intentionally developed later. Some specialist design cannot be completed before procurement. Some authority matters remain subject to review. Some client decisions may be carried for a limited period because other work can proceed safely around them.

The problem is not residual uncertainty.

The problem is invisible residual uncertainty.

A mature project should be able to distinguish between three conditions.

First, matters that must be resolved before progression because the next stage cannot safely work around them.

Second, matters that may proceed conditionally because the residual risk is understood, an owner is identified and the consequence is acceptable.

Third, matters that are legitimately not yet active but must be picked up at a defined future point.

That distinction allows a project to move without pretending that every issue is closed.

Proceed, proceed with accepted risk, or do not proceed

This suggests a practical way of thinking about stage-gate outcomes.

A project can PROCEED when the stage purpose has been achieved and the remaining open matters do not undermine the reliability of the next stage.

It can PROCEED WITH ACCEPTED RISK when specific unresolved matters are visible, owned and judged acceptable for a defined period.

Or it can DO NOT PROCEED when the design is being asked to move forward while carrying issues that make the next stage unreliable.

The middle category matters.

Projects often need to progress before every uncertainty has disappeared. Governance should not become a reason to stop intelligent progress. But conditional progression should be explicit.

"We know this is unresolved, we know what it affects, we know who owns it, and we know when it must be closed" is very different from "we will sort that out later."

Risk acceptance is also a design decision

Sometimes a project knowingly proceeds with an unresolved matter. That can be entirely reasonable.

The question is whether somebody with the appropriate authority has understood what is being accepted.

What is the unresolved condition?

What are the plausible consequences?

What future work depends on it?

What would trigger escalation?

When does the risk become unacceptable if it remains unresolved?

Who has authority to accept it?

If those questions are not visible, the project is not really accepting risk. It is simply allowing uncertainty to travel.

What proves readiness?

Readiness should leave evidence.

The form of the evidence varies with the project and stage. It may include coordinated drawings, a model review, a signed-off decision, an updated cost plan, an authority response, a completed design-risk review, an operator comment closure record, a room-data milestone, an agreed procurement strategy or a documented residual-risk register.

The point is not to create a thick stage-gate report for every project.

The point is that the decision to progress should be based on more than a date and a feeling.

The evidence should answer the questions the next stage will depend upon.

The missing link: downstream dependency

One of the strongest ways to test readiness is to look forward.

What does each unresolved issue block next?

If a plant-room decision remains open, can the structure progress? Can the services routes be fixed? Can acoustic treatment be designed? Can procurement move?

If an operator decision is outstanding, does it block room data, MEP, FF&E, mock-ups or cost planning?

If an authority matter is unresolved, does it threaten consent, building form, access, fire strategy or staging?

If a value-engineering decision is not incorporated, can the tender package be relied upon?

This downstream view changes the stage-gate conversation.

Instead of asking only whether the current team has finished its deliverables, the project asks whether the next team has trustworthy inputs.

Closure must also be real

Another common stage-gate weakness is the use of status labels without evidence.

An issue may be marked closed because it was discussed, because a consultant responded, or because the client acknowledged the recommendation.

But if the issue affects design information, the project should be able to show where the consequence has actually been resolved.

A revised drawing. An updated model. An amended specification. A recorded approval. A cost-plan adjustment. A procurement confirmation. A certificate.

Closure evidence is important because stage gates are transfer points. The next stage should not have to rediscover supposedly closed issues.

Who should participate in a stage gate?

A stage gate should not become the design manager's private judgement. The value comes from assembling the perspectives that the next stage will depend upon. Depending on the project, that may include the client, architect, engineering leads, project manager, cost consultant, BIM or information lead, operator, contractor adviser and relevant statutory specialists.

The group does not need to review every drawing. It needs to test the small number of conditions that define readiness at that point. The cost consultant may confirm whether the current information supports the cost plan. The approval lead may identify conditions that still affect design. The BIM lead may confirm whether the model exchanges are aligned enough for the intended use. The operator may identify unresolved standards that would otherwise become late changes.

This multidisciplinary view is important because design maturity is rarely owned by one discipline. A package can be complete within architecture while still being immature as a project input.

What should a stage-gate record contain?

The record can be concise. It should show the gate decision, the evidence reviewed, any mandatory closures, any residual risks being carried forward, the owner of each carried item, the downstream dependency and the date or trigger by which the matter must be resolved.

That record becomes part of project memory. When a question reappears later, the team can see whether the risk was unknown, accidentally missed, or consciously accepted. That distinction matters commercially and professionally.

Stage gates are not bureaucracy

The phrase "stage gate" can sound corporate. Used badly, it can become bureaucracy: another meeting, another checklist, another approval box.

That is not the objective.

Good governance reduces confusion. It should concentrate attention on the few things that matter most at the transition point.

A useful gate makes open risk visible, clarifies responsibility, records what is being accepted and protects the next stage from unreliable information.

It should make projects faster by reducing avoidable rework, not slower by adding ceremonial process.

Stage gates improve learning as well as control

There is another benefit. When the same stage-gate questions are used across several projects, patterns become visible. A developer may discover that authority assumptions are repeatedly being carried too late. A design practice may see that plant and riser space is routinely under-tested at concept stage. A contractor may find that specification alignment is a recurring tender problem.

Those patterns can improve future briefs, consultant scopes, fee allowances and project programmes. The gate is therefore not only a control point for the current project. It can become a learning mechanism for the organisation.

The senior question

At every stage transition, one question deserves to be asked plainly:

Can the next stage safely rely on what we are handing over?

If the answer is yes, proceed.

If the answer is yes with conditions, record the conditions and the risk owner.

If the answer is no, a programme date should not be allowed to disguise the problem.

A stage gate is not a date.

It is a decision about the maturity of the information being transferred - and the quality of every downstream decision that will rely upon it.

Architecture Needs to Name the Design Manager

 

Conceptual image generated using AI under author's direction

The familiar parable of the blind men and the elephant offers a useful way to understand contemporary project delivery. Consultants, architects, consent reviewers and contractors may each possess valid knowledge of the part they touch. The problem begins when no one is explicitly responsible for seeing how those parts relate. That whole-project view is the particular responsibility of the design manager.

If design management is essential to project delivery, why is it still treated as an informal responsibility?

The recurring all-nighter exposes more than a difficult deadline. It reveals the absence of clear responsibility for managing design decisions, information, interfaces and change. Architecture already relies on design management; it is time to recognise and name the role.

In my recent ArchitectureLive! article, The All-Nighter Is a Governance Failure, I argued that the recurring late night in an architectural office is rarely just a deadline problem.

It is often the visible end of something that began much earlier: an unsettled brief, a delayed appointment, an unrecorded decision, an unresolved interface, an unrealistic promise or a change whose consequences were never fully examined.

The architectural team eventually absorbs these accumulated uncertainties because the drawings become the place where everyone else’s information must agree. What appears to be a production crisis is frequently a governance failure.

But that diagnosis leads to another question.

If projects need someone to manage decisions, information, interfaces, change and design-stage readiness, why does architecture still struggle to recognise design management as a distinct professional role?

The responsibility exists even when the job title does not

Design management is already happening on almost every complex project. The problem is that it is often happening informally, partially or too late.

A project architect may maintain the consultant programme. A senior architect may chase client decisions. A BIM coordinator may identify clashes. A project manager may track deliverables. A technical lead may review compliance. A director may intervene when an issue becomes critical.

Each person is addressing part of the design-management problem, but no one may be explicitly responsible for seeing the design-delivery system as a whole.

That fragmentation matters.

When responsibility is distributed without clear ownership, gaps become difficult to see. The programme records when drawings are due but not whether the decisions required to complete them will be available. Consultant appointments identify disciplines but not always the interfaces between them. Design meetings generate discussion, but actions may not be linked to accountable owners, consequences and decision dates.

The project appears organised because it has meetings, programmes, models and reports. Yet its unresolved dependencies continue to accumulate beneath that visible administration.

Design management is not the existence of more project information. It is the disciplined conversion of that information into timely, coordinated and traceable decisions.

A design manager is not simply another name for a project manager

One reason the role remains poorly understood is that design management is frequently absorbed into adjacent job descriptions.

It is not the same as project management, although the two must work closely together. Project management typically governs the wider obligations of time, cost, procurement, contracts, stakeholders and delivery. Design management concentrates on whether the design itself is sufficiently defined, coordinated, reviewed and evidenced to move safely from one stage to the next.

It is not the same as BIM management. BIM provides a digital environment for creating, exchanging and coordinating information. Design management determines what information is required, why it is required, who must provide it, what decision it supports and whether the project is ready to rely on it.

It is not identical to the lead architect’s role. The lead architect may be responsible for design quality, architectural resolution and the integrity of the design intent. The design manager protects the conditions under which that intent can be translated across disciplines, approvals, procurement and construction.

Nor is design management simply technical coordination. Coordination is one of its central functions, but the role begins before clashes appear and continues after drawings are issued. It includes the structure of the brief, decision authority, stage deliverables, review gates, change control, interface ownership, risk escalation and the relationship between design maturity and project commitments.

The distinctions are not territorial. They are necessary because modern projects are too interconnected for critical responsibilities to remain implicit.

The role sits at the point where authority and information meet

Architecture now operates within dense networks of specialist knowledge.

A seemingly small change to a hotel room can affect the operator’s requirements, structure, fire strategy, accessibility, services, acoustics, finishes, procurement, cost and programme. A façade decision can alter waterproofing, energy performance, structural support, maintenance access and consenting evidence. A ceiling coordination issue may reveal not a drawing error but a chain of unresolved spatial and engineering decisions.

Someone must see those relationships before they become late-stage emergencies.

That is the design manager’s distinctive field of attention.

The design manager asks:

• Is the brief sufficiently resolved for the stage being entered?

• Are decision-makers identified, and do they understand when their decisions are required?

• What information must be available before a design package can be completed?

• Which interfaces carry the greatest delivery risk?

• Are changes being assessed for their downstream consequences?

• Has each discipline worked to a compatible level of design maturity?

• Is there adequate time for coordination, checking and approval before issue?

• Does the evidence support the project’s claim that the design is ready to proceed?

These are not administrative questions. They determine whether the design can survive the journey from intention to construction.

Design management should make uncertainty visible

A well-managed project is not one without uncertainty. Architecture cannot eliminate uncertainty, because design develops through iteration and projects respond to changing technical, commercial and human requirements.

The objective is to prevent uncertainty from becoming invisible.

An unresolved matter should have an owner, a required decision date and a clearly stated consequence. A change should be understood not only as an instruction but as an intervention in a connected system. A stage review should establish whether the project is ready to advance, rather than merely confirm that a scheduled date has arrived.

This is where design management differs from bureaucracy.

Bureaucracy can record that a meeting occurred. Design management asks whether the meeting produced the decisions the project needed.

Bureaucracy can list deliverables. Design management tests whether those deliverables are coordinated, sufficiently mature and suitable for their intended use.

Bureaucracy can circulate a change. Design management makes its effect on other disciplines, approvals, cost, programme and completed work visible.

The purpose is not to create more control for its own sake. It is to prevent creative and technical effort from being consumed by avoidable rework.

The profession needs a clearer job description

Many architectural employment structures still move from architect to senior architect, associate and director, with specialisation recognised mainly through design, technical or commercial leadership.

Design-management capability often sits between those categories. It may be expected from senior staff but neither explicitly defined nor adequately supported. On contractor- and client-side teams, the title is better established, although its scope can still vary widely. Within architectural practices, it is often mistaken for diary management, document control or meeting coordination.

That understates both the expertise and the authority the role requires.

A meaningful design-manager job description should include responsibility for:

• design-planning and information dependencies;

• brief and deliverable alignment;

• consultant scopes and interfaces;

• decision schedules and responsibility structures;

• design reviews and stage-readiness assessments;

• change-impact evaluation;

• coordination and technical-risk escalation;

• design-quality assurance across issue cycles;

• connections between design maturity, procurement and construction; and

• organisational learning from repeated delivery failures.

The role also needs sufficient authority to challenge an issue date, escalate an absent decision or identify that a design package is not ready. Accountability without authority merely creates another person who can be blamed after the event.

From an informal craft to a professional discipline

I have been developing these ideas through a wider body of work provisionally structured as a Design Manager’s Manual.

The purpose is not to reduce architecture to checklists or to suggest that every project can be controlled by a universal procedure. It is to articulate the recurring governance questions that arise across the life of a project—from the formation of the brief and appointments through design development, coordination, approvals, procurement, construction and eventual learning.

The emerging framework examines design delivery across successive project stages and treats it as a control loop: establish requirements, allocate responsibility, coordinate information, test readiness, record decisions, manage change, verify outcomes and carry lessons forward.

The manual is therefore less about prescribing one way to design and more about protecting the conditions required for good design to reach the built outcome.

Architecture already teaches design history, representation, technology, professional practice and construction. It now needs a more explicit understanding of design management: not as an inconvenience imposed after design, but as a discipline that connects design intent with collective delivery.

Better design management is not less architecture

Some resistance comes from the fear that naming this role will make architecture more managerial and less creative.

The opposite is more likely.

When architects spend their most valuable hours reconstructing decisions, locating missing information, correcting unmanaged changes or resolving interfaces that should have been addressed earlier, creativity is not being protected. It is being taxed by disorder.

Good design management does not decide what architecture must become. It ensures that the people responsible for designing it have a credible brief, coordinated inputs, visible constraints and enough time for judgement.

It also creates a fairer professional culture. Teams should not have to compensate through private sacrifice for risks that were visible at project level. If a deadline depends on unresolved decisions, inadequate resources or incomplete information, those conditions should be surfaced while leaders still have choices—not transferred silently to the people producing drawings at midnight.

Name the role before the next crisis

The design manager will not eliminate every difficult deadline. Unexpected site conditions, urgent approvals and genuine opportunities will still demand extraordinary effort.

The test is whether extraordinary effort remains extraordinary.

When late working becomes predictable, the profession should stop treating it as evidence of commitment and examine the system that made it necessary. That examination requires more than general calls for better communication. It needs a person with a defined responsibility to connect decisions, information, interfaces and design-stage readiness.

Architecture already relies on design management. It is time to stop treating it as an unnamed extra carried by whoever happens to notice the gap.

The recurring all-nighter tells us that the responsibility exists.

The next step is to recognise the discipline, define the authority and name the job.

---

This essay accompanies “The All-Nighter Is a Governance Failure,” published by ArchitectureLive! Read the original article here: [ARCHITECTURELIVE ARTICLE LINK].

Working Smart - 3

Search emails in Outlook 2016

Finding that elusive email from someone can become a life and death situation for us in Outlook. Multiple projects, client emails, and a swamped email box with 50+ emails received on a daily basis can be difficult to track. You know the mail was from X with an attachment but several emails over months make it impossible to zero down on the particular email especially if it was sent several months back

This version of Outlook can make your life easier if you are willing to spend some time reading this post. Follow the 9 easy steps below and you can quickly search for that elusive email

1. Open Outlook and go to your Inbox. Click your mouse on the “Search Current mailbox”.

2. The moment you click in the search bar, the cursor will start flashing in anticipation of your search

3. Your tab will change as per the screen above.4

4. Now go to the dropdown box as per the black arrow

5. The dropdown box should display all the fields you could possibly search from

6. Click on the fields you want and they will start stacking up below the search bar as you click on the fields. These will then drop down every time you put your cursor in the search bar - ready to aid you in a search.

7. Typically you would need the subject, cc, To, Attachments(Yes/No) and From.

8. You can also use Body which is quite useful when you want to search by a word in the body of the email.

9. This can be done in your “Sent” folder as well.

Work Smart and Happy Searching!

Also Read:

Working Smart - 1 Finding that Directory

Working Smart - 2 Save your files with a date

Working Smart - 2

Saving your files with a date

On an average, you would be creating and accessing at least 10-12 documents, spreadsheets etc. Soon there would be hundreds if not thousands of documents piling up in your directory with different file names. Accessing it alphabetically may be an option but prefer to name my documents with a yymmdd_filename format which lists the documents in the directory in a nice organised way starting with the most recent ones on the top.

When I create documents in such numbers, I often forget the name of the document which I have created. Sometimes, I don’t access a document for several weeks which removes it from the recent documents list of word and excel. That’s where I end up using the search function in the Windows explorer. Explorer searches all the directories and subdirectories and highlights all the filenames starting with the year and month - if you have been saving all your files starting with the yymmdd prefix.

Work Smart and share your experiences of Working smart.

Working Smart - 1 Find that Directory

Working Smart - 3 Find that email

Working Smart - 2

Saving your files with a date

On an average, you would be creating and accessing at least 10-12 documents, spreadsheets etc. Soon there would be hundreds if not thousands of documents piling up in your directory with different file names. Accessing it alphabetically may be an option but prefer to name my documents with a yymmdd_filename format which lists the documents in the directory in a nice organised way starting with the most recent ones on the top.

When I create documents in such numbers, I often forget the name of the document which I have created. Sometimes, I don’t access a document for several weeks which removes it from the recent documents list of word and excel. That’s where I end up using the search function in the Windows explorer. Explorer searches all the directories and subdirectories and highlights all the filenames starting with the year and month - if you have been saving all your files starting with the yymmdd prefix.

Work Smart and share your experiences of Working smart.

Working Smart - 1 Find that Directory

Working Smart - 3 Find that email

Working Smart - 1

Over the years as we have transitioned from a traditional workplace with physical files to the networked environment with information being stored virtually. With numerous people working on projects from multiple locations, information cannot be kept on individual machines and needs to be saved on servers. Information needs to be accessible instantly and to everyone.

Most companies have IT protocols in place instructing people of the do’s and don’ts. But rarely will you find tips about how to work smart and these posts are all about working smart and having information at your fingertips. 

Finding that directory

A large part of my work is to update the various documents, reports, and registers that need to be maintained in a Project Management environment. I prefer to use a shortcut on my desktop with the link to the directory saved and I am ready to go. 

This way, I access the correct folder every time and I do’t have to remember the long path to the directory.  which more often than not would be nested several levels below your project folder. These links can then be safely saved on your desktop. 

If you have too many links – create a word document on your desktop and use the function available in word to hyperlink to your directory/directories and you will panic less when you need that information quickly.

Work Smart and share your experiences about Working Smart

Also Read:
Working Smart - 2 Save your files with a date
Working Smart - 3 Find that email

10. Entertain the team with emails written in (im)proper English

Image courtesy rakratchada torsap / Freedigitalphotos.net

As the last post in the series 10 (un)common mistakes to avoid in Project Management, I conclude the series with this post. here are some lines extracted from emails written. The lines have not been modified and I will leave it to the reader to interpret some of the meanings. If this becomes impossible or if you end up doubling in laughter or both, go to the end of the post where I have put in some hints about the lines. I have highlighted the faux pas in bold and italics. Some of them are really priceless nuggets. Have fun

1. … let us give pleasure to the client …
   
2. I don't what you to advice or work on any problem......
   
3. If [Person] what any information from your end or what your input for any …...
   
4. Let's discusses in detail when we come there......
   
5. I thought much , now can a they say the submission is on [day of the week] . All the tender which you see in [Place], they is no fixed date for submission. Anyways we will submit the same on [Date] .
   
6. I don't what you to work on your …....
   
7. How whats the problem …...
   
8. we have haired him has [Designation]. I what him to do that...
   
9. he what's [Place] team to make a ….
   
10. I what this to be done before …..
    
11. they what Engineers full time....
    
12. Please advice , so that we don't what 100 idea in between. I what every one.....
    
13. Please note - Team is busy with Project can waste time in training every day. Let's do it once and close it asap.

Hints

• For the first one read pleasure as pressure
• Read what as want
• Now and how are interchangeable
• they and there are interchangeable

Links to the previous posts
9. Don’t govern by threats
8. Support the team on the Ground
7. Provide Mission Critical information to the Project Team
6. Resource appropriately
5. How to (not) do your budget in five easy steps
4. Read the contract you just signed
3. Don't promise the impossible in a ridiculous timeframe
2. How (not) to win a contract
1. New Business Areas

9. Don’t govern by threats

Image courtesy Stockimages / Freedigitalphotos.net

As a cherry on the cake, complete the circle by threatening employees by a variety of threats and bully them into submission. Completely politicise the working atmosphere by turning each employee against the other and follow through by asking each employee to “report” about the others privately. Although these may be stone age tactics, these are used effectively by managers in dealing with a new and superbly qualified professional team. 

International organisations world over recognise bullying to be detrimental to the work process. Some of the signs of bullying are :

• Micromanagement at all stages of the work process hamper the flow of the work and indirectly question the integrity of the employees. This effectively reduces an experienced employee to a rookie who needs to ask for instructions at every stage
• Intruding privacy with phone calls at odd hours and clear threats to answer emails received on hand held devices within minutes of receiving them. Not answering phone calls or emails would lead to a “dressing down” in front of other employees – another clear bullying tactic.
• Displaying intimidating behaviour about specific employees in front of other employees in their absence by threatening to fire them – incessantly and constantly.
• Constantly deflecting requests for personal time off which is contractually due to the employee thereby traumatising employees.

To top it all, none of these “rules” are available in the company rule book or available from the Human Resource department.  The employee has little or no choice but to fall in line with the bullying tactics of the boss. The employee can

• Establish ground rules and areas to allow the “micromanagement” to slowly metamorphose to a stage where it becomes redundant or even stupid
• Gradually and firmly, establish the limits of office time and private family time.
• For the intimidating behaviour, the employees could unite against such behaviour and stand up to the bully. After all, one can’t “fire” the team all at once.
• For the requests of leave, if it is clearly due and official, the employees should stand up for their rights. Eventually, the bully will back down.

In the tenth and concluding post, look forward to an entertaining piece on email writing. Links to the previous posts are below

8. Support the team on the Ground
7. Provide Mission Critical information to the Project Team
6. Resource appropriately
5. How to (not) do your budget in five easy steps
4. Read the contract you just signed
3. Don't promise the impossible in a ridiculous timeframe
2. How (not) to win a contract
1. New Business Areas

8. Support the team on the Ground

Image courtesy:  africa / Freedigitalphotos.net

Mistakes happen. Sometimes several of them at once or in a sequence. The team on the ground, under most circumstances at least has the strong support from the core team which is experienced and has encountered many such difficult project situations. Not So.
The core team is busy with other projects or is simply interested in churning out the monthly invoices to protect the bottom lines and manage salaries of the team. Support and advice in the form of a conference call can become difficult to organise.  In strictly hierchical firms, independent decisions by project teams are vigourously controlled where the project delivery becomes a risk.
Looking back at such situations, one could:

• Draw up clear protocols for raising project related issues all the way to the top of the hierarchy of the firm. Even top management including owners should remain accessible for project related issues. The access can of course be controlled and monitored so as to involve them in only crucial issues.
• Regular contact with the project team in forms of conference calls or meetings.
• If meetings or calls do not become possible, regular reports should be scrutinised and advice given for crucial, unanswered issues

In the next post, I shall be discussing the ninth point in the series – Don’t govern by threats.
Links to the previous posts
7. Provide Mission Critical information to the Project Team
6. Resource appropriately
5. How to (not) do your budget in five easy steps
4. Read the contract you just signed
3. Don't promise the impossible in a ridiculous timeframe
2. How (not) to win a contract
1. New Business Areas

7. Provide Mission critical information to the project team

Image courtesy Stuart Miles / Freedigitalphotos.net

After all the mistakes listed so far, an employee would definitely expect to start the project with all the critical and important information necessary for the project. Not likely. The team who has put together the project does not deem it necessary that the Project delivery team has all the critical information required for the timely delivery of the project. This is often due to lack of trust while passing on the information and mistaking the delivery team to be a an adversary rather than an important part of the project delivery process. When members of the team come from several different cultures, countries and time zones this often becomes a major problem to the delivery of the project.
Important milestones in the contracts are missed consistently because of this lack of communication. This affects the overall project delivery and in some serious cases this has led to the entire contract being terminated and the teams of the stakeholders entering into arbitration. This is a messy, time consuming affair which can be avoided.
Simply put,

• Communicate with your team about the key milestones of the projects
• Ensure that the team is “on the same page” and everyone is not following their own agendas.
• Communication protocols should be clearly established especially when teams from various nationalities, cultures, educational backgrounds and disparity of ages is coming together to deliver the projects in countries of the Middle East or Africa. This becomes critical when people are working across several time zones at once.

In the next post you can look forward to Support your team on the Ground.
Links to previous posts
6. Resource appropriately
5. How to (not) do your budget in five easy steps
4. Read the contract you just signed
3. Don't promise the impossible in a ridiculous timeframe
2. How (not) to win a contract
1. New Business Areas

6. Resource appropriately

To recruit the right person for the job is an an extremely rare expertise for companies to have in today’s fast paced world. A lucrative package with a fancy tag in an exotic sounding location sounds great but comes with its own pitfalls. By promising  a stable, lucrative position in today’s unstable job market, an employee is led to believe that past experience and expertise has helped him/her get the post but in all likelihood one is being set up by the employer. This becomes a necessity when all the mistakes listed in the past five posts have happened – either by conscious design or by an unnatural twist of fate.

While your employer may have signed a milestone based contract, they may have provided resources based on a timesheet based contract. Needless to say, resources that may be required at construction stage are not useful at early design stages. Construction Management resources adept at handling complex sites end up twiddling their thumbs while Design Coordination struggles due to lack of resources.

Several such situations like this may have arisen where such challenges in some form or the other present themselves to Project Managers. Under such situations, choices are limited to:

• Adapt to the challenge by accepting the situation as it unfolds in a new job situation
• Be pro active and raise a flag about the inadequacy and wrong type of resources which could potentially backfire.

A compilation of experiences on similar situations may add to our body of knowledge and will improve Project delivery to clients and modify our working methods.

Links to previous posts

5. How to (not) do your budget in five easy steps

4. Read the contract you just signed

3. Don't promise the impossible in a ridiculous timeframe

2. How (not) to win a contract

1. New Business Areas

5. How to (not) do your budget in five easy steps

Image courtesy patpitchaya / Freedigitalphotos.net

If you have reached to the point where you have to give the budget for your project after you have systematically made all the four mistakes listed previously, you are either plain lucky or a sitting duck. More likely the latter!
Here’s how to (not) do a budget. Imagine the scenario in the Post # 3. For that scenario, do the following:

1. Get the rates for a single house from a local contractor. Extrapolate the rates to 1500 houses. Simple
2. Cross check the rates against your home country rates. Rest in the comfort that they are much higher than your home country rates.
3. Ridicule all the advice by your own staff related to employing qualified Quantity surveyors by saying “That’s how we do it here.”
4. For the rates that are not available locally, use your home country rates, multiply them by some factor and build them up. Simple. Not rocket science is it?
5. Float your budget to the client

The fact that the project is the first of its kind in a less developed place, in a ridiculously impossible time frame, should not matter. Armed with this “budget” go ahead and float your tender to international contractors.
Obvious lessons from this post are

• Budgets prepared by such rudimentary methods can not be the basis to go to tender. This clearly misguides the client into believing a budget which will not stand the test when the bids come back.
• The Project Manager’s budget – if prepared at all, should not be shared as a Cost Plan document to the client.
• Do not hesitate to employ local professionals who will give you a correct picture of the rates and an accurate and reliable number.

Links to previous posts of this series
4. Read the contract you just signed
3. Don't promise the impossible in a ridiculous timeframe
2. How (not) to win a contract
1. New Business Areas

4. Read the Contract you just signed

Sounds strange? Impossible? Three out of four times? Chances are that the contract that you have been handed over to execute has not been read by the person who signed it.  

Unbelievable as it may sound pressures of time, lack of appropriate resources and a desire to grab the contract often lead to these situations. In the contract that has been signed for you to execute has all the deliverables in the world that the client could think of. Not to mention the ridiculous time frame in which to execute them. It would be an unfortunate situation if you have such a situation to deal with. Disastrous if this is the fourth in the series of mistakes that have happened and you happen to inherit the consequences.

Some lessons you could learn would be (Pardon me for stating the obvious)

• Read the contract (before signing it of course!) and iron out the kinks. Both parties entering into the contract have an unsaid right to review the contract before it gets to the signing stage.
• It does a lot of good to your company’s professional reputation if you suggest a few changes which may have been missed out inadvertently.
• Save on “fan cleaning” costs at  later.

The next in the series is about getting your budgets right.

Links to the posts in this series

3. Don't promise the impossible in a ridiculous time frame

2. How (not) to win a contract

1. New Business Areas