Skip to content

Acceptance Criteria for Demonstration Video Deliveries

By Noah Loul · Reviewed by Noah Loul · Updated

  1. 01Your data spec
  2. 02Matched to businesses
  3. 03Rights and samples reviewed
  4. 04Licensed delivery
How it works with SourceX: Your data spec → Matched to businesses → Rights and samples reviewed → Licensed delivery.Illustrative

Short answer

Accept a demonstration video delivery only after it passes file checks (every clip decodes, constant frame rate, no dropped or duplicated frames, expected resolution), content checks (task and hands visible, usable exposure and blur), sync and calibration checks, annotation and metadata checks against the plan, and a rights check on every clip. Agree each test, threshold, sample size and remedy in the contract before delivery.

Where this checklist fits

This page adds video-specific tests to the general process in acceptance testing for dataset deliveries, which covers manifests, lots and sign-off. Catching bad recordings while collection is still running is a different job, covered in quality control during collection; detailed label metrics are in measuring annotation quality in task video.

Every pass criterion below is an example. You set the thresholds from your model's needs and write them into the contract before the first file arrives.

How to run acceptance

Run automated checks on every file. Review content manually on a sample stratified by site, demonstrator, device and task, so a single bad station cannot hide in an average. For the manual part, attribute sampling plans of the kind defined in ISO 2859-1, which indexes lot-by-lot sampling schemes by an acceptance quality limit and applies to records as well as products, give a ready framework for sample sizes and accept/reject numbers (ISO, 2026); confirm which edition your contract references. Record every result against the clip ID so failures can be traced and re-delivered.

Checklist

1. File integrity

CheckExample pass criterion (buyer sets)Evidence to request
CompletenessEvery file in the manifest is present and its hash matchesManifest with hashes
Full decodeEvery clip decodes end to end without errorsDecode log
Container and codecMatch the specificationStream probe report
DurationMatches metadata within toleranceProbe report vs metadata
DuplicatesNo identical or near-identical clipsHash and similarity report

2. Video technical quality

CheckExample pass criterion (buyer sets)Evidence to request
Frame rateConstant; no variable-frame-rate segmentsPer-frame timestamp report
Dropped or duplicated framesBelow a set fraction per clipPer-clip counts
ResolutionAs specified; no upscaled footageProbe report; sample frames
Stabilization and croppingAbsent where the spec forbids themDevice settings log
ExposureClipped-pixel share below threshold on sampled framesExposure statistics
BlurShare of blurred frames in task segments below thresholdSharpness score distribution

3. Content usability

CheckExample pass criterion (buyer sets)Evidence to request
Correct taskSampled clips match their task codeReviewer log
Hand visibilityPer-task share of time with both hands visible meets targetPer-task report, not an overall average
Task completenessClip includes the start and end of the task instanceReviewer log
Off-task contentBelow a set share of clip timeReviewer log
ViewpointMount and angle as specifiedDevice and mount metadata

4. Synchronization and calibration

CheckExample pass criterion (buyer sets)Evidence to request
Calibration presentIntrinsics for every device unit, extrinsics for every multi-camera sessionCalibration files
Calibration qualityReprojection error below thresholdCalibration reports
Stream alignmentSlate or tap offset within tolerance in every sessionSync test results
TimestampsMonotonic, with the clock source documentedTimestamp report

Planar-pattern calibration is standard practice (Zhang, 2000), and toolboxes such as Kalibr write a PDF report, a text summary and YAML that can be delivered as evidence (ETH Zurich ASL). Robot datasets such as DROID ship calibration with every episode (Khazatsky et al., 2024); per-session calibration is a reasonable expectation for commissioned human capture too.

5. Annotations

CheckExample pass criterion (buyer sets)Evidence to request
CoverageEvery required label layer present on every clipLabel inventory
AgreementDouble-annotated subset meets boundary and label thresholdsAgreement report with sample size
Gold-set auditYour own audit of a sample meets thresholdYour audit results
VersioningGuideline version recorded on every labelLabel metadata

