Weekly, monthly, and quarterly reports: what to include in each

Home / Everything About / Everything About Analytics / Weekly, monthly, and quarterly reports: what to include in each

Your ecommerce company did twenty thousand dollars in revenue last week. You include this in the weekly report.

Next month you look back. Last week of the month revenue was twenty-five thousand. Week before was eighteen thousand. Week before that was twenty-two thousand.

Weekly reports showed different numbers every week. You thought performance was erratic.

But monthly total was eighty-five thousand. Last month was eighty-three thousand. Month before was eighty-one thousand. You were actually on a steady growth trajectory of two thousand dollars monthly growth.

Weekly reports created false urgency. Monthly report showed true pattern.

Weekly reports: catching emergencies in real time

The job of weekly reports

Weekly reports have one job: catch problems before they become disasters.

You run a lead generation company. Weekly report shows leads dropped fifteen percent this week. Last week was one hundred leads. This week is eighty-five leads.

Is this an emergency. Maybe. Maybe not. You need to know right away.

Wednesday of that week you read weekly report. You investigate. You find out ad platform had a bug on Monday and Tuesday that broke tracking for half your campaigns. Bug was fixed Wednesday. You fix tracking retroactively. Crisis averted.

Without weekly report, you would not have found the bug for a week. You would have lost four days of data and possibly continued paying for broken campaigns for another week.

Weekly reports catch problems in hours, not days. Cost of finding problem early: zero. Cost of finding problem one week later: thousands of dollars.

What to include in weekly reports

Headline metric and variance: revenue this week: twenty thousand. Goal: twenty-five thousand. Status: behind by five thousand (twenty percent below goal). Immediately tells reader: we are below goal. Needs investigation.

Variance explanation: why are we below goal. Which days were below goal. Revenue was twenty-three thousand Monday through Thursday. Friday and weekend dropped to two thousand. Why. Black Friday campaign ended Friday morning. Expected drop. Seasonal pattern. Explanation prevents false alarm.

Performance against last week and last month average: this week: twenty thousand. Last week: twenty-two thousand. Four-week average: twenty-one thousand. This week is slightly below average. Not alarming. Historical context prevents over-reacting to normal variation.

Any breakdowns or alerts: did any system break. Did traffic drop unexpectedly. Did conversions plummet. Did error rate spike. Alert on abnormal events only. Do not alert on normal weekly fluctuation.

Action items if any: did anything break that needs fixing. Did anything succeed that should be scaled. Do not include action items for things that are normal or expected.

Length: one page. Five to ten metrics maximum. Weekly report should be skimmable in five minutes. If it takes longer, you included too much.

Monthly reports: understanding the true pattern

When weekly variation confuses and monthly clarity helps

Example: weekly reports show:

Week one: revenue increased ten percent. Excited. Week two: revenue decreased twelve percent. Concerned. Week three: revenue flat. Confused. Week four: revenue increased five percent. Relieved.

Monthly report shows: revenue overall increased one percent month over month. Weekly ups and downs were normal variation around one percent growth trend.

Without monthly report, you would have made four different decisions based on four weekly reports. With monthly report, you make one decision based on one percent growth trajectory.

What monthly reports should include

Opening: was the month successful. Revenue goal was one hundred thousand. Revenue was ninety-eight thousand. Two thousand short of goal. By how much. Ninety-eight percent achievement. Opening tells story. Were we successful or not.

Month over month and year over year comparison. This month: ninety-eight thousand. Last month: ninety-five thousand. Three thousand growth. Three percent month-over-month growth. Last year same month: ninety thousand. Eight thousand growth. Nine percent year-over-year growth. Trajectory is positive both month over month and year over year.

Seasonal context. Is month normal. December revenue is typically higher due to holiday shopping. March revenue is typically lower due to post-holiday slowdown. This month is January which is typically recovery month. Revenue of ninety-eight thousand is above expected for January based on last three years. January average was eighty-five thousand. This month is thirteen percent above January average. Positive surprise.

Channel breakdown: which channels drove revenue and how efficient were they. Email: twenty thousand revenue. Ten thousand spent on email platform and staff. Return on investment: two hundred percent. Paid search: thirty thousand revenue. Thirty thousand spent on ads. Return on investment: one hundred percent. Organic: thirty thousand revenue. Four thousand spent on content staff. Return on investment: seven hundred fifty percent. Affiliate: eighteen thousand revenue. Zero cost. Return on investment: infinite. Clear winner: organic. Most efficient channel. Budget should increase. Worst performer: paid search. Breaking even. Budget should decrease until efficiency improves.

Page performance: which pages earned revenue and which were waste. Product pages: seventy thousand revenue. Total traffic to product pages: five thousand. Conversion rate: four point two percent. Strong. Blog pages: eight thousand revenue. Total traffic to blog: thirty thousand. Conversion rate: zero point two percent. Weak. Checkout pages: fifteen thousand revenue. Traffic to checkout: five thousand. Conversion rate: three percent. Strong but traffic is low. Recommendation: increase traffic to product pages. They convert well. Maintain blog for SEO. It drives brand but does not convert. Fix checkout flow. Traffic is low relative to product page traffic. Could be drop-off point.

