Weekly Business Review Template: Track Cash Flow, Projects, Leads, and Priorities
small businessoperationsbusiness templatesweekly reviewproductivity workflows

Weekly Business Review Template: Track Cash Flow, Projects, Leads, and Priorities

TToolkit Top Editorial Team
2026-11-21
7 min read

Use this weekly business review template to track cash, projects, leads, customer issues, capacity, and next-week priorities.

A weekly business review turns scattered updates into a short, repeatable operating habit. This guide provides a practical weekly business review template for checking cash flow, projects, leads, customer issues, workload, and priorities without building an elaborate reporting system.

Overview

A small business dashboard does not need dozens of metrics. It needs a consistent view of the few conditions that determine whether work is being delivered, money is moving, customers are supported, and the next week is properly focused.

Set aside 30 to 60 minutes once a week. Use one spreadsheet, project board, or document as the review location. The tool matters less than the operating rule: record the same fields, compare them with the previous review, and turn material changes into named actions.

Keep the review separate from daily task management. Daily tools answer, “What am I doing next?” The weekly review answers, “Is the business moving in the right direction, and what needs attention before next week?” This distinction prevents a long task list from hiding financial, delivery, or customer risks.

A simple weekly scorecard

Begin with a compact scorecard. Use a status of green, amber, or red, plus a short note explaining the status.

  • Cash: Green if expected receipts and available cash support near-term commitments; amber if timing is uncertain; red if a shortfall or overdue payment needs action.
  • Delivery: Green if important projects are on schedule; amber if a milestone is at risk; red if a commitment requires renegotiation.
  • Sales: Green if priority opportunities have a clear next step; amber if leads are aging; red if the pipeline is too thin for the planned workload.
  • Customers: Green if open issues are progressing; amber if an issue lacks an owner or deadline; red if a serious problem is unresolved.
  • Capacity: Green if the coming week is realistic; amber if work is unevenly distributed; red if deadlines exceed available capacity.

This scorecard is a decision aid, not a performance grade. Its purpose is to direct attention to exceptions and make changes visible from one week to the next.

What to track

1. Cash collected and cash due

Record money collected during the week and money expected but not yet collected. Separate confirmed receipts from estimates. Useful fields include customer or source, invoice reference, amount, due date, payment status, and the next follow-up date.

Do not treat revenue, invoiced work, and cash collected as interchangeable. A project can be profitable on paper while creating a short-term cash problem if payment is delayed. If you use invoices or quotes regularly, a reusable freelancer business toolkit can help keep payment information consistent.

2. Project and delivery status

List active projects or major workstreams with five fields: current status, next milestone, owner, due date, and blocking issue. Add a confidence note such as “on track,” “at risk,” or “needs decision.” Avoid copying every task from a project tool; the weekly review should show whether an outcome is moving, not reproduce the entire backlog.

For fixed-fee work, also check remaining effort against the agreed scope. If the estimate is drifting, review the assumptions before the project becomes urgent. An hourly-to-project price calculator can support future estimates, but the weekly review should focus on the commitments already in progress.

3. Leads and sales activity

Track the number of active opportunities, their current stage, estimated value if you already use that field, and the next action date. More important than a raw lead count is whether each priority opportunity has a specific next step, such as a discovery call, proposal revision, technical answer, or decision date.

Flag opportunities that have had no movement since the previous review. Either schedule a useful follow-up, move the opportunity to a later stage, or close it as inactive. This keeps the pipeline from becoming an optimistic archive.

4. Customer issues and operational risks

Record open support issues, complaints, renewal concerns, defects, or repeated questions. For each item, capture the owner, customer impact, next action, and target resolution date. Repeated issues deserve a separate note because they may indicate a missing process or unclear documentation.

When a task is repeated, link it to an operations template or standard operating procedure. The small-business SOP toolkit is useful when a recurring issue should become a documented process rather than a weekly reminder.

5. Workload and next-week capacity

Compare confirmed work with realistic capacity for the coming week. Include meetings, support time, administration, planned leave, and concentrated work—not just billable or project hours. Mark overloaded areas early and decide whether to reschedule, delegate, reduce scope, or protect a focus block.

