How to Track DA Conditions Without Losing Your Mind (or Your OC)

A typical residential development in NSW might have 60–90 DA conditions. A commercial project can have 150+. Each condition has a different responsible party, a different trigger point (prior to commencement, during construction, prior to OC), and a different evidence requirement (certificate, report, inspection, payment).

The traditional approach is a spreadsheet. Someone creates it at the start of the project, assigns conditions to team members, and then... it stops being updated. By the time you're applying for the OC, half the conditions are marked 'in progress' with no supporting documentation, and you're scrambling to close out items that should have been done six months ago.

The direct cost of a missed DA condition is the delay to your OC. In Sydney, a 3-month OC delay on a 20-unit project with $8M in presales typically costs:

- Holding costs on construction finance: $40,000–$80,000 - Extended site supervision and management: $15,000–$25,000 - Penalty interest on delayed settlements: $20,000–$60,000 - Total: $75,000–$165,000 for a single missed condition

And that's before you account for the reputational damage with buyers and the stress on your team.

The firms that consistently get their OCs on time have one thing in common: they treat DA conditions as a project management problem, not an admin problem.

Here's the framework that works:

1. Categorise every condition at the start of the project Group conditions by trigger point (pre-commencement, during construction, prior to OC) and by responsible party (developer, builder, certifier, council, consultant).

2. Assign ownership with accountability Every condition needs a named owner and a due date. 'The builder' is not an owner. 'John Smith, Site Supervisor' is an owner.

3. Define the evidence requirement upfront For each condition, document exactly what evidence is needed to satisfy it. A certificate? A report? An inspection? A payment receipt? This prevents last-minute surprises.

4. Set automated reminders Conditions should trigger reminders 30 days, 14 days, and 7 days before their due date. By the time a condition is overdue, it's already a problem.

5. Maintain a live compliance dashboard Your PM should be able to see the status of every condition at any time, without asking anyone.

BuilderHQ's Reporting & Compliance module imports your DA conditions directly from your consent document. Each condition is automatically categorised, assigned to the relevant party, and tracked through a structured workflow.

The platform sends automated reminders before due dates and escalates overdue items to the PM. When a condition is satisfied, the evidence is uploaded and attached to the condition record — creating a complete audit trail for your OC application.

For a recent client with 94 DA conditions on a 36-lot subdivision, the platform reduced compliance reporting time from 4 hours per week to 20 minutes — and the OC was issued on schedule for the first time in 4 years.