In the ACT, strata schemes can start with assets and planned maintenance, jobs and contractor management, then switch on more of OpsChase as they grow.
Operations leads in the ACT want plant rooms in central Canberra and common areas in Tuggeranong followed up the same way, with the same proof at the end.
In the Australian Capital Territory, strata businesses with one site or many still need attendance with proof, not another email thread. Typical ACT tickets look like a basement leak, a failed booster pump, a lift fault or a fire-panel defect on common property.
Head office and the site leads in Woden and Tuggeranong see the same queue: who confirmed, who checked in, whether uploads landed. A crew that covers Queanbeyan does not automatically hold the access rules and inductions for a Civic plant room. Send the crew that already holds the induction, not a Sydney number on a spreadsheet.
When a job goes quiet, managers see the next follow-up time instead of guessing whether anyone is attending Canberra or Tuggeranong. Put crews who actually confirm for Woden first, not a roster that goes quiet.
Committee packs export follow-up steps and sign-off timestamps per scheme — useful when owners compare metro and regional attendance.
You can run Canberra, Woden and Tuggeranong separately. Import schemes as sites. Send jobs to your building manager or your fire, lift, plumbing and cleaning contractors. Set proof per trade. Raise from the building manager, not from a group chat. Your own team and your contractors confirm jobs on their phone.
Commonwealth offices, campuses, civic buildings and a dense apartment belt with strict access and security inductions. Follow-up reminders fire on missing confirmation, attendance or proof.
A national agreement only counts if someone attends ACT suburbs on time. Keep committee evidence, common-property by-laws and owner notifications on the template, so every job closes the same way.
Commonwealth and territory access rules, security clearances and quiet-hours around precincts decide whether a contractor can attend the slot. OpsChase records proof on the strata job, so committee evidence, common-property by-laws and owner notifications are visible at close-out.
Common-property jobs go quiet between committee meetings
Owners email contractors directly. The strata manager finds out when duplicate invoices arrive — with no shared attend clock on the leak.
Fire, lift and plumbing jobs need follow-up, not another inbox
The retainer book is real. Silence between annual cycles still blows certificate due dates if nobody escalates the work order.
Attend is logged somewhere; close-out proof is still missing
Gate sign-in or a text from the contractor is not a committee pack. Photos, certificates and sign-off belong on the scheme’s job.
Dozens of schemes and one thin ops bench
Building managers raise in phone notes; regional ops cannot see stalled confirmations or missing proof across the portfolio until someone forwards a thread.
- Can we keep our existing contractors for strata schemes in the ACT?
- Yes, and you don’t have to use contractors at all. Give maintenance at your strata sites in the ACT to your own team or your contractors, and see each job through to proof.
- Does a national maintenance agreement cover ACT strata schemes?
- Only if the crew you send can actually attend Canberra and Tuggeranong. A national banner is not the same as an on-site confirmation in the ACT, and a job cannot close without proof from that site.
- What proof do Australian Capital Territory strata sites expect?
- A meeting pack needs who attended, what they proved, and whether the certificate is current. The job can’t be closed until that proof covers committee evidence, common-property by-laws and owner notifications.
- Can one vendor cover all strata sites in the ACT?
- Only if they actually attend. Keep a separate first choice for Canberra, Woden and Tuggeranong, and see every job there closed with proof.