Your manager asks, “How is the project going?” You have been busy all week, but when you try to answer, you ramble. You mention a meeting, a problem you solved, something you are waiting on, and a question you forgot to ask. Your manager nods but does not seem to have a clear picture of where things stand.
The problem is not that you did not do enough work. The problem is that you did not organize your update before sharing it. A clear work update tells people what is done, what is in progress, and what comes next — in a way they can scan quickly.
Why regular updates matter
Managers and teammates cannot see what you are doing all day. They rely on your updates to know whether a project is on track, whether you need help, and whether they should adjust their own plans.
Without updates, a few things happen:
- Your manager assumes everything is fine until a deadline passes and something is not done
- Your teammates make plans based on outdated information
- Problems stay hidden until they become urgent
A short, regular update prevents all of these. You do not need a long report — just a clear snapshot of where things stand.
The three-part update
The simplest way to structure a work update is three parts:
What is done. Tasks you completed since the last update.
What is in progress. Tasks you are currently working on, and when you expect to finish.
What is next or what is blocked. Tasks you have not started yet, or problems that are holding you up.
Here is an example:
Project: Johnson proposal
Done:
- Drafted sections 1–3
- Got feedback from the design team
In progress:
- Writing section 4 (expect to finish by Thursday)
- Waiting on budget numbers from finance
Blocked:
- Cannot finalize the timeline until the client confirms their schedule
This tells your manager everything they need to know in thirty seconds. They can see what is moving, what is waiting, and where they might need to step in.
How long should an update be
Short enough that someone can read it in under a minute. For most projects, three to six bullet points are enough. If your update is longer than that, you are probably including too much detail.
The goal is not to document everything you did. It is to give a clear picture of progress and blockers. Details belong in project documents, not in status updates.
When to send updates
The right frequency depends on your team and your projects:
Weekly updates work well for ongoing projects. Send them at the end of the week or the beginning of the next one. Your manager knows when to expect them and can plan around them.
Daily updates make sense when things are moving fast — during a launch, a deadline week, or when multiple people are coordinating closely.
Milestone updates work for long projects with clear phases. Send an update when you finish a phase, hit a problem, or reach a decision point.
If your manager has not asked for updates, send them anyway. A short weekly update is almost always appreciated, and it protects you if something goes wrong later — you can point to your update and say “I flagged this last week.”
What to do when things are not going well
Updates are easy when everything is on track. They are harder when you are behind schedule, waiting on someone else, or stuck on a problem.
When things are not going well, be direct:
Do not hide problems. If a deadline is at risk, say so now — not the day before it is due. Your manager can help only if they know about the problem in time.
Explain the impact, not just the problem. “The budget numbers are late” is a problem. “The budget numbers are late, which means I cannot finish the proposal by Friday” is an impact. The impact helps your manager decide how urgently to act.
Suggest a solution if you have one. “I am waiting on budget numbers from finance. Should I follow up with them directly, or can you escalate?” This turns a blocker into a clear question your manager can answer.
What to avoid in updates
Being too vague. “Working on the project” could mean anything. Be specific: “Writing the project proposal — finished sections 1–3, starting section 4 tomorrow.”
Being too detailed. Your manager does not need to know every email you sent or every meeting you attended. Focus on outcomes and blockers, not activities.
Only reporting good news. If you only mention what is going well, your manager will not know about risks until they become problems. Include blockers and concerns in every update.
Waiting until you have a complete picture. You do not need to finish something before you mention it. “Started the budget review — will have results by Wednesday” is useful information even though the task is not done.
Related guides
- How to Write a Clear Email Subject Line — making sure your update gets opened and read
- How to Plan a Weekly Schedule — planning your week so updates reflect real progress
- How to Make a Simple Work Plan — tracking work at a project level