One issue creates three conversations
A tenant reports a leak. The property manager asks for a photograph, contacts a contractor, offers an appointment, and later needs confirmation that the repair was completed. Those steps may happen in separate channels. The tenant sees silence, the contractor sees only the latest message, and the manager holds the complete story in memory.
The workflow is not merely a list of tickets. It is a controlled exchange between people who should not all see the same information. Tenants need progress. Contractors need access details and scope. Managers need costs, responsibility, and internal notes.
Use one request with separate views
A focused first version could accept a request with property, category, description, photographs, and access preferences. The manager sets priority and assigns a contractor. Appointment, attendance, quote, work-started, and completion events build a dated timeline. The tenant receives selected updates while commercial and internal notes remain private.
- Make emergency guidance visible before ordinary submission.
- Record who owns the next action at every stage.
- Require completion evidence and a manager review before closure.
Begin with coordination, not automation
Automatic contractor selection, tenant compensation rules, and complex integrations can wait. The first useful version should reduce repeated status calls and prevent requests from losing an owner. It also needs clear privacy and access rules for occupied properties. Starting with one portfolio and a small contractor group will reveal the real status language. The goal is a dependable timeline, not a promise that software can decide how every repair should be handled.
Property managers
This guide describes a possible starting point, not a prebuilt product. A real scope would follow a discussion of your current process.