Skip to main content

England and Wales · Court of Appeal and Supreme Court

When must the appellant serve its appeal skeleton and proposed index?

Under PD52C 21 Part 1, the appellant must serve its appeal skeleton or confirm reliance on its permission skeleton, and serve proposed appeal-bundle indexes,14 days after the listing-window notification date.

5.0Rated by lawyers in California, London and Singapore“The platform is really easy to use.” — Michael B., California“The Evidence Record saved us time with our insurance on bankruptcy matters.” — Maria, London, UK“The most up-to-date service we could find.” — Li Chen, Singapore
Calculate my deadline
Period
14 calendar days after the established operative event
Trigger
Date of the listing window notification
Rule
PD52C 1,21,31
PD52C 1,21,31

PD52C 1,21,31 and its official supporting provisions were retained on October 8, 2026. This review concerns when must the appellant serve its appeal skeleton and proposed index, not an earlier rule edition or a different appeal route.

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 the appellant serve its appeal skeleton and proposed index?

Under PD52C 21 Part 1, the appellant must serve its appeal skeleton or confirm reliance on its permission skeleton, and serve proposed appeal-bundle indexes,14 days after the listing-window notification date.

Responsible actor. Appellant.

This is the proposed-index service stage. The final paginated index follows at sixty-three days and hearing bundles use a separate fixed-hearing anchor.

No. The timetable permits confirmation that the appellant relies on the permission skeleton.

The listing-window letter starts this service timetable. The appellant has an election concerning its earlier permission skeleton, but proposed indexes remain part of this step.

PD52C 1,21,31

How does this provision count time?

  1. Under PD52C 21 Part 1, the appellant must serve its appeal skeleton or confirm reliance on its permission skeleton, and serve proposed appeal-bundle indexes,14 days after the listing-window notification date.
  2. The appellant must serve every respondent under Part 1 of the timetable.
  3. Serve every respondent with the skeleton or reliance confirmation and proposed core and supplementary bundle indexes as applicable.

For PD52C 1,21,31, exclude the established starting day and count the next 14 calendar days. CPR 2.8(3)(b) does not exclude an additional fixed compliance day. This is the ordinary fixed-after branch, not a minimum interval between two specified events.

The appellant’s skeleton and proposed-index service is an interparty act. A closed court office does not automatically move this service date; establish effective service and the actual listing direction.

PD52C 1,21,31

What do independently checked examples show?

Fictitious example

The listing-window notification letter is dated October 08. The appellant must serve its appeal skeleton or confirmation of reliance and proposed bundle index. The listing-window letter starts this service timetable. The appellant has an election concerning its earlier permission skeleton, but proposed indexes remain part of this step.

Example counting steps
StepWhat is countedDate
Example 1. Ordinary established factsThe listing-window notification letter is dated October 08. The appellant must serve its appeal skeleton or confirmation of reliance and proposed bundle index. The listing-window letter starts this service timetable. The appellant has an election concerning its earlier permission skeleton, but proposed indexes remain part of this step. Exactly 14 counted calendar dates follow the established event; the starting date is excluded.Thursday, October 22, 2026
Example 2. Closed-day boundaryThe listing-window notification letter is dated October 10. The appellant must serve its appeal skeleton or confirmation of reliance and proposed bundle index. For this calendar counterexample the case and event branch are otherwise established. The listing-window letter starts this service timetable. The appellant has an election concerning its earlier permission skeleton, but proposed indexes remain part of this step. Exactly 14 counted calendar dates follow the established event; the starting date is excluded.Saturday, October 24, 2026
Example 3. Material procedural branchThe appellant relies on its existing permission skeleton. The listing-window letter is dated Monday, August 17, 2026; the appellant must serve reliance confirmation and proposed indexes. The listing-window letter starts this service timetable. The appellant has an election concerning its earlier permission skeleton, but proposed indexes remain part of this step. This example establishes the stated operative branch independently of the calendar arithmetic. Exactly 14 counted calendar dates follow the established event; the starting date is excluded.Monday, August 31, 2026
Example resultThursday, October 22, 2026

Fictitious established facts. These examples do not establish eligibility, effective service, relief or a direction.

Try these dates in the calculator

Which conditions and exceptions apply?

Established procedural branch
The listing-window letter starts this service timetable. The appellant has an election concerning its earlier permission skeleton, but proposed indexes remain part of this step.
Required completion
Serve every respondent with the skeleton or reliance confirmation and proposed core and supplementary bundle indexes as applicable.
Related procedure distinction
This is the proposed-index service stage. The final paginated index follows at sixty-three days and hearing bundles use a separate fixed-hearing anchor.
PD52C 1,21,31
  • The listing-window letter starts this service timetable. The appellant has an election concerning its earlier permission skeleton, but proposed indexes remain part of this step.
  • This is the proposed-index service stage. The final paginated index follows at sixty-three days and hearing bundles use a separate fixed-hearing anchor.

What must the responsible actor complete?

Questions about this procedure

When must the appellant serve its appeal skeleton and proposed index?

Must the appellant always draft a new appeal skeleton?

No. The timetable permits confirmation that the appellant relies on the permission skeleton.

PD52C 1,21,31

Who receives the appeal skeleton or reliance confirmation?

The appellant must serve every respondent under Part 1 of the timetable.

PD52C 1,21,31

Are proposed bundle indexes included in this step?

Yes. The proposed core appeal-bundle index and any supplementary-bundle index are served with this timetable step.

PD52C 1,21,31

Does the period begin at grant of permission?

This dated step uses the listing-window notification letter, even though an earlier prompt case review follows permission.

PD52C 1,21,31

Is the proposed index the final paginated index?

No. The final index is a later sixty-three-day timetable step.

PD52C 1,21,31

Does a closed court office extend this service-only date?

The court-office extension in CPR 2.8(5) does not automatically extend this interparty act.

CPR 2.8, calculation of time

Official sources and review

Provisions used (3)
Provisions used in this guide
ProvisionPurpose
PD52C 1,21,31Check the identified procedure, event, counting rule or qualification
CPR 2.8, calculation of timeCheck the identified procedure, event, counting rule or qualification
CPR 52.15, variation of timeCheck the identified procedure, event, counting rule or qualification
Read the official controlling provision

Cookie preferences

Deadline Engine uses necessary cookies for authentication and security. You can choose whether we may load Plausible Analytics to measure aggregate site use. We do not use advertising or marketing tracking. You can change this any time from the footer. Read the Cookie Policy.