A maintenance request system so repairs don’t get lost

Why repair requests slip through

A lost request often wasn’t ignored. It landed somewhere nobody checks twice. One tenant texts the manager’s personal phone on a Saturday. Another leaves a voicemail after hours. A third mentions the dripping tub to the cleaner in the hallway. Each request is real, and none of them is written down in the same place.

For example, a landlord with 12 units in two buildings might take the calls. A maintenance tech takes texts, and the bookkeeper reads the email inbox. On Monday morning, nobody has the full list. The tub keeps dripping, the tenant asks again, and by the third ask it’s a stain on the ceiling of the unit below.

Three things go missing at once: the request, the date it came in, and the proof it was handled. The tool matters less than the habit. Every request, from every channel, becomes one record with a date on it.

What a maintenance request system has to do

Whatever you use, from a shared spreadsheet to a custom system, it has five jobs. If one is missing, requests still slip.

Notice what isn’t on the list: dashboards and charts. They can help later. They don’t fix a request that was never written down.

• One front door. Tenants know exactly how to report a problem, and every other channel gets copied into the same list.
• One record per request. Each one gets a number, the date and time you first heard about it, and the unit.
• A clear urgency. Someone decides within hours whether it’s an emergency, urgent or routine.
• A person and a date. Every open request is assigned to a staff member or a vendor, with a target date.
• A closed loop. The tenant hears back when it’s logged, scheduled and done, and the record keeps the proof.

What to record in your tenant repair request log

A good record lets someone who wasn’t there pick up the request and finish it. It also answers what an owner, a tenant or a lawyer might ask months later. Use these fields, whatever tool you choose:

Two dates matter more than the rest: the day you first heard and the day it was fixed. The gap between them is your real response time. If a repair turns into a dispute, the time from notice to fix is what California’s repair rules look at.

Keep the history per unit, not only per request. Three clogged-drain requests in one unit in a year is a pattern worth a camera inspection, not a fourth snaking. The same records help at move-out, when California deposit deductions for repairs and cleaning usually need photos and receipts.

• Request number, and the date and time you first heard about it, even if it was a phone call.
• How it came in (text, call, voicemail, email, form or in person) and who took it.
• Property, unit and the spot in the unit, like “kitchen sink, under the cabinet.”
• Tenant name and the best way to reach them.
• The problem in the tenant’s own words, with their photos or a short video.
• Urgency (emergency, urgent or routine) and who decided it.
• Access notes: pets, where the key is, and how entry was agreed, with the date any entry notice went out. Keep alarm and lockbox codes out of any log vendors can see.
• Assigned to: a staff member or vendor, and the target date.
• Status: new, scheduled, waiting on parts, done or closed.
• What was done, the date it was fixed, after photos, and the cost or vendor invoice.
• The date the tenant confirmed it was fixed, or the date you followed up.

Getting every channel into one log

You can’t make every tenant use one channel. You can make sure every channel ends up in one log. Choose the front door first, then set a rule for everything else.

For example, a manager with 60 units across nine owners might send after-hours calls to an answering line. It logs every call, and pages the on-call tech only for the listed emergencies. Everything else waits for the morning review, already written down.

• Pick one front door. A web form or tenant portal works best, because it asks for the unit, the problem and photos every time. Put the link in the lease packet, in move-in emails and on a sticker with a QR code inside each unit. Our guide to choosing a client portal covers what to look for.
• Give calls and email a shared home. Use a maintenance phone number and email address that aren’t anyone’s personal ones, so requests don’t leave when a person does.
• Set a logging rule. Whoever hears about a request logs it the same day, calls and hallway chats included. Voicemails get logged at set times, like 8 am and 4 pm.
• Answer every request with its number. A short reply, like “Got it, request 214, we’ll call you by noon tomorrow,” tells the tenant it landed and stops repeat calls.
• Say what counts as an emergency, and give an after-hours number for those only.

Sort by urgency before you schedule anything

