Why strata councils need their own maintenance history
When a pipe bursts on the 14th floor, the council needs to know: has this happened before? What was done last time? Who was the contractor? How much did it cost?
If the answer lives only in the property manager's system, the council is one management change away from losing it entirely.
Records belong to the building, not the manager
Property management companies come and go. Contracts renew, firms merge, portfolios get sold. The strata corporation — identified by its plan number — is the permanent entity. Its maintenance history should be anchored there too.
Councils that delegate all record-keeping to their manager often discover, years later, that:
- Historical invoices are scattered across multiple systems
- Work orders from a previous manager are inaccessible
- The council has no independent audit trail of what was approved and spent
What councils actually need to track
Not every document needs to live in the council's system. But the operational history — the day-to-day work of running a building — should:
| Record type | Why it matters |
|---|---|
| Open maintenance issues | So nothing falls through the cracks between meetings |
| Completed work history | For warranty claims, insurance, and depreciation reports |
| Vendor assignments | So the next council does not start from zero |
| Cost records | So treasurers can answer owner questions with facts |
| Council decisions | So you know why something was done, not just what |
The risk of a single point of failure
Relying on one person's memory — or one company's portal — creates fragility. Consider:
- The long-serving council member who retires and takes 8 years of context with them
- The property manager who switches platforms and does not migrate old data
- The emergency repair at 2 a.m. when nobody can reach the manager's after-hours line
A council with its own maintenance log can act on incomplete information far less often.
Independence without adversarial relationships
Owning your records is not about distrusting your property manager. Most managers welcome informed councils — they reduce back-and-forth, speed up approvals, and make meetings more productive.
The goal is a council intelligence layer: your own view of the building that complements whatever the manager provides. When both sides have access to the same facts, conversations get shorter and decisions get better.
History should never be gated
Whatever tool a council uses, one principle should be non-negotiable: completed maintenance history is always accessible. Locking councils out of their own building's past — whether through tier limits, export restrictions, or platform churn — destroys trust at exactly the moment it matters most: during a dispute, an insurance claim, or a council handover.
Getting started
You do not need to migrate a decade of records on day one. Start with what is open right now:
- Log every active maintenance issue with a clear status
- Attach the contractor name and quoted cost
- Close items when work is done — but keep them searchable
Six months of consistent logging beats ten years of scattered PDFs. The council that starts today is the council that hands over cleanly at the next AGM.