How do strata managers stop approval requests disappearing into email?

Short answer

Strata managers stop approvals disappearing by giving every request one visible record with the scheme, documents, decision owner, deadline, status and exception path, while leaving authority and judgement with the right people.

The problem is rarely that nobody cares. It is that the approval exists as a conversation instead of a controlled piece of work. One person has the latest quote, another has the committee context, a third has replied to an older thread and the contractor is waiting for an answer. The manager becomes the only person who can reconstruct the truth.

For a Sydney strata firm, that is more than annoying admin. It uses portfolio capacity, delays repairs or renovations and makes an otherwise capable team look unresponsive.

The expensive moment is the status chase

A common approval starts sensibly. A resident reports a repair, a contractor sends a quote or an owner submits a renovation request. The strata manager identifies who can decide and circulates the information.

Then the workflow fragments. A committee member asks for a second quote. Someone replies privately. A document is missing. The preferred supplier changes availability. The manager sends another follow-up because there is no single status that everyone trusts.

The NSW Government describes different decision responsibilities across owners corporations, strata committees and strata managers. It also notes that major repairs may need a committee meeting, quote approval and attention to spending limits. That makes the authority path important. It does not make a scattered email chain a good operating system.

The commercial symptom is visible when a manager has to ask: Who still needs to decide? Which version was approved? Is the contractor waiting on us? Did we tell the resident?

Create one approval record, not another inbox rule

The practical fix is a single approval record that sits between the incoming request and the final outcome. It can live in an existing property platform, CRM, case system or a small connected workflow. The technology matters less than the fields and ownership.

Every record should show:

• the scheme, property or matter it belongs to
• the request and the outcome being sought
• the latest quote, form, scope and supporting documents
• the person or group authorised to decide
• the date the decision is required
• the current status and last meaningful action
• the normal next step and the exception path
• the final decision, reason and communication sent

Email can still be a channel. It just stops being the only place where the state of the work exists. Replies, documents and decisions should update the same record so the team does not have to search several threads before answering a client.

Connect the trigger to the next commercial step

A useful workflow begins when a recognisable event occurs. That might be a repair request, a renovation application, a quote above a delegated limit or a contractor response. The system creates or updates the approval record and checks whether the required inputs are present.

If the normal path is clear, it can prepare the committee pack, notify the decision owner, set the deadline and surface overdue action. Once the decision is recorded, it can update the work order, notify the requester and preserve the supporting evidence.

That is where Run Lighter is relevant. We can connect the inbox, forms, document store, property platform and task system so routine information moves once. The objective is not more alerts. It is a reliable baton change from request to decision to action.

This is the same operating principle behind a strong client handoff after lead generation and a useful on-site automation review. One owner, one state and one visible exception path matter more than adding another tool.

Keep authority, risk and judgement human

Approval automation should not make the decision. It should make the decision ready, visible and traceable.

Human judgement remains essential when the scope is disputed, information is incomplete, safety is urgent, a conflict exists, the requested work falls outside delegated authority or a committee must weigh competing interests. The system should route those exceptions to the responsible person with the evidence they need.

That boundary matters in strata because the right decision-maker can vary with the scheme, by-laws, agency agreement, spending limits and type of work. The NSW Government also notes that some minor renovation requests may be taken as approved if a written refusal is not provided within three months, where the relevant by-law allows the committee to decide. A workflow can make that deadline visible, but it cannot replace advice about the scheme's actual obligations.

Measure recovered capacity, not email volume

Do not judge the change by the number of automated messages sent. Measure whether the firm can see and move approvals with less recovery work. Useful checks include:

• time from complete request to recorded decision
• number of approvals without a named decision owner
• number of overdue approvals with no exception recorded
• manager time spent reconstructing status
• contractor or client chasers before an update
• approvals returned because information was incomplete

The strongest first project is one frequent approval type with a known trigger and enough commercial consequence to matter. Test the normal path and several real exceptions before expanding it across the portfolio.

Start with one approval that keeps coming back

Choose a recent approval that needed repeated chasing. Put every email, document, person, deadline and decision on one page. The gap usually becomes obvious: no agreed source of truth, no named owner, no deadline, no exception path or no connection to the next action.

Run Lighter can trace that approval on site, show where the handoff breaks and design the smallest practical connection around the systems your team already uses. The result should give the manager more control, not remove the committee's judgement.

If one approval keeps creating a dozen follow-ups, book an on-site automation review. We will follow the real request from arrival to outcome and identify the first fix worth making.