"Unverified" Is an Answer: Three-State Compliance Explained

"Unverified" Is an Answer: Three-State Compliance Explained

General information for South Australian landowners and small developers only. This is not planning, legal, financial or tax advice, and nothing here assesses any particular site or any particular report. Route questions about which planning standards apply to a specific site — and what their values actually are — to a planning consultant, keeping in mind that the relevant authority determines those matters when it assesses an application; questions about relying on a feasibility document in a purchase contract or a partnership agreement to an SA property lawyer; questions about what a lender will accept as evidence to your own finance broker or bank; and questions about the tax treatment of any project a report informs to a registered tax agent. Statutory arrangements and the Planning and Design Code change over time, so confirm the current position for your own site before relying on anything here.

A tick can claim more than anyone has checked

Open a typical feasibility document and somewhere in the middle you will find a compliance table. Down one side, planning standards: minimum allotment area, minimum frontage, setbacks, site coverage. Down the other, a column of green ticks, perhaps the odd red cross. The table reads like an audit. It can be something weaker: a display convention.

A tick is a compound claim. It asserts that the standard is real, that its value for this site is known, and that the scheme meets that value. Only the last leg is visible in the tick itself. The value behind it can be an assumption — a figure carried over from a template, from another zone, from the last project, or from "what council usually wants around here" — and the scheme is then measured faithfully, and honestly, against a number nobody confirmed.

Binary reporting cannot express that situation, because it offers only the pass cell and the fail cell. Whatever has not been confirmed must still be rounded into one of them, and neither rounding serves the reader: rounded into fail, an open question reads as a defect; rounded into pass, it disappears from view and the table overstates the state of knowledge. Either way you lose the ability to tell a checked row from an assumed one. That is not a problem confined to unusual projects — on ordinary ones too, a standard nobody has yet confirmed for this site is common enough to plan for.

To be clear about scope: this piece is about how findings should be displayed. The prior question — what a feasibility model is entitled to claim in the first place, and where its jurisdiction ends — is a separate subject, taken up in what a feasibility model can and cannot tell you. Display comes second in that logical order, but it is where false certainty is actually manufactured, which is why it deserves its own treatment.

What three-state compliance means

Three-state compliance is a reporting rule: every standard a feasibility document checks is shown in exactly one of three states — compliant, non-compliant, or unverified — where unverified means the standard's value for this specific site is neither evidenced nor confirmed within the report, and where nothing uncertain is ever displayed as a pass. The third state is not a hedge and not an apology. It is a finding in its own right: it tells you precisely which questions remain open, who is the right person to close each one, and what the answer would change about the scheme.

Read that way, an unverified row is more useful than a soft tick could ever be. A soft tick tells you to relax; an unverified row tells you what to do next. It converts a silent assumption into a visible task — confirm this value with your planning consultant, put that question to the authority through the proper channel, order the search that settles the other one. A report written under this rule arrives with its own due-diligence list attached, and the list is exactly the set of things the report declined to pretend it knew.

The rule also restores meaning to the passes. When nothing uncertain is allowed to wear a tick, a tick becomes information again: the scheme was checked, as a preliminary matter, against a documented input for this land, and it held — subject to your planning consultant's advice on the standards that apply, and to the relevant authority's own assessment when it determines an application. In a binary table you cannot tell the audited ticks from the assumed ones. In a three-state table, the sorting has been done before you start reading.

The three states are the conceptual model. A particular report may add tolerance sub-bands inside the compliant and non-compliant sides — a comfortable pass, a marginal one, a near miss — without ever collapsing unverified into either; the third state survives the extra resolution intact.

Where the third state comes from

The third state is not a philosophical flourish. It comes from a concrete feature of how planning standards work in South Australia: the values vary, and they vary at a finer grain than most owners expect.

The minimum allotment area that governs a site is not a citywide constant. It is read from the Planning and Design Code as it applies to that particular zone and that particular parcel, and a planning consultant's site-specific review may identify overlays or technical variations that shift the answer between neighbouring streets — with the relevant authority determining the result when it assesses an application. A value that is common in one zone is not a rule in the next one. We have written about this concretely before: why the minimum block size for a subdivision depends on where you are standing, and, one step earlier in the owner's chain of questions, whether your block can be divided at all. Both pieces turn on the same fact — the governing values must be confirmed for the specific parcel, not inferred from the suburb.

