A tenant messages that the geyser's broken. Someone calls an electrician. It gets fixed, eventually. Then the whole thing evaporates — no record of what broke, what it cost, or whether it actually got resolved versus just quieted down. Here's what it looks like when that trail doesn't disappear.
Quick answer (for the impatient)
- A maintenance issue becomes a real request record — created, assigned, and tracked through to completion.
- The room's status reflects reality automatically — flagged as under maintenance when a request opens, restored only once every open issue on that room is actually resolved.
- Cost has a place to live — parts and labor logged against the specific job, not lost in a vague monthly "repairs" total.
What actually happens today
The informal version of PG maintenance — a WhatsApp message, a phone call to a known electrician or plumber, a verbal "it's done" — works, but it leaves nothing behind. Ask a PG owner three months later how much they spent on repairs that quarter, or how many issues came up in a specific room, and the honest answer is usually a guess.
Nothing about that informal path is dishonest — it's just unrecorded, which means it can't be reviewed, budgeted against, or pointed to later.
Cost has a place to live too
Each maintenance request tracks parts cost and labor cost separately, rolling up into a total cost against that specific job — not a lump "maintenance expense" figure with no way to trace what it was actually for. Requests move through a real lifecycle too: created, assigned, and completed, so "is this actually fixed" has an answer beyond someone's memory.
The room itself reflects this automatically — creating a request flips that room's status to under-maintenance, and it only reverts once every open request on that room is genuinely resolved, not the moment the first one closes if a second issue is still pending.
Where AXOIX is honest about its limits
- No structured vendor/contractor records. You log what something cost; the electrician or plumber themselves isn't tracked as a formal vendor entity with their own history.
- A tenant complaint doesn't automatically become a maintenance request. If a tenant reports an issue through the messaging side of AXOIX, that's a separate record today — someone still has to open the maintenance request themselves.
FAQ
Does the system track parts and labor cost separately?
Yes — both are logged individually and rolled up into a total per job.
Does a room's status update automatically when something breaks?
Yes — the room flips to under-maintenance on request creation and only reverts once all open requests on it are resolved.
Can I see maintenance history for a specific room?
Yes — every request is a persistent record, not a one-off note.
The bottom line
Maintenance always gets handled one way or another — a broken geyser doesn't stay broken for long. What usually doesn't survive is the record of it: what it cost, whether it's really fixed, whether the same room keeps breaking. Turning that into a tracked request instead of a phone call is what makes "how much did repairs actually cost this year" an answerable question instead of a guess.
See how room turnover is tracked, the full PG system overview, or pricing.
Turn repairs into a record, not a memory. Start free →
Comments