Property management

Maintenance requests from intake to closed

At many management companies, every maintenance request lands with one coordinator, and the emails, texts and portal tickets get worked top to bottom in the order they arrived. An A/C outage in a unit with a baby can sit behind a running toilet and a humming dishwasher until mid-afternoon.

Who it is forResidential property management companies managing 200 to 3,000 units with 5 to 50 staff
Who decidesThe maintenance coordinator
Where the work livesEmail, texts and tenant portal → AppFolio or Buildium work orders → vendors and owners
BuildTen business days
An apartment front door with a paper door hanger on the handle marked with a unit number, a red tag clipped to it, a plumber's toolbox on the hallway floor beside a coiled drain snake and a pipe wrench.

Who does what

The hours go into sorting, chasing and re-telling, not into fixing anything.

Intake and triage The agent reads each email, text and portal ticket, logs it as a work order in AppFolio or Buildium, and ranks it against the company's emergency list.The agent
Vendor dispatch The agent proposes the preferred vendor for that property and trade and checks that the insurance on file is current before anyone is sent.The agent
Owner approvals Where a cost passes the owner's limit, the agent sends the request the way that owner prefers and follows up when there is no answer.The agent
Tenant updates and open items The agent drafts tenant updates on the company's schedule and chases vendors for dates and completion on every open work order.The agent
Costs, exceptions and judgment calls The coordinator approves vendor choices and costs, handles disputes and odd jobs, and decides when a rule should bend.The maintenance coordinator

What you get

A logged work order for every request, ranked by urgency, with a proposed vendor, an owner approval request where the owner's limit calls for one, and a drafted tenant update.

Draft for review

Text
A tenant at a managed property texts that the A/C stopped working overnight, the apartment is hot, and there is a newborn in the unit.
Draft
An emergency work order logged in Buildium for HVAC, dispatch proposed to the property's preferred HVAC vendor, and a reply to the tenant saying the job is logged as urgent and a technician is being scheduled.
Based on
The company's emergency list (no cooling with a vulnerable occupant), the preferred HVAC vendor for this property, and that vendor's current insurance certificate on file.
How sure it is High
Why a person decides Emergency dispatch goes to the coordinator to confirm, and if the quoted repair passes this owner's approval limit, the coordinator decides whether to proceed under the emergency clause or wait for the owner.

The rules it follows

It follows each owner's approval limits from the first day.

These are your company's own rules, written down and confirmed with your team during the build. It works on its own only within limits you set.

  • The preferred vendor for each property and trade, with a backup when the first one can't come.
  • Each owner's approval limit for repairs and how that owner wants to be contacted.
  • What counts as an emergency, such as no heat, no cooling with a vulnerable occupant, or an active leak.
  • How often tenants are updated on an open work order, and that no vendor is dispatched without current insurance on file.

What it learns when your team adjusts its work

Useful from the first day, and it keeps getting better. The maintenance coordinator reviews its work.

The busywork it takes off the maintenance coordinator. It takes the data entry, vendor chasing, owner follow-up and repeat tenant updates off the maintenance coordinator. That time goes back to the work only they can do.

What it starts out knowing

  • The preferred vendor for each property and trade
  • Each owner's approval limit and contact preference
  • The company's list of what counts as an emergency
  • Each vendor's insurance expiry date

It works from these sources, shows which one an answer came from, and asks when the answer is not there.

Who reviews its work, and when review can stop

At first the coordinator reviews every work order, vendor choice and owner message before it goes out. Review stops for a routine type of job, such as a standard plumbing call under the owner's limit, once the agent's record on that type is good and the business agrees.

Emergency dispatch, costs above an owner's limit, and any dispute with a tenant, vendor or owner keep going to a person.

It no longer needs review once its record on them is good and you agree, one type of task at a time. New, unusual and high-stakes work stays with a person.

When your team adjusts its work

