Free Excel weekly status report template.
Rules you can check.

What should the report help someone decide?

“Weekly update” is a schedule, not a purpose. Write down what the reader needs to decide: which delivery needs attention, which owner needs help, or which deadline needs a new plan.

• Audience: who reads it, and who acts on the exceptions?
• Cutoff: when must updates be in, and which time zone applies?
• Output: what exact file, view, or summary should the owner produce?
• Scope: which records belong in this report, and which do not?

Keep a copy of the current report and note the work needed to prepare it. Track the time spent collecting updates, correcting data, formatting and reviewing. You can then compare that with the work needed after a change.

Make one row mean one thing.

Choose one workbook or list that everyone agrees to use. State what each row represents, such as one work item. Give every record a unique ID that stays the same when someone renames the task.

Record ID

A unique, stable value, such as WR-101. Check blanks and duplicates.

Work item and owner

A clear description and the person responsible for the next update. If no owner is listed, decide who is responsible.

Status

A fixed set of labels that everyone understands. Do not use color alone to record status.

Due date

The date used in the overdue rule. Decide what a blank date means.

Last updated

The date of the latest meaningful update. Agree how long an item can go without an update before it needs attention.

Next action

A specific action and, where needed, a decision owner. “Follow up” needs more detail.

Keep the data rows separate from report totals and notes. If workbook tabs use different headings, agree on what each field means before building the report. Note where the data is kept and who approves access.

Write the rules before counting.

The same label should mean the same thing to everyone updating the source. These are example definitions to adapt with your team:

Keep health and date checks separate. A record marked On track can still have a past due date; the report should flag that contradiction for review.

• Open: status is anything other than Done.
• Overdue: open and due date is strictly before the reporting date. Due on that date is not overdue.
• Stale: open and last updated more than seven calendar days before the reporting date.

These limits are choices for this example. Agree on the rules your team will use. A blank date or unknown status needs checking; it should not automatically count as On track.

Check the report with a small sample.

Use a few made-up records that include normal work and unusual cases. Work out the expected result before running the workflow, then compare the results row by row.

Add the cases that tend to break a report.

• A blank owner, a duplicate ID, and an unfamiliar status should appear in an exception list.
• An open item due exactly on the reporting date should be excluded from overdue.
• An empty source should show a clear empty result. An inaccessible source should show a failure, not a reassuring zero.
• Running the report again with the same data should give the same totals.

Review late changes separately. State whether a correction belongs in this reporting cycle or the next, and retain the cutoff used for each output.

Try the free Excel weekly status report template.

This separate practice file has 12 invented work items and focuses on deadline exceptions. Change the reporting date or sample inputs, then check how the summary and deadline flags respond. It is free, with no signup or email required.

XLSX · 7.6 KB · one worksheet, “Weekly report”. No macros or external data connections. All names and work items are synthetic.

Use it in four steps.

1. Open and keep a copy. Open the downloaded workbook in Excel. Start with the supplied reporting date, September 23, 2026, and compare the results below before editing.
2. Set the reporting date. Change cell B5 to the date you want to review. You set this date yourself, so the example does not change with today’s date.
3. Edit the sample inputs. Use columns A–F in rows 19–30 for the ID, work item, owner, status, due date and next action. Choose Not started, In progress, Blocked or Done. Leave the calculated deadline flags in column G and summary cells unchanged.
4. Review the exceptions. Recheck the summary after an edit and trace each count to its source rows. Resolve any “Check status” or “Check due date” flags before relying on the totals. Summary counts include rows hidden by a filter. Confirm what the owner should do about an overdue item or a missing due date.

The workbook has 12 fixed input slots. Clear columns A–F in an existing row to remove that record. Adding rows requires extending the table, formulas, validation and summary ranges. This exercise covers deadline rules; the four-row example above also illustrates stale updates.

For help using your own data and rules for a regular report, see the reporting sprint scope or prepare a reporting brief.

How does the template calculate overdue work?

The reporting date in B5 is the cutoff. The deadline formula in column G first checks whether the row has an ID and a recognized status. Done items are labeled Done. For unfinished work, it checks for a valid due date and reporting date before comparing them.

The examples below use the workbook's starting date, September 23, 2026. They explain the deadline rules, not customer results.

The overdue summary counts those flags.

Cell C10 uses this formula. If the reporting date is blank, nonnumeric, zero or negative, it asks you to set that date instead of displaying an overdue total.

=IF(AND(ISNUMBER($B$5),$B$5>0),COUNTIFS(G19:G30,"Overdue"),"Set report date")

Keep the formulas in column G intact. A pasted, unrecognized status produces “Check status”; an unfinished item with a nonnumeric or nonpositive due date produces “Check due date”. Correct those inputs before treating the summary as complete.

Why do totals stay the same when I filter the rows?

The summary counts the full input range, including hidden rows. Filtering lets you look at fewer rows, but the totals still include all of them.

Can I add more tasks or use it as a team tracker?

The exercise has 12 fixed input slots. To add more, extend the table, formulas, validation and summary ranges together, then check that the totals match the rows. If people need to update shared records, compare Excel, SharePoint and Dataverse for the workflow before choosing the next tool.

Define what “works” means.

A clear layout is only part of the job. Agree how the process owner will check that the report works.

1. Match the records: every source ID that belongs in the report appears in the details or list of problems, and the totals match those records.
2. Handle exceptions: missing or invalid data stays visible, and someone is responsible for fixing it.
3. Run again: the owner can run the next report using the instructions and knows where to check the result.
4. Handle failure: the owner can spot a failed run and follow the instructions to try again or use a backup process.

The handover should explain where the data comes from, the data cutoff, how to run and check the report, where to find it, what it needs to run and who maintains it. Compare preparation time and corrections over agreed reporting cycles before claiming savings.

Prepare a short description.

Work through this checklist with the report owner. It helps you plan; checking the boxes does not send information or confirm that the project is ready.

Copy this outline for a first conversation.