Tasks · Today · Calendar

Deadlines tracked by the system, not by memory.

Every job for every client in one queue — kanban or list, recurring or one-off — with approvals that leave a trail and statutory deadlines pulled straight from Companies House. The Today screen tells you what needs a human this morning; the calendar's DUE band shows what the month will cost you.

Practice — Tasks

This week, banded by whose problem it is34 open · 3 waiting on approval · deadlines from Companies House

This week6

VAT return — HarbourviewDue Thursday

Bank rec — Meridian & CoToday

Payroll run — FenwickDue Friday

Waiting on client4

Missing bank statements — Oak & IronChased Monday

Approval to file — Delta FabricationSent yesterday

With reviewer2

Year-end accounts — Marlow InteriorsSign-off requested

CIS return — BrightworkApproved

The queue

Assignee and approver are different columns

A bottleneck should be visible by reading, not by asking around. Every task carries who's doing it and who signs it off; recurring jobs regenerate themselves; task groups keep a client's year in one band. Import the backlog by CSV and it's all in by lunch.

Kanban and list over the same queueRecurring jobs and task groupsApprovals with an audit trailCSV import

Deadlines

Companies House does the remembering

Confirmation statements and accounts deadlines arrive from the register itself, become tasks, and stand in the calendar's DUE band — repeats collapsed to a count so a heavy month reads at a glance. Booked work sits below in the hour grid. Nothing is typed in twice; nothing lives in someone's head.

Statutory deadlines synced per clientThe DUE band — obligations, not appointmentsTasks and calendar are the same data

Every morning, already triaged.

Today's answers-waiting view, the queue and the DUE band — from your first connected client.

Deadlines tracked by the system, not by memory.