Repair requests stay tied to the property and unit from day one.

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 status
• Attach photos, documents, and notes
• Review activity history before closing the ticket