DGA Ltd All articles
Client Guidance

Before the Deadline: Reading a Client's Fiscal Year as a Scheduling Document

DGA Ltd

A delivery date is not the same as a usable date. That distinction matters most when the client is a UK business with a fixed financial rhythm. Work handed over on 29 January may be technically on time, but if the client's finance team is closing the Self Assessment window, the document will sit unread until February. By then, the assumptions behind it may already have moved.

For professional services firms, the lesson is straightforward: the client's fiscal calendar is a delivery constraint. It belongs in the schedule alongside resource availability, review time and sign-off. It is not a courtesy to be noted late in the engagement, and it is not an excuse to be offered after a missed step. It is a planning input.

Delivery is not the same as use

Most schedules are built forwards from the kick-off. The team estimates the work, adds review time, allows for a client comment period and publishes a date. That method answers a useful question: when can we finish? It does not answer the more important one: when can the client actually use this?

A management report delivered during the year-end audit may be read, but it will not be acted on. A contract review completed just before a VAT quarter close may be signed, but only after the finance director has surfaced from the return. A tender response submitted in the same week as a board pack may be accepted, but the client's attention will be elsewhere. In each case, the work is not wrong. It is simply late in practice, even when it is early on paper.

The constraint is not only the statutory deadline itself. It is the preparation window around it. Finance teams clear space before a filing date, not after it. Approvers become unavailable. Queries that would normally take a day take a week. A schedule that ignores this window is a schedule that assumes a client with unlimited attention.

Build a one-page fiscal map

Before a schedule is agreed, ask for a short fiscal map. It should fit on one page and cover the dates that affect attention, not just the dates that affect tax. For a typical UK client, the map should record:

Record the owner of each date and mark the weeks when finance sign-off is unlikely. A simple red, amber and green rating is enough. Red means do not plan a decision that week. Amber means plan it, but confirm the approver. Green means normal access.

The map should be agreed with the client, not assembled from memory. A short email with the provisional dates and a request to correct them is usually sufficient. That email also creates a record. If a later delivery slips because the client's own reporting crunch was not disclosed, the conversation is about the map, not about blame.

Work backwards from the crunch

Once the map exists, set a usable-by date before the delivery date. The usable-by date is the point at which the client can read, decide and act without competing against a filing deadline. Then work backwards from that date through client review, sign-off and final production.

This often changes the sequence more than the deadline. Evidence gathering and decisions should move earlier. Draft material should reach the client before the blackout week, even if the final version follows afterwards. Where a final document must land during a crunch, agree a named signatory and an asynchronous review route in advance. Do not assume that a meeting will be possible.

A useful test is to ask three questions of every milestone: who signs this off, what evidence do they need, and what happens if they query it? If the answer to any question depends on a finance team in a red week, the milestone is in the wrong place.

Put the constraint in the engagement record

The fiscal map should not stay in a planning folder. Summarise the key dates and blackout windows in the engagement letter or schedule. State that the client will provide the map, update it if dates change, and nominate a deputy approver for blackout periods. This is not bureaucracy. It is the same discipline we apply to scope and fees, applied to the client's own calendar.

When the map changes, the schedule should change with it. A moved year-end or a new group reporting date is a variation, not a private inconvenience. Record it, assess the effect and confirm the revised usable-by date in writing.

A calendar, not a courtesy

The most reliable schedules are not the ones with the most buffer. They are the ones that understand when the client is able to pay attention. A fiscal map takes perhaps thirty minutes to prepare and a few minutes to maintain. In return, it protects review time, reduces rework and prevents the quiet failure of work that was delivered on time but used too late.

At DGA Ltd, the practical test is simple: if the schedule does not show when the client can use the output, it is not yet a schedule. It is only a promise about our own activity.

All Articles

Related Articles

The Second Reader: Designing Deliverables That Survive the Forward

The Second Reader: Designing Deliverables That Survive the Forward

The Quiet Days: Auditing the UK Calendar Before a Delivery Date Is Promised

The Quiet Days: Auditing the UK Calendar Before a Delivery Date Is Promised

Reading Their Rulebook: A Pre-Commencement Review of Client Terms

Reading Their Rulebook: A Pre-Commencement Review of Client Terms