How to set up a maintenance request system for a small, self-managed HOA

In a self-managed HOA, maintenance requests arrive the same way everything else does: a text message, a hallway conversation, a Post-it on the board president's door. There is no front desk. There is no work-order system. There is just whoever happens to be standing nearest when a pipe drips.

For a 4-unit building, this works fine. You know your neighbors. If unit 2's deck railing is loose, someone mentions it at the Saturday barbecue and someone else grabs a drill.

But around 10 or 12 units, the informal method breaks. Requests get dropped. Two people call different plumbers for the same leak. A board member spends an afternoon on a repair that a different board member already scheduled last week. And when an owner asks "what happened with the garage door?", nobody can answer without searching three different text threads.

A maintenance request system does not need to be complicated. It needs three things: a single place requests go, a way to know who is handling what, and a record that survives when someone leaves the board. Here is how to build one.

Start with one intake point

The first problem is that requests arrive everywhere. Email, text, Slack, WhatsApp, carrier pigeon. Pick one channel and make it the official one for maintenance.

For most small HOAs, a shared inbox is the right answer. Something like yourhoa@hoamail.app. Give all owners one address and tell them: if it is broken, send it here. The whole board sees it. Nobody has to forward a text message to the group chat.

The key rule: every request goes through the intake point. Even the one your neighbor mentions in the elevator. "Would you mind sending that to the board inbox so we don't lose track of it?" is a sentence every board member should get comfortable saying.

Triage before you act

Not every maintenance request is urgent, and not every board member needs to act on every one. A simple triage step prevents the four-people-responding-to-one-email problem.

After a request comes in, assign it to one person. That person owns it until it is done. The other board members can see the status, but they are not responsible for acting.

For triage, use three buckets:

1. Immediate. Safety issues, active leaks, broken locks on common doors. Someone acts today.
2. Scheduled. Deck staining, gutter cleaning, HVAC servicing. These go on the calendar for the next board meeting or the next available weekend.
3. Deferred. Cosmetic issues, nice-to-have upgrades, things that need a reserve-fund conversation first. These get logged and reviewed quarterly.

That third bucket matters more than it sounds. When an owner asks "did anyone ever look into repainting the stairwell?", you have the record. The board discussed it on March 15 and tabled it until the reserve study comes back. End of conversation.

Track to completion

The best system is the one you actually use. A spreadsheet works. A shared Google Doc works. What matters is that every open request has exactly these fields:

• What needs fixing (unit, location, description)
• Who reported it and when
• Who on the board owns it
• Current status (new, in progress, waiting on vendor, done)
• When it was completed

The status field is the one that earns its weight. "Waiting on vendor" is different from "in progress." If a board member is waiting for a plumber to call back, the rest of the board should know that so they are not also calling plumbers.

Build the vendor file as you go

Every time you hire someone for a repair, save their contact info, what they did, and how it went. This sounds tedious until the first time you need a roofer and someone on the board says "didn't we use someone for the skylight two years ago?"

A shared vendor file, even a simple one, prevents the cycle where every board generation starts from scratch. For each vendor, track:

• Company name and contact
• What they worked on, when, and for how much
• Whether you would hire them again (this is the field that matters most)

After three years of this, your board has something a property management company charges for: a vetted vendor list for your specific building's specific problems.

Make it the new board's problem to use, not to invent

Board turnover is where most small-HOA systems die. The person who built the spreadsheet leaves, and the spreadsheet leaves with them.

Two habits prevent this:

Store the system somewhere shared. Not on a personal Google Drive. Not in a board member's Gmail account. On a shared drive, a platform the whole board can log into, or a physical binder in a common area that everyone knows exists.

Document the process, not just the data. A one-page document called "How maintenance requests work" that lives next to the vendor file. It should answer four questions: (1) where do owners send requests, (2) who triages them, (3) how do we track status, and (4) where do we keep vendor records. When a new board member joins, this is page one of their onboarding.

The real goal is reliability, not heroism

Small self-managed HOAs run on individual effort. The board member who repaints the hallway on a Saturday, the treasurer who notices the insurance bill is due, the president who handles every email because nobody else wants to. It is admirable work. It is also fragile.

A maintenance request system does not replace that effort. It makes it visible, distributes it, and keeps it from evaporating when the person carrying it steps down. That is the actual deliverable: not a spreadsheet template, but a board that knows what needs doing, who is doing it, and what happened to the last thing someone reported.

Start with the intake point. Add triage. Track to completion. Build the vendor file. Write down the process. None of these steps requires software. All of them together are what separates a board that handles maintenance from a board that just hopes nothing breaks.