Free resource

Task follow-up and handoff templates for small teams

Most missed deadlines start with an unclear request or a follow-up nobody sent. These copy-and-paste templates cover the messages small teams write most: the task request, the follow-up, the handoff and the weekly update. Replace the brackets and send.

Start with a clear task request

A task needs one outcome, one owner and one date. Everything else is context that saves a back-and-forth later.

Task: [one clear outcome, starting with a verb]
Owner: [one person]
Due: [date and time zone]
Priority: [high / medium / low]
Why it matters: [one sentence of context]
Done when: [what the finished result looks like]
Where to look: [link or file]
Questions? Reply here before [date].

Follow-up messages that stay polite

Start light, get firmer only when needed, and make it easy to answer in a sentence.

Hi [name], quick check on [task]. It is due [date]. Is it on track, or is anything in the way? A one-line reply is plenty.

Hi [name], following up on [task], which was due [date]. Can you tell me by [time] whether it will be done today, or give me a new date? If priorities have changed, tell me and we will adjust.

Hi [name], I noticed [task] has not moved since [date]. Are you blocked on something? If so, tell me what you need and who could help, and I will try to clear it today.

Hi [lead], [task] was assigned to [name] on [date] and was due [date]. I have checked in twice and have not had a reply. It affects [what depends on it]. Can you help decide whether to reassign it or move the date?

Handoffs and weekly updates

Work changes hands, and status goes stale. Two short formats keep both under control.

Handing over: [project or task]
Status: [where it stands now]
Done so far: [list]
Still to do: [list, in order]
Risks or open questions: [list]
Where things are: [links, files, accounts]
Who to ask: [name, for what]
My last day on this: [date]

Weekly update, [date range]
Finished: [list]
In progress: [list, with owners]
Blocked: [list, with what is needed]
Due next week: [list, with dates]
Decisions needed: [list]

Tips for using the templates

• Send the follow-up where the request was made, so the context is one scroll away.
• Name a date and a time zone. “Soon” is not a deadline.
• Keep priority levels to three, and use them the same way every time.
• Ask a question that can be answered in one line.
• Save the versions that work for your team and reuse them.

If you would rather not chase by hand

AI Workflow Coordinator can turn requests from conversations into tasks with an owner, a priority and a deadline, and it can send Slack follow-ups on stalled high-priority tasks. New to the idea? Read the guide to AI task management.

Template questions

Are these templates free to use?

Yes. Copy and adapt them for your own team. A link back to this page is appreciated but not required.

When should I follow up on a task?

A sensible rule is to follow up once soon after the due date passes, again with a firm time to reply, and then involve whoever sets priorities. Adjust the timing to how urgent the work is.

Should I send follow-ups in public or in private?

A private message is usually the kinder first step. Move to a shared channel or to a lead when the work blocks other people.