Guide

How to write a weekly update people actually read

Updated November 2026 · by Jerry Liu, Dayflow's founder

Open with the one thing that changed this week, put any decision or help you need right under it, then list outcomes rather than effort, in the same order every week. Gather material with a two-minute daily note on paper or a template. If you work on a Mac and forget to log, Dayflow can keep an automatic record you check and edit before sending.

It is 4:40 on Friday. You open a blank doc called “Weekly update,” scroll back through your calendar and chat to remember what happened since Monday, and end up with eleven bullets that start with “Worked on,” “Synced with” and “Continued.” You send it. Nobody replies. On Tuesday your manager asks a question that bullet seven already answered.

It is easy to read that silence as “nobody cares.” Usually it means the update was hard to use. The important part was buried, there was no clear ask, and it read like a log of effort instead of news. That is fixable, and most of the fixes need a pen and a few minutes, not new software.

This guide covers why weekly updates go unread, six changes to try on your next one, and where an automatic record of your day can fit. Dayflow, a free Mac app, is our product. It appears in one section near the end, followed by a section on when it is the wrong pick.

The short version

Why does nobody read my weekly update?

Most unread updates share the same few problems, and none of them are about the writer being bad at their job.

They are written from memory at the worst moment. Friday afternoon is when you are most tired and the week is most blurred. What happened Thursday feels huge, and Monday’s real win has faded. So the update reflects what you remember, not what mattered.

They describe effort, not change. “Met with design,” “reviewed PRs,” “continued the migration” all prove you were busy. They do not tell the reader anything they can act on. Many people write this way because it feels safer: a long list of activity looks like a full week.

Readers skim the top and stop. An update competes with dozens of other messages. Many people read the first few lines in a preview pane and decide whether to open the rest. If your one real ask sits in paragraph four, it often never gets seen.

The ask is missing or vague. “Let me know if you have thoughts” asks for nothing. Readers who are not sure what you need from them usually do nothing.

Every week looks the same length. When a quiet week and a dramatic week both produce twelve bullets, readers learn that the length carries no signal and stop reading closely.

The fixes below address these one at a time. You do not need all of them at once. Pick one or two for your next update.

Start with the one thing that changed

What to do: Before writing anything else, finish this sentence: “The most important thing that changed this week is…” Make it the first line of your update. Not a greeting, not context, not a summary of your calendar.

If you cannot pick one, ask which item your main reader would be most annoyed to learn about later from someone else. That is usually the headline.

Illustration: A product designer’s update used to open with “Hi all, here’s what I worked on this week.” Their new first line reads: “The onboarding redesign is approved and goes to engineering Monday; the old flow will be removed in the next release.” Everything that follows is supporting detail.

How to tell after a week: Notice whether replies or follow-up questions reference your first line. If people respond to the headline, or stop asking you questions the update already answered, it is landing. If questions still come in about the details, the headline might be the wrong item, so try a different pick next time.

Put your asks where they cannot be missed

What to do: Right under the headline, add a short section titled “Needs from you” or “Decisions needed.” Each line names a person, the specific thing, and a date. If you need nothing this week, write “Nothing needed this week.” That line tells readers they can skim the rest without worry.

Keep asks concrete. “Thoughts on pricing?” becomes “Sam: approve option B for the pricing page by Wednesday, or tell me what’s blocking it.”

Illustration: A support lead had been ending updates with “Happy to discuss any of the above.” She moved two lines to the top: “Priya: sign off on the new refund macro by Tuesday. Leo: confirm whether weekend coverage continues in November.” Both were answered the same day, which had not happened with the closing line.

How to tell after a week: Count how many asks got a response before your next update. If asks at the top get answered and old asks at the bottom did not, you have your answer. If asks still go unanswered, check whether each one names a single person. Asks addressed to “the team” often belong to nobody.

Keep a two-minute note at the end of each day

What to do: At the end of each working day, write three short lines on paper or in a note: what moved, what got stuck, and anything you need from someone. Two minutes, no formatting. A sticky note on your monitor works. So does a notebook you keep by the keyboard. If you want structure, the daily work log template has the fields already laid out.

On Friday, read your five notes before writing. You will find the Monday win you would have forgotten, and the stuck items become your risks section almost by themselves.

