Legal Services Offshore blog
Audit a matter intake handoff for hidden assumptions
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
In legal support operations, matter intake often begins as a small favor from supervising attorney, which makes it easy to skip the evidence that would let someone else reconstruct the decision. The cost shows up later as a reopened case, an unexplained deadline completion change, or a correction that takes longer than the original task. The record can be short, but it must be specific enough for a second reviewer to repeat the check without asking the original operator what happened. The control should also cover the quiet case: an item that sits open because nobody knows who owns the next step. For the October 28 review at Legal Services Offshore, log the matter intake check with the matter intake and the deadline completion result. Most matter intake problems in legal support operations start before the work is done: the request is accepted without a source, a deadline, or a clear boundary around what the operator may change. The practical consequence is conflict overlooked, and the first sign is often a question from paralegal that nobody can answer from the record. Use the document management system as the destination of record, and use the conflict packet to prove what the operator saw before making the change. At Legal Services Offshore, the first check is whether the request is a new matter intake or a correction to a case that is already open. The October 28 control note for Legal Services Offshore should name the matter intake source, the owner, and the next review time.
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. When two conflict packet versions conflict, preserve both and route the conflict to client contact; do not silently choose the cleaner-looking value. Use a separate reason code for conflicting evidence so the pattern can be reviewed without reading every message. Record the source identifier and the extraction time when the value comes from the document management system. At Legal Services Offshore, keep the conflict packet attached to the matter intake case and record the document index completeness observation date. Record the document index and the time it was observed, because a later screenshot cannot prove what the record said when the first action was taken. For recurring matter intake work, use the same document index 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. The team should test one matter intake case each week by reconstructing it from the evidence map alone. The October 28 evidence trail for matter intake should show the source version and the vendor decision. If supervising attorney supplies the instruction, keep the instruction and the underlying privilege log together rather than replacing one with a summary of the other. The reviewer should be able to open the privilege log from the case without searching a personal drive or asking for a screenshot. If the privilege log is incomplete, the safest next step may be to pause matter intake rather than fill the gap with a plausible assumption. Record the source identifier and the extraction time when the value comes from the deadline calendar. For this October 28 pass, Legal Services Offshore should record which matter intake exception was paused and who released it.
Decision rights for matter intake
The approver should see the evidence packet, not a paraphrase that removes the conflict or the missing document index. Do not let urgency expand the role; if the request affects privilege mislabel, the boundary stays in place even when the deadline is tight. Record the approval in the matter intake case with the approver, the time, the scope, and the evidence reviewed. A standing approval should have a limit, a review date, and a clear description of the matter intake work it covers. The matter intake review at Legal Services Offshore should state whether the document index was current on October 28. Supervising attorney may prepare, compare, label, and route the matter intake, while paralegal keeps the decision that changes the destination record in the deadline calendar. 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. The approval record should point to the privilege log that was reviewed, not only to the request that started the work. If the approver changes the scope, restart the evidence check rather than stretching the old approval. On October 28, Legal Services Offshore should compare the matter intake queue count with the matter reopen rate denominator.
Daily workflow for matter intake
If the queue cannot be reconciled in the morning, record the gap and assign an owner before starting new matter intake work. When a request changes scope, stop the old action, record the change, and route the new scope before continuing. Before the shift ends, reconcile the matter intake queue and write a carryover note for every item that is still open. A case with no next action should be treated as an exception even if its status is marked in progress. The October 28 matter intake note should distinguish a missing privilege log from a confirmed negative. Open the matter intake queue in the privilege log and mark every item with the current owner, the next action, and the time it is due. When the next step belongs to vendor, write the request and the due time instead of leaving the case in a waiting state. Record any correction made during the day and link it to the original matter intake record. A case with no next action should be treated as an exception even if its status is marked in progress. At Legal Services Offshore, record the October 28 matter intake correction and link it to the original source. Start with the cases that affect stale matter record, then move to routine requests; age alone is not the only priority signal. When the next step belongs to supervising attorney, write the request and the due time instead of leaving the case in a waiting state. Close the day by checking that each completed matter intake has a destination update in the billing portal and a confirmation for the requester. A case with no next action should be treated as an exception even if its status is marked in progress. The supervising attorney decision on matter intake should be dated October 28 and linked to the outside counsel invoice.
Exception handling for matter intake
When billing error is involved, use the highest escalation path even if the matter intake request looks routine. If the owner asks for more evidence, record the request, the due time, and the person responsible for obtaining it. 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. For the October 28 sample, Legal Services Offshore should include one matter intake case that crossed owners. Track repeated exceptions separately from one-off errors; a pattern may point to a form, a queue rule, or a permissions problem. 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. A stop-work decision should be visible to the requester so they know why the matter intake work is paused. The October 28 matter intake close should name the destination field, the approver, and the privilege exceptions check. Use separate reason codes for missing matter intake, conflicting source, wrong matter intake, expired approval, unavailable client contact, and an outage in the matter management system. If the owner asks for more evidence, record the request, the due time, and the person responsible for obtaining it. When the source is unavailable, do not substitute a familiar value from an earlier matter intake; stop and record the gap. Do not close an exception because the customer stopped replying; record the last contact and the next attempt. At Legal Services Offshore, the October 28 matter intake review should name the backup owner and the coverage window.
Close and verify matter intake
A sent message, a closed ticket, or a verbal yes is not proof that the matter intake outcome reached the record. Sample the closed matter intake cases for missing evidence, not only for speed; a fast close with no outside counsel invoice is not a strong control. Do not overwrite the first close note; add a correction entry so the history remains readable. A quality reviewer should be able to reproduce the close from the source and the approval without reading the operator’s inbox. The October 28 matter intake exception log should show the reason code, owner, and release decision. A correction after close should reopen the matter intake record rather than disappear into a separate note. Sample the closed matter intake cases for missing evidence, not only for speed; a fast close with no matter intake is not a strong control. When the same matter intake reopens repeatedly, review the intake, the matter intake, and the approval boundary rather than only the final step. Use a consistent close reason so the monthly review can separate completed work from cancelled or duplicate requests. For the October 28 audit walkthrough, Legal Services Offshore should be able to open the matter intake from the case.
Review cadence for matter intake
Each week, sample matter intake cases across owners, channels, and risk levels, including at least one unresolved case. A good measure should lead to a decision: change the form, add a reviewer, adjust access, or stop a workaround. Record the decision to accept the risk when the team chooses not to change the process; an explicit acceptance is better than an invisible workaround. Review at least one case handled by a backup owner and one that crossed a time zone. The October 28 matter intake recovery test should record the restore point and the deadline completion result. Use the same checklist each week so conflict check cycle can be compared without renegotiating the definition. Report open cases by age and dependency, not only the total, because a stable total can hide an aging tail. Assign one owner and one due date to each review action, and check the action at the next sample. If a high-risk gap is found, pause the affected matter intake work while the action is implemented. For the October 28 review at Legal Services Offshore, log the matter intake check with the conflict packet and the conflict check cycle result.