Weekly Business Review Template for Small Teams

A weekly business review keeps small problems from waiting until the end of the quarter. The meeting works best when everyone receives the scorecard and exceptions beforehand. Thirty minutes can then cover decisions and ownership because the data collection is already complete.

The weekly review has one job

Use the review to answer: What changed this week that requires action?

Long-term strategy belongs in quarterly planning. Full financial analysis belongs in the monthly report. The weekly review looks for near-term movement across revenue, customers, delivery, cash, people, and the few initiatives that matter now.

The one-page weekly template

1. Headline

Write three sentences:

• The most important positive movement.
• The most important miss or emerging risk.
• The decision or action that matters most this week.

2. Scorecard

Metric	This week	Target	Previous week	Status	Owner
Qualified pipeline created
Revenue or bookings
Customer retention signal
Delivery on time
Cash or collections measure

Five to nine metrics is enough for most small teams. Every metric needs a definition and owner.

3. Exceptions

List only the items outside the expected range:

• What moved?
• What evidence explains it?
• What is still unknown?
• Does it need a decision, an owner, or continued watching?

4. Priority progress

For each active company priority, show status, the next milestone, and the specific blocker. A green status with no evidence adds little. Include the completed milestone or measurable movement that supports it.

5. Decisions and actions

Close with a short table:

Decision or action	Owner	Due date	Evidence needed

A 30-minute agenda

• Five minutes: read the headline and confirm material data corrections.
• Ten minutes: work through red and yellow scorecard items.
• Ten minutes: decide the two or three open issues.
• Five minutes: read back owners, deadlines, and the message the wider team needs.

Send the report at least a few hours before the meeting. People should add questions early so the owner can bring the right evidence.

What to leave out

The weekly review becomes slow when it absorbs every department update. Remove items that have no movement, decision, or risk. Put detailed project status in the relevant project system and link it when an exception needs context.

Avoid turning the meeting into a forecast rebuild. Use the current agreed forecast and take a separate follow-up when assumptions need deeper work.

A prompt to prepare the review

Prepare a one-page weekly business review for [dates]. Use the selected Projects and connected sources. Start with a three-sentence headline. Show the agreed scorecard with this week, target, previous week, status, and owner. Include only material exceptions, documenting the available explanation and open questions. Summarize progress on [list priorities]. End with decisions and actions, including owners and due dates only when the source material names them. Mark missing data clearly. Send the report only to me.

Deck can use supported sources such as HubSpot, Notion, Slack, Granola, calendars, web research, and selected Project files. Each scheduled run creates a fresh report, so include the date range and any comparison material the task needs.

The weekly review routine offers a lighter personal version. For the monthly layer, use the monthly management report guide. For commercial reporting workflows, see business reporting automation.