By Greg Allan, tradesman and creator of Data First Coaching
Why do subdivisions keep stalling even when the council isn't the hold up?
A subdivision only moves once the boundary survey, the title work and the council approval line up. When a surveying business is already behind on detail surveys, set outs and as-built reports, the subdivision plan sits waiting for field crew time or drafting, long before it ever reaches the council's desk. The client sees a council delay. The real hold-up is often sitting in the surveyor's own job queue.
Councils have their own queue for subdivision applications and certificates, and that part of the process is genuinely outside the surveyor's control. But a developer or builder waiting on a plan rarely separates the two delays. If the cadastral measurement, the contour data or the as-built report hasn't been drafted and checked, the application can't go in on time, and the clock the client is watching never really started where they think it did.
Why does a surveying business say yes to every boundary and subdivision job even when the diary's full?
Most surveyors remember the quiet months, the stretch with no boundary work, no set outs and an empty diary, and that memory makes it hard to turn any job away. So when the busy season hits, a detail survey here, a subdivision there, a set out for a builder who needs it this week, the owner says yes to all of it without ever stating a real turnaround time.
Without a stated lead time, jobs get double booked across the field crew, titles sit half drafted, and a plan promised to one developer slips behind a job that landed on the desk after it. The client blames the council for the delay. What actually happened is a surveying business that kept saying yes through a season when the diary was already full, and never told anyone where their job actually sat in the queue.
What number in the business actually shows where a subdivision is getting stuck?
The honest answer sits in how long a job actually waits at each stage, from the field crew finishing the boundary pegs to the plan being drafted, checked and lodged, against what you told the client it would take. Memory says the business is coping. The job data, read stage by stage, usually tells a different story, and it tells it whether the week was quiet or flat out.
This is why a data first view matters more than a feeling about how busy the season is. A surveyor can be certain the backlog is manageable and still have three subdivisions sitting in drafting longer than the council took to respond to any of them. Reading the job data instead of the memory of how it usually goes is what shows where the real bottleneck sits, rather than where it's easiest to point.
How can AI agents stop the backlog before it reaches the council?
An AI agent is software that does a job the way you would do it, using your prices, your wording and your rules. For a surveying business, that can mean an agent that watches job stage and flags, before you say yes to another boundary job, that the drafting queue is already stretched past what you've promised other clients.
Picture a surveying business that regularly responds to council tenders for set out and subdivision work. Writing the full methodology and chasing subcontractor prices for each tender used to take days and days, or get rushed through at the last minute when two tenders landed in the same week. An agent now pulls the tender in, drafts the emails asking subcontractors for their prices, writes the methodology with a timeline built in, and brings the subcontractor replies back in as they arrive. AI agents handling that non-billable chasing, in the background, done the way the business always did it, is what frees up field crew and drafting time instead of eating into it.
What changes when a developer or builder is told the real turnaround time?
Telling a developer or builder the honest lead time at the point of quoting, rather than quietly absorbing the backlog, is what actually stops the spiral. A client who knows a subdivision plan will take a stated number of weeks can plan their own build and council lodgement around it. A client who's told to leave it with you has no idea they're behind three other jobs until the date they expected comes and goes.
This is also where the quote itself can do some of the work. Presenting a standard turnaround alongside a faster, priority option, each one checked against the margin it actually protects, gives the developer or builder a real choice instead of a single promise that's already shaky. Closing on an immediate booked date, rather than leaving the client waiting on an answer, is what keeps the job queue honest from the start, instead of letting every new yes quietly reshuffle the ones already on the board. AI agents that already know your pricing and wording can present those turnaround options and lock in the date without extra admin time.
How does Data First Coaching approach this?
Data First Coaching starts from the surveying business's own job data, not from a conversation about how busy the season feels. Greg Allan looks first at where subdivision, boundary and detail jobs actually sit against what clients were told, because that's usually where a council delay turns out to be a backlog that started on the surveyor's own desk. Greg puts it simply: “It really comes back to communication.” The how, building the agents and the systems that make the real turnaround visible and honest, is worked through inside the Academy, with other members. It's built for surveyors who are open minded, innovative and willing to share, because the Trade Business Intelligence gets smarter from every member who puts their own data into it.

