Airbnb Maintenance Tracking Software: What It Records and What a Small Host Actually Needs

Updated September 16, 2026

Airbnb maintenance tracking software records four things about a broken item — what the fault is, who reported it, who is fixing it, and whether the unit can still be sold tonight — and keeps that record open until somebody confirms the repair. Everything past those four fields is an extra, and at 3 listings most of the extras are sold to people with thirty.

I work on the product side at BnBGenius, so the boundary before the advice: we open cleaning and repair tasks after checkout from what a guest reports. We do not keep an asset register, a warranty log, a parts inventory or a scheduled-maintenance calendar, and we are not a channel manager, a calendar sync, a pricing tool or owner accounting. At 3 listings the honest answer is often a shared note, and I would rather show you where that stops working than sell past it.

What is Airbnb maintenance tracking software?

Four fields, each one there because of a specific failure that happens without it:

• The fault. What is happening, not “bathroom problem.” “The shower keeps dripping with both handles closed” sends a plumber to the valve. “Bathroom problem” sends him to the drain, and you pay for the visit anyway.
• Who reported it. Guest, cleaner, contractor or you. Without a source, nobody knows who to ask for the photo or the follow-up question a week later.
• Who is fixing it. A named person, not a category. With 3 people on a thread — host, cleaner, handyman — all 3 can assume one of the others called the plumber.
• Whether the unit can be sold tonight. Blocking or not. A loose drawer handle waits until Friday; a front door that will not lock does not.

Tobias hosts 3 units in Asheville with one cleaner and one local contractor, and he is the worked example for the rest of this page. On a Tuesday evening he has 2 open faults: a loose kitchen handle reported on Monday, and a ground-floor bedroom window in Unit B that will not latch, reported at 7:40 p.m. that night. Sorted the way a message thread sorts things, the handle comes first because it arrived first. Sorted by whether the unit can be sold, the latch comes first and the handle waits a week: Unit B’s Wednesday night is still on sale, and a ground-floor window that will not lock is not something you let a guest arrive to. That reordering is the whole product; the rest is storage.

BnBGenius covers one link in that chain. It answers guest messages around the clock on Airbnb and VRBO, and it opens a cleaning or repair task after checkout from what the guest reported. It does not hold the equipment history behind that task. If what you need is serial numbers, purchase dates, warranty expiry, spare-part counts or recurring inspections, that is a different product and I would not pretend otherwise.

Setup is a Chrome extension, about 5 minutes, no API keys and no password sharing — no PMS needed to install it, which is not the same as doing what a PMS does. The difference shows up the moment a repair needs the calendar changed: we do not sync calendars or block inventory across channels, and you do that by hand. Whether you need an Airbnb PMS and what a channel manager actually handles cover that side.

How does a repair get from a guest message to a fixed item?

If you have just started hosting and you are looking for software to manage maintenance requests, what you are missing is not a database — it is a chain with 6 steps, and 2 of them are where it breaks. Here is the chain for a dripping shower reported during a stay, with the next check-in at 4 p.m. the following day:

1. 9:10 p.m. The guest writes that the shower keeps dripping. Her sentence and her photo become the fault description, copied out of the thread.
2. 9:15 p.m. Marked non-blocking: the shower runs, nothing is flooding, the stay continues. That is an operational call, not a diagnosis.
3. 8:00 a.m. Sent to the plumber with the unit, the photo, the access window and the check-in time.
4. 11:30 a.m. He replaces the cartridge and sends the invoice.
5. 12:00 p.m. The cleaner runs the shower for 2 minutes, photographs the dry fixture and confirms the drip has stopped.
6. 12:05 p.m. Cost recorded, item closed — 14 hours 55 minutes after the report, with 3 hours 55 minutes to spare before the 4 p.m. check-in.

Those times are an example; steps 1 and 5 are not. They are where I watch this chain break. Step 1 is capture: the report never leaves the message thread, and once the thread moves on nobody can find which guest said what. Step 5 is confirmation: somebody says “looked at it,” and nothing records whether the symptom actually stopped. A tool that skips either one is a filing cabinet.

Money is a separate chain. BnBGenius does not do owner accounting and does not pay plumbers — a task can describe the work, but the invoice belongs in whatever you use for the books, and our guide to Airbnb accounting software covers that. Nor does the task diagnose the valve, choose the contractor or check the closing photo. Treat it as step 1 of 6, and the other 5 as yours.

Keep the reply and the repair apart, too. The guest needs an answer at 9:10 p.m.; the fault needs a record that survives until Wednesday lunchtime. Airbnb automated messaging and what to do about late-night messages handle the first half.

What should a maintenance record contain?

