Daily status update template: Needs you, Since last briefing

A daily status update that a product leader will actually read has three sections, in this order: Needs you, Since last briefing, and Worth a look. Every line names its product and links its evidence. The order matters because the first section is the only one that requires you to act, so it goes where you will not skip it. Below is the template to copy, the rules for each section, a filled example, and the mistakes that make these updates useless.

This is the format Biddle sends each weekday morning, written so a team can produce it by hand.

What does a daily status update template for a product leader look like?

Here is the template. It works pasted into a Slack message, a pinned doc or an email. Replace the square brackets.

MORNING BRIEFING, [weekday, date]
Covers: [time of last briefing] to now
 
NEEDS YOU
1. [Product]: [the decision or action, one sentence].
   Why now: [what happens if it waits].
   Options: [A] / [B]. Leaning: [A or none].
   Evidence: [link to PR, thread or commit]
 
(No items? Write: Nothing needs you today.)
 
SINCE LAST BRIEFING
- [Product]: [what changed, in outcome terms, one line]. [link]
- [Product]: [what changed]. [link]
 
(Group by product. Maximum one line each.)
 
WORTH A LOOK
- [Product]: [something not urgent that a sharp leader would want to know]. Why: [one clause]. [link]
 
(Nothing qualifies? Leave this section out.)

The thesis behind the format is simple. AI-native teams create context faster than a person can sync, manage or remember it. Agents open PRs all day, decisions land in Slack threads, and plans shift mid-week. A status ritual built for human-speed change (everyone says what they did) cannot keep up. A briefing helps by doing the filtering for you: it tells you what needs a decision, then what changed, then what is merely interesting.

What are the rules for each section?

The table below is the part worth keeping. Each section has an entry test, a window and an empty state. Without these, the update decays into a list of everything that happened.

Needs you

This is the section that earns the update its place in your morning. Each item should be answerable in a minute: what is being asked, why it cannot wait, and what the options are. If you have to open three tabs to understand the item, the author did not finish the job.

Keep it short. If more than three or four things need you every day, either the team is routing too much through you or the section is absorbing things that belong lower down. Both are worth knowing.

Since last briefing

Write outcomes, not activity. "Checkout: refund flow merged, behind a flag" is an outcome. "Checkout: 6 PRs merged" is a count that tells you nothing. Group by product so you can skip what you do not own, and cap each line at one sentence.

The window is the previous briefing, not "yesterday". On a Monday, the window covers the weekend. That sounds obvious, but it is the first thing people get wrong when they write it by hand.

Worth a look

This section is where judgment shows. It holds things that are not decisions yet but might become one: a thread where two people are converging on an approach you have not seen, a workstream that has gone quiet, a change that touches an area you care about. If you cannot say why it is here in a clause, it does not belong. Silence beats a weak item.

What does a filled example look like?

An illustration with sample data: the products, PR numbers and decisions below are invented to show the format.

MORNING BRIEFING, Monday, March 9
Covers: Friday 9:00 to now
 
NEEDS YOU
1. Checkout: Choose whether refunds are issued instantly or after the
   payment provider confirms.
   Why now: the refund PR is approved and waiting on this answer.
   Options: instant (faster, risk of mismatch) / after confirmation (slower, safe).
   Leaning: after confirmation, per Thursday's thread.
   Evidence: PR #412, thread in #checkout
 
2. Onboarding: The merged change in PR #431 skips the email step, which
   the team agreed on March 2 to keep. Confirm it is intentional.
   Evidence: PR #431, decision thread March 2
 
SINCE LAST BRIEFING
- Checkout: Refund flow merged behind a flag. PR #409
- Onboarding: Welcome screen redesign shipped to staging. PR #428
- Search: Index rebuild reverted after a latency regression. PR #433
- Billing: No changes.
 
WORTH A LOOK
- Search: The reverted rebuild is the second attempt this month.
  Why: it may need a plan, not another try. Thread in #search

Three things to notice. Item 2 in Needs you is a conflict between a merge and an earlier decision, which is the kind of thing that disappears if nobody writes it down (we cover that in plan drift). The Since last briefing lines are outcomes, one line each. And Billing gets an explicit "No changes", so the absence of news reads as information rather than as a missed update.

What mistakes make a daily status update useless?

• Writing an activity list. "12 PRs merged, 4 reviews, 2 deploys" describes motion, not state. On a busy product it is also huge. One Liouville product, for example, had 197 merged PRs in the 14 days to October 3, 2026. Nobody can absorb that as a list, and a count is not a decision.
• Leaving out links. A line without evidence forces the reader to trust it or go hunting. Every line should point to the PR, commit or thread it came from.
• Marking everything urgent. If every item is in Needs you, the section stops meaning anything. Be strict: only things that need you, and only you.
• Reordering by recency. Putting the latest event first buries the decision under news. Keep the order fixed so the reader knows where to look.
• Padding Worth a look. A section that always has three items is a section people stop reading. Let it be empty.
• Skipping the empty states. "Nothing needs you today" is useful. A missing section makes people wonder whether it was forgotten.
• Ignoring corrections. If the update gets something wrong, the author should hear about it and stop repeating it. In a hand-written version, ask readers to reply in the thread when something is off.

If your team still runs a live standup alongside this, see why the daily standup fails an AI-native team for what to cut.

Should you write it by hand or automate it?

Start by hand for a week. It teaches you what qualifies for Needs you on your team, and that judgment is the real work. Budget the time honestly, though: reading PRs, threads and reviews to write ten good lines usually takes much longer than the lines themselves, and it has to happen every weekday morning, before you have context of your own.

That gap is what Biddle, an AI chief of staff for product teams, is for. It sends this three-section briefing to a leader's Slack DM every weekday, reading GitHub and Slack (those are the only sources today; Linear and Notion are coming, not integrated). Each line links its evidence, and a teammate can reply "Correction:" in the briefing thread so later briefings treat it as a standing instruction. Biddle is in early access and runs every weekday for Liouville's own team. Member notes are in shadow: written and reviewed, not sent. Drift detection is still being built: Biddle is learning to flag a merged PR that contradicts a decision. You can see how the pieces fit in how it works. If a tool reading Slack gives you pause, who sees what in AI answers in Slack spells out the visibility rule. To judge the format for yourself, see a sample daily status update in this format.

Common questions

Can this replace a standup?

For a leader's awareness of what changed and what needs them, often yes. It does not replace a conversation when the team needs to talk something through, so keep a meeting for that.

How long should the update be?

Short enough to read in a couple of minutes. If Since last briefing runs past a screen, group more tightly or drop lines that did not change a product's state.

Who should write it if there is no leader to receive it?

Write it for whoever owns the decisions that week. The format works the same for a team channel, but Needs you should name a person, or it will go unanswered.

Read next

• The decision was made in a thread nobody can find: a decision log template for Slack: a companion template for the decisions your Needs you section keeps surfacing.
• Why the daily standup fails an AI-native team: why the briefing replaces the ritual rather than adding to it.
• Your GitHub channel posts every event and nobody reads it: notifications, digests and briefings compared.