Finish this section by selecting three to five priorities for the next week. Each priority should describe an outcome, have an owner, and include a definition of done. “Work on onboarding” is vague; “publish the onboarding checklist and send it to the first three customers” is reviewable.

Cadence and checkpoints

Choose a fixed review time, preferably near the end of one workweek or at the start of the next. A reliable sequence reduces preparation time:

  1. Gather: Update cash, project, sales, customer, and workload fields from the systems already in use.
  2. Compare: Look at the previous review, not only the current snapshot. Note new, resolved, overdue, and repeated items.
  3. Decide: Identify the few changes that require a decision, escalation, or trade-off.
  4. Assign: Give every action one owner and one due date. If an action has no owner, it is an intention rather than a commitment.
  5. Schedule: Put important actions into the relevant calendar, project board, or follow-up queue before ending the review.

Use a monthly checkpoint to examine trends that are difficult to see week by week. Review overdue receivables, project slippage, lead aging, recurring customer problems, and capacity patterns. A quarterly checkpoint can be used for larger decisions such as changing priorities, reviewing pricing assumptions, or assessing whether a software subscription is earning its place in the workflow. For investment decisions, a break-even and ROI calculator guide can provide a structured way to test assumptions.

How to interpret changes

One unusual week is a signal to investigate, not automatic proof that a process is failing. Look for direction, repetition, and cause.

  • Cash collected falls: Check whether the cause is billing timing, delayed approvals, missing follow-up, or lower sales. Then assign the smallest useful corrective action.
  • Projects turn amber: Identify the specific constraint. It may be an external dependency, unclear scope, insufficient capacity, or a decision that has not been made.
  • Leads age without movement: Improve the next step or remove inactive opportunities. A larger pipeline is not necessarily a healthier one.
  • Customer issues repeat: Look for a documentation, product, training, or handoff problem. Track the pattern separately from individual tickets.
  • Capacity stays overloaded: Stop treating this as a personal productivity problem alone. Revisit scope, deadlines, staffing assumptions, meeting load, and work-in-progress limits.

Keep explanations short but concrete. A useful note says, “Two invoices are awaiting approval; follow up with the customer on Tuesday,” rather than, “Cash is a concern.” Specific notes make the next review faster and reduce repeated discussion.

Also avoid optimizing a metric in isolation. Faster delivery may increase rework; more sales activity may reduce customer support capacity; fewer meetings may delay a necessary decision. Read the scorecard as a connected operating picture.

When to revisit

Complete the review weekly, but update the template when the business changes. Revisit the fields after adding a product, changing pricing, taking on a new type of customer, introducing a new project system, or discovering that a recurring risk is not visible in the current scorecard.

At least monthly, remove fields that are never used and add fields that repeatedly appear in decisions. If the review regularly takes more than an hour, reduce detail before adding automation. A dashboard that is difficult to maintain will eventually become unreliable.

Use automation selectively. A project tool can supply milestone status, an invoicing system can supply payment data, and a calendar can show meeting load. Keep decisions and explanations human-reviewed. Automated fields should reduce copying, not replace judgment.

Copy-and-use weekly review template

Review date: ____   Reviewer: ____

  • Overall status: Green / Amber / Red — What changed since last week?
  • Cash: Collected ____; due ____; overdue ____; next follow-up ____.
  • Projects: On track ____; at risk ____; blocked ____; decision needed ____.
  • Leads: Priority opportunities ____; next actions ____; inactive items to close ____.
  • Customers: Open issues ____; repeated issues ____; owners and dates ____.
  • Capacity: Available time ____; committed work ____; conflicts ____.
  • Next-week priorities: 1. ____ 2. ____ 3. ____
  • Actions: Action / owner / due date / status.

Save each completed review with the same naming convention, such as “Weekly Review — YYYY-MM-DD.” After several weeks, the archive becomes a lightweight operating record: it shows what changed, which actions were completed, and where the same problems keep returning. Pair it with a focus workflow for deep work so the priorities you choose are protected in the calendar rather than left as intentions.

The best weekly operations checklist is deliberately modest. Start with the fields above, complete the review at the same time each week, and refine it through use. Consistency will reveal more than a complex dashboard that is updated only occasionally.

Related Topics

#small business#operations#business templates#weekly review#productivity workflows
T

Toolkit Top Editorial Team

Editorial team

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.