Automate the weekly team digest
At seven on Monday the team channel already says what was finished last week, what is due this week and what has been sitting untouched – with the source of every block named underneath it. Anything no system can supply appears as a gap in the digest rather than as a guess.
Writing it takes ten minutes, finding it takes an hour
A team's weekly position is rarely held in one place. Tasks sit in Planner or Jira, customer topics in the CRM, faults in the ticket system, appointments in the calendar, and half of what actually matters is buried in a chat nobody read after Friday lunchtime. Before the Monday meeting one person clicks through all of it, takes notes, sorts them and types up half a page. The work is not demanding, but it always falls due at the moment there is least time for it.
The harder part sits one level down. “Done” is not a value a system hands over, it is an interpretation. Does a task that was ticked off at four on Friday count if the invoice for it is still missing? Is a ticket set to “waiting on customer” closed or stalled? Is a quote that went out a result, or only the beginning of one? For as long as a person builds the digest, those questions get answered afresh every week, in someone's head, usually sensibly – and every week a little differently. Which is why two digests from two different weeks are barely comparable, even though they look identical.
Then there is the more uncomfortable half. Part of what belongs in a weekly digest exists in no system at all. The phone call with the annoyed customer, the agreement made in the corridor, the reason a job has not moved for five days – none of that is recorded anywhere and none of it can be read out. Automation cannot close that gap, but it can mark it. That is what this product is about: every block states which system it came from, which filter applied and when the source was read. Anything a person added is labelled as an addition. So in the meeting nobody has to argue about what is actually being discussed.
Which weekly digests are worth automating
We start with the digest that gets written every week anyway and has the most recipients. Further versions later draw on the same sources and the same definitions.
Monday overview for the team
The most common starting point: four to six blocks, always in the same order, delivered before the week begins. The digest replaces the gathering, not the meeting.
Weekly view for installation and service
Jobs signed off, appointments for the coming week and orders waiting on parts – pulled together from scheduling and stock control.
Service week from the ticket system
Tickets resolved and newly raised, plus the cases that have been waiting days for a reply. By team, not by person.
Weekly update for the client
The same data in a shortened outward version: what happened and what is coming, without internal notes and without the names of the people handling it.
Agenda for the recurring meeting
The digest is not an attachment to the meeting, it is its running order. What gets discussed is what sits in the blocks “stalled” and “needs a decision”.
Handover for cover and on-call
Before leave or a weekend shift, the same mechanics with a different cut-off: jobs in progress, promises made and appointments in the next few days.
What the finished digest looks like
The Monday digest of a service team as it appears in the team channel: four blocks, each with the source its lines came from underneath.
Completed in week 3018
- Meyer cold store, maintenance signed offFri 15:20
- Quote for ventilation, bay 2, sentThu 11:05
- 16 further jobs, each linked in the post
Due by Friday9
- Ruhland bakery, commissioningWed, 2 fitters
- Inspection report bay 2 to the clientThu
- 7 further tasks falling due this week
Untouched for over five days4
- Krause GmbH quote, no reply11 days
- Cooling plant repair, north bay8 days
- 2 further jobs with no change of status
Not in this digest2
- Open complaintssource silent
- Sickness and staff mattersexcluded
Three of the four stalled jobs are waiting on the same spare part delivery, promised for Wednesday. The Krause appointment was moved by the customer, not by us.
Source record: 3 of 4 sources read at 06:45, 1 source did not answer. Everything the grey lines vouch for comes out of a system; the note underneath was written by a person.
The grey line at the foot of each block is the real difference. It names the system, the filter and the time of reading – which makes it checkable why one line is in the digest and another is not.
The colours judge the state of the source, never the work of the team. Four stalled jobs are not a fault; a ticket system that does not answer is. That is why the complaints figure appears as a gap in the digest rather than as a zero.
From cut-off to delivered digest
-
Fix the blocks and their sources
For each block we record which system is authoritative, which filter applies and which period is read – for instance “Planner, bucket Service North, status done, Monday to Sunday”. This step takes the most discussion and determines everything that follows.
-
Read at the cut-off
At the agreed time every source is queried read-only, each with its own timestamp. Nothing is written back into a source system, so no new tasks and no status changes appear.
-
Filter rather than list
Only what has been completed since the last digest, falls due this week or has sat longer than agreed without movement makes it in. Everything else stays in the system, otherwise nobody reads the digest after three weeks.
-
Build the digest and attach the source
The checked lists become a post with a fixed structure: per block the lines, the direct links back into the original record, and underneath the source line with system, filter and time of reading.
-
Deliver, add context, archive
The digest goes to the team channel or out by email. On request the team lead receives it an hour earlier and can add two sentences that stay marked as a human addition. Every version is filed with its date.
What changes day to day
Today
- Monday morning spent clicking through five systems
- A slightly different structure every week
- Anyone who doubts a line has to go and look
- Stalled work only surfaces during the meeting
- No digest at all when the usual person is away
With an automated weekly digest
- The digest is in the channel before the meeting
- The same blocks in the same order every week
- Every line links back into the original record
- Anything sitting too long gets a block of its own
- The digest runs regardless of who is in the office
What an automated weekly digest will not do
We settle these four points before quoting. On the third one we regularly advise against the project:
- What nobody records nowhere appears. Tasks that only live in a chat or in someone's head cannot be collected by any digest. In the first few weeks the automated version therefore often looks thinner than the hand-written one – not because less happened, but because less was written down. That is a question of working habits, not of technology, and it cannot be configured away.
- The order of the blocks is not a priority list. Sorting follows due date, status and how long something has been sitting – whatever is measurable. What genuinely matters this week is beyond the digest, and we will not let it guess. That judgement stays with the team and happens in the meeting, for which the digest provides the basis.
- For a team with a single system it is not worth it. If every task sits in Planner and one person can pull a list from it in ten minutes, that does not justify €990. The effort and the benefit only appear once three or more systems are involved, several teams need the same structure, or recipients outside the team are included. With one source and five people we recommend a saved filter and a recurring calendar entry.
- The digest is not a performance report per person. As standard we do not build a view that sets tasks, hours or tickets against individual employees – not for technical reasons, but because a digest that gets read that way makes the underlying data worse. If you do need a person-level view, settle it first with your works council and your data protection officer; after that we can talk about building it.
Fits your source systems
Scope and price
The entry price covers one digest with up to six blocks from up to three sources, including the source line, the recipient list and the archive.
- One digest with up to six blocks in a fixed structure
- Read-only connection to up to three source systems
- Source line per block: system, filter and time of reading
- Direct links from every line back into the original record
- Schedule, recipients and delivery in Teams or by email
- Approval window for the team lead to add context
- Documentation, handover session and 30 days of support
What increases the price
- More than three sources, or sources without an interface
- A separate digest with its own structure per team
- A shortened version for clients alongside the internal one
- Calculated values instead of counted records, such as weekly utilisation
- An archive with week-on-week comparison instead of single delivery
Several teams with their own structure, or an extra version for clients, typically land in the range of our Workflow Advanced package from €2,490. We quote the binding fixed price after the intro call.
All prices excl. VAT · operation and further development optionally via a support package
What you get
-
Digest definition per block
Authoritative system, filter, period and cut-off – the document that lets you verify any line later
-
Weekly delivery in production
Schedule, channel and recipients set up and signed off with two complete test runs
-
Rules for silent sources
What happens when a system does not answer at the cut-off, how the gap appears in the digest and who is told about it
-
Handover session for your team
How to add a block, change a filter and take on a new recipient
Frequently asked questions about the automated weekly digest
These solutions fit alongside
Automated Status Reports
One level up: metrics for management instead of individual jobs for the team.
Automated Meeting Notes
What gets decided in the meeting becomes a task in the source of the next digest.
Automated Tasks & Reminders
So the block “untouched for over five days” never grows long in the first place.
Support Tickets in Teams
For teams whose week happens in the ticket system rather than in a task list.
Who writes the Monday digest in your team?
In the free intro call we go through your last weekly digest block by block: which line came from which system, which filter sits behind it and what somebody added from memory. Afterwards you will know whether automating it pays off – or whether a saved filter is the more honest place to start.
Book a free intro callWhere automated team digest creates value in everyday work
The workflow reads approved sources at a defined cut-off, bundles tasks, dates and metrics, and distributes a structured report with direct links.
Three concrete operating scenarios to compare with your own process.Send a Monday overview
Open tasks, dates and blockers are ready before the team meeting.
Summarise the sales week
Pipeline movement, open quotes and next activities are consolidated.
Monitor the project portfolio
Milestones, risks and overdue actions become visible across projects.
A strong fit when …
Recurring office tasks follow clear rules, consume small blocks of time every day and should run reliably without replacing existing systems.
- You handle recurring team digests using repeatable rules.
- The intake, target system and accountable business role can be named clearly.
- Exceptions are allowed to remain visible and move to people deliberately.
Deliberate automation boundary
Automatically generated text marks assumptions and missing data. Performance assessment, root-cause analysis and confidential people data stay outside the standard digest.
Explore the technical approach and platformsEstimate time savings with your own volume
The calculator uses 90 minutes today and 20 minutes after automation as fixed example assumptions. It does not replace process analysis.
Illustrative estimate based on the visible assumptions — not a guarantee.