The aim of the Claimant Party accelerator is to provide a custom work type to enable claimant level case handling, data capture and activities. The Claimant Party work type is not intended to be used as a standalone matter type, but as a related child work type to existing defendant matter work types. This enables cases to be handled holistically at a matter level, but with the ability to capture appropriate information at claimant level, such as reserves, and information about the different claimants and their role on the matter. Data on the claimant party work item can be ‘rolled up’ and presented at matter level.
Context/Background
In law firms managing defendant dispute cases there can often be multiple claimants on a case. In this scenario it is often required that case handling and data capture is specific to each claimant, for example when there are multiple claimants…
- The status of each claimant may need to be recorded and tracked
- The damages/losses claimed of each claimant may need to be recorded and tracked
- Claimant specific data may need to be captured, such as whether they are claiming personal injury, their liability status, their role in the incident/claim, etc.
It is intended that the Claimant Party work type is ‘plugged in’ to existing matter work types and is not intended to be used as a standalone matter work type. When the claimant party work type is utilised on relevant defendant matters, the user journey is designed to be as seamless as possible, with claimant party work items created (either automatically or manually) with one claimant party work item per claimant on the parent matter.
The claimant party work items should be visible on the parent matter; a custom widget displays them as a customisable card list, with configurable buttons to open the relevant claimant party portal page.

The claimant party work type has a defined portal; tailored portal pages provide distinct purposes to guide the user to the information they need, such as reserve details or claimant MI (management information). This portal is designed to look ‘embedded’ within the matter – showing the parent matter menu in the left hand navigation, so it is easy for users to navigate back to the matter.
