
Guides
Short-Term Rental Fault Log: What to Record and When to Repair or Replace
Short-term rental repair costs: how to log each fault (invoice, blocked nights, guest remedy, owner time), a worked dollar example, and a rule for repair versus replace.
What to take away
- For short-term rental repair work, record the invoice, blocked nights, any guest remedy, and owner time in the fault log. These are inputs for review, not a standardized cost estimate.
- Review the logged terms to see which ones matter in your operation; finding faults earlier can change some of them.
- Treat a second failure of the same item as a replacement review point. Replace when the item's logged cost over twelve months reaches its replacement cost, or when one repair quote exceeds half of it. The worked example below shows the sums.
- Track the share of faults found by inspection versus found by a guest. This shows how often faults are reaching guests before they reach your log.
Record the terms of a fault
For each fault, define four terms: I is the repair invoice, N is the value of the nights the property could not be sold, G is the value of any guest remedy, and A is the value of owner time spent handling the fault.
Total cost of one fault
I + N + G + A
I = invoice: labor, parts, call-out
N = blocked nights at achievable rate
G = guest refund, remedy or relocation
A = your own time, priced at market
Total cost is I plus N plus G plus A. This is a recordkeeping framework, not a valuation method: use actual recorded amounts where available and mark an amount unknown rather than inventing it.
Now notice which terms a cheaper vendor may move. A lower rate reduces I. A slower response can increase N and, if the guest is in the property, may affect G as well. That is a reason not to choose on rate alone for work that can stop a stay.
A sample log entry with dollar figures
The figures below are illustrative, not averages. A fault log entry holds one line per fault. For example, a water heater fails during a stay at a property that earns $180 a night:
- Property and itemUnit 2, water heater. Class one, because it affects water.
- Found byguest, on the second night.
- I (invoice)$450 for an out-of-hours repair.
- N (blocked nights)two nights at $180, or $360.
- G (guest remedy)one night refunded, $180.
- A (owner time)three hours at $30 an hour, $90.
- Total$450 + $360 + $180 + $90 = $1,080.
Eight months later the same heater fails again. The repair invoice is $300, one night is blocked ($180), no remedy is given, and owner time is two hours ($60). That second fault totals $540, and the two faults together total $1,620.
A rule for repair versus replace
Use two tests and write the thresholds down. These are suggested starting points, not industry rules, so adjust them to your own costs.
- Twelve-month test.Replace when the item's logged total over twelve months reaches its installed replacement cost.
- Half-price test.Replace when a single repair quote is more than half the replacement cost, because you are close to paying for a new one.
In the example, a new heater installed for $1,400 is cheaper than the $1,620 logged so far, so the first test says replace. Schedule the installation in a gap between stays so it blocks no nights.
A second failure of the same item prompts the review. It does not by itself decide the answer. A cheap part on an old item still falls under the tests above.
Typical faults, response targets and logging tools
Class one faults involve heating, water, locks or power. Common examples are a failed heating or cooling unit, a water heater, a leak, a keypad or smart lock and a tripped or dead circuit. Class two covers the rest: an appliance, a blind, wifi, a broken chair or a stained mattress.
Set a response target for each class and put it in your vendor agreements. As a starting point, class one gets a same-day response and class two gets a visit within three days. Those are suggested targets, not published standards. Vendor response time is the main lever on N, so record when each vendor arrived.
For the log itself, a spreadsheet with one row per fault is enough to start. Operations tools such as Breezeway, and property management systems such as Guesty and Hostaway, also track maintenance tasks. Check which fields each supports before you commit, since you need the four terms and the finder.
Read the scenarios as prompts
| Fault handling | I | N | G | Usual total |
|---|---|---|---|---|
| Found by inspection, fixed in a gap | Full | Zero | Zero | Lowest possible |
| Found by inspection, needs a part, dates blocked | Full | Some | Zero | Moderate |
| Found by guest, fixed inside the stay | Full, often out of hours | Zero | Some | Moderate to high |
| Found by guest, stay cannot continue | Full | Several | Large | Highest, by a distance |
| Second failure of the same item | Full again | Again | Again | Highest, and repeated |
Treat the table as a qualitative prompt, not a calculated comparison. It gives no dollar values for N or G and omits A from its totals. The sample entry above shows how the dollar amounts build up. Assess a repeat failure using its own logged history, not the table's ranking.
Fault handling cost by scenario
Scenario
- Found by inspection, fixed in a gap
- Full
- Found by inspection, needs part, dates blocked
- Full
- Found by guest, fixed inside stay
- Full, often out of hours
- Found by guest, stay cannot continue
- Full
- Second failure of the same item
- Full again
I
- Found by inspection, fixed in a gap
- Zero
- Found by inspection, needs part, dates blocked
- Some
- Found by guest, fixed inside stay
- Zero
- Found by guest, stay cannot continue
- Several
- Second failure of the same item
- Again
N
- Found by inspection, fixed in a gap
- Zero
- Found by inspection, needs part, dates blocked
- Zero
- Found by guest, fixed inside stay
- Some
- Found by guest, stay cannot continue
- Large
- Second failure of the same item
- Again
G
- Found by inspection, fixed in a gap
- Lowest possible
- Found by inspection, needs part, dates blocked
- Moderate
- Found by guest, fixed inside stay
- Moderate to high
- Found by guest, stay cannot continue
- Highest, by a distance
- Second failure of the same item
- Twice the highest
Usual total
- Found by inspection, fixed in a gap
- Found by inspection, needs part, dates blocked
- Found by guest, fixed inside stay
- Found by guest, stay cannot continue
- Second failure of the same item
Reviewing the terms in the log can show whether earlier detection or a change to repair decisions is worth more attention than negotiating on I.
Track who finds faults
Track, per property, the share of faults found by inspection versus found by a guest.
Inspection ratio predicts repair bill
- Faults found by inspectiontop two rows
- Faults found by guestbottom two rows
- Cost per fault when guests find themseveral times as much
Inspection-led records may resemble the first two scenarios, while guest-found faults may resemble later ones. Do not infer a fixed saving from that pattern; compare it with your own records.
When that ratio is unfavorable, review the inspection pass: do it separately from the clean, use a list in a fixed order, and include everything the listing promises. The process is covered in Short-Term Rental Maintenance: A Management Framework.
Log the ratio quarterly. It moves quickly when the inspection changes, which makes it one of the few operating numbers that gives fast feedback.
Review a second failure
A repeat failure is a review trigger, not proof that replacement will save money.
Replace on the second failure
Has this item failed twice in the same property?
Replace it, do not repair again
Repair and keep logging failures
Any item that fails twice in the same property goes to review. Add up the I, N, G, and A recorded for that item and compare the total with the replacement cost, using the two tests above.
The review avoids repeating a repair without reading the item's history. A fault log makes that pattern visible and gives you a record to use when deciding whether to repair or replace.
Building that log, and setting inspection intervals from it rather than from a template, is covered in our maintenance management framework.
Track blocked nights alongside invoices
Blocked nights are an operational impact to record. Whether they can be avoided depends on the fault and the response.
Four ways to shorten blocked nights
- Spending limit so someone can act without calling you
- Second vendor per trade, no single point of failure
- Small stock of parts that failed before
- Class one faults block dates immediately
Blocking a property as soon as an issue is found can seem to cost nights rather than save them. It may prevent additional booked nights from being affected, but the outcome depends on the fault and response. Compare blocked nights and any guest remedy in your own records.
For what to agree with vendors before the first emergency, see the repair vendor checklist for owners.
Other operating issues to track
Some operating issues sit outside the fault log. Track them separately rather than treating them as repair totals.
Three costs hiding outside the fault log
- Soft goodslinen and towels retired against a condition standard
- The listingany amenity described belongs on the inspection list
- Accessfailed locks are class one, vendor codes rarely withdrawn
Soft goods. Linen and towels wear gradually, they are replaced without being logged, and they never appear as a repair. Set a condition standard, retire against it, and count it.
The listing. An amenity that stopped working and was never fixed becomes a claim you cannot support and eventually a remedy given to a guest, which lands in G rather than in I. Anything described in the listing belongs on the inspection list.
For this log, class one means a failure involving heating, water, locks, or power that can disrupt a stay; class two means any other logged fault. A failed lock is class one. Access devices are the third cost area outside the fault log: codes handed to vendors and staff are rarely withdrawn, an exposure that is not a repair cost until it becomes a much larger one.
What not to cut
Two things look like savings and are not.
Keep class one preventive checks on the schedule: heating, water, locks, and power can affect a stay. Record faults and check outcomes rather than assuming a saved check will outweigh a repair.
And qualified work. Regulated trades carry licensing requirements that vary by jurisdiction, and the cost of getting that wrong is not a repair cost at all.
The same applies to safety obligations where your own people do the maintenance. The Occupational Safety and Health Administration's standard on the control of hazardous energy is one established framework. Whether it reaches your operation depends on the work and on how the people doing it are engaged. Establish both locally rather than saving money by assuming.
Keeping the numbers you need
All four terms come out of one record per fault: property, item, class, who found it, invoice (I), blocked-night value (N), remedy value (G), and owner time value (A).
That record settles disputes and feeds the maintenance plan. For business record-keeping, see the Internal Revenue Service guide Starting a Business and Keeping Records. Our overview of service-quality audits shows how the log fits with inspections.
Adding properties in a second market restarts the vendor bench and the parts stock rather than extending them. That is one reason repair cost per property can rise with geography, not just with property count, a trade discussed in the short-term rental expansion and market guide.
Common questions
Should I negotiate vendor rates?
Yes, but compare invoices and response outcomes in your own records. A lower invoice alone does not show the effect on blocked nights, guest remedies, or owner time.
Is a maintenance contract worth it?
It may be worth considering if it reliably improves response time in season. Compare the service with blocked nights and other recorded outcomes rather than the invoice alone.
How much should I hold in parts?
Only what has failed before in your own properties. A general parts inventory is money spent on faults you have never had.
What is the fastest saving available?
Separating the inspection from the clean can make faults easier to identify before a guest reports them. Track whether that changes your own results.
Do older properties always cost more?
Not necessarily. Compare repair logs by property before including an assumed age-related cost in your fee or rate.







