How to handle tenant maintenance requests in NZ without losing your weekends

The short answer

The best way to handle tenant maintenance requests is to run them through one system, not through memory.

That means every request gets:

• logged in one place
• triaged by urgency
• approved or booked clearly
• closed with a record of what happened

If you self-manage a rental, that is the difference between a manageable workflow and a Saturday morning that disappears into texts, missed calls, and follow-ups.

Why maintenance requests feel bigger than they are

Most landlords do not struggle because there are too many maintenance issues. They struggle because the workflow is messy.

A dripping tap, a broken extractor fan, and a burst hot water cylinder often arrive in exactly the same format, a message on your phone. When every issue arrives as just another text, three things happen fast:

• Urgency gets blurred. Small jobs and genuine emergencies compete for the same attention.
• The record disappears into messages. It becomes hard to prove when something was reported, what was booked, and whether the tenant was updated.
• Your personal time becomes the system. If your phone is the workflow, your evenings and weekends become the workflow too.

The issue is not only convenience. It is control.

What NZ landlords are actually responsible for

Tenancy Services is clear that landlords must provide and maintain rental properties in a reasonable state of repair, and keep the plumbing, wiring, structure, locks, and fastenings safe and in working order.

Tenancy Services is also clear that tenants must tell the landlord straight away if they know something needs to be repaired or maintained.

That means the landlord problem is not just "fix things eventually". The real job is:

1. make it easy for tenants to report issues properly
2. decide what is urgent and what is not
3. act quickly enough that small issues do not turn into legal, cost, or tenant-trust problems

The maintenance workflow that actually works

For most self-managing landlords, the cleanest system is a four-lane workflow.

1. Reported

Every issue lands in one place first.

At minimum, the report should include:

• what the issue is
• which room or area is affected
• when the tenant noticed it
• whether the issue is getting worse
• a photo or video if one helps

This is where most landlords already save time. A single place to capture the issue is much better than reconstructing the story from scattered texts later.

2. Triaged

Once the issue is logged, decide what lane it belongs in.

A practical NZ-landlord triage stack looks like this:

• Emergency, same day: burst pipes, gas leaks, total power faults, serious security issues, no heating in winter where habitability is affected
• Urgent, within 24 to 48 hours: no hot water, blocked drains, broken appliances that materially affect daily living
• Routine, within 1 to 2 weeks: dripping taps, minor leaks, sticking windows, worn fittings
• Planned, next maintenance window: upgrades, repainting, items worth bundling into a later tradie visit

This is the step that stops every tenant message from feeling equally urgent.

3. Approved and booked

Once the priority is clear, decide the next action.

That usually means:

• approve the repair now
• ask one clarifying question
• bundle it with other routine work
• or book the right tradie and confirm the time with the tenant

This is where many landlords still lose time. They know a job needs doing, but the booking, quoting, tenant update, and approval trail all happen across different apps.

A better system keeps the decision with the landlord, but removes the admin sprawl.

The first-approval checklist before you say yes

A lot of maintenance waste happens at the approval step. The landlord is not deciding whether maintenance matters. They are deciding what should happen next, how quickly, and with how much admin drag.

Before you approve a job, run this quick checklist:

1. What lane is this really in? Emergency, urgent, routine, or planned. If the lane is wrong, everything after it usually gets slower or more expensive.
2. Do I have enough evidence? A photo, a clear description, the affected room, and whether the issue is getting worse are usually enough to avoid a wasted callout.
3. Does this need make-safe action first? Water isolation, electrical shutdown if safe, a locksmith, or a temporary repair may matter before the full fix is booked.
4. Is this the right trade? A plumber, electrician, drainlayer, locksmith, appliance technician, or general maintenance contractor are not interchangeable.
5. Do I approve now, ask one question, or request a quote? Good systems make that decision explicit instead of burying it in a message thread.
6. What does the tenant need to know next? Acknowledgement, expected timing, access plan, and what to do if the issue worsens.

This is where Keel's review-led model matters. The landlord still makes the call, but the approval lives inside a clear workflow instead of inside memory, scattered texts, and half-finished follow-ups.

4. Closed with a record

A maintenance job is not finished when the tradie leaves. It is finished when the landlord has:

• confirmation the issue is resolved
• the invoice or cost record
• the completed timeline
• the note of any follow-up work still needed

That record matters later for disputes, insurance, tax, and simple memory.

What changes when you stop using your phone as the workflow

The old way looks like this:

• tenant texts the issue
• landlord replies when they can
• a tradie gets called later
• the update sits in another thread
• the invoice lands in email
• the history lives nowhere useful

The better way is review-led:

• the issue is captured in one queue
• urgency is assigned once
• the next step is approved clearly
• the tenant gets updated
• the job history stays attached to the property

That is the operating-model shift Keel is built around.

Keel does not ask the landlord to stop being in control. It changes the job from manually running each maintenance task to reviewing, approving, and escalating when needed.

Where Keel fits

If you are using Keel, the goal is not just to store maintenance notes. The goal is to make the workflow calmer.

That means:

• tenant requests come into one place
• the issue can be triaged into the right urgency lane
• the landlord reviews and approves instead of running the whole job from their phone
• the record stays attached to the property instead of disappearing into scattered messages

For self-managing landlords, that is usually the real win. Not fewer maintenance issues, just fewer messy decisions.

What to tell tenants at the start of a tenancy

A good maintenance system starts before the first repair. Set the rules early:

• how tenants should report maintenance
• what details to include
• when they should expect acknowledgement
• what counts as an emergency
• when they should call directly instead of waiting for a message reply

That last point matters. Genuine emergencies should never sit in a low-priority inbox. A clear reporting process reduces avoidable back-and-forth and helps tenants trust that issues are being handled properly.

The real payoff

A structured maintenance workflow does not remove landlord responsibility. It removes friction.

You still approve the work. You still decide what matters most. You still keep control.

But you stop using your own attention span as the maintenance system.

That is how a self-managing landlord gets closer to calm control instead of always feeling one tenant text away from another lost weekend.

If you want the same review-led approach across maintenance, rent ops, tenant comms, and compliance, see how Keel works for landlords.

Source notes

• Tenancy Services, Property maintenance: landlords must provide and maintain rental properties in a reasonable state of repair and keep core systems safe and working.
• Tenancy Services, Damage and repairs (updated 16 April 2026): tenants must tell the landlord straight away if something needs repairing or maintaining.
• Related reading: Emergency maintenance: what NZ landlords must respond to immediately