Maintenance history
The Maintenance History provides a complete view of all maintenance activities across your properties.
Accessing maintenance history
Full history
- Click Maintenance in the sidebar
- View all tickets across all properties
Per property
- Go to Properties → Select property
- View Maintenance section
- Shows tickets for that property only
Per unit/lease
- Go to Leases → Select lease
- View Maintenance tab
- Shows tickets for that unit
Maintenance list view
The Maintenance page is a plain, searchable/filterable list — there's no KPI summary cards, no charts, and no export button.
| Column | Description |
|---|---|
| Title | Brief description |
| Property/Unit | Location |
| Priority | Low, Medium, or High |
| Status | Open, In Progress, Resolved, or Closed |
There's no Ticket #, Category, Created/Updated column, and no cost tracking anywhere on a ticket.
Filtering and searching
- Status: filter pills for Open, In Progress, Resolved, Closed
- Search: free-text search box
- A property can be pre-filtered via a link from that property's page
There's no Priority filter, no Category filter (there's no category field at all), and no explicit date-range filter control.
Viewing ticket details
Click any ticket to see its full description, current status, and — if used — the email conversation thread with the tenant and any attached photos/receipts. There's no separate "resolution details" section, since resolving a ticket doesn't collect structured resolution data (see Ticket workflow).
Using history for evidence
Maintenance history is crucial for:
LTB hearings
- Shows you maintain properties
- Documents response to requests
- Proves reasonable landlord behavior
Insurance claims
- Documented property conditions
- Record of repairs made
- Timeline of events
Tax purposes
- Deductible repair costs
- Expense documentation
Best practices
- Review regularly - Check for open tickets weekly
- Close resolved tickets - Keep data accurate
- Add details - More information is better
- Use maintenance evidence bundles - For a portable record, generate one instead of exporting the list (see below)