When the decision is made and the remaining risk is approval. Pivot is a two-product delivery-stage package — Pivot Planning for the recurring permit-pathway work, Pivot Ready for the delivery document set. Strategy must qualify the case first.
Pre-DA engagement — the council conversation before a development application (DA) is lodged — permit-pathway research, council requirements mapping, sequenced methodology, and consultant scope-out. Runs the council clock month-by-month through the pre-DA window.
DA package, consultant coordination, tender-ready scope of works (SOW), capital-deployment sequence, and a project-side financial feasibility model. Ships the artefacts that take a qualified case from decision to deployment.
The Strategy ladder runs the diagnosis. Pivot runs the delivery. Pivot is engaged only after the case has cleared Strategy — a current Intelligence Pack, plus a Capital Readiness Pack where capital is in scope. There is no shortcut.
Quick Scan · Intelligence Pack · Capital Readiness Pack. Diagnoses the case and qualifies the decision. Prices the carry — the cost of holding.
Pivot Planning + Pivot Ready. Takes the qualified case from decision through permit edge to deployment-ready.
Curated routing into capital, buyers, tenants, operators, or partners — only after the case is fully qualified.
If a case has not had a current Intelligence Pack, Pivot is declined and the client is sent back to Strategy. The Strategy → Pivot move is a re-engagement, not a continuation — no upgrade credit applies. Pivot does not re-do Strategy work.
Not qualified yet? Begin at Strategy — Sheet 01 →Pivot Planning is the process engagement across the pre-DA window. Five components — pre-DA conversation with council, permit-pathway research, council requirements mapping, sequenced methodology, and consultant scope-out — run on a monthly cadence until the pathway is locked. Then Pivot Ready takes over.
Pivot Ready is the deliverable artefact set that takes a qualified case from decision through to deployment-ready. Five components, itemised below — from the DA package through to the project-side feasibility model — assembled on one fixed scope. One handover, no rework.
The screen a Pivot Planning case runs on — a slice of the Axis ops console, redrawn with invented data. One row carries the whole engagement: stages, clock, documents, consultant triggers, each stamped the minute it happens. If a stage moves, it moves here first.
Victorian councils assess a standard permit on a 60-day statutory clock. Most applications lose whole weeks in the hand-offs — nobody is watching. The console is. This case: day 34, paused by an RFI (council's request for further information), and Axis idle time still zero. Dead weeks stripped, decision sooner.
On a typical application the updates thin out by week three, and the owner reads a six-figure decision from the length of the silence. Owners on Axis watch the same screen we do — live in the client portal, read-only, down to the timestamp. The traffic-consultant trigger on this file? Stamped 14:02, 28 June. Stamped, not summarised.
A permit in Victoria, a development application in New South Wales — every state runs its own rulebook. Underneath, each reduces to stages, documents, sign-offs and a clock. That is what the console tracks, in any state. Victorian depth, national method.
Victoria gives a council 60 statutory days before its silence can be appealed; New South Wales deems a development application refused after 40. Different rulebooks, same four primitives. The five stages underneath don't move.
On Axis rails, no week dies quietly on the council clock and no stage happens out of the owner's sight.
Pivot Planning is recurring monthly across the pre-DA window. Pivot Ready is scope-priced as a fixed deliverable. They are sold separately and may run sequentially or in parallel depending on case timing. Working prices, last re-locked 2026·05·04.
Runs the five S.01–S.05 components above — council engagement through consultant scope-out — on one monthly cadence. Billed across the pre-DA window.
One fixed scope agreed before work starts, then a single handover of the artefact set. Runs after Planning, or in parallel once the pathway is locked.
Cases entering Pivot must already carry a current Intelligence Pack. If your case is qualified at Strategy, talk to us about engaging Pivot. If it isn't yet, begin at Quick Scan.