Now put a feasibility report into that picture. Where one is prepared early — before a planning consultant has confirmed the standards for the site, and before any authority has determined anything — it faces exactly the following honest choices about a governing value it does not yet hold: wait until the value is confirmed, assume a value and present it as the rule, or state the check and mark it unverified. Waiting destroys the report's usefulness at the stage it is most needed. Assuming manufactures certainty and hides the borrowed number inside a tick. The third choice keeps the report early, useful, and honest at the same time — which is the entire case for it.

The disciplines that travel with it

Three-state compliance does not stand alone. It belongs to a family of reporting disciplines with a single common root: a report must never claim more knowledge than exists. The siblings are worth naming, because each blocks a different way of smuggling certainty into a document.

No invented thresholds. A tempting shortcut in early feasibility work is to borrow a common value from elsewhere and present it as this site's rule. The discipline says: a value may appear in the report only with its provenance attached, and where no provenance exists for this site, the row is marked unverified rather than filled with someone else's number. An invented threshold is worse than a blank, because a blank invites a question and an invented threshold answers it wrongly.

Sample sizes travel. Statistical claims — what comparable applications experienced, what similar allotments achieved — must carry the size of the case set behind them wherever the claim goes. A conclusion drawn from a handful of cases must not dress itself as one drawn from many; the reader is entitled to know which of the two they are holding, because the same range means something different depending on the depth behind it. In research we co-authored on South Australian planning applications, the depth of each comparable set was treated as part of the finding rather than a footnote, for exactly this reason.

No auto-ranking. When a report compares options, the options sit side by side with their assumptions exposed, and the recommendation — if the owner wants one — is signed by a named professional. Not because arithmetic is untrustworthy, but because a ranking cannot carry a judgement. That signed recommendation is limited to project-delivery matters — sequencing, documentation, how the inputs from your advisers are coordinated — while the financial, tax and legal comparison between the options belongs with your own accountant, registered tax agent and lawyer. An algorithm's ranking cannot be questioned in a meeting or held to account afterwards; a named professional can be both.

Each discipline polices a different border of the same territory. Three-state compliance stops uncertainty being displayed as knowledge; no invented thresholds stops other people's rules being displayed as yours; travelling sample sizes stop thin evidence being displayed as deep; no auto-ranking stops a calculation being displayed as a judgement.

The admitted boundary is the credible one

The predictable objection: a report with unverified rows looks weaker. Fewer ticks, more open questions — surely the confident document sells the project better.

For the readers who matter, the opposite holds. Think about who actually reads a feasibility report hard: a bank's credit assessor, a prospective partner's advisers, your own lawyer. Their professional job is scrutiny. Hand them a document in which everything is green and you have issued a challenge — find the one tick that should not be there. If they do find one, the damage is not confined to that row. Every other tick in the document is now suspect, because the reader has learned that in this report a tick does not reliably mean checked. One overclaimed cell discounts the whole table.

Hand the same reader a three-state document and the encounter runs differently. The boundary of the report's knowledge is pre-declared, so scrutiny confirms the document instead of puncturing it. The unverified list doubles as a work programme — it shows a partner exactly what diligence remains and lets it be priced, scheduled and assigned rather than discovered mid-transaction. And the passes carry weight, because the rule behind them is known: nothing uncertain was allowed to wear one.

That is the bank-and-partner argument in full. A report that admits its boundaries is the one that holds up when it is read hard, not despite the admissions but because of them — though what any particular lender or partner requires, and accepts as evidence, is for them to determine. Credibility is not the absence of open questions; it is the accurate labelling of them.

How our catalogue applies this

These are not abstract virtues we are recommending to other people. They are the operating rules the Cyberate PM report catalogue is written under, and they are stated openly on the reports page as the principles behind every document in the set. The worked example is the land division feasibility report: its compliance marking is that same model at working resolution, adding tolerance sub-bands either side of the compliant line to make five in all, with unverified kept as a state of its own, its concept schemes are subject to planning consent, and its output is an evidence-based assessment built from historical cases — never a guarantee of any outcome, and never a substitute for the planning consultant who advises you on your site or the authority that determines your application. The same rule governs the wider appraisal work described at property development feasibility. If you want to see what that kind of reporting would look like on your own parcel — which rows could be verified today, and which would honestly stay open — start a conversation with us; a conversation is a practical way to sketch that boundary before you spend anything on crossing it.