Urgency decides the order of work, so set the tiers before requests arrive. Write them down with examples, and share them with tenants, staff and vendors. The targets below are a starting point we suggest, not legal deadlines. The California section covers what the law says.

Your tenant instructions should also say who to call first when safety is at risk, like the gas company or 911. Then track two clocks for each request: time to first reply and time to fix. A tenant who hears back within the hour waits for a part more patiently than one who hears nothing for three days.

Different properties lean differently. Scattered single-family homes need more vendor trips, so routine work can be batched by area. A building with an on-site tech can clear routine requests in a weekly round. A commercial tenant, like a café, may count a broken walk-in cooler or front door as an emergency, because it stops their business.

• Emergency, act now: a gas smell, active flooding or a burst pipe, sewage backing up, no heat in freezing weather, an entry door that won’t lock. Call back within the hour and get someone moving.
• Urgent, within a day or two: no hot water, a stove or refrigerator that stopped working, the only toilet not flushing, a leak that’s contained for now.
• Routine, scheduled within a week: a dripping faucet, a sticking door, a broken cabinet hinge, one light fixture out.

Assign it, schedule entry and close the loop

Every open request needs a name next to it: your tech, a handyman or a vendor. Set the target date when you assign it, not when someone remembers. If it goes to an outside vendor, the work order, the visit and the invoice need tracking of their own. Our guide to vendor work orders covers that part.

Before anyone goes in, record how entry was agreed. That’s the written notice and the date it went out, or the tenant’s okay for a set day and time. Then tell the tenant three times: when the request is logged, when the visit is booked and when the work is done.

Close a request only when the record is complete. That means what was done, after photos, the cost, and the tenant’s confirmation or a dated follow-up. “Fixed” in a tech’s head isn’t fixed in the log.

Review the open list once a week, sorted by age. Anything past its target date gets a reason and a new date, written into the record.

Use the same list for checks you plan, not only repairs tenants report. For example, furnace filters, gutters and water heaters can each get a seasonal or yearly record per unit. A check that finds a small problem early can mean one less emergency call.

California: why the date on every request matters

This section is for California residential rentals. These rules cover homes and apartments, not commercial leases. It isn’t legal advice. Confirm your process with a landlord-tenant lawyer. Check your city too: local tenant laws can add rules, and cities and counties enforce their own housing and building codes.

Civil Code section 1941.1 says a rental is untenantable, meaning unfit to live in, if it substantially lacks certain basics. They include a weatherproof roof and walls with unbroken windows and doors, and working plumbing and gas. Hot and cold running water, heating and electrical lighting are on the list too. It also covers clean, pest-free areas the landlord controls, enough trash bins, and floors, stairs and railings in good repair.

For leases entered into, amended or extended on or after January 1, 2026, the list adds a working stove and refrigerator, with some exceptions. A recalled stove or refrigerator must be repaired or replaced within 30 days of the landlord getting notice of the recall.

Under Civil Code section 1942, a landlord has a reasonable time to fix that kind of problem after the tenant’s written or oral notice. If the landlord doesn’t, the tenant may repair it and deduct the cost from the rent, or move out. The repair can’t cost more than one month’s rent. A tenant can use this no more than twice in 12 months, and not for a problem they caused. A tenant who acts after the 30th day following notice is presumed to have waited a reasonable time. A shorter wait can count when the circumstances require it.

The Department of Real Estate’s landlord-tenant guide says the law usually treats 30 days as reasonable. A shorter time may be reasonable, though: one to two days for a broken furnace in very cold weather. The guide also notes the repair laws mention oral or written notice, not texts, email or fax. So it tells tenants to follow up a text or email with a letter.

For your records, that means the clock can start with a phone call to you or your manager, long before any letter arrives. Log the date you first heard, in any form, and keep the original text, email or voicemail with the record. Two more rules make the log worth keeping:

