Score the handoff between your systems
A product comparison can miss the handoff between systems: who owns an inquiry, who records the engagement decision, and who checks that an approved transfer reached the matter system. Start by tracing those steps through your own process.
This scorecard does not compare Clio, Lawmatics or any other product. It scores your handoffs: the moments a record, a decision or a document moves from one system, or one person, to another. Work through it with whoever owns intake, attorney approval and matter administration at your firm.
This is an operational worksheet. Your responsible attorney determines the firm's legal and professional obligations, and defines the decisions, engagement requirements and access rules the workflow must honor. The scores below are a discussion aid. They have not been validated as a risk assessment.
The five handoffs worth scoring
Score these five using the order in your actual process. Record any difference from your onboarding documentation.
1. Inquiry to triage
A person or a form submission becomes something a specific staff member is responsible for. Check whether an inquiry in the shared inbox has a named owner and a visible next action, including when its usual owner is absent.
2. Triage to consultation booked
The prospective client's information becomes a scheduled meeting with the appropriate attorney. Check who confirms the routing, who follows up after no reply, and what happens after a cancellation. A booking link alone does not assign those responsibilities.
3. Consultation to engagement decision
The responsible attorney reviews the required conflict and acceptance information and records a decision under the firm's process. Staff and software can prepare the record and route it for review. Check that later steps wait for the required human decision and that “pending” cannot silently become “approved.”
4. Engagement decision to signed agreement
For a workflow that requires a signed agreement, an approved engagement moves into the firm's document and signature process. Check that the correct agreement version and its status are linked to the recorded decision. The attorney defines the engagement requirements; a pipeline status does not establish that they were met.
5. Signed agreement to matter open
After the firm's required engagement conditions are confirmed, an authorized transfer creates or links the matter with the intended type, permissions and billing arrangement. Check who verifies the destination record and who investigates a missing or duplicate matter.
Score each handoff
For each of the five handoffs, answer these four questions. Score 0 for no, 1 for partly, 2 for yes. A single handoff can score from 0 to 8.
| Question | Score 0 looks like | Score 2 looks like |
|---|
| Does the record move to the next system without someone retyping it? | Retyped by hand | Moves on its own |
| Is it visible, to more than one person, who or what the handoff is waiting on? | Known to one person, if anyone | Visible in a shared place |
| Where a human decision is required, does the process itself enforce that requirement? | Easy to skip by accident | Cannot proceed without it |
| If the step fails halfway, is there a safe way to retry without creating a duplicate? | Unknown or risky | Confirmed safe |
What your total tells you
Use these bands to prioritize investigation. They summarize your answers; they do not prove that a process is ready to release. A deliberate manual step can be appropriate if it has a named owner, a recorded result and a clear recovery path.
| Score | Suggested next step |
|---|
| 0 to 3 | Start with missing ownership, evidence and recovery steps. Record which answers are unknown. |
| 4 to 6 | Trace the partly connected steps and make each remaining manual responsibility explicit. |
| 7 to 8 | Demonstrate the expected path and the failure path before relying on the connection. |
Keep critical gaps outside the total. If a required human approval can be skipped, matter permissions are unverified, or a failed write has no reconciliation owner, mark that handoff “not ready” regardless of its score. Record unknown evidence as unknown; do not turn a guessed answer into a 2.
Attorney-owned decisions do not get a shortcut
A high score on the third handoff, consultation to engagement decision, never means the decision itself is automated. It means the conflict question and engagement decision are visible and the required approval cannot be skipped. In the workflow described here, the responsible attorney owns those decisions. This scorecard does not authorize software to clear conflicts, accept an engagement or advise anyone on their matter.
A worked inquiry-to-matter handoff
Synthetic demonstration: invented records. Inquiry Q-104 and its staff roles are fictional. This proposed administrative sequence has not been implemented as a connector. No real firm or client is shown, and no practitioner has reviewed it yet.
Follow the expected path
- Inquiry received. A form creates Q-104 in the intake system. The intake coordinator owns routing and the next contact attempt. A receipt confirms submission only; it makes no engagement promise.
- Consultation follow-up. The coordinator records booking or no reply. In this example, a missed consultation returns to a named follow-up queue instead of advancing the engagement stage.
- Human decision recorded. The responsible attorney reviews the firm's required information. Pending or declined stays outside the matter-opening path. Approval records the person, time and scope of the decision; a generic “won” tag is insufficient.
- Engagement conditions confirmed. This example requires the approved agreement version to be signed and a designated reviewer to confirm the firm's prerequisites. A signature alone does not bypass that check. The firm's attorney defines what confirms an engagement; this sequence does not establish a universal legal rule.
- Matter handoff verified. An authorized job requests the destination matter using Q-104 as a stable correlation reference. The matter administrator checks the returned matter ID, record linkage, required fields and permissions. Only a confirmed result changes the transfer status to complete.
To choose the record owner at each step, use the CRM, intake and practice-management comparison. Keep the inquiry ID and destination matter ID distinct so staff can trace the handoff.
Work the failure route before calling it connected
Suppose the matter system accepts the create request, but the connection stops before the response arrives. The intake record now has an unknown transfer result. This example does not assume that a timeout means nothing was created.
- Put Q-104 in a reconciliation queue owned by the matter administrator. Keep the engagement evidence linked; do not mark the transfer complete or create another matter blindly.
- Check the destination for the correlation reference using supported lookup methods. If one matching matter exists, verify it and record its ID. If the result is absent or ambiguous, keep the exception open for investigation.
- Retry only through a verified duplicate-prevention path supported by the chosen API or integration design. A local reference alone does not prove that the destination enforces uniqueness.
- If permission was revoked, the access owner restores only the approved access before a controlled retry. If the human approval is missing, route back to the responsible attorney; a technical retry cannot supply it.
The acceptance demonstration is specific: withhold approval and confirm that no create request is sent; interrupt a write and confirm that staff can reconcile it without a duplicate; deny access and confirm that the failure remains visible. These are tests to run, not results we have observed. The integration-limits guide supplies questions about rate limits and retries for the actual provider.
Record the decision beside the score
For each handoff, write: score / unknown evidence / critical gap / owner / next test / actual result. In Q-104's proposed matter transfer, automatic movement and visible ownership might look promising, but retry behavior and destination permissions remain untested. The result stays “not ready,” even if the other answers earn a high total. No numeric score overrides those missing checks.
What to do with a low score
Treat a low score as a starting point for the next conversation. Three options, roughly in order of effort:
- Configure what you already have. Check the current product's available configuration before assuming you need new software.
- Add the missing connection. Sometimes one handoff just needs a specific integration or a small piece of custom work.
- Build the handoff you are missing. When the first two options do not reach the workflow you actually run, compare a scoped handoff build with the cost and disruption of replacement.
Common mistakes
- Scoring the software instead of the handoff. A well-reviewed intake tool can still sit next to a handoff that breaks on its way to the next system.
- Letting a "closed" or "won" status stand in for attorney approval. A status change inside a CRM is not the same event as an attorney's engagement decision.
- Treating a workflow status as an engagement decision. Keep inquiry, approval, agreement and matter-transfer states separate. Have the responsible attorney define when and how the firm's engagement requirements are recorded.
- Skipping the confidentiality question because the pilot is small. Access and permission questions do not get smaller with the size of the project.
- No named person accountable for a handoff that involves an approval. If everyone is responsible for a step, it tends to wait on whoever happens to remember it.
Using this with us, or without us
This scorecard is useful whatever you decide, including staying with the systems you run today. We are new to working with law firms, and we say so plainly on every page of this site. If you want a second read on your scores, we do that as the mapping step of our process, after a discovery call, and you keep the result either way.
For a first conversation, share system names, the administrative bottleneck and who owns the approval. Leave confidential matter details and documents out of the inquiry.
Discuss an intake handoff