Missed expiries are expensive and avoidable. A board with time buckets turns them into a routine.
Record every approval
Approval type, authority, issue date, expiry and owner. Add land and title records beside them.
Use time buckets
Propto groups items as lapsed, within 30, 60 or 90 days, or valid. Start renewals when something enters the 90-day bucket.
Automate the nudge
Approval expiry rules alert the right team. Keep a log of renewals for audits.
Why compliance deadlines are risky
Real estate projects depend on many approvals and clearances, each with its own validity period, renewal process and conditions. When these dates live in a lawyer’s diary or a single spreadsheet, a lapse can go unnoticed until it blocks a registry, a sale or a construction stage.
A compliance tracker makes every approval and its deadline visible to the right people, with time to act before anything lapses.
Record every approval
List every approval, licence and clearance for each project: what it is, the issuing authority, the date issued, the expiry or renewal date, conditions and the person responsible. Attach the document to the record.
Include land and title records, building approvals and any project registrations relevant to your jurisdiction. Completeness matters; one missing item can cause the biggest problem.
Use time buckets
Group approvals by how soon they lapse: already lapsed, within thirty days, within sixty days, within ninety days and valid beyond that. A compliance board organised this way shows immediately where attention is needed.
Review the thirty-day bucket weekly and the sixty- and ninety-day buckets monthly, so renewals start early.
Assign clear owners
Every approval needs an owner who tracks renewal, gathers documents and coordinates with authorities. Assign a backup for leave periods. Without owners, everyone assumes someone else is handling it.
Record progress on each renewal, so managers can see whether work has started.
Automate the nudge
Operations rules can alert owners and managers when an approval enters the ninety-, sixty- and thirty-day windows. Staged alerts give time for preparation and escalation if renewal stalls.
Preview alert rules before enabling them and make sure messages reach people who can act.
Linking compliance to sales and registry
Some approvals affect whether units can be sold or registered. Make these dependencies visible, so sales and legal know when a lapse could affect buyers. Early warning allows you to manage expectations honestly.
Communicate with buyers carefully if a delay is likely, with accurate information and realistic timelines.
Keeping documents organised
Store approval documents in the project’s compliance records with restricted access. Keep previous versions, so you can show the history of renewals if questions arise.
Avoid scattered copies in email attachments and personal folders.
Why it matters for the business
A single lapsed approval can halt registries, delay possession or create legal exposure. The cost of tracking is small compared with the cost of a lapse, both financially and in buyer trust.
A visible compliance board also reassures management, banks and investors that obligations are under control.
A worked example
A compliance board shows an approval entering the sixty-day window. An automatic alert reaches the owner, who starts gathering documents. At thirty days, the renewal application is submitted and recorded. The approval is renewed before expiry, and the new document replaces the old one with the updated date.
Without the alert, the renewal might have started only after a registry was blocked.
Common mistakes
Common mistakes include tracking only a few major approvals, relying on one person’s memory, starting renewals too late and storing documents in scattered places.
Another mistake is failing to connect compliance status with sales and registry planning.
Questions teams often ask
Who should own the compliance board? Usually legal, with project managers responsible for specific approvals.
How far ahead should alerts start? Ninety days is a sensible default for most renewals, earlier for complex ones.
A compliance checklist
Every approval recorded with authority, dates, conditions, owner and document. Board grouped by lapse window. Weekly review of the thirty-day bucket and monthly review of longer windows.
Staged alerts configured and previewed. Dependencies on sales and registry visible. Documents stored centrally with history and restricted access.
In practice
Start by listing every approval for one project and entering its expiry date. You may discover gaps immediately. Assign owners, set up staged alerts and review the board weekly.
Once the first project is complete, repeat for the others.
A final thought
Compliance is rarely urgent until it suddenly is. A simple, visible tracker keeps it calm and predictable.
In short
Record every approval with dates and owners, group by lapse window, automate staged alerts, link compliance to sales and registry, store documents centrally and review the board regularly.
Getting the whole team involved
Compliance is not only legal’s job. Project managers know when site work depends on an approval, sales knows when buyers are waiting for registry and accounts knows when payments depend on milestones. Share the compliance board with each of them in the right level of detail, so concerns surface early from every side.
A short monthly update to all teams on upcoming renewals keeps everyone aligned.
In one line
Track every approval, alert early, assign owners and never let a renewal depend on memory alone.
Are expiry alerts available?
Operations rules include approval expiry reminders.