How to Write Weekly Updates That Get You Promoted

Here's the uncomfortable math of your manager's week: they're managing seven or eight other people, sitting in five-plus hours of meetings a day, and fielding a constant stream of questions, escalations, and decisions. What you shipped on Tuesday is unlikely to survive in their memory through Friday, let alone to your next performance review.

That's not a criticism of your manager. It's the reality of what their job looks like.

A survey by Harvard Business Review found that 63% of managers fail to recognize their employees' achievements. A 2025 Predictive Index study of 1,000 workers found that 44% had been passed over for raises or promotions because their manager didn't fully understand their contributions. Not because the work wasn't good. Because the manager didn't have the information, or the language to use it.

The weekly update is how you fix that. Not as a formality. As a deliberate strategy.

Your manager thinks they know what you're doing. They don't.

One of the more consistent findings in workplace research is that managers systematically overestimate their own awareness of what their reports are working on. A Perceptyx survey found that 50% of managers believe they frequently initiate career conversations, but only 21% of employees agree.

That gap between what managers think they know and what employees actually experience shows up in hard numbers: the same Predictive Index study found that 46% of workers say their manager only somewhat or rarely understands their contributions.

The moment this gap becomes expensive is calibration. If you work at a company with a formal review process, your manager sits in a room without you and defends your case to their peers. They say what they know. They say what they can remember. Other managers in that room are advocating for their own reports with specifics: dates, projects, outcomes. Your manager needs the same.

If you haven't given them the material, they're improvising. Improvised cases lose calibration. Understanding how performance review calibration actually works makes it clearer why the information your manager carries into that room determines what happens to you.

What a weekly update actually is

A weekly update is not a task list. It's not a way of demonstrating you've been busy.

Think of it as building the paper trail your manager pulls from when they go to bat for you.

Your manager needs to be able to say specific things about your work. Not "she's been doing great things on infrastructure" but "she diagnosed the alerting issue that had been causing on-call false positives for three months, fixed it before it escalated, and wrote the runbook so the next engineer isn't starting from scratch." That level of specificity doesn't come from memory. It comes from your updates.

When you write a weekly update, you're creating the language your manager needs to advocate for you. The engineers who get promoted faster aren't always the strongest engineers. They're the ones whose managers can explain what they do and why it matters.

Three things to put in every update

You don't need a template with five sections and a mood score. Three things cover it.

What you finished

Not what you worked on: what you completed, shipped, or closed. "Finished" signals forward motion. "Worked on" signals process. Your manager needs to know what crossed the line, not what's still in flight.

One thing that mattered

This is where most updates go wrong. Engineers write task lists when they should be writing impact statements. "Reviewed three PRs" is a task. "Reviewed the auth refactor PR and flagged a session token issue that would have been a security finding. It's merged and clean." That's an impact. Your manager can repeat that second version in a calibration meeting. They can't do anything with the first.

What you're picking up next

This one is underrated. It signals you're thinking ahead, not just executing. And if there's a misalignment between what you think your priorities are and what your manager thinks they are, this is where you catch it early, before you spend a week on the wrong thing.

Three items, once a week, under 150 words total.

What strong and weak updates look like

Here's the same week, written two different ways:

Weak:

This week I worked on the data pipeline refactor, reviewed some PRs, and was in a few meetings about Q2 planning.

Strong:

Shipped stage 1 of the data pipeline refactor. Batch jobs that were hitting timeout are now processing 40% faster. Caught a schema migration issue in Felix's PR before it merged (would've required a rollback). Next: finishing stage 2 and syncing with the ML team on their ingestion requirements.

The weak version tells your manager you existed. The strong version tells them you had impact. Same week. Different record.

The format matters less than the specificity. Send it as a Slack DM, a message in a dedicated channel, or a short email, wherever your manager actually reads. What matters is regularity and detail.

Why consistency beats quality

You don't need every update to be brilliant. You need to send one every week.

The engineers who benefit most from this habit aren't the ones who write perfect updates. They're the ones who show up with useful information every Friday for six months. Over time, the updates add up to something your manager can reference, summarize, and use.

For engineers dealing with a manager who checks in more often than they'd like, that consistency tends to reduce the interruptions. It's the foundation of managing a micromanaging boss: giving them the visibility they need before they have to ask for it.

When it's time to write your self-review, you'll have a week-by-week record of what you actually did. Most engineers spend days reconstructing the last six months from memory. Engineers with 24 weeks of updates can draft their self-review in an afternoon, because the updates are already in impact-statement format. The software engineer self-review guide walks through how to turn that record into a strong self-review.

An update you send every week at 70% quality does more for your career than a perfect update you send once a month.

The mistakes that make updates backfire

Too long. If your manager has to spend more than 90 seconds reading your update, they stop reading your updates. Under 150 words, every time. If you find yourself going longer, cut the least specific item first.

No impact framing. A list of tasks tells your manager what you did. An impact statement tells them why it mattered. Train yourself to end every bullet with a consequence, not just an action. "Investigated the payment retry logic" is a task. "Found the retry logic was double-charging on timeout and fixed it before it hit production" is an impact statement.

Skipping weeks. One missed week is fine. Two missed weeks breaks the habit. Three and your manager stops expecting to hear from you. The value is in the regularity. A short update on a slow week, two bullets, is better than silence.

How the habit compounds

Weekly updates don't just help your manager. They build your own record.

Three months of consistent updates gives you a running log of impact statements that become your self-review. By six months, your manager has the language to advocate for you at calibration. Give it a year and both of you have evidence to draw on when the promotion conversation happens.

Promotion decisions come down to whether the case for you is stronger than the case against you. The manager who can say "here's what she did, here's why it mattered, here's when she did it" wins that argument. The manager who says "she's been doing really solid work" doesn't. Weekly updates are one piece of a broader set of habits that distinguish self-promotion from bragging. The same discipline of documenting impact applies across 1:1s, standups, and the record you build throughout the year.

The paper trail you build week by week is the case your manager makes when the moment comes.

Start this Friday

Five minutes before you log off. Three lines: what you finished, one thing that had real impact, what's next. Send it wherever your manager reads.

Your manager ends most Fridays with a clearer picture of what you do. A few months in, they have the language to advocate for you. By the time a promotion conversation comes up, you have the evidence to advocate for yourself.

The habit is simple. The compounding is the point.

---

CareerClimb helps you log your wins and track your progress every week, so when self-review, calibration, or a promotion conversation comes around, your record is already built. Download the app to start your weekly log.