How do I hand work from one person to another without losing what was promised?

What goes in a work handover checklist

A handover usually happens when the person who knows the work is about to leave the room. They are on their way to a plane, a hospital bay, or another job. The person taking over has a notebook and not much time. What gets written down decides what survives.

A work handover checklist should cover these headings.

• Open work. What is partly done, and what is needed to finish it. Give each piece a verb: “Check the proof,” not “Proof stage.”
• Promises with dates. What you owe, what you are owed, and by when. The date turns a wish into a commitment.
• People who matter. Who is waiting, who has asked, who holds a decision. A customer who is waiting does not have to be found again.
• Decisions and reasons. What was agreed, and why that choice made sense. “We chose the cheaper supplier because the customer asked to cut cost” prevents a long debate.
• Where things stand. The state of each piece, in a line the next person can say back.

Keep each line plain. A handover is not a report. It is a map drawn for someone who has never walked the road. If the line needs a name, a date, or a figure, put it in. If it would not help a stranger act, leave it out.

A checklist is most useful when it describes the present moment, not the whole history.

Why handovers lose the promises

The promise was made on a phone call. The person who made it wrote a note in their own shorthand, tucked it into a file, and moved on. When the work changes hands, that note stays where it was. The new person opens the file and sees a task title: “Order samples.” A short title. No customer, no date, no reason.

The lost part is never the task but the promise inside it. Someone is waiting for those samples before they approve the rest. Someone else was told they would arrive before the holidays. The new person cannot see any of that in “Order samples,” so they treat it as a small errand.

Handovers fail when the writing is thinner than the conversation. The person who leaves knows the reasons, the tone, the names, the order of things. The person who arrives has a page of clipped nouns. So the questions start again: Why are we doing this? Who asked? By when? The work does not move forward. It pauses while the same ground is covered again.

The habit of a good handover is to write the whole thought, not the abbreviation. If the thought contains a person, a date, a decision, or a condition, put it on the page. That is the thread the next person needs.

Write it for a stranger

Write for a person who was not in the room, and use the checklist above as the page. A good handover checklist is boring. That is a compliment. It carries the facts without needing the author to explain them.

Let the record carry the thread

When the handover is written from memory, the memory has gaps. You remember the promise, but not the date. You remember a decision, but not why it was made. You remember the customer was keen, but not what they were keen about. Then the person taking over has to fill those gaps from guesswork.

The record holds the notes and promises you have recorded for a person or company in one place. The person taking over reads it instead of guessing, and each promise sits there with its date.

After a conversation you type a sentence about what happened, and Felesh drafts the note and the promise with its date for your yes.

So the record is not a pile of titles. It is a thread with the promises and their dates attached.

Picking it up on the first morning

The morning after a handover is usually spent guessing. The new person opens the work, sees a list, and wonders which item matters, which date has passed, and who is waiting on what. It takes time to learn the shape of it. A common move is to open the last file and hope the title explains itself.

On Felesh they can ask in their own words. “What is open?” “What have we promised?” “What are we waiting for?” Felesh answers from your own records.

Every promise on the record is kept with its date, so the new person can ask what was promised and by when, and the answer comes from the record.

When they spot a piece of work that is not in the record, they can add it directly. There is no approval step for tasks.

Holidays and sick days

The handover you plan is the easy kind. You have time, you know the date, you can write the checklist over a quiet afternoon. The handover you do not plan is different. A child is sick, or you wake up too ill to work, or the colleague has already left when you remember what you owed them.

When time is short, write the essentials from the checklist above and stop. A page of essentials beats a long document that never gets finished.

The test is simple. If you walked in tomorrow without the person who knows, could you act? Whatever makes that possible is the handover.

Hand over with the record

A good handover leaves the next person with a thread they can pull. Keep your notes and promises in one record, and whoever takes the work over starts from the thread, not from a guess.