Legal Services Offshore blog
Create a source-preserving entry check for matter intake
A grounded legal support operations note for law firm administrators: matter intake with explicit evidence, decision rights, and a verified close.
The operational risk around matter intake
A legal support operations team can look responsive while the matter intake trail is too thin to support a correction, a customer answer, or a review by supervising attorney. The practical consequence is missed deadline, and the first sign is often a question from supervising attorney that nobody can answer from the record. The control should make the matter intake path readable from the request, the matter intake, the named owner, the decision, and the confirmation in the matter management system. A familiar vendor, member, candidate, or client name is not evidence that the underlying matter intake value is still valid. The risk around matter intake is not that staff forget a task; it is that the record can look complete even when the conflict packet was never checked against the document management system. Without a visible owner, the request can sit in a shared inbox while everyone assumes someone else has checked the document management system. Make the queue owner visible for every matter intake item, and give that owner the authority to pause the work when the evidence is not enough. The risk is highest when the document management system looks current but the conflict packet behind it was never opened.
Evidence map for matter intake
For matter intake, the governing source is the document management system; a note in the queue is only a pointer to that source. For recurring matter intake work, use the same conflict packet type and the same field labels so a sample can be compared across owners. Resolve the conflict by naming the authoritative source, the owner who decided, and the correction applied to the document management system. Keep the conflict packet in the approved repository and link it to the matter intake case instead of attaching it to a personal message. Start the evidence map by naming the field in the conflict database that the matter intake action is supposed to change. When the document index is missing, write missing rather than leaving the field blank; missing, unavailable, and confirmed negative are different states. Resolve the conflict by naming the authoritative source, the owner who decided, and the correction applied to the conflict database. If the document index contains personal or confidential data, use the approved access path and record only the reference in the queue. Record the privilege log and the time it was observed, because a later screenshot cannot prove what the record said when the first action was taken. When the privilege log is missing, write missing rather than leaving the field blank; missing, unavailable, and confirmed negative are different states. Keep an exception note that explains which value was used, which was rejected, and why; a later reviewer should not have to infer the choice from the final number. A late privilege log is still evidence, but it should not be presented as if it existed at the time of the first decision.
Decision rights for matter intake
Write the matter intake boundary in plain language: which systems the operator may touch, which fields may change, and which questions must go back to supervising attorney. The approver may accept, reject, or ask for more evidence, but the response should be recorded in the matter intake case rather than left in a chat. An approval that cannot be linked to a specific matter intake case is too vague to support the destination change. Write the approval channel next to the decision right so the operator knows where a yes must appear. Name the role that can approve matter intake before the work begins; a shared inbox can receive the request, but it cannot own the decision. A decision right is not the same as system access; the operator may be able to edit a field without being authorized to decide its value. When approval is conditional, write the condition and the person responsible for checking it; a conditional yes is not a clean yes. For high-risk matter intake work, require a second reviewer who is not the person who prepared the packet.
Daily workflow for matter intake
Start with the cases that affect incomplete document index, then move to routine requests; age alone is not the only priority signal. If the operator touches the deadline calendar, record the before-and-after value and the approval that allowed the change. Record any correction made during the day and link it to the original matter intake record. If the queue is too large to review, split it by risk or channel rather than sampling only the newest items. The daily matter intake routine should begin with a queue count by owner and age, not with the easiest request in the inbox. At mid-day, check the matter intake items that have no next action; those are the ones most likely to age silently. The end-of-day review should show what was completed, what is blocked, who owns the next step, and which deadline entry is still missing. Use a queue view that shows owner, age, next action, and missing evidence in one screen. Use the same matter intake queue for new work, corrections, and reopened cases so the daily count reflects the real load. When the next step belongs to supervising attorney, write the request and the due time instead of leaving the case in a waiting state. Use the final queue count to test the day’s document index completeness; a lower count achieved by hiding open items is not progress. If the queue is too large to review, split it by risk or channel rather than sampling only the newest items.
Exception handling for matter intake
A missing deadline entry and an unreadable deadline entry are different exceptions and should not share the same reason code. Keep the escalation in the matter intake case so the response is visible to the next reviewer. When the request conflicts with policy or the approved scope, the operator should route it rather than negotiate a workaround in the queue. Keep a separate escalation log for items that required supervising attorney, so response time can be reviewed. An exception is not a generic failure; name the evidence problem so the team can fix the source instead of blaming the operator. An escalation packet should include the matter intake link, verified facts, the unresolved decision, the deadline, actions already taken, and the safest next step. If access is wrong or unexplained, stop the matter intake work before opening the billing portal with borrowed credentials. A stop-work decision should be visible to the requester so they know why the matter intake work is paused. Do not let an exception close because the requester stopped asking; keep the case open until the evidence or the decision is resolved. An escalation that ends in silence should remain open; silence is not approval. Record the stop time, the reason, and the release decision so the delay can be reviewed without guessing. Do not close an exception because the customer stopped replying; record the last contact and the next attempt.
Close and verify matter intake
For matter intake, completion means the requester can see the result and the next reviewer can reconstruct how it happened. Compare the outside counsel invoice, the approval, and the final value in the billing portal before marking the matter intake complete. The reopen reason should use the same reason codes as the exception queue so patterns are visible. If the final value differs from the approved value, record the variance and the person who accepted it. If the destination is another team, the matter intake is not closed until that team acknowledges the handoff. Use a second reviewer for high-risk matter intake closures, and record the review even when the result is accepted. If the correction affects missed deadline, notify vendor before the next dependent action. When the outcome affects a payment, access, schedule, or customer promise, confirm the value with the owner before close.
Review cadence for matter intake
Record the sample frame, the reviewer, the criteria, and the result before discussing the cause. Compare deadline completion before and after a process change, using the same definitions and observation window. Keep the review notes with the matter intake batch so the next owner can see why the procedure changed. Compare the close evidence with the source rather than trusting the status field. A useful sample includes a routine close, a reopened case, a missing conflict packet, and a handoff that crossed a shift. Track conflict check cycle with a clear denominator and a review owner; a count without context is not a control. Escalate a repeated high-risk matter intake gap to law firm administrators with the case evidence, not only a summary count. If a high-risk gap is found, pause the affected matter intake work while the action is implemented.