Capture acceptance
Specify resolution, frame rate, focus, framing, continuity, task completion and permitted interruptions. Define accepted-hours counting and what causes rejection.
A project framework for recording quality, documented permissions and controlled delivery. Controls are defined in the project agreement; no certification or blanket legal-compliance claim is made.
Specify resolution, frame rate, focus, framing, continuity, task completion and permitted interruptions. Define accepted-hours counting and what causes rejection.
Check the demonstrated sequence against the brief. Where annotations are commissioned, agree taxonomy, boundary conventions, review sampling and discrepancy handling.
Confirm recording permission, suitable participants, equipment restrictions, induction and confidentiality boundaries. An employer agreement alone does not replace any necessary individual authorization.
Agree contributor and site documentation, licensing scope, permitted downstream uses, distribution restrictions and any exclusivity before recording.
Plan for bystanders, faces, voices, screens, labels, credentials and sensitive locations. Avoid unnecessary personal data; define redaction or exclusion and how the result is checked.
Agree the transfer method, authorized recipients, file manifest, retention period and deletion responsibilities. Do not imply security controls or regions that have not been agreed and implemented.
Meets agreed criteria. Recorded as accepted duration or deliverable units.
Reason documented against the protocol. Excluded from accepted delivery unless otherwise agreed.
Scope and terms checked before another attempt. No automatic promise of free recapture is implied.
The signed license defines permitted users and uses. Training, evaluation, redistribution, resale and exclusivity should be addressed explicitly rather than inferred from delivery.
Only where a suitable protocol, qualified personnel, site permission and safety requirements can be satisfied. Some requests may be limited to staged or isolated equipment, or declined.
The proposal defines accepted footage, review records and any rejected-file handling. The buyer should know which files are excluded and why.
No blanket compliance or certification claim is made here. Data roles, legal basis, notices, agreements, safeguards and any applicable transfer requirements must be assessed for the actual project with appropriate review.
Before capture, the project agreement defines permitted uses, site authorizations, participant information and treatment of faces, voices, screens and bystanders. The delivery package includes only the rights evidence agreed for the project and appropriate to share.
Storage, access, transfer and deletion requirements are assessed for each brief. The capture and review steps on this page describe the proposed project process.