Shutdowns cluster on event days and Monday mornings. The ACT has sharp winters and a short brutal summer.
In Canberra, multi-site teams still need lifts attendance with proof, not another email thread. Typical ACT tickets here look like a shutdown, a repeated fault, a failed landing door or a certificate cycle that is overdue.
Commonwealth precincts, campus belts and security-induction-heavy buildings where ranked trades must already hold territory access. Commonwealth and territory access rules, security clearances and quiet-hours around precincts decide whether a contractor can attend the slot.
Release notes, attendance and any certificate the site must keep. A phone call from the OEM call centre is not a close. Chase keeps lift service contracts, entrapment response and compliance tags visible on the work order before anyone marks complete.
Template the lifts job once for Canberra: proof for lift service contracts, entrapment response and compliance tags, chase intervals, after-hours routing. Clone it across sister sites in ACT.
Import the lift vendor per site. Raise against lifts. Chase accept and attendance inside the window the building can actually offer. Preferred assignees accept in the portal, check in on site, upload evidence. Release notes, attendance and any certificate the site must keep. A phone call from the OEM call centre is not a close.
Corridor coverage (Belconnen and Woden) is a separate rank from Canberra CBD pins. Onboarding blocks uninsured first attendances.
When sites hit a shutdown, a repeated fault, a failed landing door or a certificate cycle that is overdue, chase intervals stay on the template for Canberra — not ad-hoc reminders in email.
Operators export the audit trail when a centre manager, landlord or franchisee asks who last attended Canberra and what lift service contracts, entrapment response and compliance tags evidence was uploaded. That is the operating model for lifts here, not another shared inbox thread.
Preferred lifts vendors go quiet after assign
The book has a name. The accept never arrives. Ops finds out when the site asks whether anyone is coming.
Lifts proof is a photo on a phone
The person who will be asked later cannot find the work order, the attendance or the certificate.
A national lifts agreement is not a local crew
Coverage on a slide. The suburb still waits because nobody ranked a backup who can actually attend.
- Can we keep our existing lifts contractors in Canberra?
- Yes. Import the Canberra book, invite them once, and they work your jobs from the tradie portal. You are not forced onto a public marketplace for day-to-day lifts work in Canberra.
- Does a ACT-wide lifts agreement cover Canberra sites?
- Only if the ranked crew can actually attend Canberra. Corridor sites (Belconnen and Woden) and Canberra pins need separate ranks. A state-wide slide is not a local accept, and a job cannot close without proof from that pin.
- What makes Canberra different from the rest of Australian Capital Territory for lifts?
- Commonwealth precincts, campus belts and security-induction-heavy buildings where ranked trades must already hold territory access. OpsChase ranks Canberra separately so chase clocks reflect real travel and access, not a generic ACT template.
- When should we RFQ lifts in Canberra?
- When preferred rank cannot cover Canberra or peak demand — Shutdowns cluster on event days and Monday mornings. Onboard winners before their first ACT attendance.
- How do we fill a Canberra site our lifts book cannot reach?
- Run an RFQ for the lifts category in ACT, then onboard the winner. They do not receive a first work order until insurance, licences and lift service contracts, entrapment response and compliance tags checks are verified.