Write for the person taking over

Begin with the customer or project, the outcome required, and the current state. Include the latest confirmed agreement and its source, then separate any suggestion or unresolved point from that agreement.

Name the next action and its owner. If the recipient needs a decision from you, say exactly what decision is missing and when it is needed. A handoff is not complete merely because a note exists.

  1. State the job and desired result.
  2. Record what has been agreed, with a source or location.
  3. List open questions, risks, and the next action.
  4. Check access and ask the recipient to acknowledge the handoff.

An example: from estimate to job preparation

A fictional estimator hands a bathroom renovation to the person arranging materials. The estimate includes a vanity, but the customer's preferred finish is still undecided. The customer approved the labor price, while the supplier has not confirmed a delivery date.

The handoff identifies the approved estimate, marks the finish and delivery date as open, and asks the recipient to confirm both before ordering. It is complete when the recipient has the record, access, and responsibility for those questions, not when a draft order is created.

Separate an agreement from a possibility

Use plain labels such as "confirmed," "proposed," and "waiting for reply." Include the date and source for a change in scope, price, or timing. If two sources disagree, give the recipient both and say who will resolve the difference.

Before closing your part of the handoff, check whether the recipient can open the original documents. If access is unavailable, provide an approved alternative rather than assuming a link is sufficient.

Where Areinum fits

The pre-production demo gives an owner a general assistant and work areas for information such as files and tasks. A handoff can start with a request to organize the relevant facts and open questions from information available in that environment.

Ask about current team access and collaboration options for your handoff. You can also use the method with your existing tools.

Questions you may have

What is the minimum a handoff should contain?

Name the matter, the desired result, the current state, the next action, and the person responsible. Include where to find the source of any commitment the recipient must rely on.

When is a handoff complete?

When the intended recipient has the information and access needed to take responsibility, and has acknowledged the next step. A note saved in a folder is not enough if nobody knows it is there.

Should I include every message?

Usually the next person needs the decisions and exceptions first, with a route back to the original messages. Include the full history when the context is necessary to resolve a dispute or understand the work.

What if the previous owner is unavailable?

Mark the points you cannot verify, identify the best available source, and assign a person to resolve the gap. Do not convert a missing answer into an assumed commitment.

The demo uses sample business data and is in English. Access may need to be arranged.

Explore the demo