Maintenance approval workflow NZ: stop chasing every repair

The best maintenance approval workflow for a self-managing NZ landlord is one place to receive the tenant report, triage the urgency, line up the next step, update the tenant, and keep the record attached to the rental. The landlord should still make the decision. The admin around that decision should not live across texts, calls, quotes, invoices, and memory.

This is general information for New Zealand landlords, not legal or technical advice. Use Tenancy Services, qualified tradespeople, insurers, accountants, and lawyers as the source of truth for legal, repair, safety, and tax decisions.

Why does maintenance approval get messy?

Maintenance gets messy because the landlord is often approving work without a single operating view of the issue. The tenant report arrives in one channel, the photo sits in another, the quote is in email, the tenant update is still unsent, and the final invoice lands days later.

That means the landlord is not only deciding whether to approve the repair. They are reconstructing the job.

For a small-portfolio landlord, the painful part is usually:

• deciding whether the issue is emergency, urgent, routine, or planned
• asking the tenant for enough context without starting a long back-and-forth
• choosing whether to approve now, request a quote, or ask one clarifying question
• keeping the tenant updated before they chase
• saving the record for disputes, repeat issues, insurance, tax, or Healthy Homes context

The fix is not to become a full-service property manager. The fix is to move every repair into one approval workflow.

What should happen before a landlord approves a repair?

Before approving a repair, the landlord should know what was reported, how urgent it is, whether there is a safety issue, what evidence exists, which trade is likely needed, and what the tenant has been told. A fast approval is only useful when the decision is based on enough context.

A practical pre-approval check is:

1. What exactly was reported?
2. Where is it in the property?
3. Is there any immediate safety or property-damage risk?
4. Is the issue getting worse?
5. Do we have useful evidence, such as photos, video, or error codes?
6. Is this the right trade, or does it need make-safe action first?
7. Does the tenant need an immediate update?
8. What record needs to stay with the property afterward?

If those details are scattered, the landlord usually starts coordinating instead of approving.

What does a clean maintenance approval workflow look like?

A clean workflow turns the repair into a sequence:

1. Tenant reports the issue. The report captures the affected room, what happened, when it started, whether it is worsening, and any useful photos or video.
2. The issue is triaged once. The landlord or operating system marks it as emergency, urgent, routine, or planned.
3. The next step is prepared. That may be a make-safe instruction, a quote request, a trade booking, a tenant question, or an approval request.
4. The landlord approves the decision. The landlord stays in control without doing all the chasing.
5. The tenant is updated. The tenant knows the issue has been seen, what happens next, and when to follow up.
6. The record closes with the job. The invoice, photos, notes, and decision trail stay attached to the rental.

That workflow is simple, but it changes the job. The landlord is no longer the person holding the whole process together manually.

How does this change the landlord's role?

The old role is coordinator. The better role is reviewer.

The coordinator role sounds like:

• "Can you send a photo?"
• "I will call someone."
• "Can you be home Tuesday?"
• "I need to find the quote."
• "Did we ever close that job?"

The reviewer role sounds like:

• "This is the issue."
• "This is the urgency lane."
• "This is the recommended next step."
• "Approve, ask one question, or request a quote."
• "The tenant update and record are handled in the same workflow."

That is the operating-model shift Keel is built around. The landlord still controls the decision. Keel helps carry the request, triage, tenant update, approval, and record through one system.

What should the tenant update say?

The tenant update should say the issue has been received, what urgency lane it sits in, what happens next, and what to do if the issue gets worse. It should not overpromise timing or give legal, electrical, plumbing, gas, or building advice by message.

For example:

Thanks for sending this through. We have logged the repair and are checking the urgency and right next step. Please let us know if there is any smell, sparking, active leaking, loss of security, or other safety concern.

If the next step is clear:

We have logged this as an urgent repair and are arranging the right trade. We will update you once the booking is confirmed and keep the repair notes with the property record.

If one detail is missing:

We have the report. Before approving the next step, please send one photo of the affected area and confirm whether the issue is getting worse.

The best tenant update is plain, specific, and tied to the next action.

Where Keel fits

Keel helps self-managing landlords keep the decision seat without becoming the repair coordinator for every issue.

In Keel's model:

• tenant reports come into one flow
• the issue is easier to triage before it drifts
• approval moments are clearer
• tenant updates and follow-ups stay connected
• repair evidence stays closer to the property record
• the landlord reviews the next step instead of rebuilding the whole job from messages

That matters most when maintenance volume is not huge, but every loose end is expensive in attention.

If your rental maintenance work is still spread across phone messages, email, calendar reminders, and memory, see how Keel works for landlords.

Source notes

• Tenancy Services, Property maintenance.
• Tenancy Services, Damage and repairs.
• Related Keel guide: Tenant maintenance request workflow NZ.
• Related Keel guide: How to handle tenant maintenance requests in NZ.