The reader is not your dashboard
Most weekly reports fail because they are written for the person who made them. A VP does not have time to reconstruct the story from six charts and a blended ROAS line.
Write as if the reader will give you ninety seconds. If the first paragraph does not name the change, they will skim the rest or skip it.
Open with the sentence they can forward
Start with what happened in money and time, not in channel jargon. Then say whether that is good, bad, or mixed.
A usable opening usually includes:
- The change in money and time
- Whether that is good, bad, or mixed
- The cause in one sentence
- The action you want this week
- What to ignore until next week
- Who owns the follow-up
- When the next report lands
We spent $142K on ads last quarter. The short version: every dollar brought back $2.30, and it cost 14% less to acquire each customer than the month before.
Name the cause, then the action
After the opening, explain the cause in one paragraph. Paid social carried efficiency. Search held volume. Display lagged. That is enough.
Then name the action. Hold spend. Refresh two ad sets. Pull branded search back to exact match until CPA cools. A report without a next step is a recap, not a memo.
Keep supporting numbers in the document, not as the document. The chart can wait until the story is clear.
Keep the middle short
If the VP was not in the working session, they still need the same three answers. Write as if they will forward the memo without you on the thread.
- What changed this week
- The important decisions made together
- The work delivered
- The measurable or observable outcomes
- What you want them to do
Avoid a long list of tasks. The purpose is to make the change visible in the reader's language.
When final results will take time to appear, separate immediate outputs from expected future outcomes and agree on when they will be reviewed.
Write for the person who was not in the meeting
A concise weekly report helps stakeholders act. It may include the period, the spend, the return, the cause, and the ask.
Write it so it can be shared with people who were not in the data. That is the whole job.
Review before it leaves your desk
Have a teammate comment before it goes out. Ask whether the opening can be forwarded, and whether the action is actually an action.
Useful questions include:
- Can the first sentence be forwarded without a chart attached?
- Is the cause one sentence, or a tour of every channel?
- Does the action name a person, a date, and a dollar amount?
- What should stay in the working file and never leave the desk?
- Which number would change the decision if it moved ten percent?
- What should the VP ignore until next Monday?
Create space for honest feedback without immediately defending the process. Clarify examples and capture specific improvements.
Separate the draft from the send
The version you send should read like a memo. The working file can keep extra charts and unfinished questions.
Run the review the same afternoon you close the numbers. A weekly memo that waits until Thursday is already late for a Tuesday staff meeting.
Assign ownership for operational improvements. A lesson that remains in meeting notes rarely changes future work.
Reuse a template, not last week's file
Reuse a template so the shape stays familiar. Same audience, same questions, new numbers. That is how a weekly report becomes readable.
Do not wait until quarter-end to fix the shape. If last week's memo was too long, shorten this week's before you paste the new numbers.
If a number is confidential, leave it in the working file. The version that goes out should be safe to forward to finance without a second briefing.
End with one decision
End with one decision. Keep spend concentrated where the story is already working, and review display before the next cycle.
For each recommendation, explain:
- The problem or opportunity
- Why it matters now
- The likely outcome
- The suggested timing
- The level of effort or investment
Some readers need a weekly memo. Others need a tighter note. The recommendation should match how they actually read.
Send it on a schedule, not when you have time
Send it on the same weekday every week. The VP should know the memo lands Monday at 8am, not whenever the dashboard finishes refreshing.
Look at what they need next Monday, what is still unresolved, and what new question showed up in the numbers. Then pick one owner for the follow-up.
Give them enough time to act without burying the ask in a long appendix.
Give someone else a place to comment
Every report should leave the system with a named owner and a next send date. Without ownership, even a clear memo can disappear.
Schedule the next send around a real event: a weekly close, a launch, a budget cycle. A relevant memo is more useful than another dashboard ping.
Use the same shape every week
Twelve weeks of the same three questions is more useful than one brilliant recap. The VP already knows where the decision lives.
Use the follow-up to confirm the action happened. If you asked to hold display spend, the next memo should say whether it was held.
Close the loop in the document
Archive last week's draft. Keep the current memo as the only version in the thread. A VP should never have to guess which attachment is live.
A clean record makes last week's numbers easy to find when a new question shows up, and keeps the current memo the only version in the thread.
The report is the product
The weekly memo is the product. Charts are supporting evidence. If the document cannot stand alone in an inbox, it is not finished.
Teams that send the same shape every week get answers faster, because the reader already knows where the decision lives.