Home › Blog › Automating weekly reports

Automating the weekly report — template and prompt included

Weekly reports automate better than meeting notes, because the structure is a person re-transcribing information that already exists somewhere. Here is the structure and the prompt, in full.

Template included Prompt published Repeats weekly

The short answer

Most of the time spent writing a weekly report is not thinking time — it is gathering time. Finding what happened last week, reformatting it, and re-checking the numbers. Those three steps are the automation target.

Based on Divii Consulting engagements, automating meeting notes and weekly reporting cut document work by 70%. Weekly reports repeat on a fixed day in a fixed format, which makes them one of the better-conditioned automation targets there is.

The structure — three stages

Collect — Decide where last week’s activity is recorded: completed items in your collaboration tool, meeting notes, commit logs, ad and revenue dashboards. This stage is not about consolidating them — it is about fixing the locations to read from.

Generate — Summarise the collected raw material into a fixed format. The prompt is decisive here. Without specifying the format you get a differently-shaped report every week, which increases review time rather than reducing it.

Review and send — The owner reviews the draft for five minutes and sends it. Aiming for fully unattended sending costs you trust. Keeping the review step is what makes it last.

A prompt you can use as-is

The prompt below has three devices in it, for format stability and to prevent invention: it specifies the order of sections, it makes unsupported items stay blank, and it derives next week’s plan from last week’s unfinished items.

Prompt: "Draft a weekly report from the following raw material. Fix the format in this order: (1) completed this week (2) in progress (3) next week’s plan (4) issues and requests. Write each item on one line with the owner in parentheses. Never guess or fill in anything not supported by the raw material — leave that section blank instead. Use only figures present in the raw material, and where a calculation is needed, show the calculation. Derive ‘next week’s plan’ primarily from in-progress items and last week’s unfinished items."

The weekly report template

Section	Content	Writing rule
Completed this week	Work finished and its outcome	One-line summary plus owner. Include the resulting figure where there is one
In progress	Progress and expected completion	Never estimate progress — state it only where the raw material has it
Next week’s plan	Three to five items, in priority order	Derived from in-progress and unfinished items
Issues and requests	What is blocked and what decision is needed	Name who the request is directed at. Leave blank if none

Where it commonly fails

There is no raw material — In an organisation where nothing is recorded in the collaboration tool, the collect stage does not exist. The recording habit comes before the automation.

It fills gaps by guessing — Without "leave it blank if unsupported" in the prompt, you get plausible sentences. Nothing destroys trust faster.

The format changes weekly — If the reader has to interpret a different structure each week, the saving evaporates. Format stability matters more than quality.

The review step is removed — Switch to fully automatic sending and one error ends the trust. Keeping the five-minute review is what makes it durable.

How far a tool alone gets you

If there is one place to collect from and a person can copy and paste it, a free summarisation tool is enough. Five to ten minutes a week.

If there are three or more sources, or a draft has to arrive automatically at the same time every week, you need a build. That is where integration with collaboration tools and dashboards enters, and it is the line between a tool and a pipeline.

Frequently asked questions

Can we use the prompt exactly as written?

You can. But after the first week, rename the sections to your own internal terminology. Using words the reader already knows cuts review time further.

What if a number comes out wrong?

That is why the prompt includes "use only figures present in the raw material" and "show the calculation". With the calculation left in, the review step catches it in five seconds.

Teams use different formats — do we have to standardise?

Better to, but not essential. Keep a separate prompt per team. Once you pass about five prompts the management burden appears, and that is the point to consider standardising.

Can reporting up the chain be automated too?

Once team reports accumulate in a fixed location, aggregating them into a department draft follows. But reporting upward involves interpretation and judgement, so a draft is the realistic limit.

Try it on this week’s report

Past three collection sources, you are into a build

Tell us where the raw material for your weekly report is scattered and we will separate what a tool can do from what needs building.

Automation enquiry