Write a useful handoff note for a shared task

Published · Updated · Sources checked 2026-11-06

Describe what exists, one next action, where to find the materials and what remains undecided. Includes a fictional shared-work handoff example.

A shared handoff should answer five practical questions: what currently exists, what the next person should do first, where the relevant material is, what is still undecided, and how to ask a question. This guide turns those answers into a short note using Lumahari’s public task fields.

A concrete worked example

Imagine Priya is leaving a website content update to Mateo. Priya has drafted the opening section, but the final headline and the location of two source images still need attention.

Priya writes this handoff note:

What exists: A draft for the “Using saved research in a team guide” page is ready. The opening section is written. The source images are identified, but the second image still needs a final selection.

Next action: Review the three draft headlines, choose one, and replace the temporary headline in the draft. Keep the selection brief and plain.

Where to find it: The working draft is in the shared project folder under “Website drafts / May updates.” The three headlines are in the handoff section of the project brief. Candidate images are in the same brief under “Image options.”

Not decided: The final headline has not been chosen. It is also undecided whether the second image should be cropped. Priya’s rough preference is the wide image, but Mateo should check how it looks beside the first image before using it.

Question: If Mateo is unsure about the image crop, leave a question beside the image option in the project brief: “Should this stay wide, or should I crop the empty right side?”

This example gives Mateo a defined first move without pretending the entire task is settled. It also separates completed work from open choices, so he does not have to infer either from the draft.

Turn the handoff into task fields

A practical next action belongs in The smallest action you could take. Focus on this step is the button that displays it. For this example, Priya could enter:

Choose one of the three draft headlines, then replace the temporary headline in the website draft.

The activity field can state what the task concerns:

Select the final headline and confirm the second image for the team guide.

When Mateo completes the headline selection, he can use I did this step to acknowledge that specific piece of work. The app does not reveal a next item automatically. Mateo must choose and enter another action manually if he wants to continue.

If choosing among the headlines feels awkward to begin, Priya can use the optional 2-, 5-, or 10-minute timer as a small time box for the first review. The timer has start, pause, and reset controls, with no sound or notifications. This is optional: the note itself should still make the first action clear without requiring a timer.

Record temporary thoughts without hiding the next step

Sometimes the person handing off a task has an observation that is useful but not yet a confirmed decision. Priya might temporarily park this note:

Image B may have too much empty space on the right; compare it with Image C before cropping.

Temporary parking notes are useful for such unresolved details. Priya should still keep the main next action in the task fields, so the parked thought does not replace the actual instruction. Before clearing the parking area, the interface asks for confirmation; Mateo can keep the relevant question in the project brief before anything is removed.

Keep the handoff usable

A strong shared-task handoff is specific enough for someone else to start without a meeting. Replace broad statements such as “draft mostly done” with named materials, locations, and the next visible change. Describe where files or materials live in plain language, without relying on platform-specific commands.

Use short sections for:

Do not bury uncertainty. “The headline is nearly finished” is less useful than “Choose one of the three options and replace the temporary headline.” Likewise, do not present a preference as a decision unless it has actually been confirmed.

Before handing it over

Priya should reread the note from Mateo’s perspective: Can he identify the next action in seconds? Can he find the relevant materials? Does he know which choices are still open? Does he know where to ask a question? If any answer is no, revise that part before moving on.

Entries clear on refresh or leaving, so Priya should copy any lasting handoff note into the shared project brief. The task starter keeps entries only in the current page’s memory. Refreshing or leaving clears them. She should also copy the final headline and agreed crop instruction into the brief rather than relying on a temporary note.

A final handoff might read:

Start with the headline choice. The draft and source options are in “Website drafts / May updates.” The headline decision and image crop remain open. Record questions in the project brief. Once the headline is replaced and the second image is confirmed, mark that step complete.

Using the task fields

Enter one activity and one smallest action, up to 200 characters each, then select Focus on this step. Both inputs are required. Park a thought holds up to 3,000 characters. Clear thoughts removes that whole area after confirmation. Choose a different step lets you edit the current instruction; there is no task history.

The task starter keeps entries only in the current page’s memory. Refreshing or leaving clears them. Copy lasting notes elsewhere before leaving.

For a related next step, see how to write a simple three-item meeting agenda and how to start an email reply: a two-sentence draft. Find more examples in the task initiation guide hub.

Lumahari task starter

Sources

General information, not a diagnosis or personalized treatment advice.