Legal Services Offshore blog
Keep matter intake moving through leave and time-zone gaps
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
The risk around matter intake is not that staff forget a task; it is that the record can look complete even when the deadline entry was never checked against the conflict database. The team may also overstate document index completeness, because a closed status is counted before the deadline entry and the destination update are verified. The operating standard should distinguish preparation from approval and show both in the same matter intake trail. The control should also cover the quiet case: an item that sits open because nobody knows who owns the next step. A busy legal support operations desk can process dozens of matter intake requests in a day and still leave law firm administrators unable to explain which request was approved, which was only discussed, and which was never entered. A single missing outside counsel invoice can turn a routine matter intake request into a search through messages, spreadsheets, and memory, which is exactly when the team is most likely to guess. Use the deadline calendar as the destination of record, and use the outside counsel invoice to prove what the operator saw before making the change. If paralegal cannot name the desired outcome, the request is not ready for the matter intake queue.
Evidence map for matter intake
The matter intake evidence set should include the request, the outside counsel invoice, the owner decision, the action taken, and the final value in the deadline calendar. For recurring matter intake work, use the same outside counsel invoice type and the same field labels so a sample can be compared across owners. A conflict is not a reason to rewrite history; it is a reason to show the reviewer exactly where the matter intake record stopped agreeing with itself. A source that cannot be opened by the reviewer is not a usable source, even if the operator can see it on their screen. Do not treat a forwarded email as the record itself when the governing value lives in the privilege log; the email may explain intent, but it does not replace the field. When the matter intake 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 privilege log. Record the source identifier and the extraction time when the value comes from the privilege log. Start the evidence map by naming the field in the billing portal that the matter intake action is supposed to change. Keep the original conflict packet and the corrected version side by side, with the reason for the change and the person who approved it. After the conflict is resolved, add a short correction entry to the matter intake log and link it to both source versions. A late conflict packet 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
For legal support operations work, the safest split is preparation by the operator and judgment by the accountable owner, with both actions visible in the privilege log. A complete packet is not an approval; the decision needs a named person, a time, and a scope that matches the matter intake. When approval is conditional, write the condition and the person responsible for checking it; a conditional yes is not a clean yes. Write the approval channel next to the decision right so the operator knows where a yes must appear. The operator can make the conflict packet usable, but should not invent the rationale for an approval that paralegal never gave. Do not let urgency expand the role; if the request affects incomplete document index, the boundary stays in place even when the deadline is tight. For repetitive matter intake work, use a standing approval only when its scope, limits, and review date are written down. For high-risk matter intake work, require a second reviewer who is not the person who prepared the packet.
Daily workflow for matter intake
Use the same matter intake queue for new work, corrections, and reopened cases so the daily count reflects the real load. If the operator touches the billing portal, record the before-and-after value and the approval that allowed the change. The end-of-day review should show what was completed, what is blocked, who owns the next step, and which conflict packet is still missing. If the queue is too large to review, split it by risk or channel rather than sampling only the newest items. If the queue cannot be reconciled in the morning, record the gap and assign an owner before starting new matter intake work. If the operator touches the matter management system, record the before-and-after value and the approval that allowed the change. Use the final queue count to test the day’s privilege exceptions; a lower count achieved by hiding open items is not progress. A daily stand-up should review exceptions and aging items, not read every completed ticket aloud. Start the matter intake review by opening the document management system, sorting the oldest unresolved item, and checking the privilege log before reading the latest summary. For each open matter intake, record the source, the privilege log, the decision, and the destination field before moving to the next item. Do not carry an item forward without a dated next action; an unexplained carryover is an exception, not a plan. A case with no next action should be treated as an exception even if its status is marked in progress.
Exception handling for matter intake
Use separate reason codes for missing document index, conflicting source, wrong matter intake, expired approval, unavailable supervising attorney, and an outage in the matter management system. An escalation that ends in silence should remain open; silence is not approval. When the source is unavailable, do not substitute a familiar value from an earlier matter intake; stop and record the gap. The escalation packet should be short enough to read on a phone and complete enough to decide without a meeting. Use separate reason codes for missing privilege log, conflicting source, wrong matter intake, expired approval, unavailable paralegal, and an outage in the document management system. Send the exception to the named owner with the privilege log attached and a specific question, not a general request to review. If the same stop trigger appears repeatedly, change the intake rule or the privilege log requirement instead of coaching around it. A workaround used during an outage in the document management system should have an expiry time and a reconciliation owner. Classify exceptions by whether the work can continue, must pause, or needs an immediate owner decision. Keep the escalation in the matter intake case so the response is visible to the next reviewer. If access is wrong or unexplained, stop the matter intake work before opening the conflict database with borrowed credentials. Do not close an exception because the customer stopped replying; record the last contact and the next attempt.
Close and verify matter intake
Use the same close definition for routine and exception cases so the deadline completion does not improve by redefining completion. If the destination value differs from the approved value, keep the case open and route the variance. A reopened case should show what changed, who noticed it, and which earlier decision is now in question. If the destination is a downstream team, keep the matter intake open until that team acknowledges receipt. If the destination is another team, the matter intake is not closed until that team acknowledges the handoff. When the deadline entry is sensitive, record the approved reference and the access location rather than copying the content into the queue. A reopened case should show what changed, who noticed it, and which earlier decision is now in question. 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. A good measure should lead to a decision: change the form, add a reviewer, adjust access, or stop a workaround. If the gap is caused by an unavailable supervising attorney, add a backup decision path rather than letting the matter intake queue wait indefinitely. Keep a short action log with the decision, the owner, the due date, and the next sample that will test it. Include a case where the owner said no or asked for more evidence; those decisions show whether the boundary is working. Review the exception mix each month; a rising missing-evidence count may be an intake problem rather than an operator problem. Review the action after two cycles and report what moved, what did not, and what remains unknown. Compare the close evidence with the source rather than trusting the status field.