ToC

Table of Contents

Part 7 Proceedings - Functional Accelerator

This is a Legacy Accelerator Pack, which is an older accelerator developed in earlier versions of Clio Operate. Legacy Accelerator Packs differ from new Functional Accelerators in several important ways:
  • They do not include implementation guidance or notes
  • They may not leverage the latest Clio Operate product features
  • They may not reflect current recommended implementation approaches
Users adopting a Legacy Accelerator Pack should carefully review and validate the configuration and processes described, and consider how the design may need to be updated, extended, or modernised to align with current product capabilities and their organisation’s specific requirements.
 

Background

The Civil Procedure Rules (CPR) set out the procedural code and requirements for dealing with court cases in England & Wales, including requirements for pre-litigation (pre action protocols), issuing and litigation management.  Not all cases reach litigation, however where there is a dispute over facts, the majority of civil claims that litigate will follow the ‘Part 7’ procedure. Part 7 proceedings refer to the procedures for initiating and managing claims in the civil courts under the Civil Procedure Rules (CPR). These rules outline the process for handling most civil cases, providing a framework for fairness and efficiency.

Overview

The Part 7 Proceedings accelerator encompasses both ‘Raise’ (claimant) and ‘Respond’ (defendant) routes of litigation, with sub types for the respective sides. Where there are ‘common’ elements such as key dates, processes, etc. then the configuration is built at the Part 7 abstract work type level (to leverage the inheritance model and remove the need for duplication or unwanted variation).  

During the lifecycle of a Part 7 litigated case there will be key ‘phases’ with slight variance on initial steps to raise or respond to the proceedings.

Raising proceedings specific:

  • Issuing (drafting/filing/serving proceedings and receipt of the AoS/Defence)
  • Default Judgment (if applicable)

Responding to proceedings specific:

  • Issued proceedings (receipt and review of proceedings)
  • AoS/Defence (drafting/filing/serving AoS/Defence)

Common proceedings phases:

  • DQ (drafting/filing/serving the Directions Questionnaire)
  • Disclosure/Exchange (preparing for and drafting/filing/serving documents, reports, evidence, etc. based on court directions)
  • Pre Trial (preparation for trial/final hearing)
  • Trial (attendance at and outcomes from the trial/final hearing)
  • Discontinue (with slight variation based on which side discontinues proceedings)

Example phase plan for raising proceedings (claimant):

Example phase plan for responding to proceedings (defendant):

The Part 7 proceedings accelerator aims to:

  • Assist the case handler/case team in complying with court directions (instructions and deadlines)
  • Drive efficiencies through streamlined ‘micro’ processes for common activities such as instructing experts or counsel
  • Streamline data capture of litigation related information, to drive consistency in data capture and reporting, and enable intelligent workflow automation based on relevant variables such as track type or method of litigation
  • Track the key dates associated with the litigation ensuring that deadlines are not missed

This accelerator is intended to be used as a child of appropriate matter work types and follow the below wider solution design: