Feature

Maintenance request software for property teams

Turn a reported problem into a tracked task with a status, an assignee, and a photo — so nothing gets lost in a group text three days later.

  • Every request becomes a task with a status, assignee, and due date
  • Photos attached at the moment something is reported
  • Completed work flows straight into the property's financial record

A status everyone can see

Most maintenance problems in property management are not maintenance problems — they are tracking problems. A tracked task with a status — reported, assigned, in progress, completed — replaces the group text that only shows the current state to whoever scrolls back far enough to find it.

A cost that shows up automatically

When a maintenance task is marked complete, its cost flows into the property's financial record and the next owner statement without anyone re-entering it from a receipt weeks later. That connection between the task and the ledger is what keeps statements accurate without extra manual work every month.

Built for teams, not one inbox

Assign a request to a specific vendor or staff member, not "someone will get to it." Photos travel with the task from the moment it is reported, so whoever picks it up has the context immediately, without a separate thread of forwarded messages to reconstruct.

A maintenance request that starts in a text message stays in a text message

The common failure mode is not that nobody fixes the leak — it is that the report of the leak lives in a phone that was not passed on when the tenant coordinator changed roles, or in a voicemail nobody transcribed. Whoever handles maintenance next has to reconstruct what was reported from scratch, and half the time the photo is gone.

A request logged directly as a task keeps its origin: who reported it, when, and what the property looked like at the time. Nothing has to be re-typed into a second system for it to count as tracked.

Vendors need less back-and-forth than a phone call gives them

A vendor arriving to a job with only "there's a leak somewhere in the kitchen" wastes the first ten minutes of a callout finding what a photo would have shown immediately. Attaching photos and a specific location to the request at the moment it is reported means a vendor can often triage before they even arrive.

Where the same vendor handles recurring work across several properties, having every past request on record — what was fixed, when, and at what cost — turns "has this happened here before" from a guess into a lookup.

Maintenance cost is a statement problem as much as a repair problem

An owner reading a statement with an unexplained "$340 repair" line has a reasonable question, and answering it after the fact means finding the receipt, the vendor, and the date from memory. Tying the cost to the maintenance task at the point of completion means the line on the owner statement already carries that context.

It also means nothing gets forgotten between the invoice arriving and the books closing for the period — a completed task with a cost attached posts once, rather than waiting on someone to remember to enter it before the statement goes out.

Recurring problems are visible instead of anecdotal

A single water heater failure is a repair. Three in one building over a year is a pattern worth flagging to an owner before the fourth one happens — but only if the history is somewhere searchable rather than scattered across old messages nobody thinks to check.

Because every request sits on the property's record permanently, spotting "this unit's HVAC has come up four times" is a matter of scrolling one list, not interviewing whoever happened to handle each call.

Common questions

Can tenants submit maintenance requests directly?

Yes, with photos attached, and the request becomes a tracked task immediately rather than sitting in an inbox waiting to be logged.

Does a completed repair show up on the owner statement automatically?

Yes. Marking a maintenance task complete with a cost attached posts that cost to the property's record, so it appears on the next statement without anyone re-entering it.

Can I assign a request to a specific vendor?

Yes. Requests are assigned to a named vendor or staff member with a due date, rather than sitting unassigned in a shared queue.

Is there a history of past maintenance per property?

Yes, every request stays on the property's record permanently, which makes recurring problems visible instead of something only one person remembers.

Do photos stay attached to the request?

Yes. Photos travel with the task from the moment it is reported, so whoever picks up the job has the full context without a forwarded message chain.

Run your properties on one system.

Bookings, owner statements, and maintenance connected, not stitched together.

Create your account