Guide
Validated Hours vs Raw Capture Hours
Short answer
A validated hour is 60 minutes of footage that has passed QA against a written spec — synced within the ceiling, calibration solved, coverage cells filled, consent documented. A raw hour is unfiltered recording time before that check. Teams routinely discard most bulk egocentric footage as unfit, so budgeting and billing in validated hours is what keeps a coverage or volume number honest.
What is a validated hour?
A validated hour is footage that has been checked against the sync-error ceiling and the capture spec before it counts toward a delivered dataset. That check covers sync within the measured ceiling, calibration solved and within drift tolerance, coverage cells filled against the spec, and consent documented for every participant in frame.
What is a raw capture hour?
A raw hour is simply 60 minutes of recording time, before any of those checks run. It says nothing about whether the footage is in sync, whether calibration held, whether it covers a condition your spec actually needs, or whether consent was documented — only that a camera was rolling.
Why does the difference matter?
Raw-hour billing or reporting pays for, or counts, footage a team cannot necessarily use. Teams routinely discard most bulk egocentric footage as unfit for manipulation once it is checked against a real spec. A volume or coverage number reported in raw hours can therefore overstate what is actually usable; the same number reported in validated hours means the footage already cleared the bar.
How do the two compare?
| Validated hour | Raw capture hour | |
|---|---|---|
| Passed sync-error check | Yes, within the measured ceiling | Not necessarily |
| Calibration verified | Yes, solved and within drift tolerance | Not necessarily |
| Matched to a spec | Yes, coverage cell confirmed | No — just recording time |
| Consent documented | Yes, before it counts | Not necessarily |
| What it measures | Usable training data | Camera-on time |
| How Firsthand bills | Per validated hour | Not billed — rejects are absorbed |
Which unit should you budget in?
Budget and evaluate in validated hours, not raw hours. A practical starting point is 50–100 validated hours per skill, concentrated on the conditions the policy will actually meet, then scaled further only where held-out evaluation shows it is still thin. Reporting the raw-hour number instead just measures how long a camera ran.
FAQ
Validated Hours vs Raw Capture Hours, answered.
01What is a validated hour?
A validated hour is 60 minutes of footage that has passed QA against a written spec — sync within the ceiling, calibration solved, coverage cells filled, and consent documented — rather than 60 minutes of raw recording.
02What is a raw capture hour?
A raw capture hour is unfiltered recording time before any quality check. It confirms a camera was rolling, not that the footage is in sync, correctly calibrated, matched to a spec, or has documented consent.
03Why does billing on validated hours matter?
Raw-hour billing pays for footage a team may not be able to use, since most bulk egocentric footage is discarded as unfit once checked against a real spec. Billing per validated hour aligns the price paid with the data that actually trains.
04How many validated hours do I need per skill?
A practical starting point is 50–100 validated hours per skill, then scale further only where held-out evaluation shows the policy is still thin.
05How does Firsthand handle the difference?
Firsthand quotes and bills per validated hour only, and publishes the reject log so a buyer can see what raw footage did not make the cut and why.
Check it against the sample pack.
40 episodes across 4 environments, delivered in the exact schema these guides describe.