Catching a maintenance cost early

Why it becomes an argument

The answer is almost never the amount. It is the sequence. A repair that was described when it happened, estimated before anyone was instructed and photographed while the damage was still there is a repair nobody argues about, at any price. The same repair, arriving as a single line at month end, is a question even when it was cheap.

So the work is not in explaining the cost afterwards. It is in leaving a trail while the thing is happening, when the trail costs almost nothing to leave. A photograph taken at the door on a Tuesday is free. The same photograph three weeks later does not exist.

If you run properties for somebody else, the argument is with them. If the properties are yours, it is with a month that has quietly come out worse than it should have, and you will have it with yourself in about six weeks. The remedy is identical either way.

Three moments decide it, all of them before the invoice arrives: what was recorded at the time, what was agreed before the money was committed, and what happened when the final figure did not match the estimate.

Capture it at the moment

A maintenance record is worth keeping only if it can be read by someone who was not there. That takes six things and about two minutes.

• What is wrong, in a sentence a non-specialist can picture. "Boiler showing F28, no hot water on either floor" beats "boiler fault".
• Which property, always, and which stay, where a guest caused it or a guest is sitting in it.
• When it was reported and by whom: the guest, the cleaner, a routine check.
• Photographs, taken before anything is touched. The error code, the stain, the broken hinge, the puddle.
• Who is doing the work, named, so a quote can be traced back to a person rather than to "the plumber".
• An estimate, before the work starts, even a rough one. The estimate is what makes every later step possible.

In HostHQ that record is the item itself: raised against the property, against the stay where one applies, with the contractor named, the estimate on it and the photographs attached to the item rather than filed somewhere nobody will look. Costs against the property and the stay.

Set a threshold, then hold it

The threshold is the figure above which you stop and ask before spending. Its job is not to control cost. It is to make the question of who decides automatic, so that it never gets answered differently on a Friday afternoon than it would have been on a Monday.

1. 1Below the threshold: do the work, record it with its evidence, and let it land in the month like any other cost.
2. 2Above the threshold: get the estimate agreed before anyone is instructed. The record is identical; only the order changes.
3. 3Safety, security or habitability: act now, whatever the figure, and tell whoever carries the cost the same day. A guest with no heating is not a budget decision.

Set it per property rather than across the portfolio. A four-bedroom house and a studio do not have the same ordinary repair, and one figure covering both will be wrong for one of them every time.

Get the agreement on the record

An approval given by text message is an approval you will be asked about later. Not because anyone is dishonest, but because six weeks on nobody remembers whether the figure was the quote or the ceiling.

What an approval has to carry

• The estimate as a figure, not as "a couple of hundred".
• What is being bought, in the same words the record already uses.
• A date, so that a delay in the work reads as a delay and not as a change of mind.
• A yes or a no from a named person, stored where the item is rather than in a phone.

How HostHQ holds it

An item raised with an estimate goes out for approval and waits there. Whoever carries the cost approves it, or rejects it with a reason, and the reason stays on the item. A rejected item can be revised and sent back as a new version, so the history reads as one negotiation rather than as three unrelated requests. Where the work was agreed outside the system, on a call or in person, the item can be raised as pre-approved instead, and the trail records that the gate was skipped and when.

Anything still waiting shows on the dashboard as a count of items needing a decision, which is the difference between a queue and a pile. What the dashboard puts in front of you.

When the invoice moves

The estimate and the final invoice will not always match. That is not the failure. Finding out at month end is the failure.

• Put a call-before-overrun condition in the instruction, every time, so the contractor knows the estimate is a limit and not an opening position.
• Re-agree anything material before the part goes in, not after the job is finished and the only alternative is a second visit.
• Record the actual figure against the estimate on the same item, so the variance is one number rather than two documents and a memory.
• Say what moved and why, in one sentence, at the moment you know rather than at the moment you are asked.

HostHQ writes the cost when the item is marked complete, at the actual figure, linked back to the item it came from and to the property and stay it belongs to. If the figure turns out to be wrong, reversing the completion removes the cost it created rather than leaving a second one beside it.

A repair well above what that property usually pays for that kind of work is flagged against the property’s own history rather than against a fixed limit. A £600 repair on a house that routinely spends that much stays quiet; the same figure on a studio that never has does not.

A worked example

One boiler, one flat, one March. The point of the table is not the amount. It is that every figure in it existed before the month ended, and that the one figure which changed was changed with a date on it.

The variance is £36.00 and it is not an argument, because it was re-agreed on 12 March, before the valve went in, against an estimate that was already on the record with a date attached. The same £36.00 discovered on 31 March is a phone call nobody enjoys.

Before the work starts