DA conditions · Analysis

When People Leave, Projects Forget: Keeping DA Condition Records Over Multi-Year Projects

Subdivision projects run for years, but the people running them rarely stay for the whole ride. Engineers move firms, planners change jobs, and developers restructure teams. When they go, the compliance record often goes with them, buried in a personal inbox nobody else can open. The conditions imposed at approval do not change, but the memory of how they were being satisfied walks out the door. That gap surfaces at the worst possible time: plan sealing.

The problem: multi-year projects, short-term memory

Development project information loss happens because subdivision projects outlast the individuals and firms delivering them. A reconfiguring a lot approval commonly stays live for years before the survey plan is lodged. Under the Planning Act 2016, where a development approval does not specify its own currency period, Brisbane City Council notes the default period for a reconfiguring a lot not requiring operational works is four years for the subdivision plan to be lodged for plan sealing, and six years for a material change of use to start. Staged projects can stretch far beyond that.

Over that span, the people who read the conditions, negotiated with council, and collected the early evidence frequently change. The DA condition record, if it exists at all, lives in email threads, local drives, and the working memory of whoever happened to be running the job. None of those survive a resignation, a firm changing hands, or a project being handed to a new project manager.

How the record is lost

The compliance record is lost through predictable, mundane events rather than any single dramatic failure. Each one quietly removes a piece of the picture, and the loss is rarely noticed until someone needs the missing piece.

• Evidence buried in personal inboxes. The engineering sign-off, the Unitywater confirmation, the council officer's email agreeing how a condition would be met: all of it sits in one person's mailbox. When that account is deactivated, the thread is gone, and with it the only proof of what was agreed.
• Handovers that never happen. When a consultant leaves mid-project, a clean handover of every condition and its status is the exception, not the rule. The replacement inherits a folder of documents with no map of which condition each one satisfies.
• Firms changing, not just people. When a developer changes engineers or planners between stages, the new firm starts from the approval document and has to reconstruct everything that came before it.
• Re-deriving what a condition requires. A new engineer or planner, years after approval, re-reads an ambiguous condition and reinterprets it. If council had already accepted a specific method, that context is gone, and the work risks being redone or rejected.

The conditions imposed at approval never expire from the file. The knowledge of how they were being satisfied expires the moment the person holding it leaves.

The cost surfaces at plan sealing

The bill for lost knowledge almost always arrives at plan sealing, when a complete compliance record is finally required in one place. At that point the team discovers which conditions have no evidence attached, which sign-offs were verbal, and which agreements with council were only ever captured in an email nobody can now retrieve. Chasing that history down late in a project is slow, expensive, and directly delays settlement.

How much activity a long project has to remember

The scale of what a project must remember is easy to underestimate. PlanEase tracks a large and continuous flow of development activity across Queensland, and any single multi-year subdivision is only one thread inside it.

Approximate figures from PlanEase's analysis of public registers, data updated 16 August 2026, subject to revision. Not official statistics.

The decision, the median of which PlanEase measures at about 27 days across Queensland councils plus EDQ, is only the visible front of the pipeline. Everything that follows, satisfying each condition and assembling the evidence, unfolds over the years afterward, and it is that long, unmeasured tail where records quietly leak away.

The fix: a record owned by the project, not a person

The reliable fix is a shared, durable condition register that outlives any individual or firm. Instead of the compliance record living in one person's inbox, every condition, its requirements, the evidence that satisfies it, and the correspondence about it sit in one place that belongs to the project. When someone leaves, the record stays.

A durable register changes what a handover means. A new engineer or planner does not start by re-reading the raw approval and guessing. They open a register that already shows each condition, who owns it, what evidence has been collected, and what council has accepted. Continuity becomes the default rather than something that depends on one person's diligence at the moment they resign.

This is the same discipline covered in our writing on how teams lose compliance knowledge over the life of a project and on fragmentation across project teams. It is also the foundation of managing DA conditions across a project from approval through to plan sealing.

Time saved and risk reduced

A project-owned condition record saves time by removing the reconstruction work that turnover creates: no re-deriving conditions, no hunting through departed staff's inboxes, no waiting on people who have moved on. It reduces risk by making sure that a verbal agreement or a one-off email is not the only record of a condition being satisfied, so nothing quietly disappears with a resignation. The result is continuity: the project remembers, even when the people change.

People leaving a long project is not an unusual event to guard against; it is a certainty to design for. The conditions imposed at approval do not forget, and the project record should not either. Keeping that record durable, shared, and owned by the project is the clearest way to protect continuity across the years between approval and a sealed plan.