Data quality and duplicate review
How connected workflows can preserve required information and avoid silently creating unreliable records.
On this page
Before you start
- Agreement on required data, controlled choices, and duplicate review.
Typical workflow
- 1
Define required information.
- 2
Align controlled values with the firm.
- 3
Test missing and conflicting records.
- 4
Assign exception review ownership.
Required information
Each approved workflow identifies the information needed before PlaintiffDesk can accept or act on a submission.
Firm-defined choices
Connections can be aligned with the firm’s configured choices instead of guessing at case types, sources, users, statuses, or other controlled values.
Duplicate-aware workflows
Integration plans can include matching and review expectations so an existing contact, lead, case, or external submission is not duplicated without consideration.
Keep in mind
- Validation protects the firm’s working record; it should not be bypassed merely to accept more submissions.
Still need help with this guide?Contact PlaintiffDesk