A small production may not have a dedicated Digital Imaging Technician, a full DIT cart, or a separate data-wrangling station. One person may be handling camera gear, batteries, and media at the same time. Even on a small set, the footage still needs to be copied, checked, protected, and handed off properly.

That is where a disciplined on-set data-management workflow matters. The size of the crew can change; the need to preserve original camera files (OCF), production audio (OPA), card identity, copy status, and verification records does not. The goal is a repeatable media lifecycle from camera release through verified backup and editorial handoff.

In this workflow, UP6 provides a portable ingest, storage, and collaboration layer for supported media and connected workstations. Formal checksum verification, ASC MHL histories, source verification, offload reports, advanced metadata management, and specialized QC should still be handled by the production’s approved DIT software and reader/workstation workflow.

A smaller production may combine DIT, data-wrangling, camera-assistant, and production responsibilities, but role compression should not remove the controls that protect OCF and OPA. The essentials are media identity, complete-volume offload, checksum verification, independent copies, controlled card release, access control, and a documented handoff.

Document the media owner, camera and sound units, card/volume ID convention, destination naming, required independent copies, checksum method and manifest format, whether source verification is required, off-site timing, handoff deliverables, and the person authorized to release cards.

Define the Card Release Criteria before the first card is recorded. A source card may return to camera only after every production-required destination has passed the approved verification process, required manifests/reports are saved, exceptions are resolved or documented, required QC is complete, and the designated person approves release.

Preserve the complete source volume and camera-original folder structure unless the camera manufacturer or production specification explicitly requires otherwise. Where practical, record the source volume name or another available identifier in the offload log.

Step 1: Receive, Quarantine, and Log the Card

When a card leaves the camera, confirm the camera unit and card/volume ID before connecting it to the data station. Mark it FULL/NOT RELEASED, place it in a physically separate “to be processed” area, and log custody before beginning the offload. Never allow a full source card to enter the READY/cleared-media pool based only on a completed copy bar.

Step 2: Offload the Complete Camera Volume

Use the same documented offload path for every card whenever possible. Consistency reduces operator error and makes reports easier to audit at wrap or handoff.

UP6 supports direct ingest from UHS-II SD and CFexpress Type B media; microSD/TF and CFexpress Type A media require compatible adapters. PlugBackup provides a PC-free initial-copy path that can be started and monitored from the UP6 touchscreen.

Treat that initial copy as part of the workflow, not as the final verification decision. If the production requires checksum verification, source verification, ASC MHL, or formal offload reports, run the approved DIT verification workflow before the card reaches its release criteria.

Step 3: Verify Data Integrity — Copy Completion Is Not Verification

A transfer reaching 100% only confirms that the copy process reported completion. It does not, by itself, prove bit-for-bit identity between source and destination or create an auditable checksum history.

ARRI advises against simple Finder/Explorer-style copy workflows and states that checksum-verified backups should be the minimum standard for original camera data transfers. ARRI — Data Transfer and File Handling

Netflix states that copies of OCF/OPA should include checksum verification and recommends ASC MHL as the checksum-manifest format. Netflix — Production Assets: Data Management

Where the approved workflow supports it, source verification adds another control by reading and hashing the source again rather than only checking destination copies. Retain the checksum manifest/report with the camera originals.

A useful offload record identifies the card/volume, source, destination volumes, file count and bytes, checksum method, verification result, operator, start/end time, and any warnings or retries.

Step 4: Build Independent Copies — Then Apply 3:2:1 Where Appropriate

The production should define copy count and media diversity before shooting. Netflix describes the industry-known 3:2:1 strategy as at least three copies of OCF/OPA, on at least two media types, with at least one copy in a different geographical location.

Not every production uses the same approved policy, so treat 3:2:1 as a strong reference rather than a universal law. What should never be ambiguous is whether every production-required destination has been successfully verified before the source card is released.

RAID or another redundant pool inside one storage system is not an independent second copy. Storage redundancy and independent backups solve different risks.

Step 5: Separate Data Verification from Content QC

Checksum verification answers whether the destination received the same verified bytes. It does not tell you whether a clip decodes correctly, whether image or audio is usable, or whether a problem already existed in the source recording.

