Administration and onboarding
Preparing the firm, validating imported work, and maintaining a usable configuration after launch.
On this page
Before you start
- A firm administrator who can make configuration decisions.
- Access to the prior system or systems that hold the firm’s current records and documents.
- A representative sample of users, matters, documents, and workflows for validation.
Typical workflow
- 1
Confirm firm identity, users, roles, case types, fields, folders, templates, communications, and reporting needs.
- 2
Give the onboarding team access to the prior system or systems and identify what should move into PlaintiffDesk.
- 3
Complete the agreed core setup alongside a firm administrator and representative user while accessible transfer work proceeds.
- 4
Compare record counts and representative samples, then resolve exceptions before the imported record becomes authoritative.
- 5
Walk through the firm’s daily intake, case, document, communication, and reporting work before launch.
Configuration workbook
Document firm identity, users, roles, case types, fields, folders, templates, communication choices, integrations, and reporting needs before launch.
Import validation
Compare record counts and samples for contacts, intake, cases, assignments, custom fields, activity, and documents. Resolve exceptions before users rely on the imported record.
User acceptance
Test representative workflows with administrators, attorneys, and staff using noncritical matters before broad rollout.
Ongoing governance
Assign owners for user access, case-type changes, templates, integrations, reports, data quality, and support escalation.
Keep in mind
- Core configuration timing depends on the agreed scope, available decisions, representative examples, and administrator access; record and document transfer timing also depends on source-system access, volume, and data readiness.
- Not every firm is moving from one platform. The onboarding plan can coordinate records and documents from multiple prior systems.