Make the handoff easy to understand

For a routine building-service issue, identify the property and precise location, describe what was observed and when, then use the locally approved channel. This page helps prepare context; it does not establish an emergency response route or replace an approved procedure.

If the issue may be urgent, safety-critical, regulated, or sensitive, follow the applicable approved local process and involve the trained role designated by that process.

Prepare a routine handoff

Share observations and ownership context; leave diagnosis and authorization to the responsible roles.

  1. 1

    Identify the property and location

    Name the building or community and the specific area, such as the east lobby entrance or a named shared room.

  2. 2

    Describe what was observed

    State the visible or reported behavior in plain language and include when it happened or whether it was seen more than once.

  3. 3

    Check the service family and local owner

    Use the service-responsibility guidance and approved local ownership information. If ownership is unclear, ask the local property-management role to identify the correct route.

  4. 4

    Pass along relevant context

    Include prior handoff references or known observations that help the receiving role understand the issue. Do not add unverified causes or unnecessary personal details.

  5. 5

    Confirm the handoff reached the right role

    Use the established local channel to verify that the responsible receiving role has the information. This site is not a submission or tracking system.

Worked example: a recurring lobby door fault

A fictional coordination example, not a repair instruction or service-level commitment.

A modern office building entrance with outdoor steps
Example

Useful handoff context

A Northstar colleague reports that the west entrance door at Harbor Point, Building 2, did not close fully on three observations: Monday at 08:10, Tuesday at 08:25, and Wednesday at 08:05. A prior routine maintenance note from Tuesday is mentioned so the receiving team can check whether it is relevant.

  • Property and location: Harbor Point, Building 2, west entrance.
  • Observed behavior and times: door did not close fully on three morning observations.
  • Context: prior Tuesday maintenance note; local owner determines whether it relates.
Coordination

Why this is a stronger handoff

The report gives a location, observations, and relevant history without claiming a technical cause, repair, approval, or safety outcome. The sender uses Northstar's locally approved channel, and the receiving role determines the next step under its applicable process.

  • It distinguishes observed facts from what is not yet known.
  • It gives the receiving role context to assess ownership.
  • It does not create a status or promise an outcome.