Your 2026 Development Readiness Checklist
A project rarely fails because the idea was bad. It fails because something fundamental was assumed instead of confirmed.
In 2026, development readiness is not about moving faster. It is about removing uncertainty early, before it turns into delay, redesign, appeals, or litigation. Developers who succeed are not those who push the system hardest, but those who understand it best.
This checklist sets out what private developers must prioritise if they want projects that are bankable, approvable, and deliverable.
What does development readiness means
Development readiness means you can answer “yes” to the following questions before committing serious capital:
- Are the land use rights clear and defensible?
- Is the proposal aligned with the municipality’s spatial policy?
- Do you understand the full statutory pathway and its risks?
- Are infrastructure constraints accounted for?
- Can the approvals withstand objections or appeals?
If any of these are uncertain, the project is not ready.
How to test readiness
If you want approvals that are bankable and defensible, readiness has to be tested from more than one angle, not assumed. The points below are practical readiness checks you can use at any stage to pressure-test the fundamentals, surface risks early, and strengthen the quality of what you submit. Treat them as a checklist you return to throughout the project, not steps you complete once.
Check 1: Confirm land use rights before committing design fees
Too many projects advance on the assumption that zoning can be “fixed later”. In practice, this is where risk starts.
Readiness requires:
- Written confirmation of zoning and applicable land use controls.
- Understanding of Land Use Scheme definitions and primary versus consent uses.
- Awareness of local development frameworks (precinct plans), overlay zones, title deed restrictions, and special conditions.
- Realistic assessment of rezoning or departure prospects.
Developer Action: Do not proceed beyond early concept design without confirmed land use rights.
Check 2: Build SPLUMA alignment into the business case
Approval risk increases sharply where a proposal conflicts with the SDF or spatial policy.
Readiness requires:
- Understanding where the municipality wants growth. Make sure the IDP and municipal budget make provision for infrastructure spending in your area of interest.
- Aligning density, scale, and land use with policy intent.
- Avoiding speculative proposals outside identified development areas.
SPLUMA alignment is not a planning formality. It directly affects approval certainty.
Developer Action: Include a short SPLUMA, SDF and IDP alignment assessment in early feasibility studies.
Check 3: Map the full statutory pathway upfront
Delays often arise not from refusal, but from poor sequencing.
Readiness requires:
- Identifying all required approvals.
- Understanding dependencies between processes.
- Allowing time for public participation and possible appeals.
- Knowing which approvals must precede others.
Submitting applications in the wrong order wastes time and credibility.
Developer Action: Prepare a statuory approvals roadmap at project inception.
Check 4: Identify risk early and honestly
Risk is not only financial. It includes:
- Community objection and appeal risk.
- Judicial review risk.
- Infrastructure capacity risk.
- Institutional capacity risk within the municipality.
Ignoring risk does not remove it. It only postpones its impact.
Developer Action: Undertake a formal development risk scan before submitting any statutory application.
Check 5: Treat public participation as a risk-management tool
Public participation done at the minimum level often triggers maximum resistance.
Readiness requires:
- Early engagement on sensitive or high-impact sites.
- Plain-language communication, not technical defensiveness.
- Addressing genuine concerns before positions harden.
Once objections escalate into appeals, timelines and costs increase dramatically.
Developer Action: Design a participation strategy based on project risk, not statutory minimums.
Check 6: Confirm infrastructure reality before final feasibility
Land use rights without infrastructure are not bankable.
Readiness requires:
- Written confirmation of water, sanitation, electricity, and access capacity.
- Understanding upgrade costs and funding responsibilities.
- Aligning development phasing with infrastructure availability.
Approvals granted without planning for viable services often lead to stalled implementation.
Developer Action: Secure service confirmations before finalising financial models or funding applications.
Check 7: Test approval conditions immediately
Conditions of approval can materially change project viability.
Readiness includes:
- Reviewing conditions as soon as they are issued.
- Identifying cost, timing, and responsibility implications.
- Don’t delay challenging unworkable or vague conditions through representations or appeals.
Accepting problematic conditions creates long-term delivery risk.
Developer Action: Never accept conditions of approval without a formal internal review.
Check 8: Prepare for objections and appeals
Appeals are not an exception. They are a reality of development.
Readiness includes:
- Strong motivation reports.
- Clear records of process and engagement.
- Professional teams experienced in appeal procedures.
Projects fail when appeals are treated as unexpected disruptions.
Developer Action: Build appeal, risk, and timelines into project planning from the outset.
Check 9:Choose advisors who understand the system, not just the rules
Technical compliance alone is not enough. Developers need advisors who understand:
- How municipalities actually make decisions.
- Where approval risk typically arises.
- How to resolve issues before they escalate.
The wrong advice early on is expensive later.
Developer Action: Appoint planning and legal advisors with proven approval and appeal experience.
Why this matters in 2026
This year, scrutiny on development approvals will intensify. Municipalities face pressure to enable growth while managing risk. Communities are more informed and more willing to object. Infrastructure constraints are more visible.
In this environment, development readiness is not optional. It is a competitive advantage.
Developers who prioritise statutory clarity, risk awareness, and alignment from the start will deliver more consistently, with fewer surprises.
Those who rely on assumptions will continue to lose time, money, and momentum.
Just In: High Court Blocks Attempt To Charge Business Rates On Residential Sectional Title
The City of Johannesburg tried to charge business rates on certain residential sectional title properties. That would have meant a much higher monthly rates bills for owners. The High Court has now stopped this, again.
What happened? The City wanted to classify some residential sectional title units as “sectional title business”. The Valuation Appeal Board said this was wrong and confirmed that it should be “sectional title residential”. The City then tried to take the matter further, but the High Court refused permission to appeal and dismissed the application with costs. (Judgment dated 28 January 2026.)
Why it matters for developers: Rates can make or break feasibility. If a residential scheme is incorrectly billed at a business rate, operating costs jump and affordability assumptions fail. Do not assume the rates category is correct. This case shows it can be challenged and corrected through the valuation objection and appeal process. It improves certainty for residential sectional title in Johannesburg. The court has confirmed, again, that these kinds of properties should be charged residential, not business, rates.
The bottom line: For the affected properties, owners will pay residential rates, not inflated business rates. For developers, it is a clear reminder: check the rates category early and build it into your feasibility, just like zoning and services.
Source: City of Johannesburg Metropolitan Municipality and Another v The Valuation Appeal Board for the City of Johannesburg and Another, Gauteng Division, Johannesburg High Court, Case 20074/2022, judgment dated 28 January 2026 (leave to appeal).
