How to write a weekly report: template and example

A weekly report tells your manager and team what you finished, what is still in progress, what comes next week, and where you are blocked. Write each line as a result that ends in a number or a clear status. Note the result the moment a task is done, and on Friday you pick from lines you already have instead of trying to remember your week.

What is a weekly report for?

It lets your manager and teammates see where your work stands without a meeting. They usually read several reports in a row and skim for two things: is the work on track, and do you need help. It pays off for you too. At review time, old weekly reports are a better record of what you shipped than your memory.

What should a weekly report include?

Four sections cover most teams. If yours has its own format, use it; the content usually lands in the same four buckets.

• Under done, list only work that is finished and needs nothing more from you. Half-finished work put here gets reported twice.
• For work in progress, say how far along it is and when it will be done. If you don't know the date yet, name the next step.
• Next week's plan needs two or three concrete lines, so next Friday you can check them against what got done.
• Blockers and requests are for what you can't fix yourself. Say who you need something from, what it is, and by when. If nothing is blocking you, write none.

How do you write each line?

Say what changed because of the work, and end on a number or a status. Lines that end in words like working on, reviewing, or ongoing show what kept you busy but leave the reader guessing about the outcome.

Before: Worked on payment retry logic
After:  Shipped the payment retry queue to production (9/22).
        Failed charges now retry 3 times automatically

Before: Subscription card update screen, in progress (70%)
After:  Subscription card update screen: API hooked up, waiting
        on QA. Target release 9/30

The second one is common. Seventy percent means something to the person who wrote it and nothing to anyone else. Saying what is done and what is left lets the reader judge the schedule.

Plenty of work has no number. Then end on a status: shipped, shared, confirmed, on hold. If someone asked for it, add their name so they see it's done.

A weekly report template with an example

Here is a Friday report from Minsu, a backend developer on a made-up Payments team. Copy the headings and swap in your own lines.

Weekly Report, 9/21 - 9/25
Minsu, Payments team

1. Done
- Shipped the payment retry queue to production (9/22). Failed
  charges now retry 3 times automatically
- Cut average refund API response time from 1.8s to 0.6s
- Found why users drop off at onboarding step 1 (requested by
  Jihye). Most leave at phone verification; shared with product

2. In progress
- Subscription card update screen: API hooked up, waiting on QA.
  Target release 9/30
- Automated settlement report emails: design in review.
  Development starts after Dana signs off

3. Next week
- Release the card update screen
- Start on settlement report emails; test email out by Friday

4. Blockers and requests
- Card issuer test account expires 10/2. Need ops to decide who
  requests the renewal

What mistakes do people make with weekly reports?

The usual ones are listing everything you touched, writing the process without the result, and rebuilding the week from memory on Friday.

Listing everything

Meetings, emails, code reviews. A complete list looks diligent, but the reader can't tell which lines mattered. Drop routine work or fold it into one line, and put real outcomes at the top.

Process with no result

When analyzing or reviewing shows up week after week, nobody knows when the work will end. With no result yet, move it to in progress and give it a next step and a date.

Remembering it all on Friday

Many people scroll back through chat and commits on Friday to piece the week together. By then Monday and Tuesday are just task titles, the numbers and requesters are gone, and the report turns into a list of process.

How do you avoid the Friday scramble?

Write the result down the moment you finish the task. Right then you still know how many cases you closed, who asked, and what is left. Two days later, those details are the first to go.

A notes app or a spreadsheet works, as long as it is one place. Write each note like a report line: the result, the date, who asked. Friday is then about choosing and ordering lines.

Doing this in DDirong

DDirong is a web app that keeps tasks, schedules, work logs, and weekly reports in one place, and its recording features are free. Tasks go in as single lines. Check one off and a result memo box opens for a line or two about what happened. You can also skip it.

At the end of the week, you copy completed tasks as weekly report text. The copy has each task's title, workspace, completion date, and requester, but not the memo text, and DDirong does not rewrite or add anything. Use it as the skeleton and fill in results from your memos.