England and Wales · Civil enforcement
When must enforcement notice allow twenty-eight clear days?
Regulation 6(1A) requires the notice minimum to extend to twenty-eight clear days when a qualifying provider requests it before the stated notice period expires, subject to paragraph (1B).
- Period
- At least twenty-eight clear countable days before taking control
- Trigger
- Actual proposed control date, with an established timely qualifying request
- Rule
- TCG Regulations 2013, regs 2, 6(1A)–(3)
Official Justice UK CPR text and legislation.gov.uk statutory XML retained on October 9, 2026. The retained source metadata and acquisition receipts identify each edition. No claim of later amendments or actual local court opening is made. Taking Control of Goods text includes the May 1, 2026 changes made by SI 2026/366. Earlier notice-giving regimes require separate review.
Free calculator · No account needed
Calculate your deadline
Loading calculator…
What lawyers say
5.0“The platform is really easy to use.”
Michael B.Employment litigation attorney · California
“The Evidence Record saved us time with our insurance on bankruptcy matters.”
MariaBankruptcy and commercial attorney · London, UK
“The most up-to-date service we could find.”
Li ChenArbitration practitioner · Singapore
When must enforcement notice allow twenty-eight clear days?
Regulation 6(1A) requires the notice minimum to extend to twenty-eight clear days when a qualifying provider requests it before the stated notice period expires, subject to paragraph (1B).
Responsible actor. The enforcement agent applying the eligible debt-advice notice extension.
Actual proposed control date, with an established timely qualifying request.
The request is an eligibility condition, not a new date from which twenty-eight days automatically run. Preserve the original notice period, actual provider request and debt classification.
The request is an eligibility condition, not a new date from which twenty-eight days automatically run. Preserve the original notice period, actual provider request and debt classification.
TCG Regulations 2013, regs 2, 6(1A)–(3)How does this provision count time?
- Exclude notice and control dates, and omit intervening Sundays, bank holidays, Good Friday and Christmas Day. Twenty-eight countable intervening dates must remain.
- Ordinary Saturdays count. An eligible notice for control on November 30, 2026 cannot be reduced to twenty-eight unadjusted calendar dates. Actual permitted notice giving remains necessary.
Exclude notice and control dates, and omit intervening Sundays, bank holidays, Good Friday and Christmas Day. Twenty-eight countable intervening dates must remain.
Ordinary Saturdays count. An eligible notice for control on November 30, 2026 cannot be reduced to twenty-eight unadjusted calendar dates. Actual permitted notice giving remains necessary.
TCG Regulations 2013, regs 2, 6(1A)–(3)What do independently checked examples show?
Fictitious example
The enforcement agent applying the eligible debt-advice notice extension. For the established proposed event Monday, November 30, 2026, the latest notice day is Tuesday, October 27, 2026. Count exactly 28 intervening eligible dates. Sundays and bank holidays are excluded; ordinary Saturdays count. Additional fictitious established facts. Qualifying provider request actually received. 2026-10-21T10:00:00Z. Original notice stated expiry. 2026-10-22T17:00:00Z. Established notice method. personal. Fictitious individually specified facts. The listed context makes the actual branch, actors, event history and completion facts explicit. Additional dates below are stated hypothetical facts rather than inferred client records.
| Step | What is counted | Date |
|---|---|---|
| Example 1. Ordinary established facts | The enforcement agent applying the eligible debt-advice notice extension. For the established proposed event Monday, November 30, 2026, the latest notice day is Tuesday, October 27, 2026. Count exactly 28 intervening eligible dates. Sundays and bank holidays are excluded; ordinary Saturdays count. Additional fictitious established facts. Qualifying provider request actually received. 2026-10-21T10:00:00Z. Original notice stated expiry. 2026-10-22T17:00:00Z. Established notice method. personal. Fictitious individually specified facts. The listed context makes the actual branch, actors, event history and completion facts explicit. Additional dates below are stated hypothetical facts rather than inferred client records. For the established proposed event Monday, November 30, 2026, the latest notice day is Tuesday, October 27, 2026. Count exactly 28 intervening eligible dates. Sundays and bank holidays are excluded; ordinary Saturdays count. | Tuesday, October 27, 2026 |
| Example 2. Closed-day boundary | The enforcement agent applying the eligible debt-advice notice extension. For the established proposed event Tuesday, December 29, 2026, omit the intervening Christmas Day, substitute Boxing Day bank holiday and relevant Sundays. The eligible-date list leaves latest notice Monday, November 23, 2026. No court-office rollover is substituted for the advance-notice count. Additional fictitious established facts. Qualifying provider request actually received. 2026-11-19T10:00:00Z. Original notice stated expiry. 2026-11-20T17:00:00Z. Established notice method. personal. Fictitious individually specified facts. The listed context makes the actual branch, actors, event history and completion facts explicit. Additional dates below are stated hypothetical facts rather than inferred client records. For the established proposed event Tuesday, December 29, 2026, omit the intervening Christmas Day, substitute Boxing Day bank holiday and relevant Sundays. The eligible-date list leaves latest notice Monday, November 23, 2026. No court-office rollover is substituted for the advance-notice count. | Monday, November 23, 2026 |
| Example 3. Material procedural branch | The enforcement agent applying the eligible debt-advice notice extension. A request for more time was received after expiry of the originally stated notice period. The timely qualifying request condition is not established. Additional fictitious established facts. Qualifying provider request actually received. 2026-11-30T18:00:00Z. Original notice stated expiry. 2026-08-31T17:00:00Z. Established notice method. personal. Fictitious individually specified facts. The listed context makes the actual branch, actors, event history and completion facts explicit. Additional dates below are stated hypothetical facts rather than inferred client records. A request for more time was received after expiry of the originally stated notice period. The timely qualifying request condition is not established. | The timely qualifying request condition is not established. |
Fictitious established facts. These examples do not establish eligibility, effective service, relief or a direction.
Try these dates in the calculatorWhich conditions and exceptions apply?
- Identified actor and operative event
- The request is an eligibility condition, not a new date from which twenty-eight days automatically run. Preserve the original notice period, actual provider request and debt classification.
- Provision-specific counting and closure
- Exclude notice and control dates, and omit intervening Sundays, bank holidays, Good Friday and Christmas Day. Twenty-eight countable intervening dates must remain. Ordinary Saturdays count. An eligible notice for control on November 30, 2026 cannot be reduced to twenty-eight unadjusted calendar dates. Actual permitted notice giving remains necessary.
- Required completion and separate procedural route
- Paragraph (1B) excludes noneligible business debt. The definitions are incorporated through regulation 2. An unknown provider qualification, request timeliness or debt classification must not silently select the extended branch.
- The request is an eligibility condition, not a new date from which twenty-eight days automatically run. Preserve the original notice period, actual provider request and debt classification.
- The ordinary fourteen-day branch and eligible twenty-eight-day branch share the regulation 6(2) calendar. Neither treats the provider request date as the planned control date.
What must the responsible actor complete?
Questions about this procedure
When must enforcement notice allow twenty-eight clear days?
Does any debtor request trigger the twenty-eight-day branch?
Paragraph (1A) requires a request submitted by a debt advice provider on the debtor’s behalf. The source defines that provider by reference through regulation 2.
TCG Regulations 2013, regs 2, 6(1A)Does the request have to arrive before the original notice period expires?
Yes. Paragraph (1A) expressly requires submission before expiration of the notice period indicated in the notice. Preserve the actual submission and stated expiry.
TCG Regulations 2013, reg 6(1A)Do twenty-eight days run from the provider request date?
The provision extends the minimum notice before control to twenty-eight clear days. The request establishes eligibility; it does not replace the notice or proposed control dates.
TCG Regulations 2013, reg 6(1A)Can the extension apply to noneligible business debt?
Paragraph (1B) says it does not. Regulation 2 supplies the cross-reference for that defined term; the date model does not determine the underlying debt classification.
TCG Regulations 2013, regs 2, 6(1B)Which dates are omitted from the twenty-eight-day notice interval?
Paragraph (2) expressly applies to paragraph (1A) as well as (1). It omits Sundays, bank holidays, Good Friday and Christmas Day, while an ordinary Saturday remains countable.
TCG Regulations 2013, reg 6(2)Can a court still order less than the extended twenty-eight days?
Paragraphs (3) and (4) preserve the court’s shortening power and stated dissipation condition. A requested shortening is not an actual order.
TCG Regulations 2013, reg 6(3)–(4)Official sources and review
Provisions used (9)
| Provision | Purpose |
|---|---|
| TCG Regulations 2013, regs 2, 6(1A)–(3) | Check the identified procedure, event, counting rule or qualification |
| TCG Regulations 2013, regs 2, 6(2) | Check the identified procedure, event, counting rule or qualification |
| TCG Regulations 2013, regs 2, 9 | Check the identified procedure, event, counting rule or qualification |
| SI 2026/366, reg 2 | Check the identified procedure, event, counting rule or qualification |
| TCG Regulations 2013, regs 2, 6(1A) | Check the identified procedure, event, counting rule or qualification |
| TCG Regulations 2013, reg 6(1A) | Check the identified procedure, event, counting rule or qualification |
| TCG Regulations 2013, regs 2, 6(1B) | Check the identified procedure, event, counting rule or qualification |
| TCG Regulations 2013, reg 6(2) | Check the identified procedure, event, counting rule or qualification |
| TCG Regulations 2013, reg 6(3)–(4) | Check the identified procedure, event, counting rule or qualification |