17th September

The session pushed a deadlines first workflow in Engager, using Kanban due period views and inline deadline edits to drive daily priorities.

The recommended routine was clear “Due today” first, then either fix “Overdue” or work ahead for the week.

Phases were positioned as the main engine for handoffs, assignments, billing points, and automated status emails, with checklists treated as limited and mainly useful for onboarding pacing.

If your policy is to file accounts and CT600 together, merge them into one bundled service, align pricing, and consolidate schedulers to match.

Improve form requests by building reusable email templates, organising them with categories, and ensuring key placeholders like the form link are included.

Archive old forms to prevent staff sending outdated versions, using the form’s settings to mark it as archived.

For My Work planning, use “Ignore holdups”, filter to Status “In review” when needed, and switch to Group by Week for longer range capacity planning.

Control client portal folder visibility through folder templates by company type, hiding everything except the folders clients should see by default.

Track Zama progress inside Engager using client list columns for AML, onboarding, and risk assessment, and link multiple email profiles in Zama under a single “master” where one person has several addresses.

Xenon health score in Engager currently shows all time due to API limits, with period selection only possible once Xenon exposes it via the API.

Create tax due placeholders as single line text custom fields to preserve currency formatting and pence accurately.

General principle for building phases: create a new phase whenever responsibility changes hands, because that’s where the real control and audit trail comes from.