TL;DR:
A good weekly report is short, comparable week to week, and built in three moves: pull the numbers, check them, then summarize.
Keep the same format every week so readers learn where to look and changes stand out.
Always compare against last week, and say in one sentence what you think the numbers mean.
Every Friday someone has to turn three separate numbers into one page: what sold, what customers asked about, and what marketing brought in. Done badly, the report is a data dump nobody reads. Done well, it takes twenty minutes and people actually use it.
When you need this
Any time more than one team needs a shared picture of the week. Managers want to see whether things are going up or down, and they want it on one page, not in three different tools. The same method works for a monthly report; only the time window changes.
Before you start
Decide the reader. A manager wants direction and surprises. A teammate may want detail.
Pick a few numbers per source. Two or three each is plenty. More numbers hide the story.
Fix the week. Say exactly which days the report covers, such as Monday to Sunday, so every source uses the same window.
Find where each number lives. Know which report or screen gives you each figure before Friday.
Step by step: pull, check, summarize
Pull: Copy this week's and last week's numbers from each source into one sheet, side by side. Label each with its source and date range.
Check: Make sure each number is for the same window, in the same unit. Compare against last week for sanity. If something jumped, find out why before you report it.
Summarize: Write one or two sentences per source: what changed, by how much, and your best guess why. Lead with the biggest change.
Add one next step: End with what you will do, or what you need someone else to decide.
Worked example: sales, support and marketing numbers in one page
The numbers below are an example for a small online shop, not real data. Your sheet has three rows, one per source, with this week and last week.
Source | Measure | Last week | This week | Change |
|---|---|---|---|---|
Sales | Orders | 100 | 120 | +20 |
Support | New tickets | 100 | 85 | −15 |
Marketing | Site visits | 5,000 | 4,000 | −1,000 |
Now check the arithmetic. Orders: 120 − 100 = 20, and 20 ÷ 100 = 0.20, so orders rose by one fifth. Tickets: 85 − 100 = −15, and −15 ÷ 100 = −0.15, so tickets fell by 15 in every 100. Visits: 4,000 − 5,000 = −1,000, and −1,000 ÷ 5,000 = −0.20, so visits fell by one fifth.
A third check connects two rows. Orders per visit: this week 120 ÷ 4,000 = 0.03, which is 3 orders per 100 visits. Last week 100 ÷ 5,000 = 0.02, or 2 per 100. Fewer people visited but more of them bought. That is the interesting finding, and no single source shows it alone.
Now write the page:
Week of 2 to 8 (example)
Headline: Fewer visits, more orders.
- Sales: 120 orders, up 20 from 100.
- Support: 85 new tickets, down 15 from 100.
- Marketing: 4,000 visits, down 1,000 from 5,000.
What it means: orders per 100 visits rose from 2 to 3, so
the people who came were more likely to buy. We do not yet
know why visits dropped.
Next: check which source of visits fell. Decision needed:
none this week.Everything on that page can be traced back to the sheet, and every sentence either states a number or says what the number might mean. Nothing in it is a guess dressed up as a fact.
Same format every week
Use the same headings in the same order, with the same measures, every week. Readers then scan for the change instead of learning a new layout. If you must add a number, add it at the bottom, and keep the old ones.
A template also protects you. When it is Friday afternoon and you are tired, the template reminds you to compare against last week and to write the "what it means" line.
Writing the sentence that matters
The "what it means" line is the part readers remember. Write it as a claim that the numbers support, and mark how sure you are. "Orders per 100 visits rose from 2 to 3" is a fact from the sheet. "Customers like the new page" is a guess, so it needs evidence or a softer word such as "maybe".
If two sources move in opposite directions, say so plainly. That is usually where the next question comes from, and a reader who sees it spelled out can decide what to look into next week.
Where the numbers come from
Name the source under every figure, such as the order report or the helpdesk summary, and the date you pulled it. If a number is later revised, you can then see whether the source changed or you copied it wrongly. Copy values by hand only when you have to, and re-check any you typed.
Mistakes to avoid
Mixing time windows, such as sales from Monday to Sunday and support from Sunday to Saturday.
Reporting a change without the base. "Up 20" means little until the reader knows it is up from 100.
Calling a cause a fact. If you do not know why visits dropped, say so.
Changing the measures every week, so nothing can be compared.
Leaving out bad news. A report that hides drops stops being trusted.
Doing it faster
Once the template exists, the work is mostly copying and checking. If you want a hand with the checking, DuckyHelper is one way to do it: with the sheet on your screen, you can ask out loud whether the changes add up or whether a number looks off, and you can stop it at any moment when it works in your apps. You can download it and try it for 10 minutes, no card.
Frequently asked questions
How many numbers should a weekly report have?
Few enough to read in a minute. Two or three per source is a good start; add more only if someone needs them to decide something.
What if sources use different date windows?
Choose one window for the report and re-pull each source to match it. Do not mix windows on one page.
