Legal Services Offshore blog
A privilege log QA routine for offshore paralegals
A practical quality routine for privilege log preparation that checks source support, field consistency, reviewer ownership, and correction history without deciding privilege.

Agree on the fields before checking them
A privilege log quality check begins with a shared definition of each field. The team should know what counts as a document date, how authors and recipients are recorded, which document types are allowed, and how a missing value is represented. Without that agreement, two reviewers can mark the same log correct for different reasons. Write the field rules in a short data dictionary and keep it with the log template.
Include the source system for each field, the allowed values, and the treatment of unknown or not applicable. If a value is inferred from a file name or an email signature, say so rather than presenting it as a confirmed fact. The dictionary should also define the unit of review. Is each entry one document, one attachment, or one email with its thread? A clear unit prevents duplicate entries and makes the sample count meaningful. Update the dictionary when the review platform or the client's instructions change, and record the version used for each batch.
Check source support, not just completeness
A log can be complete on its face and still lack support. For each sampled entry, compare the logged author, recipient, date, subject, and description with the underlying document. Confirm that the cited basis is the one the reviewer approved, not a category the preparer selected by habit. Record the exact location used for the check, such as the document identifier and page.
If the source is unavailable, mark the entry as unverified rather than assuming the log is correct. A missing source is a finding, even when the entry looks plausible. The reviewer can then decide whether to locate the document, revise the entry, or accept the risk with a note. Pay attention to attachments and forwarded messages, because those are common sources of error. A parent email may be logged while the attachment carries different authors or a different date. The log should reflect the document actually withheld, not the conversation that happened to mention it.
Use a small, stable set of reason codes
Corrections are easier to trend when they use a controlled list of reasons. A practical set might include missing source, wrong author, wrong recipient, wrong date, unsupported basis, duplicate entry, formatting defect, and reviewer question. Each code should have a short definition and an example. Avoid codes that blame a person or assume intent.
The purpose is to find the step that failed, not to label the preparer. If the same code appears repeatedly in one batch, check the template, the source export, and the review instructions before concluding that the team needs more training. A reason code should lead to a specific action. Missing source means locate or escalate. Wrong author means correct the field and recheck the related entries. Unsupported basis means return the entry to the approving attorney. A code without an action is only a label.
Separate preparation from approval
The offshore paralegal may assemble the log, compare entries with source documents, and flag inconsistencies. The attorney decides whether a document is privileged, whether a basis applies, and whether an entry is sufficient for production. The QA routine should make that boundary visible in the record. Use an approval field that names the attorney and the date.
If approval is given for a batch, record the batch scope and any exceptions. A general message that says the log looks fine is weaker than an approval that identifies the reviewed entries and the open questions. The preparer should not treat a conversation as approval unless it is recorded in the approved system. When an entry is returned, keep the original and the corrected version together. The correction note should state what changed and why. This history helps the reviewer see whether the issue was a one-time mistake or a recurring definition problem, and it protects the team if the log is questioned later.
Run the QA sample on a fixed cadence
A weekly sample of a few entries is more useful than an annual review of everything. Choose a mix of ordinary entries, entries with attachments, entries that were corrected, and entries the preparer found difficult. Record the selection method so the sample can be repeated and defended. Have a second reviewer check a subset independently, then compare results.
If the two reviewers disagree, discuss the field definition and update the dictionary. Do not simply average the disagreement away. The goal is a shared standard that produces the same answer when two trained people review the same entry. Track the number of entries checked, the number corrected, and the reason codes. Report absolute counts alongside rates, because a small batch can produce a misleading percentage. A rising correction count may mean the sample is stronger, the instructions changed, or the source export is worse. Investigate before drawing a conclusion.
Protect the log and its supporting material
Privilege logs and the documents behind them are sensitive. Limit access to the named review team, use the approved repository, and avoid sending the log as an unprotected attachment. If a working copy is needed, label it and remove it when the task is complete according to the retention rule. Record who accessed or exported the log and why.
Access reviews should include the log folder, the source document collection, and any shared drive used for the review. When a team member leaves the project, remove access and confirm that open items have a new owner. A privacy or security incident involving the log should follow the firm's incident path, not an informal cleanup. Preserve the evidence, notify the named contact, and avoid deleting files until the firm says otherwise. The QA routine can check that the incident path is documented, but it cannot substitute for the firm's own response.
Turn findings into one controlled change
At the end of each review cycle, choose one change that addresses the most common or most consequential finding. It might be a new required field, a different source export, a second-review rule for attachments, or a clearer approval note. Name the owner and the date of the next check. Do not stack five changes at once, because the team will not know which one helped.
Test the change on the next batch and compare the same measures. If the correction rate does not move, examine whether the change addressed the actual cause or only the visible symptom. Keep a short decision log with the finding, the change, the owner, the due date, and the result. This log is the memory of the QA routine and helps a new reviewer understand why the template looks the way it does. A privilege log process improves through these small, recorded decisions.