Why project readiness deserves the same attention
as budget and schedule
Evidence-based design changed how our industry thinks. We no longer justify a window in a patient room by intuition; we point to research connecting daylight to healing. In healthcare, design decisions are now expected to carry evidence.
The dashboards governing healthcare capital projects track cost, scope and schedule. But when we trace delays back to their origins, they tend to begin in the places dashboards don’t monitor: stakeholder alignment, governance, clinical engagement, and the preparedness of the organization itself. If we demand evidence before designing a patient room, it is strange to rely on instinct when deciding whether we are ready to proceed.
The idea of a “readiness gap” is not new. The construction industry has scored the definition of complex projects for decades. The Construction Industry Institute’s Project Definition Rating Index is one precedent, and it consistently shows that well-defined projects outperform poorly defined ones. Health services research has separately validated instruments measuring organizational readiness for change. What has been missing is a measure built for healthcare capital projects that brings those threads together.
“On budget
is not the same as Successful”
Why Readiness, and why now
Healthcare infrastructure delivery in Canada, the United Kingdom and Australia is shifting the same way: away from monolithic, multi-billion-dollar builds and toward smaller, phased investments that make better use of the buildings we already have. But more phases mean more transitions, and every transition is a readiness question.
Adhering to a budget does not guarantee a successful outcome for patients or staff. Even modest renovations introduce hidden burdens absent from financial ledgers: clinical care managed beside construction barriers, personnel navigating redirected pathways, and teams working through months of displacement.
While the builder monitors the bottom line and the architect focuses on technical specifications, readiness asks a broader question: is the institution truly prepared to realize its original vision?
Problems that refuse to stay in their lane
I recently observed how a technical question turned into something else entirely. A secure room in a clinical support area carried a strict federal construction requirement. The structural solution on the drawings was sound engineering, but it did not quite satisfy other technical and functional requirements.
The estimator flagged the correction as an added cost. Relocating the room would have unsettled users who had already absorbed several rounds of change.
In the span of one email thread, a technical problem became a cost problem that was becoming a people problem.
The reverse happens just as often. A project is green-lit, the team is working well, the schedule is holding. Then the senior leader who championed it retires or is promoted away. Nothing technical has changed, but decisions slow, momentum breaks, and a project ready to advance stalls. A dashboard records that as a change order or a schedule slip. Readiness would have seen it coming.
Readiness Index
Wellness Environment
Operational Performance
Planning
Human Resources
Financial
The Readiness Index
The Readiness Index we have developed reads a project across five categories, each carrying equal weight. Three are technical: the wellness environment (infection prevention, thermal comfort, accessibility, wayfinding) represent the qualities that make a healthcare facility worth building at all); operational performance (adjacencies, walking distances, and whether the plan works for the people who will staff it measure both facilities requirements but the workforce to run them); and planning (equipment, phasing, procurement, and a clear-eyed look at whether existing space could serve before anything new is built). A fourth component is human resources (leadership continuity, governance depth, and the organization’s capacity to make decisions and hold them. The fifth is financial.
Two choices are very explicit. The first is sequence: the technical and human categories must mature before the financial conversation means anything. You cannot responsibly cost an emergency department before knowing whether it needs ten more exam rooms or twenty-eight. The second is proportion: cost carries one-fifth of the weight. On most dashboards, it carries all of it, and cost alone has never told anyone whether a project was ready.
A SCORE THAT IS EASILY UNDERSTOOD
Each category feeds a single weighted score out of 1,000, read much like a credit rating: what matters is whether it clears the line that unlocks the next decision. Plotted by category, a readiness profile looks like a sound equalizer, five bars rising toward a midline.
The balanced project sits above that line and can proceed with confidence. The underdeveloped Project sits low everywhere; the conversation there is about building leadership, governance and a funding path before it deserves a schedule at all. Traditional project is the interesting one: planning is strong and the drawings are well ahead, but human resources and financial readiness sit well below the line. On a conventional dashboard, Traditional project looks like the healthiest project in the portfolio. On a readiness profile, it is a project about to make commitments its organization cannot keep.
The index is not a straitjacket. It does not ask whether a team chose the most elaborate solution, only whether the question was genuinely considered. A team that has thought through wayfinding earns its points whether the answer is signage or a dedicated consultant. A team that never asked does not.
Clover does not score a project alone. We facilitate the scoring conversation with the project’s steering committee, so it is owned by the people it serves. A shared score also depersonalizes weakness. “Human resources needs attention” is a very different sentence from “your department is behind.” Nobody is blamed, so nobody gets defensive.
“Consensus is easy to build when everyone can see where they are strong and where they are not.”
WHEN THE SCORE SAYS WAIT
A low score shifts the conversation from pushing forward to building a mitigation strategy: focused sessions with executives, deeper engagement with users, a targeted effort on whichever category is holding readiness back. It also leaves a record of what was known when, so consultants are not designing against an unstable brief and clients are not discovering unreadiness through a change order.
Where AI fits and where it doesn’t
Generative AI now drafts meeting minutes, assembles agendas, and organizes documentation in a fraction of the time these tasks once demanded. But readiness is strategic judgment about a particular organization at a particular moment. AI can surface the issues that deserve a conversation, but it can neither have the conversation nor resolve the complexity of working in teams.
are you ready?
Budgets tell you what a project costs.
Schedules tell you when it finishes.
Readiness tells you whether it will.
This fall, I will be joining the panel
“Closing the Loop: How Strategic Predesign Makes Activation and Accreditation Predictable” at the Canadian Centre for Healthcare Facilities conference in Toronto, part of a program dedicated to operations, readiness and risk.
If readiness is on your mind, I would welcome the conversation.