The repair was assigned and the contractor attended, but the intercom did not provide access. No work was completed. Replacing that appointment with a new date would lose the explanation for why the resident is waiting again.
We retained that interruption in our residential maintenance project. The resident timeline and manager workspace describe the same repair, with different detail for the people using them.
Preserve what the resident reported
The sample request describes water collecting around the base of a kitchen mixer after use. It includes a photograph. The property team reviews the report and assigns a contractor to inspect the base and determine the repair needed.
Those are separate contributions. The resident supplies an observation; the contractor assesses the work. Rewriting the original request as a diagnosis would make it harder to distinguish what was reported from what was established later.
Explain what must change for the return visit
The timeline records the failed access attempt and states that no work was completed. The later entry confirms a return visit: the resident will be home, and the manager has passed on the intercom instructions.
The earlier event explains the new arrangement. Without it, another appointment looks like a routine update rather than the response to a specific problem.
Keep the missed visit in the repair history
The resident view puts the forthcoming date, time window, contractor and access arrangement together. The person can understand what will happen at home without reading the manager's whole queue.
Give the manager a different view of the same work
The manager workspace includes seven requests across two properties. Five are open, one needs review and another is awaiting resident access confirmation. Each row pairs status with a contractor or next step.
A window-latch request awaiting assignment needs a different response from a dishwasher request waiting on the resident. Both are open, but the manager's task is different. That is why the queue shows more than a coloured status label.
Selecting the mixer-tap request opens its handover details, including the return-visit context and confirmed access. The manager does not need to copy the history into a separate note to explain the situation to the contractor.
Keep the repair history
- 01ReportPreserve the resident's description.
- 02AttendConnect assignment and access arrangements.
- 03Follow upRecord the outcome and confirmed next action.
Make waiting an actionable state
“Awaiting resident” needs the particular question being asked. “Awaiting part” needs a reference or review point. Otherwise a label records delay without helping anyone manage it.
Reminders should follow those responsibilities. Once access is confirmed, another request for access is unhelpful. If the visit outcome is missing, follow up with the person responsible for recording it. Our automation examples guide discusses recurring follow-up; the portal's record supplies the context for those rules.
Do not close the repair merely because a visit occurred
An attended visit may identify further work. Agree what the service means by resolved and who can record it. The project leaves repair and closure after the return visit rather than assuming the appointment will resolve the issue.
A related defects and warranty workspace may need different closure rules. Sharing a property theme does not make two processes identical.
Give the manager the next action for each request
Our portal features guide explains how to choose the first customer-facing scope. For client portal development, a useful starting scenario is a repair that did not go to plan. Follow it through the resident view, manager queue and contractor handover. The next person should be able to understand the current arrangement and why it exists.
Sources and calculation notes
The repair example follows request CG–1048 in the resident timeline and manager workspace. The manager queue has seven authored requests, including five open requests. The failed access visit and later confirmation are retained in the sample history.
- Our residential property maintenance project. The project page includes the design account, delivered scope and screenshots discussed in this article.
- Our property development defects and warranty project. The project page includes the design account, delivered scope and screenshots discussed in this article.
External references checked on 31 October 2026.