Maintenance Ledger
Open navigation menu
Sign inCreate account

Feature

Each unit gets its own maintenance record.

When leaks come back or turnover prep starts, the unit page shows the prior work, files, and shared request links already associated with that address.

Ticket historyWork historyShared file context
Start setupExplore features
Unit page timeline showing repair requests and scheduled work on one record.
Unit history gives repeat issues the last repair and the last routine visit in one view.

Review the history before you make the next call

The unit page gathers reactive tickets, recurring work, intake links, and files so the next person on your team can see the full maintenance story.

That helps when a repeated issue needs a different vendor, when a tenant references prior work, or when a property manager needs proof of what changed.

Keep the record attached to the address, not one person

Maintenance should not depend on who remembers the last repair. The unit-level record becomes the place where the team can review prior notes, attachments, and outcomes.

That is especially helpful across vendor turnover, staff changes, and repeat issues that span months.

  • See reactive and recurring work together
  • Review intake links and uploaded files in context
  • Keep repeat issues tied to the same unit instead of scattered messages

Keep exploring

See where people usually go next.

Repair requests

See how ticket detail feeds the long-term unit record.

Tenant requests

Bring tenant-submitted requests into the same unit history.

For property managers

Use unit records to keep portfolio-level maintenance organized.

Next step

Make repeat issues easier to understand

Track one ticket or one recurring schedule against a real unit and let the history start compounding from there.

Start setup