Features

Everything stays tied to the maintenance record.

Browse the core workflow: repair requests, vendor updates, recurring maintenance, and unit history that stays useful when the issue comes back.

Start tracking maintenance Compare pricing

Core workflow

Browse the workflow in the order most teams experience it.

Start with repair requests, then see how vendor updates, recurring work, and unit history stay connected.

Maintenance Ledger ticket detail page with category, status, vendor assignment, attachments, and activity. — Ticket detail keeps triage, vendor updates, proof, and notes in one maintenance record.

Feature

Repair Request Tracking

Capture repair requests by property and unit so status, photos, vendor handoff, and costs stay in one record.

Maintenance Ledger gives each issue one working record so intake details, priority, assignment, attachments, and follow-up stay together.

Unit-linked requestsPhotos and invoicesVendor assignment

Capture the issue before context disappears

Requests often start as a text, a phone call, or a quick tenant photo. The ticket becomes the place where that loose thread turns into a unit-level record.

That means the problem statement, urgency, vendor assignment, notes, files, and completion details are visible in one place instead of spread across inboxes.

Keep follow-up attached to the work

Once a repair is triaged, the team can move it through status changes without losing the thread. Vendor updates, attachments, and proof stay connected to the same ticket.

When the issue comes back later, you can review the original work instead of reconstructing what happened from memory.

Track category, priority, and statusAttach photos, documents, and notesReview activity history before closing the ticket

Learn more

Mobile vendor work order page with status choices and job details. — Vendors can review the job and send progress updates from a secure shared page.

Vendors can review the job and send progress updates from a secure shared page.

Feature

Vendor Work Order Updates

Send secure work-order links to vendors so they can review the job and send updates without needing a full account.

Maintenance Ledger creates secure vendor work-order links that share the job details, attachments, and update form needed to keep work moving.

Secure vendor linksStatus updatesProof collection

Send the work order without creating extra account overhead

Vendors do not need a separate account to acknowledge the job, share status, or review the details you chose to share.

That keeps the handoff simple while your team still manages the full job from the dashboard, ticket detail, and unit history.

Collect updates that stay on the record

Accepted, on-the-way, working, and complete updates flow back into the record instead of living in texts or call notes.

For scheduled work that requires proof, the workflow can request completion evidence before the work is treated as done.

Vendor page stays limited to the target ticket or work orderAttachments remain tied to the same maintenance recordStatus updates feed the unit-level history instead of a side channel

Learn more

Scheduled work detail page with proof attachments, invoice snippets, and vendor status updates. — Scheduled work keeps the proof, invoice, and vendor timeline attached to the visit.

Feature

Recurring Maintenance Scheduling

Turn recurring upkeep into due work with unit context, vendor assignment, proof requirements, and completion history.

Schedules create concrete work instances so the next filter change, smoke alarm check, or seasonal inspection is visible before it slips.

Due-date queueProof requirementsVendor assignment

Move from recurring intent to assigned work

A recurring schedule becomes useful when it produces work that can be reviewed, assigned, completed, or skipped with a reason.

Maintenance Ledger keeps the schedule, the generated work, and the eventual proof attached to the same unit record.

See overdue work before it becomes a surprise

Due and overdue work stays visible in the dashboard and work-order views so routine upkeep does not depend on memory or a separate spreadsheet.

That gives your team a working queue for filters, seasonal inspections, safety checks, and other repeat jobs.

Track due dates with account-local time awarenessAssign vendors and proof requirements on scheduled workReview completion history at the schedule and unit level

Learn more

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.

Feature

Unit Maintenance History

Review repair tickets, recurring work, intake links, and attachments on the unit timeline before deciding what to do next.

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

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 togetherReview intake links and uploaded files in contextKeep repeat issues tied to the same unit instead of scattered messages

Learn more

Next step

See the workflow on your own maintenance queue.

Start with one property, one unit, and one real issue so the dashboard and unit history become useful immediately.

Create account