Performance Based Ramp Solution Example
A stair at the main entry can turn a straightforward approval pathway into a design, compliance and risk problem very quickly. A strong performance based ramp solution example shows how to move beyond a simple prescriptive check and develop an access pathway that is equitable, buildable and capable of standing up to scrutiny under the NCC.
For many projects, the issue is not whether a ramp is needed. It is whether a Deemed-to-Satisfy ramp can physically fit, preserve required circulation, respect existing structures, and still deliver dignified access. This is where performance solutions become valuable. They are not shortcuts around compliance. They are alternate compliance pathways that need disciplined reasoning, evidence and careful documentation.
When a performance solution for a ramp becomes necessary
In Australian projects, the trigger is often spatial constraint. A new building entrance might sit above street level with limited frontage. A refurbishment may involve structural walls, heritage fabric, flood levels or service conflicts that make a standard compliant ramp impractical. On other sites, a DTS arrangement may technically fit but create awkward travel distances, poor surveillance, unsafe landings or an entry sequence that separates people with disability from the primary path of travel.
That last point matters. Access is not only about dimensional compliance. It is also about equivalent or improved usability. A ramp solution that sends wheelchair users to a side door while everyone else uses the front entry may satisfy a narrow brief but still fail the broader intent of equitable access. A properly developed performance pathway should address that gap rather than formalise it.
A performance based ramp solution example in practice
Consider a mixed-use retrofit with an existing floor level 900 mm above the footpath. The tenancy frontage is shallow, the boundary condition is fixed, and the available internal depth from entry door to the first major circulation point is limited. A Deemed-to-Satisfy ramp at 1:14, with compliant landings and circulation clearances, would consume most of the entry area and materially affect leasing value, queuing space and egress legibility.
In this scenario, the project team may explore a performance solution based on a shorter, steeper ramp combined with supporting measures. For example, a ramp graded at 1:10 over a limited rise, with intermediate landings, upgraded handrails, high slip resistance, continuous edge protection, strong visual contrast, improved lighting, weather protection and direct alignment to the principal entrance. The proposal may also include automatic door operation, increased landing dimensions at decision points, and a clear passing and resting strategy nearby.
Would that be acceptable? It depends on the facts, the building use, the user group, and the quality of the evidence. A steeper ramp can increase user effort and may not be appropriate in many settings. But performance solutions are assessed against Performance Requirements, not against a simple one-for-one swap of prescriptive dimensions. The key question becomes whether the proposed design delivers a level of access that is suitable, safe and dignified in the actual project context.
What makes this kind of example credible
A credible performance based ramp solution example does not begin with, "the compliant option does not fit" and end there. That statement may explain the design problem, but it does not establish compliance. The solution needs a clear framework.
1. Define the access objective properly
The objective should go beyond getting a wheelchair over a level change. It should identify the required path of travel, the expected users, frequency of use, staff support assumptions if any, weather exposure, proximity to the principal entry, emergency considerations and how the route compares with access available to other occupants.
2. Identify the relevant NCC Performance Requirements
The analysis needs to map the proposal to the applicable Performance Requirements for access, safety and usability. Depending on the project, related issues can also include egress, circulation spaces, door operation and interfaces with the public realm. If the performance solution relies on several compensating features, those features need to be tied back to a coherent compliance rationale rather than presented as a loose package of improvements.
3. Test against evidence, not preference
Evidence can include relevant standards, expert judgement, anthropometric considerations, user capability data, comparable built outcomes, risk analysis and project-specific design modelling. In some cases, stakeholder consultation and operational input are also important. The evidentiary burden is higher where the departure from DTS parameters is more substantial.
4. Document trade-offs honestly
This is where many weak submissions fall over. If the ramp is steeper, the submission should acknowledge the increased exertion and explain how the limited ramp length, landing frequency, handrail design, resting opportunities and direct entry alignment reduce that impact. If the route is weather exposed, the documentation should address drainage, slip risk and maintenance. Performance solutions are stronger when they confront the downside rather than pretending it does not exist.
The design variables that often shape the outcome
Ramp performance is rarely determined by gradient alone. Usability is affected by a cluster of conditions working together.
Landing size and location can either support independent movement or create awkward stopping points. A short ramp with generous, level landings may outperform a longer arrangement that technically complies but forces convoluted turns. Door pressure and automation matter because the user often reaches the doorway with reduced momentum or occupied hands. Surface finish matters because poor slip resistance can turn a theoretically acceptable gradient into a practical hazard, particularly in external conditions.
Handrails and kerb rails should be considered as functional elements, not decorative attachments to a compliance drawing. Their continuity, grip profile and relationship to the landing affect confidence and control. Visual contrast also has a practical role for people with low vision, especially where grade transitions are subtle or lighting changes occur at the threshold.
The broader circulation pattern is equally important. If the ramp meets the entry but funnels users into a pinch point, security gate, queue zone or heavy swing door, the access problem has simply moved further inside the building.
Where projects commonly go wrong
A frequent mistake is treating the performance solution as a justification exercise after the design is already fixed. By that stage, options are limited and the documentation tends to be defensive. A better approach is to test access scenarios early, before tenancy layouts, façade modules, structure and services lock in the geometry.
Another problem is assuming that one concession can be offset by an unrelated improvement. For instance, a steeper ramp is not automatically made acceptable by adding signage. Compensating measures need to be relevant to the actual usability issue. They also need to be maintainable. If the solution relies on staff assistance, management procedures or equipment, the project team should be realistic about whether those controls will still work in five years.
There is also a risk in over-focusing on wheelchair circulation while missing other users. People with ambulant disability, low vision, cognitive disability or reduced stamina may experience the route differently. The strongest access outcomes are usually those that consider a broad user spectrum from the outset.
Why this matters for approvals and project risk
Certifiers, authorities and asset owners are generally more comfortable with performance solutions when the logic is transparent and the drawings match the written analysis. Gaps between consultant reports, architectural documentation and operational assumptions create approval friction. They also create downstream risk if the built outcome differs from what was assessed.
For developers and builders, there is a commercial dimension as well. A poorly reasoned ramp proposal can lead to redesign, delayed approvals and expensive on-site changes. By contrast, a well-prepared strategy can protect usable floor area, maintain design intent and still deliver a compliant path of travel. That balance is often the real value of specialist access input.
On existing and heritage sites, this balance becomes even more critical. The right response may not be a single ramp at all. It may be a coordinated package involving a regraded threshold, platform transition, entry relocation, external works adjustment and a documented performance argument showing why the resulting pathway better satisfies the project constraints and access objectives than a nominal DTS overlay.
What a good submission usually includes
A strong submission usually combines concise narrative, clear plans and sections, measurable design data, references to the relevant NCC framework, and a reasoned explanation of why the proposed outcome is at least equivalent in performance. It should also describe any assumptions about operation, maintenance and user interaction. If the design depends on automatic doors, sheltered surfaces or tactile and visual cueing, those items should be shown on the documents, not left to later interpretation.
This is where an integrated architectural and access consulting approach helps. The compliance pathway is more persuasive when it is embedded in the design rather than layered over it as an afterthought.
A performance based ramp solution example is useful because it shows the discipline behind alternate compliance, not just the final detail. The lesson is simple enough: if the standard path does not fit, the answer is not to lower the bar. It is to build a better argument, supported by a better design, so the finished environment works for people in real use, not only on paper.