Who is this?
Identity, source, relationship type and the context the person knowingly provided.
The relationship record should outlast the inbox.
CaseLoad Select builds and stewards the firm-controlled CRM layer connecting inquiries, clients, former clients and referral relationships.
A portfolio of relationships needs operating context.
A list of names and email addresses does not show how a relationship began, what communication is permitted, what happened, who owns the next step or whether the information is still useful.
The CRM is the continuity layer for the marketing relationship. It connects acquisition, inquiry handling, matter-close routines, referral stewardship and permitted future contact without becoming a second legal file.
Six fields keep the next action inspectable.
This schematic is anonymous and contains no client data. It demonstrates the operating structure, not a production CRM.
Fictional illustration. No sensitive matter details, client identity or legal assessment is shown.
- Source
- Listed service page. Recorded when the inquiry entered the system.
- Consent
- Inquiry-response purpose recorded. Broader communication permission is not assumed.
- Relationship state
- New inquiry. No client or representation state is implied.
- Owner
- Assigned operator responsible for preparing the next human step.
- Last action
- Receipt acknowledged without implying acceptance.
- Next permitted action
- Prepare the submitted context for lawyer review.
The relationship record prepares a better handoff.
Source, consent and ownership remain attached as the Screen organizes observed information, interpretation, unknowns and questions for lawyer review.
- 1CRM preserves the relationship. It records how the person entered the system and what may happen next.
- 2Screen prepares the review. It separates what was observed, inferred and left unknown.
- 3The lawyer retains authority. The Screen prioritizes attention. The lawyer decides.
A useful CRM answers four questions.
What is permitted?
Purpose, consent basis, communication preference, withdrawal state and relevant restriction.
What happened?
Last meaningful action, current relationship state, responsible owner and unresolved commitment.
What is next?
The next permitted action, its reason, timing and the person responsible for review.
Preserve continuity without creating a shadow matter file.
Discovery sourceInquiryLawyer reviewClient stateMatter closePermitted follow-upReferral or relevant service
The marketing CRM records relationship and communication context necessary for its approved purpose. It should not duplicate privileged matter details or become a substitute for the firm's practice-management system.
Protect the first handoff.
Capture source and consent, acknowledge receipt without implying acceptance, preserve useful submitted context and identify who owns the next step. Incomplete forms, missed calls and no-shows should appear as distinct operating states for reviewed follow-up.
Missing information, failed delivery, no permission, an unresolved action and a completed step are not interchangeable.
Keep future contact relevant and permitted.
Record the relationship and communication permission that applies. A review invitation, referral request, useful resource or future-service note should have a legitimate purpose, clear sender and usable stop mechanism.
Automation can schedule or surface a candidate action. A person reviews relevance, permission and sensitivity before communication.
Make the relationship asset inspectable.
When relationships live only in individual memory or disconnected systems, staff changes and provider changes create commercial risk. A governed CRM makes the current state, ownership, permission and unresolved actions easier to understand and transfer.
A maintained portfolio may also matter in succession or a potential transaction because it makes relationship continuity and permitted future opportunity easier to inspect. It is not a valuation formula or a promise of future revenue.
Any value depends on data quality, permission, portability, service economics, relationship concentration and the buyer's own professional advice.
Fields, routines and permissions need named owners.
| Record | Purpose | Review question |
|---|---|---|
| Source | Preserve how the relationship entered the managed system. | Is the source observed, imported or inferred? |
| Consent | Record basis, purpose, scope, date and withdrawal state. | Is this specific communication permitted now? |
| Relationship state | Distinguish inquiry, client, former client, referral source and other approved states. | Does the label describe a verified relationship? |
| Owner | Name the person responsible for the next human action. | Can the owner see the necessary context? |
| Last action | Record the last meaningful completed step. | Was it delivered, reviewed and accurately classified? |
| Next permitted action | State what may happen, why and when. | Does the action remain relevant and permitted? |
Design continuity on day one.
Access
Named firm and operator roles with least-necessary permissions.
Portability
Documented exports and field definitions another authorized operator can understand.
Retention
Rules tied to purpose, consent, professional duties and the firm's approved policy.
Handoff
Current states, integrations, owners, open work and credential transfer documented.
Map one relationship journey.
Bring the current inquiry, follow-up and matter-close steps. Identify where context, consent or ownership disappears.