
What to Include in a Monthly Business Review for a Small Service Business
A monthly business review gives you and your team time to compare what you planned with what actually happened, then decide what needs to change. Keep the review tied to a few business goals, use records you can check, and finish with actions someone has agreed to own.
If you're the woman running the business and also the person everyone comes to for a decision, this review can help you share the reasoning behind those decisions. Your team needs to understand the priorities well enough to act on them between meetings.
AI can help organize the review notes. The judgment about what to continue, change, or stop stays with you and the people responsible for the work.
Start with the goals you already chose
Pull up the goals and commitments from the previous month. Which results were you trying to achieve? What work did the team agree to do? Keep those questions separate. Completing a campaign is an activity; getting qualified inquiries from it is a result.
If the goal was vague, say so. “Improve marketing” doesn't give the team a clear way to judge progress. You can make the next month's goal more specific without rewriting the past to make it look successful.
Business.gov.au's goal-setting guidance recommends measurable goals and regular reviews of progress. For this meeting, choose the measures that tell you whether your own goals are moving. A smaller set that the team understands is more useful than a report full of unexplained numbers.
Build a review sheet from records you can check
Use the same reporting period for each comparison. A full calendar month and the first three weeks of the next month aren't directly comparable. Label missing or incomplete records before discussing the results.
For each goal, record:
The intended result and the period it covers.
The actual result, with a link to the report or record supporting it.
The work completed and any work still open.
What the team knows about the difference, plus questions that remain unanswered.
A proposed decision and the person who needs to approve it.
Choose measures appropriate to the goal. Sales records might tell you how many suitable buyers became customers. A delivery review might track whether agreed milestones were met. Use customer feedback to understand a concern, but don't treat one comment as a finding about every customer.
Keep definitions visible. If your team counts an inquiry as qualified only after a conversation confirms fit, don't mix that count with every form submission. Someone reading the sheet next month should be able to understand how the number was produced.
Use the meeting to make a decision
Consider this fictional example. Lena owns a small design business with a project manager and two designers. The team wanted four qualified inquiries for a defined service during the month. Their records show three, along with eight other inquiries that haven't met the agreed qualification criteria.
The campaign went out as planned. Two prospective buyers asked what they would need to prepare before starting. Lena and her team don't yet know whether that question affected anyone's decision to buy.
The review should keep those facts intact. It shouldn't count all eleven inquiries as qualified or declare that preparation requirements caused the missed target. Lena can ask the team to make the existing preparation explanation easier to find and record the questions buyers ask during the next month.
That's a decision the team can carry out and review. “Try harder with marketing” gives them very little to work with.
Make room for delivery problems too. If sales activity is bringing in work the team can't deliver within its current commitments, increasing promotion may need to wait. Decide which constraint deserves attention before adding another task to everyone's list.
Ask AI to organize the notes without filling gaps
Use an AI tool approved by your business and share only the information appropriate for that account. Remove customer names or other identifying details when the review doesn't need them.
Once the review sheet is checked, this prompt can help turn it into meeting notes:
Use only the monthly review sheet I provide. For each goal, summarize the intended result, actual result, supporting record, and unresolved questions. Separate recorded facts from the team's explanations or hypotheses. Don't infer causes, invent missing figures, or count unfinished work as complete. Put proposed decisions in a separate section. Finish with an action list showing the action, agreed owner, due date, and review measure. Mark any owner or date that hasn't been agreed as unconfirmed. Preserve links to the source records. Flag contradictions for a person to resolve.
Compare the output with the original sheet. In Lena's example, a draft that says “the campaign generated eleven qualified leads” needs correcting before it becomes part of the team's record. Smooth wording doesn't make a changed definition accurate.
If the notes suggest a new action, bring it back to the team for a decision. An AI-generated assignment doesn't establish that someone agreed to take it on.
Carry the decisions into next month's work
Put approved actions where the team already manages its work. Assign an owner and a realistic due date, then state what you'll review next time. Keep unresolved questions open rather than quietly dropping them from the summary.
Lena's project manager might own the preparation-page update once they agree to it. The sales owner can record preparation questions during buyer conversations. At the next review, they can check whether the update was completed and what buyers asked. They still need evidence before attributing any change in sales to that page.
Use your repeatable business systems to keep the review consistent. Save the sheet, decisions, and source links together so next month's meeting starts with a usable record.
Need help choosing which sales, marketing, or AI work deserves attention next? Connect with Dani to discuss the business decision your team is working through.
