A Weekly Business Operations Review You Can Run with Your VA
You finish the week having answered messages, attended meetings and moved plenty of tasks. But you still cannot confidently say which projects are ready, which are blocked and what needs your attention next.
A weekly business operations review gives you and your VA a shared view of the work. It should help you make decisions and remove obstacles. It does not need to become a long meeting or a complicated dashboard.
Prepare the facts before the meeting
Ask your VA to update the project board and prepare a short summary before the review. The summary should point to source records rather than recreate every task in another document.
Include completed milestones, blocked items, overdue actions, upcoming commitments and decisions needed from the owner. Note anything that changed since the previous review, such as a client supplying assets late or a launch date moving.
A task marked complete should have a defined result. “Email drafted” is different from “email approved and scheduled”. Keep those distinctions visible so the review reflects the real state of the work.
Start with exceptions and commitments
Review anything that could affect a promise made to a client, customer or team member. That might be an upcoming delivery date, an access issue or a decision holding several tasks up.
For each exception, ask what happened, what it affects and what can be done next. Avoid letting the whole session become a recital of every activity completed during the week.
If an issue has no immediate solution, agree who will investigate and when it returns for a decision. An unresolved question still needs an owner.
A practical agenda for a small team
Delivery: which milestones were completed and which are at risk?
Incoming work: which new enquiries, client requests or projects need a next step?
Blocked work: what information, access or approval is missing?
Next week: which commitments need preparation now?
Capacity: does the planned work fit the available time?
Decisions: what must the owner approve, choose or clarify?
Actions: who does what next, and by when?
Adjust the agenda to your business. A store approaching a promotion might give more attention to customer communication and product-page readiness. A service business might focus on proposals and client delivery.
Make decision requests easy to answer
“Please advise” often sends the work back to the owner without enough context. A useful decision request includes the situation, available options, a recommendation where appropriate and the effect of waiting.
An illustrative request could say: “The launch page needs the final session time before the reminder email can be approved. Option A is the original time; option B is the revised time requested by the presenter. Please confirm by Tuesday so the page and email can be updated together.”
Your VA can organise the facts and coordinate the change after your decision. They should know which choices they can make independently and which require your authority.
Review capacity as well as deadlines
A list of urgent tasks is not a capacity plan. Look at the time available, the size of the work and any competing commitments.
When a new request arrives, identify what it displaces or whether it needs additional support. Agree the priority with the owner rather than quietly moving several deadlines.
Keep a small number of outcomes for the coming week. This gives your VA a clearer way to assess new requests. If everything is described as equally important, they will still need to ask you which task wins.
Use a few measures with clear definitions
Choose measures that answer the review's questions. Examples include overdue actions, projects waiting for inputs, upcoming milestones and leads with no next step.
Define what each measure means and link to the underlying records. A count of “active projects” is useful only if everyone agrees which projects are active. Keep confirmed outcomes separate from work in preparation.
Our lead follow-up workflow shows how to give each enquiry an owner and next action. For customer communication, the inbox management guide can help clarify what needs escalation.
Record the actions while the decision is fresh
At the end of the review, update the task system with the actions you agreed. Include the owner, date and relevant source link. Send a short recap if it helps the team confirm the same understanding.
A useful recap can contain three parts: decisions made, actions assigned and issues still awaiting a decision. Keep background detail in the linked project record.
If the next review repeatedly discovers the same forgotten action, check how the action enters the working system. A recap email alone may not be enough.
Turn repeated problems into process improvements
If every launch is blocked by missing offer details, improve the launch brief. If customer questions repeatedly need the same response, prepare approved guidance. The review should help you notice patterns and change the process.
Choose one manageable improvement and assign it like any other task. Use our SOP template to document the new step and test it with the person who will use it.
When a meeting is not necessary
If the facts are clear and no decisions require discussion, an asynchronous written review may be enough. Keep the same structure and agree a time by which the owner responds to decision requests.
Use a conversation when the trade-offs are unclear, several people are involved or the issue is difficult to resolve in writing. The format should fit the decision, not become a rule for its own sake.
Make the first review small
Begin with your current projects, blocked items and next week's commitments. After two or three reviews, keep the sections that lead to useful decisions and remove the ones nobody uses.
VAmazing supports the coordination and systems behind everyday business operations. Get in touch if you want your weekly review to lead to clearer actions and fewer loose ends.
