See what the workflow prepares
Illustrative example. Sample tasks, sample tickets, and sample project notes. This is not a customer result.
Jordan Hale is the account manager in this example. The client is Northline, a regional retailer. The report covers Monday 28 September through Friday 2 October 2026. Jordan prepares the draft on Monday 5 October, before anyone shares it.
The sources in this illustration are the task records, the tickets, a weekly project note from the delivery lead, and the client email thread. A connection to any particular tool is not part of the example. On a real project, the sources are the ones you agree.
The collection rule in this illustration: take records updated during the reporting period, keep open items that are still unfinished when the period ends, and keep the latest client commitment those open items rely on. An update with no newer record in the 7 days before 2 October is marked stale. That freshness rule belongs to the example.
| Record | What it says | Standing |
|---|---|---|
| Task T-438, loyalty welcome email. Updated 29 September 2026 by Alex Okonkwo. Status: Done. | The client contact approved the welcome email copy. | Completed. Updated inside the period. |
| Task T-441, card-payment retry. Updated 30 September 2026 by Priya Shah. Status: Done. | Retry logic is on staging for card payments. | Completed for card payments. Grouped with the gift-card ticket. |
| Ticket SUP-1882, gift-card checkout. Opened 1 October 2026 by QA. Status: Open. Owner not recorded. | Gift-card checkout still fails on the second attempt in staging. | Blocker. Conflicts with treating T-441 as done for every payment type. Owner missing. |
| Task T-452, checkout accessibility. Updated 1 October 2026 by Priya Shah. Status: In progress. | Two of five keyboard checks on the payment step remain. Priya will finish them by 9 October. | Ongoing. The next step has a recorded owner and date. |
| Task T-419, warehouse status feed. Updated 18 September 2026 by Sam Rivera. Status: In progress. | Waiting on the client API credentials. | Still open. Stale: no newer record in the 7 days before 2 October. |
| Email from Dana Ruiz at Northline, 26 September 2026. | Northline will send the warehouse API credentials by Friday 2 October. | Confirmed commitment, with a recorded owner and date. No later record shows that the credentials arrived. |
| Weekly project note from Morgan Ellis, delivery lead. | No note dated inside 28 September–2 October. | Missing update. This source was expected for the period. |
| Note from Jordan Hale, 3 October 2026, written while preparing the draft. | The team could poll the old inventory file until the credentials arrive. | Suggested action. No owner has accepted it, and no date is recorded. |
| Group | Records | What the group supports |
|---|---|---|
| Loyalty email | T-438 | Completed this period. |
| Checkout payments | T-441 and SUP-1882 | Card retry is recorded as done. The gift-card ticket is still open, so the group stays in conflict. |
| Checkout accessibility | T-452 | Ongoing. Next step recorded on the task. |
| Warehouse feed | T-419, the email from Dana Ruiz, and the missing note from Morgan Ellis | Open work, a stale task note, a commitment whose date has passed, and a missing weekly note. |
Draft for review
Progress
The loyalty welcome email copy was approved on 29 September. Source: task T-438, Alex Okonkwo, 29 September 2026.
Card-payment retry is on staging as of 30 September. Source: task T-441, Priya Shah, 30 September 2026. The line covers card payments. The gift-card path is reported with the blocker below.
Still underway
Two of five keyboard checks on the payment step remain. Source: task T-452, Priya Shah, 1 October 2026.
Blockers and flags
Gift-card checkout still fails on the second attempt in staging. Source: ticket SUP-1882, 1 October 2026. The ticket has no owner. It conflicts with any line that would call task T-441 done for every payment type.
Dana Ruiz committed to send the warehouse API credentials by 2 October. Source: client email, 26 September 2026. No record in the collected sources shows that they arrived. Task T-419, last updated by Sam Rivera on 18 September, is marked stale under the 7-day rule in this example.
The delivery lead’s weekly project note for 28 September–2 October was not found. Expected source: project note from Morgan Ellis.
Next steps
Confirmed on the task: Priya Shah will finish the remaining two accessibility checks by 9 October. Source: task T-452.
Confirmed, and still open: Dana Ruiz will send the warehouse API credentials. The date on the email has passed. The draft keeps that recorded date and leaves the new date blank, because no later record gives one.
Suggested action: poll the old inventory file until the credentials arrive. Source: Jordan Hale’s note, 3 October 2026. No owner has accepted it, and no date is recorded, so it stays a suggestion.
Status: ready for Jordan Hale. The report has not been shared with Northline. Account-manager review is required before sharing.
Weekly report template
Copy this template. The sample lines are from the illustration above. They are not a client report and not a measured result.
WEEKLY CLIENT REPORT Label: illustrative sample Client: Northline Period: Monday 28 September through Friday 2 October 2026 Prepared: Monday 5 October 2026 Account manager: Jordan Hale Status: draft for the account manager. Not shared. PROGRESS - Loyalty welcome email copy was approved on 29 September. Source: task T-438, Alex Okonkwo, 29 September 2026. - Card-payment retry is on staging as of 30 September. Source: task T-441, Priya Shah, 30 September 2026. This line covers card payments only. BLOCKERS - Gift-card checkout still fails on the second attempt in staging. Source: ticket SUP-1882, opened 1 October 2026. Owner not recorded. Conflict: do not describe T-441 as done for every payment type. - Warehouse API credentials were due from Dana Ruiz by 2 October. Source: client email, 26 September 2026. No later record shows that they arrived. Task T-419 was last updated 18 September and is stale under this example's 7-day rule. - The delivery lead's weekly note for this period was not found. Expected source: project note from Morgan Ellis. NEXT STEPS - Priya Shah will finish the remaining two accessibility checks by 9 October. Source: task T-452, 1 October 2026. - Dana Ruiz's credential date has passed. The new date is blank because no later record gives one. DECISIONS NEEDED - Who owns ticket SUP-1882? - Is polling the old inventory file an accepted workaround? Source of the suggestion: Jordan Hale's note, 3 October 2026. No owner has accepted it, so it stays a suggestion, not a commitment. ACCOUNT-MANAGER REVIEW Share the report only after the account manager checks sources, conflicts, stale items, and suggestions.
How the workflow works
-
1
Collect records for the reporting period
Read the task updates, tickets, and project records agreed for this project. Limit them to the period you set, and apply the freshness rule you set, so an older open item can appear only with a stale flag.
-
2
Group related updates
Put records that describe the same work together. A task, a ticket, and an email about one feed belong in one group before any of them is written up alone.
-
3
Separate completed and ongoing work
Use the status on the record. A closed task can be reported as completed. An open ticket in the same group stays visible beside it.
-
4
Highlight blockers and other flags
Call out blockers. Also flag an update that is stale, that conflicts with another record, or that is missing from a source you expected this period.
-
5
Draft next steps from the records
Write a next step when the record already has an owner and a date. That is a confirmed commitment. A workaround nobody has accepted stays labeled as a suggested action.
-
6
Hold the draft for the account manager
Give the draft to the account manager, with each statement tied to its source. The report is shared only after that person reviews it.
The workflow does not invent an owner, a date, or a completion. Your team defines which sources count, how old an update can be, and what the reviewer checks before sharing.
Measure the value
Preparation time shows whether the report is faster to finish. Factual corrections show whether fewer claims have to change before it is sent.
Report preparation time, including review
Keep one log on the report. Each person who collects updates, drafts, reviews, or edits adds an entry with their name, the date, the minutes, and the kind of work: collecting, drafting, review, factual correction, or stylistic edit.
Start when the reporting period has closed and the agreed sources are available to collect. Stop when the account manager approves the draft for sharing. Add every entry in between. The first draft is not the end of the clock.
Leave waiting time off the log. Minutes spent waiting for a colleague to reply, or for a client to send a file, are not preparation time.
Corrections before sending
A factual correction changes what the report claims. It fixes a status, a source, an owner, a date, or the line between a confirmed commitment and a suggested action. It also covers a stale, conflicting, or missing update that was written as a current fact.
A stylistic edit changes wording, tone, length, or order. The claim, the source, the owner, and the date stay the same. Several wording changes handled in the same pass are one stylistic pass.
Count factual corrections as claims changed. Count stylistic work as passes. Define that once and keep the definition.
How to add the minutes
This counting example shows the arithmetic. It is not a result from a client project.
The account manager logs 70 minutes collecting records and drafting. The reviewer logs 25 minutes and returns the draft: the gift-card ticket was left out, and a suggestion was written as a commitment. The reviewer also asks for a shorter opening. The author logs 20 minutes on those two factual corrections and 10 minutes on the opening. The reviewer logs 15 minutes and approves the draft for sharing.
Preparation time is 140 minutes. That includes review, the factual corrections, and the stylistic edit. Factual corrections: 2. Stylistic passes: 1.
Compare reports of a similar client, length, and reviewer from before the workflow and after it. Report the median preparation time and the median count of factual corrections. Keep the report type on the log so a long multi-project update is not compared with a short one. Collect that comparison before you claim a change.
Build it around the report you already send
This is a proposed implementation for one reporting cycle. You provide the sources you already keep, the template you send, and the review rules for that project. The workflow collects the period, groups related updates, and drafts progress, blockers, and next steps. It flags what is stale, conflicting, or missing. The account manager reviews the draft before it can be shared.
Sources, the reporting template, and the review rules are agreed per project. A connection to a task board, a ticket system, or a document store is specified in the project. It is not assumed on this page. Related patterns are on AI automation use cases.
Limit: each statement keeps the record it came from. A missing note, a stale update, or a conflict stays flagged. A task tool, ticket system, or document store is connected only when the project specifies it.
Suitable measures are preparation time, including review, and the number of returns before the account manager will share the draft. Use your own before-and-after log. This page does not report a customer result.
Start with one client, one reporting period, and a written review rule. See AI workflow automation and pricing.