A development can pass its first test and still fail the one that matters.
The numbers may support the land, demand may be credible and the concept may fit the market. Then the project meets the conditions that make delivery possible: power, water, access, approvals, funding, procurement and a programme that can survive contact with them.
That is where the real viability question begins.
Across South Africa, developers are weighing elevated construction costs, funding friction and infrastructure constraints alongside the usual questions of yield and demand. None of these pressures is new in isolation. The risk is treating them as separate workstreams, or assuming that a positive answer in one makes the others easier.
A project can show an acceptable return on a spreadsheet while depending on a municipal connection date that has not been confirmed, a cost plan built on an outdated brief, or a procurement route that cannot secure a long-lead item in time. Each assumption may look manageable on its own. Together, they can change the funding requirement, the opening date and the value of proceeding.
This is not an argument for adding another layer of reports. It is an argument for testing the decisions that carry the most consequence while they are still reversible.
Start with the critical dependencies. What infrastructure capacity is available, and what evidence supports the date it will be available? Which approvals sit on the critical path? Are access, servicing and utility interfaces understood, or merely listed as items to resolve later? A programme is only as credible as its dependencies. Giving an uncertain date a place on a bar chart does not make it less uncertain.
Then test cost and affordability against the same version of the project. If the design changes, the cost plan must move with it. If the cost moves, the effect on funding, yield and affordability needs to be visible before the next commitment is made. A contingency is not a substitute for understanding what can consume it. Nor is a low initial estimate useful if it depends on a procurement assumption the market cannot support.
The sequence matters. Early procurement can protect a programme where supply is constrained, but committing too soon can lock in a solution before design, approvals or infrastructure conditions are settled. Waiting for perfect information is not a strategy either. The practical task is to identify which decisions can be made now, which need a defined evidence threshold, and what changes if the threshold is missed.
That calls for joined-up judgement across development advisory, quantity surveying, project management and design. The point is not to make every specialist responsible for everything. It is to make the hand-offs explicit: a demand assumption informs the brief; the brief informs the cost plan; cost and procurement choices shape the programme; infrastructure and approvals test whether the proposed sequence is feasible. When those connections are visible, a director can see not only the current forecast, but the conditions under which it remains true.
The strongest project review is therefore not a single verdict of viable or not viable. It is a clear account of what must be true for the project to proceed, what evidence supports each condition, who owns the next decision and when the assumption needs to be revisited. Where uncertainty cannot be removed, it can at least be priced, assigned and managed deliberately.
For principals and development teams, that changes the conversation from “Can we make the numbers work?” to “What has to happen, in what order, for these numbers to remain credible?” The second question is less comfortable. It is also more useful before capital, design effort and reputation are committed.
Infrastructure capacity, affordability and delivery are not separate chapters in a feasibility study. They are connected conditions of the same investment decision. Test them together, early enough to change course, and viability becomes something the team can manage rather than a conclusion it hopes will hold.