Repair costs and the unit's history
Every unit has a story: the aircon that was serviced four times, the tenant who reported the same leak twice, the turnover that took twelve days. The unit's history page is that story, from the record, with costs.
The page
Unit › History: one timeline. Tenancies with move-in and move-out. Turnovers with days. Tickets with category, contractor, cost, photos, reopened or not. Expenses recorded against the unit. Cleaning visits with tasks done. Stock used. Structural changes — rename, merge. Filter by kind; search by word ("aircon"). Costs total at the top for any period you choose.
Across units
Support › Reports › By unit: tickets and repair cost per unit, this year and last, with the building average. Sort by cost. The top three are usually one appliance each.
Three decisions
Repair or replace. An aircon with ₱14,000 of repairs in eighteen months against a ₱32,000 replacement is a replacement; the history makes that arithmetic visible instead of remembered. Pricing. A unit that costs ₱3,000 a month more than its neighbours to keep running should rent for more or be fixed properly. Budgeting. Last year's repair cost per unit, with the age of each appliance, is next year's maintenance budget — and the reserve contribution.
Appliances as assets
Record appliances as inventory assets placed in the unit, with purchase date and cost. Tickets can reference the asset; the asset's page then shows its own repair history and age. Replacing it retires the old asset and places the new one. The unit's history shows both.
Related
Describes the platform as it is today. Something out of date? Tell us. · help 0.12.3