Compliance & documents

Every strata building carries ongoing obligations that don't go away once satisfied — they recur, and missing a renewal can carry real safety and legal consequences.

What typically sits in a compliance register

• Fire safety and essential services checks and certifications
• Building or plant-specific requirements (lifts, pools, fire systems) depending on the building
• Insurance renewal dates, tracked alongside the insurance record itself
• Any other recurring statutory obligation the committee is responsible for under its state's legislation

Why a register beats a mental list

Compliance obligations are usually owned informally by whoever happens to remember them — often a long-serving committee member or the strata manager. When that person is unavailable, or the committee changes over, informal tracking has a habit of quietly dropping items. A register that belongs to the building, not a person, survives that turnover.

Assignments and reminders

Each compliance item can be assigned to a specific person — a committee member or the manager — with a due date and a reminder ahead of it. This turns a vague sense that "something's probably due soon" into a specific task with an owner and a deadline.

What the register doesn't do

The compliance register tracks obligations and their due dates; it doesn't perform the inspections or certifications itself, and it doesn't replace advice from a qualified compliance provider about what's actually required for your specific building. Requirements vary meaningfully by state, building type and age, so confirm your building's specific obligations with a qualified provider or your manager rather than relying on a generic checklist.

Keeping it accurate

A register is only useful if it's kept current — when an inspection is completed, mark it done and set the next due date immediately, rather than leaving the register to drift out of sync with reality.

By-laws are one of the documents owners ask for most often, usually right before or after a dispute, which is exactly the wrong time to discover nobody's sure where the current version lives.

Why accessibility matters

By-laws set the rules of the scheme — noise, pets, renovations, parking, and more — and owners are generally entitled to access them. A committee that can't quickly produce the current, correctly registered version looks disorganised at best, and can find itself unable to properly enforce a by-law it can't clearly evidence.

Keeping the current version findable

• Upload the registered by-laws (and any consolidated version, if your state provides for one) to the documents library under a clearly labelled category
• Replace the file when by-laws are validly changed, rather than adding a new version alongside the old one and leaving both visible
• Note the date of the most recent change somewhere obvious, so owners aren't left guessing whether they're looking at the current rules

By-law changes

