A strata committee meeting should open on evidence, not on a pile of forwarded emails.
Managers and committee members already know the pain. Common-property jobs sit across text messages, resident apps, and contractor inboxes. Photos of a failed hydrant valve arrive late. A plumbing defect on a carpark sump is “done” according to someone, but nobody can show attend time or sign-off. When the agenda hits maintenance, the room spends twenty minutes reconstructing what happened instead of deciding what to do next.
OpsChase is built for that meeting moment: one queue for common-property work, your contractors followed up until photos and sign-off, and close-out packs a committee can actually read.
Common property is not a resident chat problem
Residents need a place to report issues. Committees and managers need a system of record for work on common property — who was offered the job, who attended, what proof landed, and whether complete was allowed.
Those are different jobs. Treating maintenance as another resident thread means evidence evaporates before the next ordinary general meeting or insurance query.
On strata portfolios, the operator pattern is familiar: many schemes, shared plant, after-hours faults, and trade firms that already know the buildings. The failure mode is follow-up. Nobody confirms the job. Attendance is verbal. Certificates sit in a contractor’s email. The committee pack becomes a scramble.
What a meeting-ready pack looks like
A useful pack is boring in the best way. For each material job it shows:
- Scheme and common-property location
- Trade and work raised
- Regular contractor offered and confirmed
- Attend time on the record
- Photos, checklists or certificates attached
- Sign-off on the job
That is enough for a chair to say “this is closed with proof” or “this is still open — here is the next follow-up.” It is not a novel. It is not a dump of every chat screenshot from the quarter.
OpsChase strata audit-pack exports are built around that close-out shape. Sample packs use example schemes so you can read the layout; in your account the same structure applies to your contractors and your proof templates.
Your contractors on common property
Schemes already have relationships — mechanical, plumbing, fire protection, electrical, cleaning. Those firms know riser keys, basement access, and quiet hours. Add them once, per scheme or across the book, and send the job to the regular business for that scheme and trade.
Follow-up runs on the job. Missing confirmation stays visible. Missing attendance stays visible. Missing photos or certificates keep the job open.
That is how you avoid the Monday call where three people remember three different contractors and none of them have proof. Keep the language honest: your contractors, followed up to close-out.
Fire and wet-area jobs committees actually ask about
Committees ask about life-safety and water damage more than they ask about paint colours. Fire defects, hydrant and hose-reel outcomes, and essential safety measures need certificates and clear attend records. Wet areas and plant rooms need photo pairs, not a single blurry image from a phone.
Put those requirements on the work order template. Fire protection and plumbing jobs then carry the same follow-up discipline as a simple door closer. OpsChase does not issue Annual Fire Safety Statements or regulator certificates — it stores the job proof your contractors leave so the committee can see what was done and when.
Capital works context without pretending to be the prescribed form
In New South Wales and other states, capital works planning and prescribed forms sit in their own world. OpsChase stores job proof for maintenance and defects; it is not Strata Hub and it is not the prescribed capital works form. Use it for the operational layer committees feel every month: open defects, attend status, and close-out packs.
The committee still owns decisions; the software holds the evidence trail.
How managers prepare without a late-night rebuild
Two days before the meeting, filter open and recently closed common-property jobs. Export the pack for the schemes on the agenda. Highlight anything still waiting on proof. That is the conversation: decisions and next steps, not archaeology.
If a job is stalled, the next follow-up time is already on the work order.
Getting a pack in front of the committee
Import schemes and add your contractors. Set proof expectations for fire, plumbing, and plant. Raise the next common-property defect into OpsChase. Keep resident channels for intake if you need them; keep the work order for truth.
Read the strata industry page or open the strata audit-pack samples. For a walkthrough with your scheme list, book a demo.
Meetings run better when evidence is already in the pack. Put common-property jobs on one queue, follow your contractors through to close-out, and open the agenda on facts.