01
Batching should standardise, not obscure
Queues save setup time when files share the same risk policy and export requirements. They should not hide which settings were applied to each output.
Group jobs by client, use-case and required censorship style. Avoid mixing sensitive internal footage with public creator work in the same folder structure.
02
Design the hand-off
Use predictable suffixes for protected files and include a review status. The person approving the output should never need to guess whether a file is a draft or release candidate.
- Client and project identifier.
- Source-to-output mapping.
- Chosen privacy preset.
- Review owner and status.
- Delivery destination.
03
Capacity depends on review, not only hardware
GPU acceleration may shorten unattended processing, but dense or sensitive footage still needs human attention. Plan capacity using both compute time and hands-on review minutes.
Measure corrections per hour and recurring exception types to improve quoting and scheduling.
Apply the workflow
Review real footage locally.
CensorFlow detects and tracks visible faces on your Windows PC, then lets a person correct and approve the result before export.