After data verification, perform the production’s required content QC separately. Depending on scope, that may include clip-count or duration sanity checks, selected playback, beginning/middle/end review, audio presence, metadata checks, or comparison against camera and sound reports.

Step 6: Protect the Working Set Against Different Risks

After the required copies have been created and verified, UP6 can add several product-level safeguards around the working storage environment. These controls address different failure modes and should be treated as additional layers—not as substitutes for checksum verification or independent backups.

• RAID / UDR: UP6 supports storage-redundancy options that can improve availability when certain SSD failures occur. A redundant pool inside one UP6 is still one storage system, not an independent backup.
• S.M.A.R.T. monitoring: drive-health indicators can help identify warning conditions early enough to migrate data to a healthy destination.
• Group Files Recycle Bin: shared-file deletion can be routed through an administrator-controlled recovery path, reducing the risk that a collaborator permanently removes project data.
• Built-in UPS: the internal battery provides a power buffer so an interrupted power source is less likely to turn an active transfer or mounted filesystem into a corruption event.
• Recovery Assistant: when files are accidentally deleted from supported memory cards or external media, UP6 can provide an on-device recovery path. Stop using the affected media immediately, eject it safely, and recover files to a separate destination before any new recording or write operation can overwrite the deleted data.

Recovery Assistant is a last-resort safety net for accidental deletion; it does not make an unverified copy verified, and recovery success depends on the deleted data not having been overwritten. Verified independent copies remain the primary protection strategy.

Step 7: Share Without Exposing Camera Originals

Treat OCF/OPA as protected master media. Where practical, restrict write/delete permissions on camera-original directories and provide separate shared or review locations for editorial, producers, or clients.

UP6 provides local workstation and network access through Thunderbolt 4, 10GbE, and AP mode. Use those access options for collaboration without turning protected OCF/OPA into a shared scratch workspace.

Step 8: Hand Off a Verifiable Package to Editorial / Post

A good handoff lets the receiving team identify the camera originals, verify what was transferred, understand any exceptions, and continue the chain without guessing.

Depending on scope, handoff may include OCF with original volume structure, OPA, checksum manifests (ASC MHL where specified), card/offload reports, LUTs/CDLs where applicable, camera and sound notes, proxies or review media, exception/error notes, and the agreed storage or off-site status.

Interrupted transfer: Keep the source card NOT RELEASED. Treat the affected destination as unverified until the approved copy/verification workflow reports success.

Verification failure: Isolate the failed destination, rerun the approved copy/verification process to a healthy destination, and retain the failed-job record.

Drive-health warning: Stop treating the affected destination as a trusted required copy until the footage has been migrated to a healthy destination and verified there.

Unclear card status: Do not infer readiness from file presence or playback. Use the documented Card Release Criteria and a designated approver.

• Confirm camera/sound unit and card/volume ID.
• Keep FULL / NOT RELEASED media physically separate from READY media.
• Log custody and destination path before offload.
• Preserve the complete source volume and camera-original folder structure.
• Create all production-required independent copies.
• Run the approved checksum verification; include source verification if required.
• Retain the checksum manifest / ASC MHL and offload report.
• Perform content QC separately from checksum verification.
• Confirm verified status of each required destination and note any exceptions.
• Restrict master OCF/OPA access; share derived/review media separately where practical.
• Physically separate required copies / move the off-site copy according to the plan.
• Release the source card only after the designated operator confirms all release criteria.

Q: Does UP6 replace professional DIT offload software?

A: No. UP6 provides storage, connectivity, built-in UPS protection, and a PC-free initial-copy path for supported media. When the production requires checksum-verified copy, source verification, ASC MHL, formal offload reports, metadata management, or specialized QC, use approved professional DIT software.

Q: Is RAID the same as a backup?
A: No. RAID can protect against certain drive failures inside one storage system. An independent copy exists on a separate storage system or destination.

Q: When is it safe to format a camera card?
A: Only after the production-defined release criteria are complete. Those criteria should identify the required verified destinations, manifest/report requirements, log status, off-site or handoff condition if applicable, and the person authorized to release the media. “Copy complete” alone is not a release criterion.

Q: Is playback or spot-checking enough to verify an offload?
A: No. Playback is a content-QC step. Use checksum verification for data integrity and perform QC separately according to production requirements.