When must the defendant send an EL or PL Portal CNF response?

Under the low-value EL/PL Protocol, the defendant must complete and send the CNF response within 30 business days for employers’ liability or 40 business days for public liability. The first business day after the operative paragraph 6.1 sending step is day one. Verify the route and recipient before counting. This source guide gives no automated or purchasable deadline.

Responsible actor. The defendant, including the insurer or legal representative where the context requires, sending the substantive CNF response to the claimant.

Identify the legal category. The Protocol defines employers’ liability and public liability separately in paragraph 1.1. A workplace location alone does not identify the legal category.

Check paragraph 4.1 scope, including the accident or disease-letter transition, value and small-claims boundary. Paragraph 4.3 excludes specified parties and claims, including important disease, jurisdiction and clinical-negligence categories.

If the insurer is known, paragraph 6.1(1) requires the CNF to the insurer and the Defendant Only CNF to the defendant. Where the insurer is unknown or the defendant is known to be uninsured, paragraph 6.1(2) sends the CNF to the registered office or principal place of business.

For a paragraph 6.1(2) transmission, paragraph 6.10 adds acknowledgement, forwarding and subsequent claimant Portal-submission duties. Preserve each event. Do not automatically treat later insurer forwarding as a new 30 or 40-day response period.

Paragraph 5.2 permits a wrong-defendant resend, but the published paragraph refers to 6.12, which concerns recoverable benefits. The response obligation is in 6.11. Preserve the correction evidence and establish the proper operative event rather than silently repairing that cross-reference.

The low-value EL/PL Portal Stage 1 response within England and Wales. Establish whether the claim is employers’ or public liability, the Protocol’s scope and the proper paragraph 6.1 recipient. This is not a general personal-injury limitation period, court defence time or a rule allowing every late claim to re-enter the Portal.

1. Confirm the EL or PL legal category and that the low-value Protocol applies.
2. Identify the actual paragraph 6.1 step and recipient.
3. Count the first business day after that step as day one.
4. Count 30 business days for EL or 40 for PL, excluding every defined nonbusiness day.
5. Keep paragraph 6.10 routing and acknowledgement duties separate from the substantive response.
6. Check exit, limitation and the next pre-action procedure independently.

The first business day after the operative sending event is day one. Count only business days. The protocol excludes Saturdays, Sundays, bank holidays under the Banking and Financial Dealings Act 1971, Good Friday and Christmas Day. These conditional illustrations establish England and Wales holiday facts. Do not exclude day one twice or apply the CPR five-day short-period threshold.

Exclude every nonbusiness day inside the period, not just a closed final day. These are communications between parties, not acts at a court office. A court-office closure or unavailable Portal does not by itself establish an extra protocol day. Preserve the actual sending evidence and review any exceptional event separately.

The response periods require protocol business-day counting and established paragraph 6.1 routing facts. The current generic market model instead counts calendar days. The guide therefore provides no automatic date or paid deadline record.

An in-scope employers’ liability CNF was sent under paragraph 6.1 to the known correct insurer on August 7, 2026. No routing dispute, correction or exit applies. The first business day after sending is day one. Count 30 eligible days and exclude every intervening defined nonworking day. Conditional source illustration only. The stated 30-day period ends September 21, 2026. The application must refuse an automated result.

An in-scope public liability CNF was sent under paragraph 6.1 to the known correct insurer on August 7, 2026. No routing dispute, correction or exit applies. The first business day after sending is day one. Count 40 eligible days and exclude every intervening defined nonworking day. Conditional source illustration only. The stated 40-day period ends October 5, 2026. The application must refuse an automated result.

A qualifying public liability CNF was sent April 2, 2026. The established England and Wales calendar excludes Good Friday, Easter Monday, both May bank holidays and all weekends. No routing dispute or exit applies. The first business day after sending is day one. Count 40 eligible days and exclude every intervening defined nonworking day. Conditional source illustration only. The stated 40-day period ends June 3, 2026. The application must refuse an automated result.

