Daily Work Recap: A Template for Useful Work Updates

For email, use the subject line Daily work recap: [date].

• What changed: [Outcome or decision]. [What is now different, available, or ready].
• What needs attention: [Open issue or blocker] affects [consequence]. I need [input or decision] from [person or team] by [real deadline, if there is one].
• What happens next: I will [next concrete action]. [Who needs to respond or what needs to happen first, if relevant].

For a standup, say what changed, where you need help, and what you'll do next. Keep the supporting links in your notes. If a heading is empty, skip it. Only add a deadline if there is one.

By evening, you may remember the last task you touched or the one that took the longest. A quick decision in a meeting may matter more than the hour spent preparing for it. A promise made on the way to the next call may never reach your task board.

Check your task list, including unfinished items. Look for a change of plan, a new dependency, or something you promised to follow up on.

A spoken request or change of plan may never reach those records. If you have a conversation recap, look for decisions, requests, and promises that affect the work. Check who agreed to do what and by when, then add those details to your notes.

Use those records to answer a few questions:

• What did I finish, and what moved forward?
• Did a decision change the plan or priorities?
• Where did I get stuck, and what would get the work moving?
• What did I promise, request, or agree to follow up on?
• What will I need to know when I pick this up tomorrow?

Keep these notes private. They can be messy: links, things you tried, people involved, and questions you haven't answered. Keep the order of events if it helps you check what happened.

You'll use this detail to write the update and return to the work later. Keep it in your notes so you can send a short recap without losing the context.

For yourself, write down where you stopped, why, and the question you were trying to answer. Leave enough context that you won't have to reopen every tab and conversation tomorrow.

For your manager, lead with progress and anything that changed the plan. Point out where you need a decision or a response. A list of meetings leaves them to work out what happened.

Your team needs the parts that affect their work: a decision, a dependency, or a promise they're counting on. If you're blocked, say what would help. Routine progress can be one line or left out.

For a client or a handoff, say what you delivered, what remains open, and what you need from them. Include internal detours only when they affect cost, scope, timing, or confidence in the result.

"The project moved from [previous state] to [current state]. [Decision, blocker, or dependency that matters next]."

For finished work, say what's now ready, approved, fixed, or sent. For work in progress, say which part moved forward and what's still uncertain. You don't need a finished task to have something worth reporting.

A blocker needs an explanation and an ask. "Waiting for feedback" becomes:

"Waiting for [input], which holds up [consequence]. I need [decision or action] by [time, if there is a real deadline]."

Mention meetings, emails, tickets, or hours when they help explain the change. Keep the rest in your notes.

Put each point in one place. If you've explained a decision under progress, you usually don't need to repeat it under blockers and next steps.

Find the work that never reached your task list

Pastok produces conversation recaps without a prompt. Open Activity to get the context back, then look for the details your update needs:

For a project discussed in several conversations, try this in Chat:

Across today's captured conversations about [project], what changed between the first discussion and the last? Separate agreed decisions from suggestions, and flag anything unclear.

This is useful when an early plan was revised later in the day. Check the answer against those conversations before treating the last suggestion as a decision.

Turn what you found into a manager update

Ask Chat to select the details for your reader and use the template above:

Draft a daily work recap for my manager from today's captured work conversations and spoken work notes. Use three headings: What changed, What needs attention, and What happens next. Include relevant decisions, blockers that need a response, commitments I made, and tomorrow's first move. Leave out routine activity and personal reflection. Don't invent owners or dates. Flag anything uncertain.

Before sharing the draft:

• Add work that wasn't recorded, using your project notes and messages.
• Confirm who owns each commitment and any deadline. Transcript speakers have anonymous IDs, so check who actually said what.
• For exact wording, open the full transcript on the web app at app.pastok.com.

Make the recap a regular part of your day

When the format works, ask Chat to save it as a Skill. A Skill can run on a schedule and put the result in a custom diary section:

Every workday at [time], draft my daily work recap from that day's captured work conversations and spoken work notes. Use the same three headings and manager-facing instructions. Put the result in a custom diary section.

The draft then has a place in the daily report you open, and you don't have to ask for the same format each evening. If it includes the wrong details, refine the instruction in Chat.

For changes that unfold over several days, use a weekly work recap to connect the daily records, track recurring problems, and prepare for the following week.

• How to create and schedule a Skill in Pastok

You can keep a separate private section for tomorrow's restart point. Ask for where you stopped, the question still open, and what to check first. Leave personal reflection there when preparing the manager version.

You review and send the finished update yourself. Pastok won't email your manager or post it to your team.