Weekly Team Progress Report From Your Task List, Without Guessing

A weekly team progress report built from your task list tells you what actually got finished and what has gone quiet, using the dates and statuses already in your project tool instead of a manager’s impression of who “seems busy.”

On a remote team, you can’t see anyone’s desk. That makes it tempting to judge progress by how full the calendar looks, how fast people reply in chat, or how many meetings someone attends. None of those directly measure what got done. Your task list may hold better evidence: what moved to done, what hasn’t been touched in days, and what’s blocked. The trouble is that nobody has time to read it all every Friday.

This guide shows how to turn a plain export of your tasks into a short weekly report, how to define “shipped” and “stalled” in your own terms, an AI prompt that summarizes and counts without inventing anything, and how to share the report without turning it into a ranking of people. The team and tasks in the examples are invented. Nothing here is legal or HR advice.

Why Outcomes Beat Impressions

In my view, an impression-based review has three problems. It rewards visibility over results, it depends on who speaks up in meetings, and it can’t be checked. A report based on task records can be checked by anyone on the team. When someone says “that was shipped Tuesday,” the record either shows it or it doesn’t.

That doesn’t mean task counts tell the whole story. Tasks differ in size, some work never becomes a task, and a quiet week can be a good week if someone was solving a hard problem. The report is a conversation starter that points you to places to ask questions, not a verdict.

Three Ways to Check on Progress

• Based on records: Go by impressions – No; Read the whole board – Yes; Weekly report from an export – Yes.
• Spots stalled work: Go by impressions – By luck; Read the whole board – If you notice; Weekly report from an export – By date.
• Can be checked by the team: Go by impressions – No; Read the whole board – Yes; Weekly report from an export – Yes.
• Risk of misreading: Go by impressions – High; Read the whole board – Medium; Weekly report from an export – Medium, if you add context.

Building the Report

Step One: Export the Fields That Matter

Most project tools can export tasks as a spreadsheet. You need only a few columns:

• Task name: What the work is
• Owner: Who’s responsible
• Status: Not started, in progress, blocked, done
• Created date: How old the task is
• Completed date: When it finished, if it did
• Last updated date: When anyone last touched it
• Blocker note: Why it’s stuck, if recorded

If your tool doesn’t track “last updated,” you can still report on shipped work, and you’ll need another way to spot stalled items, such as a standing weekly check-in.

Step Two: Define Your Terms in Writing

Words like “shipped” and “stalled” mean different things on different teams. Decide yours before you run anything:

• Shipped: a task whose status changed to done during the reporting week
• Stalled: a task in progress or blocked, with no update in more than a set number of days
• Aging: a task not started that was created more than a set number of days ago

Pick the number of days yourself, based on how long your team’s tasks normally go without an update, and write the numbers on the page so everyone shares the definition. The example below uses five.

Step Three: Give AI the Date and the Rules

AI can’t know today’s date unless you tell it, and it will guess if you don’t. Supply it. Here’s a prompt:

I manage a remote team. Below is an export of our tasks and today's date. Please produce a weekly progress report.

Today's date: [date]
Reporting week: [start date] to [end date]

My definitions:
- "Shipped" = status is Done and the completed date falls in the reporting week.
- "Stalled" = status is In progress or Blocked and the last updated date is more than [N] days before today.
- "Aging" = status is Not started and the created date is more than [M] days before today.

Task export:
[paste the table]

Please:
1. List shipped tasks with owner and completed date.
2. List stalled tasks with owner, last updated date, days since update (show the date subtraction), and the blocker note if there is one. If no blocker is recorded, write "NOT STATED."
3. List aging tasks with owner and days since creation (show the subtraction).
4. Give counts for each status as plain numbers.
5. List any task where the data seems inconsistent (for example, Done with no completed date), marked "CHECK."

Rules:
- Use only the data I pasted and my definitions.
- Do not guess reasons for delays, and do not judge any person's performance.
- Do not rank people or compare their output.
- Do not add tasks or details that are not in the export.

The rule against ranking people is worth keeping. In my view, task counts are a poor basis for comparing individuals, and a report that invites that comparison may lead people to game the numbers.

Worked Example for Weekly Team Progress Reports

Suppose today is March 14 (a non-leap year) and your five-day threshold applies. The invented export has eight tasks:

