A room for Teams passing work

Ready for the Next Person

Check that the next person has enough context to begin with confidence.

Why this might help

Passing work to someone else sounds simple. But it's easy to hand over a task and forget that the other person wasn't in the room when decisions were made. They don't know what you know yet. This check is about closing that gap before it becomes a problem. Think of it like leaving a clear note on the fridge instead of hoping someone figures out dinner. When the next person can start without hunting for answers, the whole team moves faster and feels less frustrated.

Does this feel familiar?

  • Someone picks up a task and immediately messages you with three questions you thought were obvious.
  • A teammate finishes their part but the next person waits a day before starting because they're not sure what 'done' looks like.
  • Files and links live in someone's inbox instead of with the task, so the new owner starts from scratch.
  • The person receiving the work quietly redoes decisions that were already made because no one told them.

Try this together

  1. Before you pass anything, write two sentences: what's done and what still needs to happen. That's your starting point.
  2. Attach the files and links directly to the task, not in a side chat. The next person shouldn't have to ask.
  3. Name one specific thing the next person should do first. 'Continue the report' is vague. 'Fill in section three using the notes in the brief' is clear.
  4. Flag anything that's still uncertain or waiting on someone else. Surprises slow people down more than problems do.
  5. Ask yourself: if I were brand new to this task, would I have enough to start? If the answer's no, add one more line.

Ready-To-Handoff Check

  1. Open the work item you're handing off and check that the Brief field has a short summary of where things stand right now.
  2. Make sure any files or links the next person will need are attached directly to the item, not sitting in a chat or email.
  3. Add a comment that names the next action clearly and tags the person who's picking it up.
  4. Check the schedule or context fields to confirm the timing is set so the next person can see when this fits into the week.
  5. Read the item once more as if you've never seen it before. If anything feels confusing, fix it before you hand it over.

Questions worth talking about

What's the one thing the next person absolutely needs to know that isn't written down anywhere yet?

Is there anything about this task that only makes sense because you were there when it started?

If the next person gets stuck in the first hour, what's the most likely reason?

A few common questions

How detailed does a handoff note really need to be?

Short is fine as long as it's complete. You need the current status, the next action, and any files or decisions the person can't find on their own. If you can read it back in thirty seconds and feel confident, it's probably enough. Don't write an essay. Write what matters.

What if the task is still changing when we hand it off?

That's actually when a clear note matters most. Write down what's settled and what's still in flux. Tell the next person which parts they can move on and which parts to hold. Uncertainty isn't a reason to skip the handoff. It's a reason to be more specific about what you do and don't know.

Can Tindlo help with this?

Yes, in a practical way. Tindlo lets you keep the brief, files, links, comments, and schedule all inside one work item. So when you hand something off, the next person can open it and see the context without asking you. It won't write the handoff for you, but it gives you one place to put everything that matters.

Keep the story close to the schedule

A date makes more sense when you can also see the reason, the owner, and the work around it. Tindlo brings those pieces together when a calendar alone isn't enough.

See how Tindlo works →

Where would you like to go next?