A status update is a short message that tells your manager or team what you have done, what you are doing next and whether anything is blocking you. It sounds simple, and it is, but it is one of the most effective habits for a new employee, especially in remote and hybrid teams.
Good status updates build trust, reduce the need for check-in meetings and make your work visible. Here is how to write them.
Why status updates matter
- Your manager knows what you are working on without asking.
- Problems surface early, when they are easier to fix.
- Your contributions are documented for reviews.
- Colleagues know when to expect your part of shared work.
Daily or weekly?
Follow your team’s norm. If there is none:
- Daily updates suit fast-moving roles, new employees in their first weeks and teams across time zones.
- Weekly updates suit roles with longer projects and more independence.
You can also ask your manager: “Would a short end-of-day update be helpful while I’m getting started?”
A simple format
Use three or four headings:
Status update format
Done: what you completed
Next: what you will work on
Blockers: anything stopping you, and what you need
FYI (optional): anything others should know
Keep it short. Bullet points are fine. Aim for something that can be read in under a minute.
Examples
Daily update – operations assistant
Done: Updated tracking for 42 shipments. Sent follow-ups to two carriers on delayed deliveries.
Next: Draft the weekly report (due Friday). Clean duplicate entries in the carrier contact list.
Blockers: Waiting on Northwind to confirm two delivery dates; I’ll chase again at 10 a.m. tomorrow.
Weekly update – customer support associate
Done: Handled 180 chat and email tickets; average first reply within team target. Drafted 3 new help articles (links). Completed product training module 2.
Next: Publish help articles after review. Shadow the billing specialist on Tuesday.
Blockers: None.
FYI: Several customers asked about the new pricing page; may be worth an FAQ.
Weekly update – junior analyst
Done: Built the monthly churn dashboard draft (link). Validated totals against the source system.
Next: Incorporate Lena’s feedback; add a region filter.
Blockers: Need access to the billing database to finish the revenue view. Request submitted to IT on Monday.
Numbers and names above are examples. Use your real tasks.
Writing good “blockers”
A blocker should be specific and include what you need:
| Vague | Clear |
|---|---|
| “Stuck on the report.” | “I can’t finish the report because the October data hasn’t been exported. Could you ask finance, or should I contact them directly?” |
| “Waiting on IT.” | “Waiting on IT for database access (ticket #4182, submitted Monday). This delays the revenue view to next week.” |
If nothing is blocking you, say “None”. It is useful information too.
Where to post it
- A direct message or email to your manager.
- A team channel used for updates.
- A shared document or project tool.
Use whatever your team prefers. Consistency matters more than the tool.
Tips for useful updates
- Be specific: numbers, names of deliverables, links.
- Focus on outcomes, not only activities.
- Flag risks early: “The report may slip to Monday if the data arrives late.”
- Keep the same format each time so it is easy to scan.
- Send it at the same time each day or week.
Use your updates for reviews
Save your updates or copy key points into a “wins” document. When your first performance review arrives, you will have a detailed record of what you achieved. Our guide to staying visible when you work remotely explains why this matters.
Send your first update today
Write your first status update today using the four headings. Ask your manager whether the length and frequency work for them, and adjust. Within a couple of weeks it will take you less than five minutes, and it will save far more time in fewer check-ins and clearer priorities.