6. Metadata and coverage

CheckExample pass criterion (buyer sets)Evidence to request
SchemaAll records validate against the agreed schemaValidation log
CoverageCounts per factor meet the plan, gaps explainedCoverage report
Held-out factorsReserved sites or operators absent from training lotsSplit report

Field definitions are in the metadata schema for workplace demonstration clips, and quotas in coverage planning for demonstrations.

7. Rights, consent and redaction

CheckExample pass criterion (buyer sets)Evidence to request
Permission referenceEvery clip points to a consent or permission recordRegister extract
RedactionSpec applied; sampled frames show no missed faces or screensRedaction report and version
WithdrawalsClips of withdrawn individuals removedWithdrawal log
Permitted usesMetadata matches the licenseLicense schedule

Large datasets document consent and de-identification as part of the release; Ego4D describes consenting participants and de-identification procedures (Grauman et al., 2021). Ask for equivalent documentation. Redaction trade-offs are covered in face and bystander redaction.

Red flags

  • Variable frame rate across the archive and no per-frame timestamps.
  • Clips re-encoded several times, or upscaled to meet a resolution requirement.
  • Calibration "available on request" that never arrives.
  • Hand visibility reported only as one average across all tasks.
  • Agreement figures without a gold set or a sample size.
  • Consent described in aggregate ("all staff signed") with no per-clip reference.
  • Metadata filled with defaults: identical timestamps, one operator ID everywhere.
  • Sample clips visibly better than the bulk delivery.

Remedies to agree in advance

Write down what happens when a lot fails: re-delivery of failed clips, re-annotation, a credit, or rejection of the lot, each with a deadline in the contract. Agree who pays for re-testing, and whether accepted clips can later be rejected if a rights problem surfaces.

Questions to ask suppliers

  1. Will you run the automated checks before delivery and share the reports?
  2. How do you detect and report dropped frames and variable frame rates?
  3. Which calibration files and reports accompany each device unit and session?
  4. What hand-visibility rate does each task meet, and how was it measured?
  5. How was annotation agreement measured, and on what sample?
  6. How does each clip reference its consent or permission record?
  7. What remedies apply if a lot fails acceptance?
  8. Were the sample clips produced by the same pipeline as the bulk delivery?

Discuss your requirements

If you are drafting acceptance terms for a demonstration video purchase, share your tests and thresholds with SourceX along with the data you need. SourceX checks the data and the supplier's licensing permissions, agrees allowed uses in a license, and coordinates delivery; it reviews each requirement and follows up about potential sources, though a request does not guarantee a match. For broader diligence, see the training data due diligence checklist, the workplace task demonstration hub and the humanoid training data guide.

Explore sourcing and licensing options with SourceX

Sources

Frequently asked questions

What should be checked before accepting a demonstration video delivery?

Each clip should decode, run at a constant frame rate with no dropped or duplicated frames, and show the expected resolution. Content checks cover task and hand visibility, exposure and blur, and sync, calibration, annotation, metadata and rights checks follow against the plan.

Why should acceptance checks use a stratified sample rather than an overall average?

Automated checks run on every file, while manual content review uses a sample stratified by site, demonstrator, device and task, so a single bad station cannot hide in an average. Hand visibility should be reported per task rather than as one overall figure.

What remedies and thresholds should be agreed in advance for a failed delivery?

Thresholds, sample sizes and remedies should be written into the contract before delivery. Remedies can include re-delivery of failed clips, re-annotation, a credit or rejection of the lot, each with a deadline, and the contract should say who pays for re-testing.

Describe the data your robots need

Describe the tasks, modalities and permitted uses you need. SourceX reviews the requirement and follows up about potential sources; a request does not guarantee a match.

Discuss your humanoid training-data requirements with SourceX
See if you qualify