DIT and Data Management: The Workflow That Protects the Shoot

In 1998, someone at Pixar ran an rm -rf command against the wrong directory and deleted roughly 90 percent of the files that made up Toy Story 2. That alone would have been recoverable, if the automated backup system had been doing its job. It hadn't. The backups had been silently failing for over a month, and nobody had noticed. The film survived because a technical director named Galyn Susman happened to have a two-week-old copy sitting on a home computer, because she'd been working from home during maternity leave. Without that accident of circumstance, a finished animated feature would have gone back to a two-week-old assembly, best case.

That story gets told a lot in software circles. It should get told more often on commercial sets, because the same failure mode, a backup system nobody actually verified, is the exact risk a DIT and a real data management protocol exist to eliminate. It is the least glamorous job on a call sheet and arguably the one with the highest downside if it's skipped.

The 3-2-1 Rule Is the Floor, Not the Whole Job

The baseline standard across professional productions is the 3-2-1 rule: three copies of every file, on two different types of media, with one copy stored offsite. It's a simple idea and it's simple for a reason, redundancy has to be dumb-proof to actually protect anything, because the moment a backup protocol requires a judgment call under deadline pressure, someone skips a step.

What the 3-2-1 rule doesn't solve on its own is whether the copies are actually good. A straight file copy can silently produce a corrupted file, a dropped frame, a partial write that looks complete in a file browser but isn't. This is where checksum verification separates a real data management workflow from someone dragging a folder from a card to a drive and hoping. Checksum tools hash every source file, MD5, xxHash, or similar algorithms, before and after the transfer and confirm a bit-for-bit match. If the hash doesn't match, the copy failed, and everyone knows it failed before the card gets wiped, not three weeks later when an editor opens a file that won't play.

The industry has actually standardized this. The American Society of Cinematographers publishes the ASC Media Hash List, ASC MHL, an XML-based specification that tracks every hash from the moment a card is offloaded through final archive, a chain of custody for the literal digital negative of the project. It's implemented in the tools that actually run on set: Pomfort Silverstack and MediaVerify, Hedge's OffShoot, YoYotta, and ShotPut Pro. A production running any of these isn't doing extra work for its own sake. It's building a paper trail that means "we don't actually know if that card copied clean" is never a sentence anyone has to say two weeks into post.

What a DIT Actually Does, Beyond Moving Files

The job title gets flattened in casual conversation into "the person who copies the cards," which undersells it by a wide margin. A working DIT manages the on-set color pipeline, applying LUTs so the director and DP see something close to the intended look in real time. They monitor exposure and sensor issues as they happen, catching a problem while there's still time to reshoot the take instead of finding it in the edit bay. They generate camera reports, the legal record of exactly what was shot: codec, ISO, lens, media ID, backup verification status, the paper trail a colorist and a VFX vendor both need months later. And they assemble dailies, syncing audio, baking in the show LUT, generating proxies, so an editor and a client reviewing footage the next morning are looking at something usable, not raw camera-native files nobody's system can even play back smoothly.

Rates for this role split sharply between union and non-union markets. IATSE Local 600's published 2025-2026 CPA scale runs $90 an hour in Los Angeles with an eight-hour minimum call, which works out to $720 for a standard day, and $89.99 an hour in the Northeast Corridor with a ten-hour minimum. Outside union scale, the range is wide: entry-level data wranglers run roughly $300 to $500 a day, mid-level union-adjacent DITs land in the $600 to $1,200 range, and senior DITs on feature-level work command $1,500 to $2,500 or more, generally with a separate kit rental fee of $200 to $800-plus a day on top, since the DIT often supplies their own cart, monitors, and backup hardware.

Whether a production needs a dedicated DIT or can get by with a 2nd AC absorbing data duties comes down to card turnover and camera count. A single-camera interview day with modest card changes is a reasonable ask for a 2nd AC to handle alongside their other duties. A multi-camera commercial shoot with frequent card swaps, on-set color decisions that matter to the client review, and same-day dailies expectations is a different job entirely, and treating it like an add-on task for someone already busy pulling focus is how corners get cut under pressure.

The Media Math Nobody Budgets For Until It's a Problem

Cinema camera data rates have outpaced what most non-technical clients assume a "video shoot" generates. Using ARRI's own published data rate calculator: ARRIRAW at 4.6K open gate, 24 frames per second, on the Alexa 35 runs approximately 2.01 terabytes per hour. The same body recording ProRes 422 HQ at UHD is far lighter, around 733 megabits per second. RED's V-Raptor 8K in RAW HQ runs roughly 1.53 terabytes per hour at 24p, climbing to as much as 3.83 terabytes per hour at 60p. A two-camera commercial shoot day with real roll time, not just picture-locked takes but rehearsals, safeties, and multiple angles, adds up fast, and the honest answer is that no single sourced figure exists for a universal "typical commercial shoot day" total, because it depends entirely on camera count, codec choice, and how much the crew actually rolls. The math above is enough to show why a production planning to shoot RAW on two bodies for a full day needs a real storage plan, not an assumption that a couple of portable drives will cover it.

Current card pricing reflects that volume. A 512GB CFexpress Type B card runs roughly $400 to $450. A 1TB card from ProGrade Digital lists around $750, with a RED-certified 1TB variant closer to $1,425. None of that is a rounding error on a production budget, and none of it should be treated as an afterthought line item added after the camera package is already locked.

Cloud Workflows Are a Supplement, Not a Replacement

The 2025-2026 trend worth noting: cloud-based dailies and storage platforms like LucidLink, now more tightly integrated with Adobe's Frame.io, are unifying dailies review with production media without forcing a duplicate copy for every review pass. Backblaze B2 has become a common landing spot for cost-effective long-term archival once a project wraps. What this doesn't do is replace the physical, on-set backup chain. Raw camera data volumes at the rates above still exceed what most set locations can realistically upload in real time, so cloud tools extend the offsite leg of the 3-2-1 rule after the fact, rather than substituting for a checksummed local backup taken the day of the shoot.

The Job Nobody Notices Until It Fails

A DIT doing the job right is invisible. Nobody at video village thinks about camera reports or checksum logs, the same way nobody at Pixar thought about backup verification until the day it mattered. That's the actual argument for budgeting this properly instead of treating it as a place to cut costs on a tight job: the entire value of the role only becomes visible in the scenario where it isn't there, a corrupted card, a dropped hard drive, a hero take that exists in exactly one unverified copy. The 3-2-1 rule, checksum verification, and a DIT who actually knows the difference between a file copy and a verified backup are not overhead. They're the insurance policy that means a bad afternoon on set stays a bad afternoon, instead of becoming the reason a shoot has to happen twice.