• Retaliation. Civil Code section 1942.5 protects a tenant who is current on rent and acts in good faith. That covers giving repair notice, complaining to you orally about the unit’s condition, or complaining to a government agency about it. The agency complaint counts once you know about it. For 180 days after, a landlord can’t retaliate by evicting, raising the rent or cutting services. The same section also bars retaliation for using legal rights, with no 180-day limit. Before you send a rent increase or a notice to end a tenancy, check the unit’s request history. If a complaint is there, talk to a lawyer first. Our guide to rent history per unit covers increase notices.
• Entry. To enter for repairs, Civil Code section 1954 calls for reasonable written notice with the date, approximate time and purpose. Entry should be during normal business hours, unless the tenant agrees otherwise at the time. Twenty-four hours is presumed reasonable, or six days if the notice is mailed. A tenant can agree orally to an entry for agreed repairs within one week. No notice is needed to respond to an emergency, or when the tenant is there and agrees at the time. Record which one applied.

References: California Legislative Information: Civil Code section 1941.1 (opens in a new tab) · California Legislative Information: Civil Code section 1942 (opens in a new tab) · California Department of Real Estate: Landlords’ and Tenants’ Rights Guide, Dealing With Problems (opens in a new tab) · California Legislative Information: Civil Code section 1942.5 (opens in a new tab) · California Legislative Information: Civil Code section 1954 (opens in a new tab)

Spreadsheet, app or custom system?

The right tool depends on how many people take requests and what else you need the software to do. Here’s how we’d choose:

Our comparison of custom and off-the-shelf software has a three-year cost check you can fill in. Whatever you pick, make sure you can export every request, with its dates and photos, to plain files you keep.

• A form and a spreadsheet, for a handful of units and one or two people logging. Google Forms can save every response into a linked Google Sheet, so each request becomes a row. Add a “date first heard” question, so a call logged the next day keeps its real date. One catch: a tenant must sign in to a Google Account to upload a photo. The weak spots are tenant updates, vendor tracking and anyone who forgets to log a call.
• A maintenance-only app, when rent and accounting already work and only requests are messy. These tools focus on a request link, work orders, vendor access and tenant updates. Check that tenants can report without creating an account. Check that vendors see only their own jobs, and that you can export every record.
• A property management app, when you also want rent collection, owner statements and leasing in one place. Buildium’s pricing page lists plans starting at $62 a month. Work order management and a resident portal are among the features. AppFolio’s page lists work order management on its Core plan, priced by quote, with a minimum spend and a 50-unit minimum. That’s what both pages said when we checked in October 2026. If one fits how you work, buy it.
• A custom system, when no app fits how your requests, vendors and owner reports work. It also fits when each owner wants their own view, or when you pay for a full suite to use one part of it.

References: Google Docs Editors Help: Choose where to save form responses (opens in a new tab) · Google Docs Editors Help: Choose a type of question for your form (opens in a new tab) · Buildium: Pricing (opens in a new tab) · AppFolio: Pricing (opens in a new tab)

How we build maintenance request tracking

We build custom business software for property managers and service businesses. For repairs, that usually means a request form or tenant portal, one log with the fields above, and assignment to staff or vendors. It includes photo uploads, email updates through Gmail or Outlook, and reports per owner and per unit. Vendor bills can go to QuickBooks Online, and visits to Google Calendar.

A focused fix, like one request form that feeds the spreadsheet or app you already use, is typically $750–$3,000 over 1–⁠2 weeks. One business system, like a full request and vendor system with owner reports, is typically $6,000–$18,000 over 6–⁠10 weeks. These are our prices as of October 4, 2026. Every launch includes 30 days of fixes. You own the code we write once it’s paid in full. Hosting runs on our account, and you can take it over after payment.

Our first call is free, and you get a fixed price in writing within 48 hours of it. Before any call, with us or an app vendor, write down:

• How many units and owners you manage, and who takes requests today.
• Every channel requests come through, and roughly how many arrive in a month.
• What happens after hours, and what you count as an emergency.
• The apps you use for rent, accounting and email, and what each costs a month.