Hand over closed document review first, not the backlog

What a firm should hand over first when outsourcing document review is a batch it has already finished. Not the oldest pile, not the matter nobody wants, and not the live production deadline. A completed batch has a known output, which means the first handover measures something useful: whether the work can travel out of the firm and come back in a form anyone can check. The batch is a test instrument. Treat it as one.

Why the first batch should be work that is already done

A closed batch gives you an answer key. When the returned coding disagrees with what the firm concluded the first time, the disagreement is readable: either the criteria were ambiguous, or they were clear and the reviewer applied them differently. Both are worth knowing in week one and cost nothing to find out, because no deadline is attached to the result.

Live work inverts that. The output arrives with no reference point, so an attorney has to reconstruct the correct answer in order to grade it, which is the same labor as doing the review. Firms then conclude that offshore review does not save time. They are right about their own experience and wrong about the cause. They ran the first test on the one batch where a wrong result was expensive and a right result was unverifiable.

The four things missing every time a handover fell apart

This is a pattern across six placements rather than a survey, and it was consistent enough inside that sample to change how I read a firm before anyone is hired. The firms that succeeded were already working remotely before the hire arrived: kanban boards, a documented org structure, written SOPs, check-ins on a schedule. The firms that struggled were missing four specific things.

• An online repository where the work actually lives, rather than attachments moving between inboxes
• A virtual office, meaning one place where people are reachable during working hours
• Defined communication channels, so a question has a known destination
• Agreed work schedules, including how much of the day overlaps

Every one of those has a direct consequence for document review specifically. With no repository, a reviewer cannot see what work exists and waits to be sent files, so throughput is capped by how often someone remembers to send them. With no agreed schedule, a clarifying question on a coding call sits overnight and a day of review goes out wrong before anyone reads the reply. A task management system is the floor, and the firms below it were not held back by who they hired.