This also helps when the bigger problem is that the whole week feels like a blur. Seeing where your day actually went, even roughly, makes it easier to write honestly about it. For more on the habit itself, see how to remember what you worked on.

Illustration: A developer kept a small notebook beside the laptop and wrote three lines each evening. Wednesday’s note said “Found why sync drops on slow networks - fix is small.” By Friday, the developer had shipped the fix and nearly forgotten finding the cause. The note turned it into the week’s headline: a long-standing bug explained and closed.

How to tell after a week: Compare how long the Friday write-up takes. If it drops from a long, frustrating session to a few minutes of editing, the notes are working. If you skipped most days, attach the note to something you already do at the end of the day, like closing your laptop or packing your bag, instead of relying on remembering.

Report outcomes, not effort

What to do: Go through each bullet in your draft and ask “so what?” Rewrite until the bullet states a result or a new state of the world. If a bullet cannot survive the question, cut it or fold it into a single “also in progress” line.

Useful rewrites follow a pattern:

Effort versionOutcome version
Worked on the billing migrationBilling migration is 3 of 5 steps done; step 4 starts Monday
Met with legal about the contractLegal approved the contract terms; signing scheduled for Thursday
Reviewed a lot of PRsUnblocked the mobile release by reviewing its remaining changes
Researched competitorsPicked two pricing models to test; doc linked

Illustration: A marketing manager had nine bullets, most starting with “worked on.” After the “so what” pass, four bullets remained, each describing something finished or decided, plus one line listing ongoing work. The update got shorter and said more.

How to tell after a week: Read last week’s update and this week’s side by side. If this one is shorter and a reader who missed every meeting could still explain what changed, it is working. If you feel the urge to add effort bullets back so you look busy, notice it. That urge is common, and an outcome-first update usually reads as more productive, not less.

Use the same shape every week

What to do: Pick a fixed order and stick to it. A shape that works for many people:

  1. Headline (one sentence)
  2. Needs from you
  3. Done this week
  4. Risks and delays
  5. Next week

When the order never changes, readers learn exactly where to look. Your manager reads sections 1 and 2. A teammate jumps to “Next week.” Nobody has to hunt. The weekly status report template gives you a ready version of this structure, and the guide on how to write a weekly status report goes into each section in more depth.

Let the length vary with the week. A quiet week might be four lines. Keeping the shape fixed and the length honest is what makes a long update stand out when it matters.

Illustration: An operations analyst switched from free-form paragraphs to the five sections above. In week one it felt rigid. By week three, a director said they had started reading the “Risks and delays” section first every Friday, because it was always in the same place.

How to tell after a week: After a week or two, notice whether people refer to specific sections (“saw your risk note”). That means they are navigating the update instead of skimming it. If a section is empty every single week, drop it.

Say bad news early and plainly

What to do: If something slipped, broke or is at risk, put it in the first few lines, not the last. Use three parts: what happened, the new expected date or impact, and what you are doing or need. Leave out long explanations; offer them if someone asks.

A delay a reader learns about from you, early, reads as someone with a handle on the work. A delay they discover elsewhere reads as a surprise, and surprises are what make managers start checking in more often.

Illustration: A project lead wrote: “Risk: the vendor API launch slipped two weeks, so our integration moves to the 24th. I’ve moved the help docs forward to fill the gap. Need: Ana to confirm the new date works for the partner announcement.” Three sentences, no apology paragraph, and the one person affected knew exactly what to do.

How to tell after a week: Watch for “why didn’t I hear about this?” moments. If they stop, the early-risk habit is working. If you notice yourself softening the wording (“slight timeline adjustment”), try rewriting it the way you would say it out loud to a colleague you trust. Plain usually wins.

A last quick check that ties all six together: before sending, ask a friend or teammate to read only the first three lines and tell you what they think you need from them. If they can say it back, send it.

Where seeing your actual day helps

The hardest part of a weekly update for many people is the raw material, not the writing. If daily notes keep slipping, an automatic record means you do not have to remember to start a timer or reconstruct the week from your calendar on Friday.

Dayflow is a Mac app that records your screen at one frame every 10 seconds and has AI write your day into a readable timeline. Recordings and the timeline are stored on your Mac. With local AI through Ollama or LM Studio, screenshot analysis stays on-device. You can instead use your own cloud provider, or Dayflow Pro, which processes selected screenshots off-device and, under the privacy policy, deletes them after processing.

