England and Wales · Civil enforcement
What date controls the ordinary validity of a TCG writ or warrant?
CPR 83.4(3) links validity to the regulation 9(1) period in which goods may be taken into control, ordinarily twelve months beginning with notice of enforcement.
- Period
- Twelve months beginning with enforcement notice, subject to the applicable regulation 9 branch
- Trigger
- Actual notice of enforcement date for the ordinary regulation 9(1) branch
- Rule
- CPR 83.4(1), (3); TCG Regulations 2013, reg 9(1)–(2)
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
What date controls the ordinary validity of a TCG writ or warrant?
CPR 83.4(3) links validity to the regulation 9(1) period in which goods may be taken into control, ordinarily twelve months beginning with notice of enforcement.
Responsible actor. The creditor or enforcement agent relying on a TCG writ or warrant.
Actual notice of enforcement date for the ordinary regulation 9(1) branch.
The instrument’s issue date does not establish this ordinary expiry. Check the actual notice, any eligible repayment-arrangement breach, actual extension and relevant historical regulation 9 modification.
The instrument’s issue date does not establish this ordinary expiry. Check the actual notice, any eligible repayment-arrangement breach, actual extension and relevant historical regulation 9 modification.
CPR 83.4(1), (3); TCG Regulations 2013, reg 9(1)–(2)How does this provision count time?
- Include the ordinary notice day in the twelve months. The final ordinary validity day precedes the corresponding anniversary. A qualifying breach or actual extension changes which source branch controls.
- Validity does not automatically roll to a later open court day. The ordinary notice-based validity boundary includes the notice day and does not change merely because the court office is closed.
Include the ordinary notice day in the twelve months. The final ordinary validity day precedes the corresponding anniversary. A qualifying breach or actual extension changes which source branch controls.
Validity does not automatically roll to a later open court day. The ordinary notice-based validity boundary includes the notice day and does not change merely because the court office is closed.
CPR 83.4(1), (3); TCG Regulations 2013, reg 9(1)–(2)What do independently checked examples show?
Fictitious example
The creditor or enforcement agent relying on a TCG writ or warrant. The established event is Friday, October 9, 2026. Use 12 calendar months beginning with that date, so the last valid day is the corresponding anniversary minus one day. The endpoint is Friday, October 8, 2027. It identifies the stated boundary rather than a guaranteed successful filing or permission grant. Additional fictitious established facts. Actual notice of enforcement. Friday, October 9, 2026. 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 creditor or enforcement agent relying on a TCG writ or warrant. The established event is Friday, October 9, 2026. Use 12 calendar months beginning with that date, so the last valid day is the corresponding anniversary minus one day. The endpoint is Friday, October 8, 2027. It identifies the stated boundary rather than a guaranteed successful filing or permission grant. Additional fictitious established facts. Actual notice of enforcement. Friday, October 9, 2026. 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. The established event is Friday, October 9, 2026. Use 12 calendar months beginning with that date, so the last valid day is the corresponding anniversary minus one day. The endpoint is Friday, October 8, 2027. It identifies the stated boundary rather than a guaranteed successful filing or permission grant. | Friday, October 8, 2027 |
| Example 2. Closed-day boundary | The creditor or enforcement agent relying on a TCG writ or warrant. The corresponding source boundary is Saturday, October 7, 2028. This fixture concerns the statutory boundary, permission threshold or instrument validity itself. A closed court office does not automatically change that boundary; it does not purport to authorize a separate court act on a closed day. Additional fictitious established facts. Actual notice of enforcement. Friday, October 8, 2027. 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. The corresponding source boundary is Saturday, October 7, 2028. This fixture concerns the statutory boundary, permission threshold or instrument validity itself. A closed court office does not automatically change that boundary; it does not purport to authorize a separate court act on a closed day. | Saturday, October 7, 2028 |
| Example 3. Material procedural branch | The creditor or enforcement agent relying on a TCG writ or warrant. The debtor entered a qualifying instalment arrangement after notice and then breached it. Establish the actual breach branch before determining this TCG validity. Additional fictitious established facts. Actual notice of enforcement. Friday, October 9, 2026. 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. The debtor entered a qualifying instalment arrangement after notice and then breached it. Establish the actual breach branch before determining this TCG validity. | Establish the actual breach branch before determining this TCG validity. |
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 instrument’s issue date does not establish this ordinary expiry. Check the actual notice, any eligible repayment-arrangement breach, actual extension and relevant historical regulation 9 modification.
- Provision-specific counting and closure
- Include the ordinary notice day in the twelve months. The final ordinary validity day precedes the corresponding anniversary. A qualifying breach or actual extension changes which source branch controls. Validity does not automatically roll to a later open court day. The ordinary notice-based validity boundary includes the notice day and does not change merely because the court office is closed.
- Required completion and separate procedural route
- Before a replacement can calculate, it must establish the complete notice and regulation 9 history. A generic issue-date or notice-date-only record cannot silently dismiss an actual breach, extension or Part 85 event.
- The instrument’s issue date does not establish this ordinary expiry. Check the actual notice, any eligible repayment-arrangement breach, actual extension and relevant historical regulation 9 modification.
- The non-TCG instrument under CPR 83.3 ordinarily runs from issue. A TCG instrument under rule 83.4 instead adopts the period tied to notice and regulation 9 facts.
What must the responsible actor complete?
Questions about this procedure
What date controls the ordinary validity of a TCG writ or warrant?
Does issuing a writ of control start a separate twelve-month validity clock?
Rule 83.4(3) links validity to the regulation 9(1) period. The ordinary regulation 9 period begins with notice of enforcement, not issue of the instrument.
CPR 83.4(3); TCG Regulations 2013, reg 9(1)Does the notice day count in the ordinary TCG validity period?
Yes. Regulation 9(1) says the twelve months begin with that date. An ordinary inclusive period ends before the corresponding anniversary.
TCG Regulations 2013, reg 9(1)Can a repayment breach change the notice-based endpoint?
A qualifying arrangement followed by the debtor’s breach engages regulation 9(2), which begins the period with the actual breach date.
TCG Regulations 2013, reg 9(2)Does an actual regulation 9 extension also extend the TCG instrument?
Yes. Rule 83.4(4) extends its validity for the same period as the actual regulation 9(3) extension.
CPR 83.4(4); TCG Regulations 2013, reg 9(3)Does a Part 85 application matter to a TCG writ’s validity?
Rule 83.4(7) requires an application during validity concerning goods taken into control under the instrument, and states the resulting extension.
CPR 83.4(7)Can the old calculator move a Saturday TCG expiry to Monday?
That unsupported carry is contained. The ordinary notice-based validity period is distinct from a time limit for doing an act at a court office.
CPR 83.4(3); TCG Regulations 2013, reg 9(1); CPR 2.8(5)Official sources and review
Provisions used (15)
| Provision | Purpose |
|---|---|
| CPR 83.4(1), (3); TCG Regulations 2013, reg 9(1)–(2) | Check the identified procedure, event, counting rule or qualification |
| TCG Regulations 2013, reg 9(1)–(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 |
| CPR 6.26 | Check the identified procedure, event, counting rule or qualification |
| CPR 83.4(3) | Check the identified procedure, event, counting rule or qualification |
| TCG Regulations 2013, reg 9(1) | Check the identified procedure, event, counting rule or qualification |
| TCG Regulations 2013, reg 9(2) | Check the identified procedure, event, counting rule or qualification |
| CPR 83.4(4) | Check the identified procedure, event, counting rule or qualification |
| TCG Regulations 2013, reg 9(3) | Check the identified procedure, event, counting rule or qualification |
| CPR 83.4(7) | Check the identified procedure, event, counting rule or qualification |
| CPR 2.8(5) | Check the identified procedure, event, counting rule or qualification |
| CPR 83.4(3); TCG Regulations 2013, reg 9(1) | Check the identified procedure, event, counting rule or qualification |
| CPR 83.4(4); TCG Regulations 2013, reg 9(3) | Check the identified procedure, event, counting rule or qualification |
| CPR 83.4(3); TCG Regulations 2013, reg 9(1); CPR 2.8(5) | Check the identified procedure, event, counting rule or qualification |