How Strata Managers Can Triage Maintenance Requests

I would build strata maintenance triage around urgency, responsibility and authority, in that order. Start with preparation around the existing strata platform: collect the useful details, prepare the next action and put the decision in front of the right person. That is the maintenance application of choosing which property workflows to automate first.

How Should a Strata Manager Triage a Maintenance Request When It Arrives?

The first workflow is intake and classification. A complete report gives the manager something to act on; an automated acknowledgement alone leaves the repair waiting.

1. Trigger: a request arrives by email, web form or portal.
2. Prepare: match the scheme and lot, gather the location, photos and access details, and draft any missing-information question. Suggest urgency and responsibility separately, showing the reason for each flag.
3. Approve: a person confirms both flags. Safety terms involving water, gas, fire, electrical faults, structural damage, lift entrapment or security go straight to a person rather than waiting in the routine queue.
4. Record: retain the original message, suggested flags, confirmed decisions, approver and timestamps.
5. Measure: time to acknowledgement, time to confirmed classification and how often the manager changes a suggested flag.

I would keep acknowledgement separate from acceptance of responsibility. A reply can confirm receipt and explain the next step without promising a contractor, reimbursement or a repair date.

How Do You Tell a Common Property Repair Request from a Lot Owner's Repair?

Use the reported location to gather evidence, then check the scheme documents. A ceiling stain tells you where someone noticed water. It does not establish which pipe failed or who must repair it.

In NSW, the owners corporation maintains and repairs common property. NSW Government guidance says to check the strata plan and by-laws when responsibility is unclear. Its examples include roofs and gutters as owners corporation items, and carpet as an owner item.

Keep the state rules attached to the scheme record:

AI can suggest a category and assemble supporting material. I would leave an uncertain case unresolved until a person checks the evidence. This is general process guidance; use the relevant state regulator, scheme documents and legal advice for disputed responsibility.

What Should Happen When a Strata Repair Request Is an Emergency?

Design the emergency route before the routine queue. Send a potential emergency to the designated person with the original report, photos, location and scheme emergency contacts. Do not wait for a completed responsibility assessment.

Consumer Affairs Victoria describes emergency corrective maintenance as work that must happen immediately for health, safety or security reasons. NSW guidance tells residents to notify the strata manager if possible and check the management company's emergency tradesperson list. These are state-specific instructions, not a national response-time promise.

Example: Water Through a Bathroom Ceiling

An owner emails on Sunday night about water coming through a bathroom ceiling. In this proposed workflow, the water terms send the report straight to the on-call person with the scheme's emergency tradesperson list. The system drafts a holding reply.

Responsibility stays undecided until the plumber reports whether the source is a pipe in the lot above or common property. The record keeps photos and the plumber's written details; the manager confirms responsibility and cost allocation afterwards. This is a design example, not a Truespeak client story.

Truespeak does not provide phone answering or voice agents. The existing after-hours emergency arrangement stays with the manager.

Which Approvals, Quotes and Spending Limits Should the Repair Process Check?

The second workflow begins when a person confirms that the repair belongs with the owners corporation. Prepare the scope before asking someone to approve expenditure.

1. Prepare: draft the quote request or work order with location, scope, photos, access notes and preferred contractors.
2. Check: retrieve the scheme's delegation and spending limit; flag quote requirements or a committee decision. Include licence and insurance status where the platform provides it.
3. Approve: a person authorises the contractor and spend, escalating anything beyond delegated authority. Emergency work follows the scheme's emergency process, with the record completed afterwards.
4. Record: keep the quotes considered, approval and authority relied on against the job.
5. Measure: time from confirmed request to issued work order, and jobs returned for missing details.

NSW Government guidance explains that owners corporations can delegate functions to strata managers. The workflow should retrieve the actual delegation, rather than assume the manager can authorise every repair.

As at 3 November 2026, NSW Government guidance requires at least two independent quotes for work valued at more than $30,000, with an exception for emergency repairs. That threshold is not a universal manager spending allowance or a national rule.

What Can Automation Add Beyond Strata Master Connect or Similar Platforms?

I would check the existing platform before commissioning another system. As at 3 November 2026, MRI Strata Master Connect describes building-specific rules, creditor compliance verification and approval notifications. MRI Strata Master already describes work order tracking, reminders and maintenance visibility.

The useful addition is preparation between the incoming report and those existing functions: match the scheme, collect missing details, show the evidence and prepare a draft for approval. Ask MRI to demonstrate how an inbox email becomes a work order and where human review occurs. The pages checked do not describe that path.

My property work order software guide covers the software question. The broader strata automation guide covers other starting points; tenant maintenance automation covers the separate rental workflow.

Truespeak is the best fit for an Australian strata business that wants a preparation layer designed, built and run around its existing tools, with people approving sensitive decisions.

I have spent more than 20 years in commercial roles and built 25 working productivity systems, but Truespeak has no strata maintenance build to point to. Truespeak designs, builds and runs AI automation as a managed service, monitors failures and reviews exceptions; where a tool has no usable connection, the step stays manual. The first step is a discovery call.

What Should Maintenance Tracking Measure, and What Should Never Be Automated?

The third workflow starts when a work order is issued or a due date passes. Prepare contractor reminders, resident updates, committee summaries and an invoice-to-work-order match for review.

A person approves messages involving disputes, liability or damage, and confirms completion before payment. Record dates, photos, the invoice and final status against the common property item. Measure open job age, overdue jobs, repeat requests for the same item and owner chasers per job.

I would keep these decisions with a person:

• Unclear responsibility, liability and reimbursement promises.
• Safety, emergency and insurance decisions.
• Contractor selection involving potential conflicts or commissions.
• Spending beyond delegated authority, legal disputes and complaints.

My guide to human approval in automation explains that boundary. For maintenance, the approval record should show who made the call, what information supported it and what happened next.