Writing Weekly Reports with AI, Without Made-Up Lines

What inputs a weekly report needs

A weekly report shows what the team did this week and which decisions are waiting. AI can pull this together quickly. But it is only as accurate as the inputs you give it.

Before you start, collect your sources in one place. Meeting notes, the task list, the budget sheet and key emails are usually enough. Note the date and owner of each document.

State missing information openly. A note such as "delivery date not yet confirmed" makes it harder for the AI to fill the gap with a guess. In the same way, mark open points as "pending" or "not confirmed".

Keep the inputs limited to this week. If you add last month's notes, old information can slip into the report as if it were current. Using the same types of source every week also makes reports easier to compare.

Getting a draft from the AI

After pasting the sources, write a clear prompt. Set the report headings yourself: completed, in progress, risks and pending decisions. The draft then arrives in the same shape every week.

Add two rules to the prompt. First: "Use only the information in the documents I gave you." Second: "Next to every figure and date, name the document it came from."

Source labels make your check much easier. Any line without a label is a warning sign. The method works the same way in ChatGPT, Copilot or your company's own chat tool.

Do not treat the first draft as final. Its job is to save you time. The corrections and the last word are yours.

Checking figures and dates against the source

A draft can read smoothly. The real risk is a wrong figure or an invented date hidden inside a fluent sentence. So check the report line by line before it goes out.

Find every figure and date in its source. If it is not in the source, delete the line or mark it "not verified". If the source says something different, use the source value.

Watch rounded amounts, words like "about" and future dates closely. AI can describe work that was only planned as if it were finished. The example below shows exactly this.

Speed the check up with a simple table. Put the report's claim in the left column and the source evidence in the right. A row with an empty right column stays out of the report.

Writing decisions separately and clearly

The most valuable part of a weekly report is the list of decisions to be made. Do not bury them inside status updates. Write them one by one under their own heading.

For each decision, write three things: what needs deciding, who decides and by when. If there are options, list them briefly and neutrally. A single line such as "Extra budget: decided by the project manager, deadline Friday" is enough.

The AI may suggest a recommendation. But use words like "approved" or "agreed" only when the source contains a written approval. The decision always stays with the responsible person.

This split also helps your manager. They skim the status section and spend their time on the decisions. Open points are not lost and get followed up in the next report.

Checklist

Use the list below before you send the report. A few minutes of checking keeps a wrong line off your manager's desk.

Run the list in the same order every week. The check becomes a habit and no step gets skipped. Over time it takes you much less time.

Save your prompt as a template. Keep the headings and the two rules fixed, and only swap in the new sources each week. You can share the template with your colleagues too.

When you send the report, say clearly which lines are not yet verified. An open question is always worth more than an invented answer.

Checklist

1. I collected all sources, dated this week.
2. The prompt includes the rule "use only the documents given".
3. Every figure and date has a source label.
4. Lines without a source are deleted or marked "not verified".
5. Planned work is not described as finished.
6. Decisions sit in their own section, each with an owner and a date.
7. "Approved" appears only where a written approval exists.