Practical note

Ryszard Cieplechowicz: the one-line handoff

A good handoff is not a long narrative. It lets the next person answer: what happened, who owns the next step, and when should it happen?

Write the line while the exchange is fresh. Keep the source record linked nearby rather than copying sensitive details into a shared note.

Pattern: Date and time | record or case ID | action taken | next action | owner | due date | where the source is kept.

Example with no real customer data: Sep 26, 2:00 PM | Case 104 | requested missing receipt | check ledger when receipt arrives | office lead | Sep 28 | shared case folder.

Three checks before handing it off

  1. Separate status from expectation. “Receipt requested” is not “receipt received.”
  2. Name the next owner. A date without an owner is easy to miss; an owner without a date leaves no useful clock.
  3. Point to the source. A case ID or filing location lets someone verify the record without relying on memory.

Make the format shorter if it needs to be used during a busy day. Do not put account numbers, medical details, or other private information in a shared shorthand. Use the appropriate restricted system for those details. For a fuller workflow, see the documentation checklist.

Why the next owner matters most

Most dropped tasks in a property office are not forgotten on purpose. A tenant call arrives, someone says they will look into it, and the record does not say who. A day later two people think the other has it. Ryszard Cieplechowicz, who worked in property administration for more than 17 years, found that adding a single named owner and one due date to the log line changed more than adding detail did.

A longer worked example

Oct 1, 9:10 AM | Case 211 | tenant reported slow drain, requested photo | review photo when received | maintenance coordinator | Oct 2 | shared case folder. The next morning the line is updated in place: Oct 2, 8:40 AM | Case 211 | photo received, vendor booked | confirm completion with tenant | office lead | Oct 4 | shared case folder. The record now shows what happened, what happens next and who is responsible, without a narrative. These examples contain no real customer data.

Where it breaks down

The method fails when the line is written once and never revisited, when the owner is a team instead of a person, or when the source link points to a folder nobody can open. It also fails when private details are pasted into the shorthand. Keep account numbers, medical information and similar details in the restricted system, and put only the case ID in the log.

A weekly review

Once a week, sort the log by due date and read only the lines whose date has passed. Each one either gets a new date, a new owner, or a closing note. That review takes a few minutes and is the step that makes the rest of the system trustworthy.