How to use this guide
This is general operational guidance for New Zealand SMEs. Adapt it to the business and the decisions involved. It is not a complete compliance checklist, legal opinion or a substitute for advice about a particular situation. Examples are illustrative and do not describe client engagements or promised outcomes.
What belongs in a routine work review?
Separate information sharing from decisions. A routine work review can focus on current priorities, blocked tasks, changing capacity and decisions due before the next review. Send background information through an appropriate shared channel where possible. Give each agenda item an owner and a question to resolve, so the meeting does not become a recital of activity without a clear next step.
Use a small set of consistently defined measures. For example, distinguish tasks completed from tasks started and explain why an item is blocked. Where a measure is uncertain or incomplete, say so. The discussion should help the team identify a workable response, not encourage people to improve a number by moving work outside the report or hiding difficult cases.
How do decisions turn into follow-through?
Close each decision with an action, a responsible person and a review point. Record what would trigger escalation before the next routine meeting. At the following review, ask what changed, whether the action helped and whether another decision is needed. Keep the action register short enough to use. Remove completed work deliberately and explain why a deferred item remains deferred.
- List recurring decisions and the people with authority to make them before choosing meeting frequency.
- Set a short agenda, common definitions and a reliable source for the information discussed.
- Review the rhythm after a trial: keep what improves decisions and stop routines that add no useful action.
A working structure
A compact review agenda
- What changed since the last review?
- Which work is blocked, and why?
- Which decision is needed, and who can make it?
- What action and support have been agreed?
- What must be escalated before the next review?
- Who updates the register and checks completion?
Illustrative example
Illustrative example: a small team replaces a long weekly status meeting with a shorter review of blocked work and decisions. Routine updates are recorded beforehand. One action register shows the decision, next owner and review date. After a trial, the team checks whether tasks are moving and whether urgent issues reach an authorised person sooner. The aim is better coordination, not a predetermined number of meetings or a promise that every delay will disappear.
Questions about this guide
How often should reviews happen?
Choose the frequency according to the work cycle and consequences of waiting. A daily operational check, weekly priority review and less frequent strategic discussion serve different purposes; none is a universal rule.
What if the same action keeps returning?
Recheck whether the action has an owner, authority, capacity and a clear definition of completion. Repeated reminders may conceal an unresolved dependency or a decision that the team cannot make.
Official sources and further guidance
These primary sources provide additional context. The operational suggestions and working outlines above are YJ Consulting’s general guidance; the links do not establish that an authority has endorsed this guide.
When YJ Consulting can help
YJ Consulting can help an Auckland or New Zealand SME map the current practice, organise the relevant records and turn the findings into an agreed improvement plan. The engagement starts by confirming the question, responsible adviser, information available and useful outputs. Legal, payroll, financial or other specialist questions should be identified and assigned separately.
Explore the relevant service · Service-scope information · Book an initial conversation