Ten fields, about 90 seconds to fill in — roughly 9 seconds a field. I hold it to 90 because a record that takes longer stops being filled in by the third fault, and the fault goes back to living in a message thread. That limit is mine, not a vendor benchmark. The test of the finished record: somebody who never read the conversation understands it in the same 90 seconds.

• Unit: the rentable unit, not the building.
• Date and time reported: this is what tells a new fault from the same fault again.
• Reporter: guest, cleaner, contractor, host.
• Description: the symptom, without guessing the cause.
• Photographs: one wide for location, one close for detail.
• Blocking: can the next guest use the unit as advertised, yes or no.
• Responsible person: who takes the next action.
• Access window: the hours available before the next arrival.
• Cost: estimate first, invoiced figure after.
• Closure evidence: a test, a photo, a receipt or a contractor note showing the symptom is gone.

Tobias’s window latch, filled in:

Manufacturer, model, serial number, warranty expiry, service interval and stocked parts are the fields a maintenance platform is built around. At 3 units they earn their place on maybe 2 items — the heat pump and the water heater, where a warranty date is worth money — and nowhere else. Filling in an asset form for a $6 remote battery is how a host quietly abandons the system in month two.

We do not hold any of those asset, warranty, inventory or recurring-service records. What we do is open the cleaning or repair task after checkout from what the guest said. If you want the wider stack, the vacation rental task management comparison lays out who holds what, and the Airbnb apps guide puts it next to the rest of a small host’s tools.

Which maintenance tools do small hosts actually use?

Four kinds of tool get used at this size: a shared task tool, a maintenance platform, turnover software, and a messaging layer that opens the task for you. They are sold on three different units — per user, per property, per unit — which is what makes the comparison awkward:

The unit of sale decides the bill. Tobias alone fits inside Asana’s free Personal plan; add the cleaner and the contractor and he is 1 seat over the 2-user cap. Put Tobias and the contractor in MaintainX Premium and that is 2 × $65 = $130 a month billed annually, whether he has 3 units or 1; the cleaner can stay on a requester account, which MaintainX does not charge for. Our $10 is per unit — the same home listed on Airbnb and VRBO counts once — so his 3 units are $30 and adding the cleaner changes nothing.

Turno is in the table because cleaners see the damage first, and its pricing runs the other way: free to the host who takes cleaners from the marketplace, $10 per property once he brings his own. Turno against BnBGenius, the alternatives for Airbnb cleaning and Breezeway against BnBGenius go through those trade-offs properly.

I pick by the missing step, not the feature count. Reports getting lost between the message and the task is the gap we close. Equipment history and recurring service is a gap we do not close. Cleaner scheduling and payment is a third category again, and buying the wrong one of the three is how hosts end up with 2 subscriptions and the same unrecorded drip.

How does maintenance tracking connect to your cleaner?

Your cleaner is the only person who sees every room, empty, on a schedule. With 3 units turning over twice a week, that is 6 inspections a week Tobias does not have to do himself — and most maintenance tools treat the cleaner as a recipient of tasks rather than the source of them.

What I ask a cleaner for is 3 things, because a 3-part report gets sent and a 10-part form does not:

1. One location photo, wide enough to identify the room and what is around the fault.
2. One detail photo of the crack, stain, leak, missing piece or error code.
3. One sentence of what happened when they tested it: “The dryer starts and stops after 4 minutes.”

Timestamps are what stop this becoming an argument about the cleaning fee. Checkout is 10:00 a.m.; the cleaner photographs the cracked dining chair at 11:00 a.m.; check-in is 4:00 p.m. That puts the damage in a 1-hour window belonging to a stay that has ended, which is a different conversation from a mark found on Friday that could have come from any of 3 guests. The report should also say which of 4 things it is — normal wear, guest damage, missing inventory, or work the last clean did not finish — because a photo shows a mark and nothing else. At 11:05 a.m. the chair is marked unusable and moved out; at 11:20 a.m. there is a photo of the room with 3 chairs instead of 4, which is what the next guest will actually see.

Our part of that is narrow and I will say where it ends: we open the cleaning or repair task after checkout. We have no SMS, no WhatsApp and no Facebook Messenger, so a cleaner does not get pinged by us on any of them — you still need a route that reaches the person holding the mop. We also have no cleaner marketplace and no damage-claim process. The Airbnb cleaning checklist is what I would hand a new cleaner, cleaning apps for hosts compares the tools that do dispatch, managing a cleaning team without text chains covers the reporting habit, and sharing your calendar with a cleaner is the schedule part — we do not sync calendars, so that one matters.

What does maintenance tracking cost?

At 3 units the software line runs from $0 to $130 a month, and which end you land on depends on whether you need a shared list, per-user work orders, turnover scheduling, or a task opened automatically from what a guest wrote.

