Statement of Compliance in Victoria (SPEAR) — How It Works

What a Statement of Compliance is

A Statement of Compliance (SOC) is issued by a council under the Subdivision Act 1988 (Vic) and confirms that the statutory requirements for a plan of subdivision have been met. Under section 5 of the Act, a person who wants a plan registered must prepare the plan, submit it to the council for certification, and then obtain a Statement of Compliance from the council — three distinct steps that must all be completed before the Registrar can register the plan.

Certification and the Statement of Compliance are not the same thing. Certification is a separate, technical check. As the Victorian planning guidance explains, "Certification is carried out by councils, in a process separate from the planning permit, to ensure your plan complies with the technical aspects of subdividing land in Victoria" — that the plan accords with the Subdivision Act, the regulations and the planning scheme. The Statement of Compliance comes afterwards and confirms the permit conditions themselves have been satisfied.

Most subdivision and planning permit applications in Victoria are now compiled and lodged through SPEAR (Surveying and Planning through Electronic Applications and Referrals), the online system operated by Land Use Victoria. For a certification application, Land Use Victoria describes the path plainly: the approval process involves referrals, certification and a Statement of Compliance, after which the plan can be lodged for registration.

Where Victorian subdivisions lose time and carry risk

The single biggest cause of Statement of Compliance delays is unmet or unevidenced permit conditions surfacing late, when the SOC is being assembled rather than as works progress. The mechanics are well documented; the difficulty is operational, not legal.

• Conditions spread across two streams. Some permit conditions require physical works to be completed and certified by engineers; others require legal instruments — drainage easements, Section 173 agreements, Owners Corporation rules — to be drafted, signed and registered. Both must be tracked in parallel.
• Referrals outside your control. Certification can involve referral authorities (for example Melbourne Water and servicing authorities), each with their own requirements that must be satisfied before the SOC can issue.
• Evidence scattered across the team. Compliance documents accumulate across surveyors, engineers, lawyers and the developer's inbox — making it hard to see, at any moment, what is actually outstanding.
• Late discovery. A single missing requirement — an unpaid contribution, an unregistered agreement, a missing works certificate — can hold registration for weeks, with holding costs and delayed settlements attached.

The solution: track conditions progressively, not at the end

The reliable way to reach a Statement of Compliance on time is to manage permit conditions as a live schedule from the day the permit is issued, rather than assembling them when the plan is ready to lodge. That means extracting every condition, assigning clear ownership, and collecting evidence as each item is met.

This is the same discipline Queensland teams apply to plan sealing. The parallel is close enough that the lessons transfer directly: structured condition tracking, clear responsibility, and a single source of truth across the project team. Our Queensland material on managing development approval conditions across a project sets out the underlying method, and the overview of plan sealing in Queensland shows how the equivalent final-approval step is run there.

Time saved

Structured condition management saves the most time at the end of a project, where it matters most — because nothing is rediscovered at lodgement. When every condition has a known status and its evidence already attached, the Statement of Compliance application is a confirmation exercise rather than a scramble.

The scale of that final step is visible in adjacent data. PlanEase's analysis of 1,674 decided development applications across 15 South East Queensland councils (29 June 2025 to 21 June 2026) found a median of 25 days from lodgement to decision. Final approvals like the Victorian Statement of Compliance and Queensland plan sealing sit downstream of that — so each avoidable round of requisitions or missing evidence adds further weeks to an already long timeline.

Risk reduced

The clearest risk reduction is removing the chance that a condition is missed entirely. Because registration cannot proceed without the Statement of Compliance, an overlooked condition does not just cause inconvenience — it blocks titles, and with them sales, settlements and the release of project finance.

Assigning each condition to a named owner also removes the ambiguity that causes work to be duplicated or dropped. Our piece on the lack of early visibility of issues explains why problems surface too late on subdivision projects, and how progressive tracking brings them forward while there is still time to act.

How the process runs, step by step

In practice, a Victorian subdivision reaches registration through a defined sequence. Understanding the order helps teams prepare evidence for each gate before it is reached.

• — A licensed surveyor prepares the plan of subdivision and the application is compiled in SPEAR
• — The plan is submitted to the council for certification, with referrals to relevant authorities
• — The council certifies the plan once it complies with the Subdivision Act, the regulations and the planning scheme
• — Permit conditions are satisfied and evidenced, and the council issues the Statement of Compliance
• — The plan is lodged for registration; when registered at Land Use Victoria, new titles are allocated

The condition-management work sits before the Statement of Compliance gate. Getting it done progressively is what keeps the final two steps short.

Frequently asked questions