User and role scope
Plan discussions account for the people who need access, the responsibilities they hold, and the administrators who will maintain the workspace.
Platform plans
Choose the operational scope and user access your firm needs.
What it does
A practical part of the firm’s workflow.
Platform plans define who will use PlaintiffDesk and which parts of the firm’s operating workspace are included. The right scope depends on the teams involved, the records and workflows they need, the administrative model, and how broadly the firm intends to roll out the platform.
Selected operational areas
Cases, documents, communication, signatures, reporting, accounting workflows, and other available areas can be considered against the firm’s intended use.
Configuration and support needs
The proposed scope can account for firm-specific setup, rollout coordination, and the level of ongoing assistance under consideration.
How it works
What the team can expect.
Identify participating teams
List the initial users, roles, offices or groups, and the matters or workflows they need to handle.
Choose the operating scope
Review which platform areas and configuration work are necessary for the intended launch.
Confirm what is included
Use the written proposal to verify access, functionality, implementation responsibilities, support, and any staged expansion.
Bring this workflow into one system.
Choose the operational scope and user access your firm needs.