Test results: which tests won and lost. Headline test: treatment beat control by five percent. Winning confidence level: ninety-seven percent. Recommendation: implement. Button color test: control beat treatment by zero point three percent. Confidence level: eighty-two percent. Recommendation: inconclusive, retest. Checkout flow test: treatment beat control by two percent. Confidence level: ninety-nine percent. Recommendation: implement immediately.

What to focus on next month. Based on this month, what should change next month. Email was most efficient. Increase email spend. Paid search was least efficient. Audit keywords and bidding. Organic was most efficient. Increase content production. Product pages converted well. Increase traffic to product pages. Blog did not convert. Stop investing in blog traffic, maintain for SEO. Checkout test won. Implement to improve conversion rate.

Quarterly reports: understanding seasonal effects and strategic progress

When monthly trends mislead and quarterly reality shows truth

Quarterly reports show whether monthly trends are sustainable or seasonal anomalies.

Example: monthly reports show: January: ninety-eight thousand. February: one hundred two thousand. March: one hundred eight thousand. Looks like strong growth trend. But quarterly report shows: first quarter average revenue is one hundred two thousand. This is typical for Q1. Seasonal effect. Not unusual growth.

Contrast with Q4: October: one hundred fifteen thousand. November: one hundred thirty thousand. December: one hundred forty-five thousand. Q4 average is one hundred thirty thousand. Significantly higher than Q1 at one hundred two thousand. Q4 is peak season. Q1 is normal season. Year over year: Q1 this year was one hundred two thousand. Q1 last year was ninety-one thousand. Q1 growth is eleven thousand. Eleven percent growth year over year. Sustainable growth above seasonality.

Without quarterly view, you would miss that Q1 this year is strong compared to Q1 last year despite being weak compared to Q4.

What quarterly reports should include

Opening: did we accomplish quarterly goal. Quarterly revenue goal: three hundred fifty thousand. Actual revenue: three hundred forty-eight thousand. Two thousand short. Ninety-nine point four percent achievement. Did we hit goal. Yes essentially.

Quarterly versus same quarter last year. Q1 this year: three hundred forty-eight thousand. Q1 last year: three hundred thousand. Forty-eight thousand growth. Sixteen percent year-over-year growth. Quarterly growth is strong indicator of health. Month to month can be noise. Quarter to quarter shows true pattern.

Annual progress. If annual goal is one point four million, and Q1 was three hundred forty-eight thousand, we are on pace for one point three nine million. We are at ninety-nine percent of annual goal pace. If we hit pace, we will meet annual goal.

Strategic initiatives and their impact. What major initiatives launched this quarter and what was their impact. New product launched month two of quarter. Generated fifteen thousand revenue. Currently at two percent of total revenue. Ramping up. Website redesign completed month one of quarter. Improved conversion rate by one point two percent. Annualized impact: six thousand revenue increase. New marketing channel tested all quarter. Cost per acquisition is twelve dollars versus historical eight dollars. Not efficient yet. Need to optimize or shut down. New team member hired in month one. Managed blog and generated eight thousand of revenue. Will annualize to twenty-four thousand with ramp.

Competitive or market context. Did anything change in market this quarter. Main competitor launched new product. Captured market share from us. Lost two thousand of revenue to them. Response: launching competitive product next quarter. Industry trend accelerated. Demand for our product category up thirty percent. We only grew sixteen percent. We are losing relative market share but growing in absolute terms.

Budget allocation review: were we efficient with spending. Q1 budget: one hundred thousand to acquire three hundred forty-eight thousand revenue. Return: three point five times. Efficient. But email channel returned five times. Paid search returned one point five times. We over-allocated to paid search. Next quarter reallocate.

What to focus on next quarter. Implement new product improvements based on Q1 learnings. Launch competitive product. Shift budget from paid search to email. Investigate organic channel for efficiency improvements. Continue website improvements. Conversion rate lift is paying off.

Timing creates or destroys value

Late reports destroy value. Weekly report sent on Friday shows previous week data but sent at end of week when stakeholders are already thinking about next week. Monthly report sent on 15th of next month shows data from two weeks ago when situation has already changed. Quarterly report sent three weeks into next quarter is old news.

Timing matters.

Weekly report: Monday morning. Shows previous week (Monday through Sunday). Delivered early so team can act. Monthly report: first business day of next month. Shows complete previous month. Early enough for strategies to execute. Quarterly report: first business day of next quarter. Shows complete previous quarter. Strategic discussions can happen about next quarter.

Frequently asked questions

If we have real-time dashboards, do we still need weekly reports?

Should weekly reports include forward projections or just historical data?

How do we handle unexpected events in reports (press coverage, competitor went down, etc)?

If quarterly report shows we are off pace for annual goal, when should we take action?

Should we report on metrics that vary widely by season differently in peak vs off-season?

How do we prevent report fatigue where people stop reading reports?