When the coordinator sends an appliance job at one property to a different vendor because the usual one is slow there, the change is saved as a rule for that property and trade, and next time the agent proposes the new vendor first. The coordinator decides whether a change becomes a rule, an example or a one-time exception.

It learns how your company does this job. It does not watch, rate or profile your employees. Your team decides what it learns. You can read everything it has learned and remove anything. Whoever runs it, your team or our engineers, makes sure on a regular cycle that what it learned stays inside the bounds you agreed.

From a request a business posted

A maintenance coordinator at a property management company, on a property management forum.

After four years in the role, the coordinator described starting most mornings with more than a dozen new requests and no way to rank them, so urgent jobs surfaced hours late. Vendor insurance had lapsed without anyone noticing until dispatch time. Dozens of owners each had their own approval limits and habits, none of it written down, and slow owner replies left tenants waiting for days.

Paraphrased from a public post, not quoted, and not a client engagement.

From first principles

Which requests are urgent, who should fix each one, does the owner need to approve it, and what does the tenant need to hear next?

Before we build anything, we take the work down to what has to be true. What is left over is habit. Habit gets deleted, not automated.

  1. What has to be true

    • Every request is logged as a work order, wherever it came in.
    • Urgent jobs reach an insured vendor first.
    • Owners approve repairs above their own limits, and tenants hear where things stand.
  2. What is only habit

    Working the inbox in the order requests arrived is only habit. So is keeping each owner's approval limit and contact preference in the coordinator's memory.

  3. What we delete before building anything

    We delete the re-entering of each request into the work order by hand and the status texts typed one at a time. We write down the owner limits that today live in one person's head.

  4. What is left

    The agent. The agent logs and ranks each request, proposes the preferred insured vendor, sends approval requests to owners and follows up on silence, and keeps tenants updated on the schedule the company sets.

    A person. The coordinator reviews vendor choices and costs, handles anything unusual, and decides whatever needs a judgment call.

The kind of work: Work that arrives by email and phone. Work orders, bills, voicemails, texts and maintenance requests reach the business as messages, and each one has to be read, sorted and entered into the system that runs the work. The software holds the record once it exists, but someone still has to decide what each message is, where it belongs and whether it fits the rules, so people do it by hand.

What the engagement needs

What we need from you, and how it runs.

The engagement needs access to the maintenance inbox, the text line and the tenant portal, plus permission to create and update work orders in AppFolio or Buildium. It also needs the vendor list with trades and insurance dates. We sit with the coordinator to write down each owner's approval limit and preferences.

How the engagement runs

  1. 01

    Fit test first

    We check the time this job takes, access to your systems and how you would review the result. If a ready-made tool is enough, we say so.

  2. 02

    Build in ten business days

    Senior engineers agree the rules with the maintenance coordinator, test on past cases and set approval limits and a way to switch it off.

  3. 03

    Ninety days of support, included

    Work with the agent in Slack, Teams or text messages. We fix problems and adjust it as unusual cases come up.

  4. 04

    Keep improving it, with your choice of operator

    You own the agent and keep its source, tests and guide either way. Your team runs it, or our engineers run it with a monthly report. Learning continues on your own servers, in your own cloud account or in our data center.

When we'd point you elsewhere

Sometimes a ready-made tool is enough.

The fit test checks this first. If one of these covers your case, we tell you, and you keep the map of the work.

  • A landlord with a handful of units, one or two trusted vendors and a few requests a month A shared spreadsheet and a texting app are enough.
  • Requests already arrive only through the tenant portal and owners approve inside the owner portal The built-in maintenance tools in the property management system may cover intake and vendor follow-up.

Honest limits

What this page does not claim.

The agent does not judge whether a repair is worth doing or approve spending; the coordinator and the owner decide that.

The situation on this page is drawn from a public request posted by a person at a management company, paraphrased, not a client engagement.

Show us the work

More use cases

More work of the same kind: work that arrives by email and phone.