Property manager calls covering several units

The decision to make first

A property manager can mention several apartments in one conversation, making a single undifferentiated problem summary difficult to dispatch. Separate locations and issues within the request, then let the office decide whether they belong to one visit or several jobs.

What the handoff should contain

Capture building address, unit identifiers, the reported issue for each unit, manager callback and the contact responsible for access.

Suggested wording to approve

Example wording: “Let’s list the affected units separately so the office can plan the next step. I’m recording requests, not confirming how many visits are needed.”

Test the difficult case

Test a building with two reported leaks, different access contacts and a shared-area issue that has no unit number. If the caller cannot distinguish units, flag the ambiguity rather than inventing a room number or attaching every issue to one apartment.

Worked example

Fictional example: A manager mentions a kitchen issue in Unit A and a separate bathroom issue in Unit C. The summary needs two clearly labeled entries and their respective access contacts. If the manager later withdraws the Unit C request, that item must not remain in the list of work the office is asked to arrange.

Review it in operation

Review whether technicians receive a clear location for every reported issue and whether unrelated units were accidentally merged.

Check before you launch

• Separate locations and issues within the request, then let the office decide whether they belong to one visit or several jobs.
• Capture building address, unit identifiers, the reported issue for each unit, manager callback and the contact responsible for access.
• Test a building with two reported leaks, different access contacts and a shared-area issue that has no unit number.
• Review whether technicians receive a clear location for every reported issue and whether unrelated units were accidentally merged.

Related guides