A useful AI-assisted weekly report starts with checked data and agreed metric definitions. Use formulas or code for calculations, then ask the assistant to summarise observations, flag gaps and propose questions. A person checks the interpretation and approves the report before it is sent or used to change a campaign.
If the difficult part is copying the same totals into a slide, a spreadsheet connection or scheduled export may solve the problem without an agent. AI becomes more useful when a reviewer needs help turning validated tables and campaign notes into a clear first draft.
ChatGPT’s official data-analysis documentation describes working with uploaded spreadsheets and CSV files, including code-backed calculations. It also tells users to review the generated code, outputs and assumptions. A fluent paragraph is not a substitute for that check.
Define the report before connecting accounts
Choose one decision the report should support. For example: “Which acquisition sources need investigation before next week’s planning meeting?” Then agree the reporting period, Europe/London time zone, currency, source accounts and comparison window. Complete weeks should be compared with complete weeks unless the partial period is explicitly labelled.
Define each metric. A form submission, a sales-qualified enquiry and a sale are different events. Platform conversions may not match CRM outcomes because their definitions and attribution differ. Keep those differences visible instead of adding incompatible totals together.
Start with exports rather than live write access. Keep an unchanged source copy and create a working table with descriptive headers and one row per record. Remove unnecessary personal information. Confirm the tool and workspace are approved for the material before uploading anything.
Record source filename or query, extraction time, date range, filters and metric definition beside each table. Give failed or missing sources an explicit state. A blank export is not proof of zero activity, and last week’s file must not quietly appear beneath this week’s heading.
Reconcile the figures with a small example
Imagine two fictional campaigns in the same currency and period. Campaign A spent £300 and produced six qualified enquiries. Campaign B spent £200 and produced four. The combined spend is £500; the combined qualified enquiries are ten; cost per qualified enquiry is £50. These are illustrative inputs, not expected performance.
Calculate the combined rate from the combined numerator and denominator. Do not average campaign rates when their denominators differ. For a zero denominator, report the rate as not calculable and explain why rather than inventing a percentage. Keep zero and missing values separate.
Before generating commentary, check that campaign IDs are unique at the intended reporting level, required columns exist and summed spend matches the source total within an agreed rounding tolerance. Do not let renamed campaigns become duplicate campaigns. Compare the same event definitions and account filters across periods.
These checks can be spreadsheet formulas or validated code. If an assistant creates the code, ask to see it and verify it on a known small example. Ask which rows were excluded and why. A plausible total can still conceal missing records.
Brief the narrative and keep the review gate
Use a brief such as: “Using only the checked tables and approved campaign notes, draft a weekly report for the marketing owner. Separate observed changes, possible explanations and missing information. Link each numerical claim to its source table. Do not claim causation from a week-on-week change. Do not invent targets or change any campaign. Return a draft and questions for review.”
For the example above, “The two campaigns generated ten qualified enquiries at a combined £50 each” is supported. “The new creative caused a lower acquisition cost” is not supported unless you have further evidence. A useful report can recommend checking a hypothesis without presenting it as a result.
Ask the reviewer to verify the headline figures, definitions, exceptions and proposed next steps. If a source fails, label the draft incomplete and block a complete-report delivery. If recipients or content change after approval, seek approval again. Permission to read performance data does not imply permission to move budgets or contact customers.
Measure the preparation time and correction burden over several cycles, not just the speed of the first draft. Keep a log of recurring errors so you can improve the data contract or prompt. If the same discrepancy needs explaining every week, fix the reporting definition rather than letting the assistant write a new excuse.
Foundry’s AI agents and MCP service lists pulling reports as an internal use case. Bring one recurring report, its agreed definitions and the systems involved to scope an export-first pilot. The right outcome may be a small integration plus a reviewable narrative, not a fully autonomous marketing agent.
