When the Finished Floor Level Has to Rise, One Number Moves a Whole Chain of Cost

When the Finished Floor Level Has to Rise, One Number Moves a Whole Chain of Cost

General information for South Australian landowners and small developers only. This is not planning, engineering, surveying, building-surveying or cost advice. This account is anonymised and simplified, and the fact that one proposal was approved is not an indication that any other will be — every application is assessed on its own merits against the Planning and Design Code by the relevant authority. What sets a finished floor level on a particular site, and what is required to achieve it, are questions for your own civil and structural engineers, your surveyor and your building certifier; questions about the assessment pathway belong with a planning consultant; questions about construction cost belong with a quantity surveyor or your builder. Requirements and standards change over time, so confirm the current position for your own site before relying on anything here.

One number on a drawing

On a set of plans, the finished floor level is a single annotation. Change it and the drawing looks almost the same.

On a sloping site, that annotation is not a number. It is the datum the entire project is built off. Raise it and a series of other things can move with it: the footing design, the extent of retaining, the earthworks quantities, how far the driveway has to climb in the same horizontal distance, where the stormwater starts its fall, and how each building reads against its neighbours in daylight and overlooking terms. Which of those actually move on a given site, and by how much, is site-specific — a matter for the project's own engineers and designers. What they have in common is that none of them are visible on the plan view, and several of them can carry cost.

This is an account of a project in Adelaide's southern suburbs where exactly that happened: the finished floor level had to rise to meet the requirements applying to the site. Five townhouses, a site with real fall across it, and one number that moved everything downstream of it.

Why a level is never just a level

It is worth being concrete about the chain, because owners routinely price the first link and miss the rest.

Footings and site classification. A deeper or differently-loaded footing system is not necessarily a linear cost. What a site requires depends on the soil beneath it, and reactive clay — abundant across Adelaide — makes footing design sensitive in ways that surprise people who have only built on stable ground. The mechanics are set out in reactive clay, site classification and what it does to footings.

Retaining. Raise a floor level on a site that already falls and you have either raised the ground or increased the step between one part of the site and the next — and either can bring more retaining with it, depending on how the level is achieved. Retaining near a boundary brings its own set of questions about who it serves, who maintains it and what it does to the neighbour — a genuinely thorny area we have covered in retaining walls, boundaries and sloping blocks.

Earthworks. Cut and fill quantities move, and so does whether material leaves the site or stays on it. That is a haulage question as much as an excavation one.

Driveway and access grades. A vehicle has to get from the street to a garage floor that is now higher, over the same horizontal run. Grades, transitions and the crossover at the kerb all have limits, and the crossover is generally handled by the council as its own process, with requirements that vary by council and by site — described in the kerb crossover and the bond nobody budgets for.

Stormwater. Water still has to reach a legal point of discharge, and raising the floor changes the levels it has to work with. On infill sites this is frequently among the constraints that shape what is buildable — see the legal point of discharge on an SA infill site.

Daylight, privacy and built form. A dwelling sitting higher reads differently from the street and from the neighbour's back garden. Overlooking and overshadowing are assessed against the Code by the relevant authority, and a level change can move a proposal from one that reads as straightforward to one that has to demonstrate its performance.

Six links in the chain. An owner told "the floor level needs to come up" hears one.

The most cautious answer is often the most expensive one

Here is the part that costs owners money quietly.

When a level requirement lands, the reflexive response is to apply it uniformly and generously — lift everything, everywhere, with margin. It is defensible, it is quick, and nobody gets blamed for it. It can also, on a site with fall across it, be the most expensive way to arrive at a compliant outcome, because it imports the worst part of the site's condition into every part of the site.

A sloping parcel is not one condition. The fall is different at the front than at the back, different at one boundary than the other, and the treatment that is genuinely necessary in one part may be significantly more than is necessary in another. Meeting the requirement in full and meeting it the same way everywhere are two different propositions, and conflating them is a design decision being made by default rather than on purpose.

The reason the default wins so often is structural, not technical. The architect is not carrying the earthworks budget. The engineer is answering the question asked of them, correctly and conservatively, within their own scope. The builder is not in the room yet. Each party is doing their job properly, and the expensive answer emerges from the gaps between the jobs — which is the same coordination failure, in a different costume, that shows up in architect and consultant coordination before building consent.

What was done: three disciplines at one table, then a complete technical case

CPM's contribution here was not a design idea and not an engineering calculation. It was getting the right three disciplines reasoning about the same question at the same time, before anything was committed.

Design, engineering and cost management were brought together to work through how the level should be achieved across each part of the site — not whether to meet the requirement, which was never in question, but which treatment each part of the site actually called for, and what each option did to the build cost. The engineers did the engineering. The design team did the design. The cost input came from people whose job is cost. CPM's job was to make sure those three answers were being produced against each other rather than in sequence, because a decision made by the first discipline to be asked is a decision the other two then have to live with.

The result of that work was a complete technical case, which was then put to the relevant authority for confirmation. That phrasing is deliberate. The authority is the assessor; it applies the Code and the applicable requirements to the material in front of it. What a full technical case does is let it do that on the actual merits — with the reasoning, the levels and the engineering basis all present — rather than on an incomplete picture. The application was determined by the authority, which applies the applicable requirements to the proposal in front of it. What the project team had worked out beforehand was the way of meeting them.

Meeting a requirement and meeting it well are different achievements

The five townhouses were approved. That is the only outcome claim worth making here.

The part that does not show up in the approval is the one worth understanding: the finished floor level treatment had been reasoned rather than assumed. The owner met the same requirement either way. What differed was how much of the site's cost chain got dragged along behind it.

That distinction is generalisable even though the result is not. It shows up wherever a technical requirement meets a site that varies across its own area — and it is usually easier to resolve well before lodgement than after, because after lodgement the pressure tends to be towards the fastest change that answers the question rather than the best one.

What an owner can take from this

Three things, none of which require you to be technical.

When a level requirement arrives, ask what moves with it. Footings, retaining, earthworks, driveway grades, stormwater, daylight. If the answer you get covers one of those, you have not yet been given the cost of the change.

Ask whether the response is uniform or reasoned. "We lifted everything" is an answer. It may even be the right one. But it should be a conclusion someone reached, not a default nobody examined.

Get cost into the room before the drawings are final, not after. A cost check performed on a completed design can only tell you what it will cost. A cost input available while options are live can change what you build.

If you are looking at a sloping site and the feasibility is tight enough that the earthworks number decides it, that is exactly the stage where the order of work matters most — it is the coordination described at development approval and planning pathway. Start a conversation with us, or read how we describe the role in what a development manager actually does.