Task creation sits inside Pro, not beside it as an add-on — the part I want to be exact about, because the voice product is the opposite. Voice Concierge is $7 per unit per month on top, so 3 units is 3 × $7 = $21 beyond the $30, and it includes 20 resolved calls a month and then $0.35 per call. Maintenance tasks do not need it. The free tier is the first 500 messages with every feature and no card.

A unit is one rentable home: the same apartment listed on Airbnb and on VRBO is 1 unit, not 2. And the bill is set by how many units you have, not by what they earn — 3 units is $30 in a $2,000 month and $30 in a $9,000 month, which is the one thing a percentage-based arrangement can never say.

The $0 note is not free either, it is just billed in attention: somebody reads every message, copies the fault out, assigns it and remembers to check it was closed. A year of Pro at 3 units is 3 × $10 × 12 = $360, which is 2.25 nights at Tobias’s $160 rate. If you have never lost a night to a fault nobody wrote down, the note is winning. Keep it. Our figures live on the pricing page; if the gap you are actually filling is wider than repairs, compare Airbnb automation software, channel managers for small hosts and voice concierge tools instead.

Do you need dedicated software at three listings?

Usually not. A shared note holds up while 1 person receives every report, no more than 3 faults are open at once, and that same person confirms each repair. Those thresholds are mine, from watching small hosts work rather than from any industry figure, and 3 listings with one cleaner sits comfortably inside all three.

The note stops working when any one of these turns up:

• A 4th open fault. Three items you can hold in your head. At 4 the order stops being obvious, and the oldest item is usually the one that quietly never closes.
• A 3rd person in the chain. Host, cleaner, contractor is already 3 handoffs. A co-host or a second cleaner makes 4, and “I assumed you called him” arrives with the fourth.
• A 2nd sales channel. The same unit on Airbnb and VRBO means a blocking fault needs 2 deliberate calendar actions. We do not do that for you.
• A 2nd report of the same fault. The duplicate is the signal: the first repair was never recorded, never done, or never verified, and you cannot tell which.
• 1 fault involving a lock, a smoke alarm or access. Safety items should not have to compete for attention with a chipped mug.

The same threshold answers the feature list. At 3 units the asset register is worth having for 2 appliances and nothing else, the parts inventory is a labelled shelf, and the scheduled-maintenance calendar is 4 recurring entries in the calendar you already own — filters, gutters, smoke alarms, boiler service. At 30 units those informal versions collapse, because 30 units is 10× the records across 30 addresses with several people touching them, and that is who the platforms are priced for.

That narrow case is also where we fit: a guest reported something, and it should become a task after checkout without you retyping it. We are the wrong tool for preventive scheduling, inventory, warranties, bookkeeping, direct bookings, pricing or calendar control across channels. If the question behind the search is bigger than repairs, what AI property management can and cannot do is the honest version of it, managing multiple listings remotely covers distance, and running an Airbnb with automation covers how much of this can run itself.

What breaks when maintenance is not tracked?

Three things, and they are cheap to count. The same fault gets reported twice. A unit stays on sale when it should have been blocked. And a guest writes in a review about something the host already knew.

Across 6 stays, Tobias gets 4 maintenance reports in his 3 Asheville units:

• Stay 1: slow bathroom drain.
• Stay 2: the same slow drain.
• Stay 3: loose kitchen handle.
• Stay 4: the ground-floor window latch in Unit B.

Counting messages, that is 4 problems. Counting faults, it is 3, because the drain appears twice: 1 duplicate in 4 reports, 25%. The duplicate is the expensive one, and not because of the plumbing. Nobody wrote down what was done after Stay 1, so after Stay 2 Tobias cannot say whether the plumber never came, came and failed, or was never called — and the only way to find out is to pay for a second visit to look.

The latch is where the money becomes visible. The contractor comes on Wednesday morning, finds he needs a part he does not carry, and the window is not secure until Thursday. Tobias takes the Wednesday night off sale at his $160 rate, so the fault costs $85 of repair plus $160 of night: $245, from one loose latch. That $245 only exists as a number because somebody wrote down which night was blocked and why. The blocking itself is manual — we do not close the calendar, sync availability or act as a channel manager — so a task marked “blocking” beside a calendar nobody touched is still a bookable night.

The review is the part I will not put a number on. Two different guests met the same drain, one after the other; whether either of them mentions it is not something tracking controls. What tracking gives you is the sequence — first report, action taken, test result, second report — so when it does appear in a review you know which of those steps was missing.

The drain has no figure attached to it at all, and that is the point: 4 messages sitting in 4 threads produce no arithmetic, while 3 records with a closure line each produce $245 and a duplicate rate you can do something about. We take one step off that chain — a guest’s message becoming a task after checkout — and the rest is a shared note, a spreadsheet or a maintenance platform, depending on which of the numbers above you have just recognised as yours.