Document review is a two-monitor discipline. The review platform — Relativity, Everlaw, DISCO — runs full-screen on one display while email, notes, and the case timeline live on the other. The arrangement feels safe: review stays on the private screen, presentations happen on the shared one. But displays aren't boundaries, and review platforms hold the most concentrated sensitive material in litigation: the document set, the privilege calls, the production decisions.
The Standard Setup (And Why It Fails)
"Review lives on Monitor 2, which is never shared."
Why it fails:
- Zoom remembers the last shared display. Yesterday it was Monitor 1; today's default is Monitor 2, and the review set is on camera before you notice the green outline.
- Screen recordings and clip tools capture the session, not the monitor: some tools grab every connected display.
- A window dragged between monitors mid-review crosses the boundary for as long as it's in transit — long enough for a frame.
- Notifications render on whichever monitor has focus: a matter email toasts over the review set during a screenshared working session.
- Window titles carry matter names and review batch labels, readable regardless of which monitor holds the window.
In review, every document is potentially privileged, and every frame is potentially producible.
The NoCapture Setup for Review Workstations
Cloak the review platform — on every monitor. The review window is excluded from capture at the compositor level: not "on Monitor 2, which is safe," but absent from the capture stream regardless of where it renders. A wrong-display share, a multi-monitor recording, a window dragged across mid-review — the capture API receives a frame that doesn't contain the review set. The boundary moves from the monitor to the window, where it actually works.
Mask the titles. Matter names, batch labels, and review-status tags live in window titles. Title masking sanitizes them in the window manager — enumeration, previews, and switchers show generic labels no matter which display the window sits on.
Shield the review session. Matter notifications and deadline alerts held during any shared or recorded period — the notification layer doesn't know which monitor is private, so the shield decides for it.
A routine for review days. The review platform launches → routine fires: platform cloaked across displays, titles masked, banners held. Protection that starts with the session, including the 11 PM review push before a production deadline.
Live preview before any share. The preview pane shows what the sharing tool receives from every display. The wrong-monitor mistake is discovered in the preview or discovered in the record — choose the preview.
The Honest Limitation
Cloaking protects the window — the review discipline itself is untouched. A reviewer who tags a privileged document as responsive has made a doctrine error no capture layer fixes; a production set exported carelessly travels regardless of what's cloaked. Quality control, privilege logs, and review protocols remain the substance. The tool keeps the review set off screens it was never meant to reach; your review process keeps the set correct.
The Bottom Line
Two monitors are a workflow convenience, not a security boundary — and review platforms hold the most sensitive material in the case. Cloak the review window across every display, mask the titles, hold the banners, and preview before every share. The second monitor should be a bigger desk, not a thinner wall.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