Changing a by-law generally requires a special resolution (the specific majority required is set by your state's legislation), and in most states needs to be registered with the relevant land titles authority to take effect. Until that registration step is completed, treat a "new" by-law as not yet in force, and make sure the version in the documents library reflects what's actually registered, not just what was voted on at a meeting.

Enforcement depends on clarity

By-law enforcement disputes often come down to whether the by-law was clear, current and properly registered at the time of the alleged breach. Keeping an accurate, dated history of by-law versions in the documents library gives the committee something solid to point to if a breach notice is ever challenged.

Owner access

Because documents in Flex Strata are organised by category with owner-facing permissions, the committee decides which categories owners can see. By-laws are one of the documents most committees choose to make visible to all owners by default, given owners are generally entitled to access them regardless.

A document library organised by upload date is barely better than a folder of unlabelled PDFs — it technically has everything, but nobody can find it without scrolling through irrelevant results.

A sensible starting set of categories

• By-laws and scheme rules
• Meeting minutes and agendas (AGM, EGM, committee)
• Insurance certificates and policy documents
• Compliance certificates (essential services, and similar)
• Maintenance records and reports
• Correspondence and notices
• Any manager-supplied reports the committee wants to retain

Matching categories to who needs to see them

Since document access in Flex Strata is set at the category level, the categories you choose double as your permission boundaries. Fine-grained categories (separating, say, "insurance" from "compliance certificates") let you open up low-sensitivity categories to all owners while keeping others restricted to the committee.

Avoiding category sprawl

It's tempting to create a new category for every slightly different document type, but too many categories makes the library harder to navigate, not easier. Aim for a set of categories that map to how people actually search for things — "where are the by-laws" rather than "where's the 2019 by-law amendment specifically."

Migrating an existing mess

If you're bringing across documents from a shared drive or a manager's portal, resist the urge to recreate their exact folder structure. Take the opportunity to simplify — most committees find they only really reach for four or five categories in practice, no matter how detailed the old system was.

Keeping it current

A document library degrades the same way a compliance register does if nobody's responsible for it — set an expectation that whoever receives a new document (minutes, a certificate, a report) uploads it promptly, rather than letting a backlog build up.

A certificate of currency is one of the most commonly requested strata documents — owners, prospective purchasers' conveyancers, and lenders all ask for it, often with little notice.

What's typically tracked

• The insurer, policy number and cover type (building, public liability, and any others held)
• The renewal date, so the committee isn't caught out at the last minute
• The certificate of currency document itself, stored where it can be quickly located and shared

Why renewal timing matters

Lapsed building insurance is a serious exposure for any strata scheme — beyond the practical risk of an uninsured event, most states require the scheme to maintain certain insurance, and a lapse can itself be a compliance failure. Tracking the renewal date alongside a reminder gives the committee time to review the policy properly rather than renewing in a rush the day cover expires.

Requests for the certificate

Because the certificate of currency lives in the documents library, it can be shared quickly when someone asks for it — a common request from owners selling their lot, or from a prospective buyer's conveyancer during due diligence.

What Flex Strata doesn't do

Flex Strata records insurance details and stores the certificate; it doesn't manage the premium payment, process claims, or replace advice from a broker about adequate sums insured. For a matter as consequential as adequate building insurance valuation and cover, that's worth reviewing periodically with a broker experienced in strata insurance, not left to a generic renewal reminder.

Building details link

Insurance sits within the broader building details record alongside lots and other core building information, giving a single place to see the building's key facts rather than scattering them across separate documents and spreadsheets.

Essential services obligations are among the least forgiving compliance items a strata scheme carries, because they exist to protect life safety and are often enforced by local councils or fire authorities rather than only by strata legislation.

What's typically involved

• Fire systems (alarms, sprinklers, extinguishers, exit signage) inspected and certified on a recurring schedule
• Other building-specific essential services depending on the building's fire safety and building code requirements
• Annual or periodic certification, often lodged with a local council depending on your state's process

Why this needs deliberate tracking

Essential services requirements are usually set by a combination of building codes, local council conditions specific to the building, and state fire safety legislation — there's no single universal Australian checklist, and requirements differ by building age, use and location. Getting the specific schedule right for your building is something to confirm with a qualified fire safety or essential services provider, not to guess from general commentary.

How the compliance register helps

Once you know your building's specific essential services schedule (from your provider or your manager), each item can be entered into the compliance register with its due date, assigned to whoever is responsible for organising the inspection, and set to remind ahead of the deadline. This turns "the fire system inspection is due sometime this year" into a specific date with an owner.

Certification and record-keeping

Certificates and reports from essential services inspections belong in the documents library, both so the committee has evidence of compliance and so a new committee or manager can see the building's history without starting from scratch.

Consequences of letting this lapse

Beyond the safety risk itself, a lapsed essential services certification can expose the committee to regulatory action from a local council or fire authority, and may affect insurance cover in the event of an incident. This is one compliance category where "we'll get to it" carries real consequences.

Record-keeping obligations for strata schemes come from state legislation, and while the general categories are broadly similar across Australia, the specifics — retention periods, what must be produced on request, and to whom — vary by state.

Categories generally expected to be kept

• Meeting minutes and notices (AGM, EGM, committee)
• Correspondence with owners and relevant authorities
• By-laws and any registered amendments
• Insurance policy details and certificates
• Financial records (though full financial record-keeping, including levies and the cashbook, sits with the full Strata Pages product rather than Flex Strata)

Why retention periods matter

If a dispute arises — a by-law enforcement challenge, a query about a past decision, an insurance claim referencing historical maintenance — the ability to produce the relevant record can materially affect the outcome. Discarding records too early can leave a committee unable to defend a decision it made in good faith years earlier.

Owners' access rights

Most states give owners a right to inspect or request copies of certain scheme records, sometimes for a fee, within a defined timeframe. Exactly what must be provided, and how quickly, depends on your state's legislation — check this rather than assuming a general practice applies uniformly.

How Flex Strata supports this

Because minutes, notices, by-laws, insurance details and documents all live in the same portal and aren't tied to an individual's inbox or personal files, records naturally persist for as long as the committee chooses to keep them, rather than depending on someone remembering to archive things before leaving.

What to check with your manager or a lawyer

Specific retention periods, and the exact process for responding to an owner's request to inspect records, are worth confirming against your own state's current legislation or your strata manager's advice — this varies enough between states that a general answer risks being wrong for your specific scheme.

An audit log sounds like a technical feature, but for a strata committee it's really a governance tool — it's what lets a decision be defended later with facts rather than recollection.

What typically shows up in an audit log

• Who approved a maintenance spend, and when
• Changes to a person's access or role
• Documents uploaded, replaced or removed
• Key actions taken on compliance items, notices and disputes

Why this matters for committees specifically

Strata committees are volunteer bodies making decisions that affect other people's property and money, and those decisions are sometimes challenged — by an unhappy owner, by a departing committee member disputing what was agreed, or by a tribunal considering a dispute. An accurate record of who did what and when is far stronger evidence than anyone's memory of events months later.

A practical example

If an owner disputes that a maintenance spend was properly approved, the audit log can show exactly who approved it, against what recorded threshold, and when — resolving the question quickly rather than becoming a dispute about who remembers what.

What it isn't

The audit log is a record of actions taken in the portal — it doesn't substitute for the formal governance record (minutes, resolutions) that gives a decision its legal standing. Both work together: minutes record what the committee formally resolved; the audit log records what actually happened in the system as a result.

Access to the audit log

Given its sensitivity, audit log access is typically limited to those with a legitimate governance reason to review it, controlled the same way other page-level access is — the committee decides who can see it, rather than it being open to every seat by default.