The MTD quarterly deadline just landed again. Who was actually rostered for it?
Saturday 7 November was the second MTD for Income Tax quarterly update. The software worked. The real question is whether anyone had deliberately decided, in advance, whose week that was — or whether it fell on whoever happened to notice. Eighteen more of these are coming. Build the rota once rather than discovering the gap four times a year.
The second MTD for Income Tax quarterly update was due Saturday 7 November 2026, for sole traders and landlords with qualifying income over £50,000. The filing itself is a short summary with no tax calculation attached, and most practices have the software sorted. What most have not built is a staffing rota for it — a named, rotating owner per quarter so the same one or two people are not quietly absorbing all twenty deadlines a year on top of their existing book. Treat each quarter date as a staffed event with a named lead, a cover plan, and a capacity check run the week before, the same way a firm already rosters January.
What actually happened this week
The second MTD for Income Tax quarterly update fell due on Saturday 7 November 2026. It applies to sole traders and landlords whose qualifying income exceeded £50,000 — the same first-wave population that filed its opening update back in August. A quarterly update is a brief summary of income and expenses for the period, not a full return: there is no tax calculation and nothing to pay at that point, and HMRC has said there is no need to ring and confirm a submission went in — the firm's own software or the client's online account shows the filing history. Corrections to an earlier quarter do not need resubmitting either; they simply flow into the next update.
Software is no longer where this gets difficult. There are several HMRC-recognised options, including free tools for simpler cases and bridging software for anyone still working from a spreadsheet, and most practices chose one months ago. HMRC even staffed phone support from 9am to 3pm on the Saturday itself, which is a tacit admission from HMRC of what this really is: not a technical problem, but a day that needs people available who normally wouldn't be.
That is the part worth pausing on. The arithmetic of whether a practice has the hours for this has been covered elsewhere and does not need repeating here. What has not had the same attention is the much more ordinary question underneath it: on 7 November, whose job was it? Not "the team's", in general — whose, specifically, with a name against it before the week started.
Twenty filing dates is a staffing problem, not just a capacity one
A firm that has done the capacity maths knows roughly how many hours the quarterly cycle costs across a year. Hours are not the same thing as a rota. A practice can have plenty of spare capacity in the building and still handle every quarterly deadline badly, because the hours exist in the wrong person's diary, on the wrong day, with no plan for when that person is on leave, off sick, or simply buried in something else that week.
Most practices currently run this the way they ran everything before MTD: it lands on whoever owns the client relationship, handled alongside their normal book, noticed because the date is in a diary somewhere rather than because a shift was planned for it. That works at one filing event a year. At four plus a final declaration, per client, it quietly becomes a second job that nobody was given the hours for and nobody is tracking as a cost.
The fix is not more people. It is treating each of the four recurring dates — 7 August, 7 November, 7 February and 7 May — as a staffed event with its own rota, the same way a firm already staffs the final week of January, rather than as background noise sitting on top of everyone's existing workload.
A worked example: building the rota for a two-office firm
Take a five-partner practice running across two offices — illustrative figures, not client data, but the shape is a common one. 210 clients are in scope for MTD for Income Tax, split roughly 130 in the larger office and 80 in the smaller one. Left unmanaged, those 210 clients default to whichever manager already holds the relationship, which in practice means two senior staff carry well over half the quarterly load between them, every quarter, indefinitely.
| Role | Office | Clients owned this quarter | Backup |
|---|---|---|---|
| Quarter lead (rotates) | Office A | 130 | Named deputy, briefed by the Friday before |
| Quarter lead (rotates) | Office B | 80 | Named deputy, briefed by the Friday before |
| Records chase (standing, not rotated) | Both | All 210, continuous | Escalates to quarter lead at day minus 7 |
The rota change is one decision: the quarter lead role rotates between four senior staff across the two offices, one quarter each, rather than permanently sitting with whoever onboarded the client. The records-chase role does not rotate, because chasing benefits from continuity and a single owned process — see how to structure a growing firm's team for the broader principle of which roles rotate and which stay fixed. The quarter lead's job for that one quarter is narrow and specific: confirm every file is either filed or has a named reason it isn't, by the Friday before the deadline, and escalate anything stuck to a partner rather than quietly absorbing it themselves on the Saturday.
Run that pattern for a year and each senior person carries one deadline quarter in four instead of all four, every deadline has a deputy who could step in without a frantic handover, and a partner reviewing the Friday-before report can see the state of the quarter at a glance instead of finding out on the Monday after.
February is the one that breaks an unplanned rota
The 7 February quarterly update sits seven days after the 31 January self assessment deadline, in the same week the team that just worked January would normally expect some recovery. A rota built casually — "whoever's free" — has nobody free that week, because everybody who could plausibly lead it has just finished the hardest fortnight of their year.
This is the clearest argument for deciding the rota months in advance rather than at the point of need. Whoever is named quarter lead for February needs to know in November, not in late January, so their post-January diary is planned around it rather than assumed to be clear. A firm that reaches January without having already named the February lead will find out, in real time, that nobody wants the job and everybody assumes somebody else has it.
Build the rota this month
- Name the four quarter leads now, one per deadline (7 Aug, 7 Nov, 7 Feb, 7 May), rotating across senior staff and both offices rather than defaulting to relationship ownership.
- Name a deputy for each lead, briefed the Friday before, not discovered on the day the lead is unexpectedly unavailable.
- Put a capacity check seven days out on the calendar for every deadline — filed, on track, or flagged — reported to a partner, not held in one person's head.
- Protect the February lead's diary in advance. Confirm who it is before Christmas, and keep their first full week of February clear of anything else that can move.
- Keep the records-chase role standing, not rotating. It is a continuous process with its own escalation point into whoever the quarter lead is that quarter — put it on the same weekly numbers as the rest of the firm's operating review.
- Review the rota after each quarter, not just before it. Ask what nearly went wrong, not just what did — near-misses are the cheapest warning a rota ever gives.
The honest framing
Nobody is going to get credit for a quarterly deadline that passed quietly. That is exactly why it is the kind of work a founder-led practice tends to under-resource: it produces no visible win when it goes well, and a very visible one when it doesn't. A named rota is how a practice turns twenty routine filing dates into twenty non-events, rather than twenty occasions for the same one or two people to quietly work a Saturday nobody scheduled them for.
The deadline on 7 November is done. The one on 7 February is not optional and is not far away. The firms that come out of this well will be the ones who named who owns it before the date arrived, not the ones who found out on the day who was willing.
Common questions
When is the next MTD for Income Tax quarterly deadline after 7 November?
7 February 2027, with the final deadline of the cycle — the final declaration for the first cohort — following on 31 January 2028. The four quarterly dates are fixed every year regardless of a client's own accounting date: 7 August, 7 November, 7 February and 7 May. Because 7 February lands exactly a week after the 31 January self assessment deadline, it is the one date in the cycle that a practice cannot staff on the fly; whoever leads it needs to be named and protected well before the January rush begins.
Do we need to ring HMRC to confirm a quarterly update has gone in?
No. HMRC has said explicitly there is no need to contact them to confirm a submission has been received — the filing history is visible through the practice's own software or the client's online account, the same way it already is for other HMRC filings. The one exception worth knowing about is that HMRC ran phone support from 9am to 3pm on the 7 November deadline itself, for anyone who did hit a genuine problem on the day, which is a reasonable thing to flag to whichever team member is rostered as that quarter's lead.
What happens if a figure in an earlier quarterly update turns out to be wrong?
It does not need resubmitting. A correction to a previous quarter's update flows into the next update rather than requiring the firm to go back and refile the quarter it relates to. That matters for how a rota should treat errors: the quarter lead who spots a mistake in last quarter's figures should log it and fold it into the current filing rather than treating it as an emergency that needs unpicking on its own, which is usually a wasted sense of urgency.
Should the same person lead every quarterly deadline, since they'll get faster at it?
Speed from repetition is real but it is a smaller gain than the risk it creates. A practice where one person leads all four deadlines has built a single point of failure into a regime that now runs twenty times a year rather than once, and that person's leave, illness or departure becomes a genuine filing risk rather than an inconvenience. Rotating the lead role across three or four senior staff costs a small amount of repeated familiarisation and buys a firm that can absorb one person being unavailable on any given deadline without a scramble.
Where does your firm actually stand?
Score it across the ten things a COO would look at first. Three minutes, an honest read on where you’re strong and where you’re exposed, and a 90-day plan for the areas holding you back.
Or book a confidential call if you’d rather just talk it through.