The insurer was unknown. A CNF was sent to the defendant on August 7, 2026 and was later forwarded to an insurer. Dates and content of the 6.10 steps remain disputed. Establish the paragraph 6.1 event and separate paragraph 6.10 duties. Later insurer forwarding does not automatically give a fresh 30-day response period. No applicable automatic date is established. Establish the paragraph 6.1 event and separate paragraph 6.10 duties. Later insurer forwarding does not automatically give a fresh 30-day response period.

The CNF was sent to the wrong defendant and later corrected. The parties dispute the response trigger. The official paragraph 5.2 points to 6.12, while 6.11 contains the response period. Preserve both records and establish the consequence rather than automatically resetting time. No applicable automatic date is established. The official paragraph 5.2 points to 6.12, while 6.11 contains the response period. Preserve both records and establish the consequence rather than automatically resetting time.

The parties agree informally to extend a PL CNF response beyond the ordinary period. Paragraph 5.5 excludes the paragraph 6.11 response from agreed variation. No extended response date follows from that agreement. No applicable automatic date is established. Paragraph 5.5 excludes the paragraph 6.11 response from agreed variation. No extended response date follows from that agreement.

Scope and disease distinctions

Paragraph 4.1 defines the date, value and normal-track conditions. Paragraph 4.3 excludes, among other matters, multi-employer disease claims, most noise-induced hearing-loss claims outside the specified list, clinical negligence, mesothelioma and injuries outside England and Wales. Check all actual exclusions.

Direct defendant and insurer forwarding

Paragraph 6.10(c) requires the claimant to submit the CNF to the insurer via the Portal as soon as possible and within its specified 30-day period from first sending to the defendant. That additional duty does not itself establish a new 30 or 40-day response period.

Wrong-defendant cross-reference

The current official paragraph 5.2 refers to a period in 6.12, while the response periods are in 6.11. This guide makes the textual mismatch explicit. A disputed correction event requires procedural review rather than an assumed reset.

No agreed response extension

Paragraph 5.5 excludes paragraph 6.11 from periods that may be varied by agreement. An agreed extension of another Stage 2 period does not extend the Stage 1 response.

Exit is not default liability

Paragraph 6.13 identifies exit for contributory negligence, failure to complete and send the response, no admission, inadequate mandatory information or the stated small-claims issue. Unlike the RTA provision, it contains no seat-belt carve-out. Paragraph 6.15 identifies the next protocol and the acknowledgement-based running event there.

Limitation and re-entry

Paragraph 5.7 addresses protective proceedings and an application for a stay. Paragraph 5.11 prevents re-entry after leaving the Protocol. Neither the 30 nor the 40-day response should be mistaken for a limitation suspension.

• The low-value EL/PL Portal Stage 1 response within England and Wales. Establish whether the claim is employers’ or public liability, the Protocol’s scope and the proper paragraph 6.1 recipient. This is not a general personal-injury limitation period, court defence time or a rule allowing every late claim to re-enter the Portal.
• The EL and PL options share the Stage 1 CNF response, but their 30 and 40 business-day periods differ. Direct-defendant routing, acknowledgement, RTA responses, limitation and court proceedings remain separate duties.

• Confirm the claim’s EL or PL legal category and the complete scope exclusions.
• Preserve the paragraph 6.1 CNF, recipient, sending method and timestamp.
• Where sent directly to the defendant, preserve all paragraph 6.10 acknowledgements and forwarding events.
• Resolve any wrong-defendant correction and the published cross-reference issue.
• Count every required business day from the first following business day.
• Complete and send the substantive response, rather than only acknowledging the CNF.
• Review exit consequences, limitation and any later court step separately.
• Complete the relevant CNF response section and send it to the claimant by the end of the applicable protocol period through the prescribed channel. The protocol provisions reviewed here do not specify an independent 4 p.m., 5 p.m. or court-clerk cutoff. Do not import one. Preserve the complete response and its Portal transmission timestamp; an acknowledgement or saved draft is not the substantive CNF response.