For a weekly update, the useful part is export: you can export a date range as Markdown from Settings → Export, then turn it into a draft using the shape above. The Claude weekly report workflow shows one way to do that. AI summaries can miss or misinterpret work, so pick the headline and asks yourself and check everything before sharing.

Dayflow is $0 and MIT licensed, with an optional Pro plan at $20 a month, and needs macOS 14 or later. Details here come from Dayflow 2.2.0 documentation as reviewed on 2026-09-06. Dayflow publishes this article.

Where Dayflow is the wrong pick

The bottom line

People read weekly updates that are easy to use: one clear headline, asks they cannot miss, outcomes instead of effort, the same shape every week, and bad news stated early. None of that needs software. Start with the habit that makes Friday easier, a two-minute note at the end of each day, and try one structural change on your next update. If you work on a Mac and keep forgetting to write things down, an automatic record can supply the raw material, but the headline and the ask should always come from you.

Frequently asked questions

How long should a weekly update be?

Short enough that the top three lines carry the whole message and the rest is optional detail. For many people that means a headline sentence, any asks, and a handful of outcome bullets. If a reader could stop after the first screen and still know what changed and what you need, the length is fine. Size it to the news, so a quiet week gets a shorter update.

What should go at the top of a weekly status update?

One sentence on the most important thing that changed, followed by anything you need from the reader: a decision, an approval, or an unblock, with a name and a date. Put risks or delays there too if they affect someone else's plans. Everything else, including routine progress, can sit below. Readers often skim only the opening lines, so that is where your asks belong.

How do I write a weekly update when nothing much happened?

Say so in one line, then say what moved, even slightly, and what is in the way. A quiet week usually still contains a decision made, a question answered, or a blocker found, and those are worth stating. Do not pad with activity to look busy. A short, honest update keeps your credibility for the weeks when you need people to pay close attention.

Should a weekly update list what I worked on or what I finished?

Lead with what changed because of your work: what shipped, what got decided, what is now possible or no longer at risk. Ongoing work can appear as one line with where it stands and when the next milestone lands. Lists of meetings and tasks touched are useful in your own notes but rarely help a reader. Apply the 'so what' test to each bullet before it goes out.

How do I remember what I did all week?

Do not rely on Friday memory. Keep a running note through the week: two minutes at the end of each day writing what moved, what got stuck and anything you need from someone. Paper, a sticky note, or a daily work log template all work. By Friday you are editing a list instead of reconstructing the week from your calendar and chat history.

How do I report a delay in a weekly update without sounding bad?

State it early and plainly, with three parts: what slipped, the new expected date, and what you are doing about it or what you need. A delay that shows up first in your update reads as control. A delay discovered by someone else later reads as a surprise. Skip long explanations; offer them if asked. Plain language beats softened wording here.

What day should I send my weekly update?

Pick a day and time that matches when your readers plan, and keep it fixed. Many teams prefer Friday afternoon or Monday morning, but consistency matters more than the exact slot. A predictable update becomes something people expect and look for. If your main reader plans their week on Monday, a Friday update with clear asks gives them time to act.

Can AI write my weekly update for me?

AI can draft from material you give it, such as daily notes or an exported work record, and that can save time. It cannot know which result matters most to your reader or what you need from them. Treat any draft as raw material: pick the headline yourself, write the asks yourself, and check every claim. AI summaries can miss or misinterpret work, so verify before sending.

Is Dayflow a good tool for collecting a whole team's weekly updates?

No. Dayflow has no team reports. It records one person's own Mac screen and writes that person's timeline. For a team rollup, a shared document or your team's existing project tracker, where each person adds a short section in the same format, is the better choice. Dayflow can help an individual gather their own material, but it will not compile or distribute a team update.

Does Dayflow work on Windows or Linux?

No. Dayflow is Mac only and needs macOS 14 or later. If you work on Windows, Linux or mostly on a phone, a paper notebook, a simple daily note in any document, or a weekly work log template will give you the same raw material for your update. The habit of writing two minutes a day matters more than which tool holds the notes.

See where your day actually went

Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.

Download for MacOS macOS 14+ · MIT licensed · no account required