Legal Services Offshore blog
Separate preparation from approval in document index
A grounded legal support operations note for law firm administrators: document index with explicit evidence, decision rights, and a verified close.
The operational risk around document index
The risk around document index 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. When the record cannot show what changed, law firm administrators cannot separate a process problem from a person problem, so coaching becomes guesswork. The control should make the document index path readable from the request, the deadline entry, the named owner, the decision, and the confirmation in the conflict database. The risk is highest when the conflict database looks current but the deadline entry behind it was never opened. Most document index 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. Without a visible owner, the request can sit in a shared inbox while everyone assumes someone else has checked the deadline calendar. The operating standard should distinguish preparation from approval and show both in the same document index trail. A familiar vendor, member, candidate, or client name is not evidence that the underlying document index value is still valid.
Evidence map for document index
For document index, the governing source is the deadline calendar; a note in the queue is only a pointer to that source. If the outside counsel invoice contains sensitive data, store it in the approved location and record only the minimum reference needed for the document index review. Resolve the conflict by naming the authoritative source, the owner who decided, and the correction applied to the deadline calendar. The team should test one document index case each week by reconstructing it from the evidence map alone. 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. A matter intake that arrives after the action can still be useful, but it must be marked late and linked to the correction it supports. When the conflict affects privilege mislabel, escalate before changing the destination record so the decision is visible outside the queue. Keep the matter intake in the approved repository and link it to the document index case instead of attaching it to a personal message. The document index evidence set should include the request, the conflict packet, the owner decision, the action taken, and the final value in the billing portal. Keep the original conflict packet and the corrected version side by side, with the reason for the change and the person who approved it. Resolve the conflict by naming the authoritative source, the owner who decided, and the correction applied to the billing portal. When the requester supplies a correction, keep the original request and the corrected value in the same document index history.
Decision rights for document index
The operator can make the matter intake usable, but should not invent the rationale for an approval that client contact never gave. Keep a short list of decisions that always require client contact, and review the list when the legal support operations process changes. Review a sample of approvals each month to confirm that the named role still matches the current legal support operations process. When the operator is unsure whether a change is preparation or judgment, the safe default is to pause and ask. The operator can make the conflict packet usable, but should not invent the rationale for an approval that vendor never gave. Keep a short list of decisions that always require vendor, and review the list when the legal support operations process changes. Record the approval in the document index case with the approver, the time, the scope, and the evidence reviewed. Write the approval channel next to the decision right so the operator knows where a yes must appear.
Daily workflow for document index
Open the document index queue in the billing portal and mark every item with the current owner, the next action, and the time it is due. At mid-day, check the document index items that have no next action; those are the ones most likely to age silently. Do not carry an item forward without a dated next action; an unexplained carryover is an exception, not a plan. If the queue is too large to review, split it by risk or channel rather than sampling only the newest items. Start the document index review by opening the matter management system, sorting the oldest unresolved item, and checking the document index before reading the latest summary. 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 document index queue and write a carryover note for every item that is still open. At the end of the day, compare the open queue with the morning list and explain every unexplained difference. If the queue cannot be reconciled in the morning, record the gap and assign an owner before starting new document index work. If the operator touches the document management system, record the before-and-after value and the approval that allowed the change. If a handoff is pending, name the receiving role and the time by which acknowledgment is expected. Use the same document index status values across owners so the daily count means the same thing to everyone.
Exception handling for document index
Track repeated exceptions separately from one-off errors; a pattern may point to a form, a queue rule, or a permissions problem. After the decision, link the response to the destination change and close the exception with the reason it occurred. A stop-work rule should name the trigger, the person who can release the work, and the evidence needed to restart. Reason codes should be short enough to use at the queue and specific enough to route the case to the right owner. A missing privilege log and an unreadable privilege log are different exceptions and should not share the same reason code. An escalation packet should include the document index link, verified facts, the unresolved decision, the deadline, actions already taken, and the safest next step. Record the stop time, the reason, and the release decision so the delay can be reviewed without guessing. When a case is blocked by access, record the system, the role requested, and the person who can grant it. Classify exceptions by whether the work can continue, must pause, or needs an immediate owner decision. 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 document index; stop and record the gap. Reason codes should be short enough to use at the queue and specific enough to route the case to the right owner.
Close and verify document index
A sent message, a closed ticket, or a verbal yes is not proof that the document index outcome reached the record. 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. Closed cases should remain searchable by object, owner, date, and source so a later correction can find them. The close condition should name the field, the expected value, the approver, and the time of the final check. If the destination value differs from the approved value, keep the case open and route the variance. If the update fails or the requester disputes the result, reopen the document index case and link the new evidence to the original record. If the destination is a downstream team, keep the document index open until that team acknowledges receipt.
Review cadence for document index
Pick the sample from the conflict database, not from the cases the team remembers, so the review is not biased toward easy work. Do not publish a quality score without the sample size and the exclusions that produced it. When the same gap appears twice, change the intake field, the approval rule, or the conflict database permission instead of repeating the coaching. If a high-risk gap is found, pause the affected document index work while the action is implemented. Pick the sample from the deadline calendar, not from the cases the team remembers, so the review is not biased toward easy work. Pair speed measures with evidence measures so a faster document index queue does not hide missing outside counsel invoice or weak approvals. If the gap is caused by a missing outside counsel invoice, simplify the collection step or move it earlier in the workflow. Review at least one case handled by a backup owner and one that crossed a time zone.