Task	Owner	Status	Date detail
Update pricing page	Ana	Done	Completed Mar 10
Fix signup bug	Ben	Done	Completed Mar 12
Draft Q2 plan	Cleo	In progress	Last updated Mar 6
Vendor contract review	Dev	In progress	Last updated Mar 13
Onboarding doc	Ana	Not started	Created Feb 20
Customer survey results	Ben	Blocked	Last updated Mar 4, “waiting on data export”
Newsletter draft	Cleo	Done	Completed Mar 11
Help-center update	Dev	In progress	Last updated Mar 3

The report would show:

• Shipped (3): pricing page, signup bug, newsletter draft.
• Stalled (3): Draft Q2 plan (8 days since update), Customer survey results (10 days, blocker: waiting on data export), Help-center update (11 days, blocker NOT STATED).
• Not stalled: Vendor contract review (1 day).
• Aging (1): Onboarding doc, 22 days since creation.
• Counts: 3 done, 3 in progress, 1 blocked, 1 not started.

The date math works out: March 6 to March 14 is 8 days, and February 20 to March 14 is 22 days in a non-leap year. Read the stalled list as questions: Is Cleo’s Q2 plan actually stuck, or deep in thinking? Who can unblock the data export for Ben? Why does the help-center update have no blocker note? All of the tasks and people here are invented.

Add the Context AI Can’t See

The report is a starting point. Before sharing, add notes only you can supply:

• Work not in the tool. A long conversation with a customer or a hard design problem may not appear as a task.
• Task size. A big task done and three small ones done aren’t equal.
• Reasons for delay that you already know.
• What you’re asking for. For each stalled item, is there a decision, a person, or a resource needed?

In my view, a good practice is to ask each owner about their stalled items before the report goes out, so nobody is surprised by seeing their name in a list.

Sharing the Report Well

Share It as a Team Document

How you share the report matters as much as what’s in it.

• Frame it around work, not people. Group by project or goal when possible.
• Share the definitions so the numbers aren’t mysterious.
• Invite corrections. If a task is wrongly marked stalled, update the record.
• Don’t use it to compare individuals. Different roles produce different kinds of tasks.
• Keep it short. One page that people actually read beats five that they don’t.

If you’re thinking about adding any tracking beyond task records, explain what it measures and why before you start, and check the rules that apply where you and your team work. This article doesn’t cover legal requirements.

Keep Sensitive Data Out

Task names can include customer names or internal details. Before pasting an export into an AI tool, remove anything confidential, check your company’s rules for using AI tools, and strip personal data that doesn’t belong. If you can’t remove it, summarize the tasks by hand.

A Weekly Rhythm That Works

1. Friday morning: export tasks.
2. Run the prompt and check the arithmetic.
3. Ask owners about stalled items (a few short messages).
4. Add context and send a one-page report.
5. Review last week’s stalled items to see what moved.

After a few weeks, you can see patterns, such as a type of task that always stalls or an approval step that causes delays. Those patterns point to fixes in the process, not in people.

Weekly Team Progress Reports: Mistakes to Avoid

• Treating counts as performance. Task size and type vary.
• Skipping the definitions. “Stalled” means nothing without a number of days.
• Letting AI guess why work is late. Ask people.
• Forgetting today’s date. Without it, any “days since” figure is invalid.
• Sharing a report that names people without asking them first. Talk before you publish.

Questions About Weekly Team Progress Reports

What should a weekly team progress report include? What shipped, what’s stalled and for how long, what’s blocked and why, and the questions that need answers. Keep it short and based on task records.

Can AI write a weekly team progress report? It can summarize an export and calculate dates if you give it today’s date and your definitions, and tell it not to guess reasons or judge people.

Is counting completed tasks a fair way to measure performance? Not by itself. Tasks differ in size and some work isn’t tracked. Use counts to start conversations, not to rank people.

How do I decide what counts as stalled? Choose a number of days that fits how your team works, and write it down so everyone shares the definition.

What if my tool doesn’t export last-updated dates? Report on shipped work from completion dates, and use a weekly check-in to find stalled items.

Should I share the report with the whole team? Possibly yes, framed around work and with definitions included. Ask owners about their items first.

How do I keep confidential information out of the AI tool? Remove names and details you shouldn’t share, follow your company’s AI policy, or summarize by hand.

Run Last Week’s Tasks Through It

Export last week’s task list, write your definitions for shipped and stalled, add today’s date, and run the prompt. A weekly team progress report built this way is a short routine and replaces guesses about who seems busy with a short list of what finished, what stopped, and who might need help.

If your report starts from meetings, our guide to meeting follow-up without recording shows a voice-memo method.

This article offers general management tips, not legal or HR advice. Workplace monitoring and data-handling rules vary by location. The example team, tasks, and dates are fictional.