I’m refining my intake protocol after a 28 GB opposing production last week. I load to Relativity, run dedupe and email threading, build a custodian log, then draft an issue-tag schema tied to elements for depo prep — how do you sequence this and when do you escalate anomalies to counsel? General information only; for case-specific advice, consult a qualified attorney.
I ran a quick time-and-motion on our Apollo PM, carved a 45‑min “critical-path PM” (leak, vaporizer cal, alarms), and moved software verifications to a weekly after-hours batch, all documented in a change-control memo citing the service manual and NFPA 99; loop in Risk and have counsel bless it so Admin sees it’s defensible, @OP. Want the memo template?
Consider using Canvas Badges to auto-issue the three badges and capture time-on-task (https://www.instructure.com/canvas/badges); we mapped each badge to 2–3 Essentials domains with one common rubric and let experienced adjuncts “test out” via a microteaching artifact — think LEGO bricks, not a junk drawer. For load, we paid a flat stipend for completion and counted coached practicum separately as contact hours; if your contract language is murky, a quick HR/legal check helps. Which badge are you planning to pilot first?
One tweak that’s saved me: right after threading, I run a quick “gap report” — custodian-by-date histogram and domain summary — to catch missing date ranges, zero-volume custodians, or off-domain spikes, and I escalate those to counsel in the first hour so scope gets fixed before tagging. Small caveat: if there’s any chance cross-custodian uniqueness affects privilege, I confirm with counsel before finalizing global dedupe. Have you tried Relativity’s Communication Analysis for that domain pass?
I bake in a 2% stratified QC sample right after threading and before issue-tagging as a quick canary check: if “empty text,” password-protected, or container errors top about 1% overall or hit key custodians, I escalate to counsel to set scope and timelines. Then I seed the issue schema from a concept cluster/subject-line pull so depo themes match how the data groups; in Relativity, Analytics clusters make this fast (https://help.relativity.com/RelativityOne/Content/RelativityOne/Analytics/Cluster.htm). What threshold do you use for early escalation — do you go lower on VIP custodians?
But on a 28 GB drop in Relativity, I insert name normalization + domain aliasing immediately post-dedupe so the custodian log doesn’t fracture and threading is truer. Do you also diff the legal hold list against the custodian roster to surface “ghost” senders early, @simon98lee? I brief counsel only when exceptions or non‑English exceed a small baseline, summarized in a one‑page anomaly snapshot.