Built from inside practice. Built by Mr H Hammad FCCA, ACA, ICAEW Chartered Accountant with over 20 years in practice.
ProductFor ClientsClient PortalResourcesWhy BalansixPricingAcademySupportFree practice guideBook a demoLogin
BalansixAcademy

Run a focused weekly practice review

Use Balansix tasks, stages, ownership and client context to turn a busy work list into a clear weekly action plan.

Intermediate18 minute lessonPractice Management and Clients

What you will learn

A useful practice review ends with named decisions and next actions. Learn to prioritise deadlines, distinguish missing information from review work, and leave each task with the right owner and evidence of its current position.

By the end, you can

  • Prioritise a mixed queue using deadline, stage and dependency.
  • Give preparation and review clear ownership.
  • Use client and engagement context before changing a task.

Before you begin

  • Understand your own task and client access.
  • Know how to open the Tasks view; detailed controls are linked below.
Use the example, then apply the method. The people, businesses and figures in this lesson are fictional. Work through the activity on paper before applying the method to authorised client work.

Read the queue as a set of decisions

Start with tasks due today and overdue tasks, then look at the next seven days. The earliest date needs attention, but the next action depends on the stage. A job awaiting a client document needs a precise request. A prepared job awaiting review needs reviewer time.

Balansix provides due-date, status, service and task-owner filters. Use them to answer one question at a time. For example, “Which tasks due in the next seven days have no task owner?” is more actionable than looking at the whole list and relying on memory.

Open the client context before changing a deadline or stage. Check the period, agreed service and source of the deadline. A stage should describe the current work, while a due date describes when that work must be done.

Worked example: a Monday review

Imagine you manage three fictional client jobs. These are training dates, not filing-deadline guidance.

Monday’s practice queue
ClientPositionDecision
Maple DesignDue Tuesday; awaiting information; owner SamAsk for the two named missing records today and agree who follows up.
Orchard ServicesDue Wednesday; awaiting approval; reviewer unassignedAllocate an authorised reviewer and reserve review time.
River StudioDue Friday; not started; no task ownerConfirm scope and allocate preparation work now.

Maple has the nearest deadline, yet Orchard’s unassigned review is also urgent. Spending the whole meeting chasing Maple would leave a preventable bottleneck at Orchard. Work on both dependencies, with one person accountable for each.

Connect the task to the client record

Before assigning River’s work, check the client’s agreed services, relevant people and engagement position in Client Administration. A client appearing in a list is not evidence that every service has been commissioned.

Suppose the note says “annual accounts agreed; payroll discussed”. Allocate the annual accounts work covered by the engagement. Ask the responsible colleague to resolve the payroll scope before treating it as agreed recurring work. This prevents a helpful conversation from silently becoming an obligation.

Where your role permits, use Task owner, Reviewer, Priority and Budgeted hours to make the allocation explicit. The reviewer is a separate responsibility: allocating preparation to Sam does not by itself establish who will review Sam’s work.

Write a stage note that survives the meeting

A stage note should explain the reason for the current position. “Chased” says little. “Requested invoice refs 201 and 203; client agreed to supply them Tuesday morning” tells the next colleague what to expect.

When the invoices arrive, check that both are usable before moving the task forward. When the work is prepared, identify the reviewer and the evidence they need. Mark the final stage only when the service outcome is actually complete. This also keeps recurring work and reminders aligned with the true position.

At the end of the review, read back decisions rather than totals: Maple’s evidence request has an owner; Orchard has a reviewer; River has a preparer and agreed scope. A smaller task count would not prove any of those decisions had been made.

Exercise: resolve a misleadingly tidy queue

Your case. A task due Thursday is marked “In progress”. Its preparation is complete, the review has not started and the owner is on leave from Wednesday. A second colleague proposes leaving it unchanged because it is already assigned.

Write three actions that make the position clear. Include what should change in the task and what you would confirm with the team.

Model answer. First, confirm the prepared work and supporting evidence are ready. Second, move to the available stage that accurately reflects the review requirement, with a short note naming what is ready. Third, arrange an authorised reviewer and confirm cover before the owner’s leave begins. Retain preparation responsibility in the history instead of making the reviewer reconstruct it.

The expected result is a review that somebody can start today, with the right client, period, evidence and deadline. If you lack allocation permission, send that specific request to the responsible manager.

Check your understanding

A prepared job is due soon and has no reviewer. Which action most directly removes the next dependency?

Read the answer and explanation

Confirm the evidence is ready, allocate an authorised reviewer and agree review time.

The next dependency is review. Clear evidence, ownership and time address that dependency; a priority label alone does not.

Continue learning