Copy the weekly team report
Weekly status report for [team or workstream]
Reporting period: [start date] to [end date]
Prepared by: [name]
Current position
[State where the work stands and any change to the agreed plan.]
Completed during this period
[Name the finished result and link to the work.]
Open work and blockers
[State what remains, what prevents progress, and who handles it.]
Decisions needed
[Name the decision, its owner, and the point when it is needed.]
Next period and handoff
[Name the next task, its owner, and what they need to begin.]
Reference
[Link to the shared work record or approved files.]
Keep the period visible when you save or forward the report. A teammate should be able to distinguish the current report from an older one without reading every paragraph. Remove empty prompts before sending, but keep an explicit note when there are no blockers or decisions needed.
Fill in each weekly progress report section
Reporting period and author
Use the actual start and end dates for the work covered. The sending date alone does not tell a reader which work belongs in the report. Name the author so teammates know who can explain an entry or correct an error.
Keep late information separate from the closed period. If a decision arrived after the end date, mark it as a later note. Do not silently change the period to include it. A stable boundary helps the next author avoid reporting the same result again.
Current position
State whether the team can continue under the agreed plan. Name any condition that prevents the next step. Avoid a bare colour label or an unsupported percentage. A reader needs to know what is ready and what still needs attention.
Compare the position with the previous report when the plan has changed. Explain the effect on the next task rather than recounting every discussion that led to the change.
Completed work
List results finished inside the reporting period. Include a direct link when teammates need to inspect or use the result. Distinguish a draft from an approved file, and distinguish submitted work from accepted work.
Do not copy the full task log. Include work that affects the next owner, a shared dependency, or the agreed goal. Leave personal activity notes in the task record.
Open work and blockers
Name unfinished work even when there is no blocker. For blocked work, state the missing input and the person responsible for getting it. Explain which task cannot proceed until the input arrives.
A handoff requires more than naming another team. Confirm who accepts the work and where they can find the context. Keep responsibility with the current owner until the receiving person accepts it.
Decisions needed
Write each request as an action someone can answer. Name the decision owner and the stage when the answer is needed. Use a confirmed deadline when one exists. Do not invent a date to make the report look complete.
Keep decisions separate from general concerns. A concern needs an owner to investigate it. A decision needs someone with authority to choose an option.
Next period and reference
List the next useful result and the person responsible for it. Include the starting condition so the next owner knows whether work can begin. Link to the shared record for detail, with access checked before sending.
Carry unresolved items into the next report until someone closes them. Do not remove an item just because it appeared last week. Record its current state instead.
Filled example for a team handoff
The following example is illustrative. It describes invented work, not a customer project. Replace the period label with actual dates when using it.
Weekly status report for Website content team
Reporting period: The completed reporting week
Prepared by: Content lead
Current position
The draft pages are ready for editorial review. Publication remains on hold until the contact details are approved.
Completed during this period
The content team saved the revised service descriptions in the shared review folder.
Open work and blockers
The contact page is still a draft. The account owner is responsible for confirming the contact details.
Decisions needed
The account owner needs to approve the contact details before publication review begins.
Next period and handoff
The editor will review the service descriptions. The content lead retains the contact page until approval is recorded.
Reference
Use the shared review folder and the contact approval task.
The example separates finished drafts from publication readiness. The editor has work to begin, while the content lead still owns the unresolved page. No one needs to infer responsibility from a list of names.
Send the report as an email
Use the team name and reporting period in the subject. Put the current position first in the body, then paste the remaining sections. Keep the decision request visible rather than hiding it beneath attachments.
Subject: [team name] status report, [start date] to [end date]
Hello team,
[Paste the completed report here.]
Please reply to the decision request assigned to you. Record any accepted handoff in [shared work record].
[Your name]
Check recipients and file permissions before sending. Keep private account details out of a broad team report. If a client also needs an update, write a separate note about the results and decisions relevant to them. The weekly client update guide explains that shorter format.
Common questions
What should a weekly status report include?
Include the period, current position, completed results, open work, decision requests, and next owners. Add links for detail. For audience differences, read how internal reports differ from client updates.
What if nothing was completed?
State that no result was completed during the period. Explain the open work and its next action. Do not describe time spent as a finished result or leave teammates guessing about a delay.
Can the report go in email?
Yes. Keep the period and section labels in the email body. Store the same report in the agreed shared location if teammates need a continuing record. The article on a regular update habit covers choosing a consistent time to send updates.