You Track Your Clients' Deadlines Carefully. Nobody Tracks Yours
· 7 min read · Written by Faceela Research & Editorial Team
Reviewed by Ahmed Hassan Algammal — Founder and Enterprise Systems Consultant
Walk into any established compliance practice in this country and you will find a wall of deadlines. Client returns, client renewals, client filings, tracked in a way that is genuinely impressive given the tools most firms are using.
Then ask the same firm when its own trade licence expires, and watch what happens. Somebody checks a photograph on a phone. Somebody else says the PRO usually reminds us.
That asymmetry is not carelessness, and it is not funny. It is structural, and once you see the structure you cannot unsee it: the client work is somebody's job and the firm's own work is nobody's, and neither of them is written down in a form that survives the person who knows it.
An obligation is not a task, and the difference is four fields
Take one obligation — any one, a return or a renewal, it does not matter which — and ask what you would need to write down to hand it to somebody else tomorrow morning.
You need the trigger: what starts the clock. Not the deadline; the thing that produces the deadline, which is usually a period ending or a date printed on a document.
You need the lead time: how long the work takes before the deadline, and therefore when it actually has to start. A deadline with no lead time is a reminder that arrives on the day the work should already have finished.
You need the owner: the named person, and the named person who covers them.
And you need the evidence — both halves of it. What has to arrive before the work can be done at all, and what you keep afterwards to prove it was done.
Most firms hold the deadline. Some hold the owner. Almost nobody holds the lead time or the evidence, and those two are the ones that decide whether the obligation is actually under control or merely known about.
The shape of it
One obligation has five fields. A task has one and a half
1. Trigger
What starts the clock?
On a task list
A date somebody typed in, once. When it is ticked, nothing creates the next one — the tick is the end of the record.
In an obligation register
A rule tied to a period or a dated document. The next occurrence exists before anyone remembers it, because the rule made it, not a person.
2. Lead time
How long does the work take before the deadline?
On a task list
Not held at all. The reminder arrives on the due date, which is the day the work should already be finished.
In an obligation register
A working start date carried separately from the deadline, so the deadline is the end of the work rather than the beginning of the panic.
3. Owner and cover
Who does it, and who does it when they are away?
On a task list
Assigned to whoever created it — often a partner, who is not the person who does the work and is not reading the list.
In an obligation register
A named owner and a named deputy. Leave becomes a handover with a list attached rather than a month with a hole in it.
4. Evidence in
What has to arrive before it can be done at all?
On a task list
Not modelled. Waiting on the client is invisible, so an obligation blocked for six weeks looks exactly like one nobody has started.
In an obligation register
The inputs listed against the obligation, each with a state. Blocked is a status somebody can be asked about, not a private worry.
5. Proof out
What shows, later, that it was actually done?
On a task list
A tick. Six months on it proves that somebody clicked something, which is not what anyone asking will want.
In an obligation register
The filed document, its reference and its date, held against the obligation itself — so the answer to a query is retrieved rather than reconstructed.
And the property a task list cannot have
An obligation regenerates. Closing this year's creates next year's, with its owner, its lead time and its inputs already set. A task list is emptied by being finished; a register is never empty, and that is the entire difference.
A task list is emptied. A register is never empty
Here is the distinction the whole article turns on.
A task list is a set of things to do, and its natural end state is empty. That is what a task list is for. Ticking the last item is the reward.
An obligation register is a set of things that are true about the business. Closing this period's occurrence creates next period's, with its owner, its lead time and its inputs already attached. It cannot be emptied, because the obligations have not gone anywhere — only this cycle of them has.
Firms that run compliance on a task list are not doing something lazy. They are doing something that works perfectly for eleven months and then produces one silent failure, because a task list has no mechanism for regenerating itself. Somebody has to remember. And the moment "somebody has to remember" enters the design, you have built a system whose reliability is a person's attendance record.
What actually repeats
None of this is exotic. Every firm knows this list. The question is not whether you know it, it is whether it exists anywhere other than in the head of the person who knows it.
| What repeats | What starts the clock | What proves it was done |
|---|---|---|
| VAT returns | The end of each tax period assigned to the registration | The submitted return and its acknowledgement |
| Corporate tax registration, then filing | Incorporation, then each financial year end | The registration confirmation, then each filed return |
| Economic substance notifications, for the years they applied | The financial year end, for a relevant activity | The submitted notification and its reference |
| Ultimate beneficial owner records | A change in ownership or control, plus periodic confirmation | The updated register and the filing receipt |
| Trade licence and establishment card | The expiry date printed on the document itself | The renewed document, dated |
| Visas, Emirates IDs, labour cards, medicals | Per person, per issue date — dozens of independent clocks | The renewed card, filed against the employee |
| Audited financial statements | The financial year end | The signed audit report |
| AML registration and periodic confirmations, for designated firms | Registration, then each confirmation cycle | The portal record |
Eight families. In a firm of twenty people that is not eight obligations, it is several hundred occurrences a year, most of them small, none of them optional, and about a third of them attached to individual human beings whose dates have nothing to do with each other.
Note what the third column is doing. Every row has an artefact, and the artefact is what somebody will ask you for — an auditor, a bank, a buyer in due diligence, a regulator. A tick in a spreadsheet is not that artefact. It is a record that somebody once believed the artefact existed.
The month the owner is on leave
Test any obligation you like with one question: if the person who normally does this were away for the whole of the month it falls due, would it still happen?
For an obligation that is scheduled, the answer is yes. It appears, it has an owner, the owner is out, the deputy sees it.
For an obligation that is remembered, the answer is no — and worse, nobody finds out. There is no queue it fails to leave, no exception report it lands on, no red line anywhere. The first evidence is a notice, or a renewal that has already lapsed, or a question during due diligence that nobody can answer from a document.
This is the same shape as every failure in this cluster. It is not that people are careless. It is that a system with no state cannot report a state, and a firm that has genuinely no idea whether something was done is indistinguishable, from the inside, from a firm where everything is fine.
Why the firm's own renewals are the ones that go
There is a reason the shoemaker's children go barefoot, and it is not irony.
Client obligations have three things the firm's own obligations do not. They are billable, so they compete successfully for attention. They have an external party who chases — the client rings. And they belong to a named engagement with a named manager, because that is how the firm organises work.
The firm's own licence renewal has none of the three. It is a cost, nobody outside chases it, and it belongs to "the office" — which is to say to the managing partner, who is the single busiest person and the one least likely to be reading a task list.
So the firm's own obligations sit in the one category the practice has no machinery for: unbilled, unchased, unowned. Putting them into the same register as the client work is not tidiness. It is the only way they acquire the three properties that make client work reliable. Where that register also drives the invoice — the compliance calendar that generates the fee as well as the work — the firm's own rows are the ones that stay unbilled, and they stay visible anyway because they are on the same list.
What to make a vendor show you
On a live system, with real obligations, not on slides.
- Close one occurrence of a recurring obligation and show the next one already existing, with its owner and its start date set.
- Show an obligation whose start date is not its deadline — and show the report that lists work that should have started and has not.
- Reassign an owner for one month and show every obligation that moved, before the month starts.
- Show an obligation blocked on a client document, as a state somebody can be asked about rather than as an empty field.
- Attach the filed artefact to the occurrence, then retrieve it two years later from the obligation rather than from a folder.
- Show the firm's own obligations — licence, cards, visas, the audit — in the same register as the client work, filtered in one click.
- Show every obligation falling in the next ninety days across the whole practice, by owner, with the ones that have not started marked.
Item 1 decides it. Everything else on the list can be faked with a well-maintained spreadsheet by a diligent person, which is exactly what most firms already have. Regeneration is the one property a spreadsheet cannot have, and it is the property that removes the person from the critical path.
Item 4 is the quiet one. Most systems pass 1 to 3 and have no concept of an obligation waiting on somebody else — so the two states that matter most in a practice, not started and cannot start, are recorded identically.
The short version
A recurring obligation has four parts. Most firms hold the deadline and hold the other three in a person.
The difference between a task list and an obligation register is not features. A task list is emptied by being completed; a register regenerates, so the next cycle exists whether or not anybody remembered it. That single property is what takes the firm off a person's attendance record.
And the firm's own renewals go missing for a reason that is structural rather than ironic: they are unbilled, unchased and unowned, which is the one combination a practice has no machinery for.
What that looks like built rather than remembered is on the professional and business services page, and the system is ServX. If the obligations are known but the work around them is the problem, process automation is the narrower engagement. The neighbouring pieces are corporate tax readiness, surviving an FTA audit with your ERP, and — for the deadlines that carry a document rather than a filing — VAT and e-invoicing on Odoo.