Records
Clients, entities and registrations
Each client carries its entities, and each entity its registrations, with the obligations that follow from them.
Why it matters here This hierarchy is the firm’s actual risk model, and it is usually collapsed into a single client row.
In practice Ninety-six clients producing four hundred registrations, each generating obligations on its own cycle.
Work
Filings, audits and certifications
Every obligation and engagement is work with a deadline, a start-by date, an owner, a state and recorded effort.
Why it matters here Scheduled and unscheduled work compete for the same people, and only one of them is usually in a system.
In practice Two hundred and twelve obligations due in thirty days alongside nine audits in fieldwork.
Workflows
Notices, queries and assessments
Unscheduled matters are workflow with their own dates, owners, escalation and document trail.
Why it matters here Notices carry hard dates and senior time, and a firm that does not plan them is planning most of its year.
In practice Three notices with hearing dates and no owner, surfaced nine days ahead rather than the week before.
People
Partners, managers and articles
The team is modelled once with availability, and every obligation, audit and notice shows who owns it.
Why it matters here Articles are a constrained, rotating resource and their allocation determines whether both audit and compliance land.
In practice Article allocation across fieldwork and compliance, so a conflict is visible before it is committed.
Relationships
Clients, groups and promoters
Clients are records with their entities, obligations, responsiveness, fee basis, notices and balances.
Why it matters here A group is one commercial relationship and many compliance exposures, and both views are needed.
In practice A group whose entities collectively generate forty obligations a year, with recovery measured across them.
Control
Review, sign-off and access
One permission model and one audit trail, with review and sign-off as recorded steps.
Why it matters here Professional sign-off carries personal liability, and it should be a record rather than a signature at the end of a rush.
In practice Every sign-off carries the reviewer, the working papers referenced and the time.
Reports and analytics
Exposure, capacity and recovery reporting
Obligation coverage, deadline compliance, notice load, audit progress, capacity against calendar and recovery come from the operational records.
Why it matters here The number a CA firm most needs — total obligations against capacity in the coming quarter — cannot be produced from a client list.
In practice Committed obligation hours against team availability, including expected notice load.
Verity AI
Ask the practice a question
Verity AI answers from your own registration, obligation, audit and notice records, respects permissions, and can create assigned follow-ups.
Why it matters here The questions worth asking cross registration, date and person at once, which no spreadsheet answers quickly.
In practice "Which obligations due inside fifteen days have not started?" returns thirty-eight, with records chases raised.
Communication
Client correspondence on the obligation
Requests, reminders, responses and notice correspondence attach to the obligation or matter they concern.
Why it matters here Correspondence with a client about a specific registration is evidence, and it should not live in one person’s inbox.
In practice The client’s response about a registration change, on the obligation it affects.
Locations
Offices and fieldwork sites
Offices and client premises are locations, with work, allocation and reporting following the same structure.
Why it matters here Audit fieldwork happens away from the office and consumes the same people the office needs.
In practice Articles allocated to fieldwork sites, visible against the office’s compliance load.