Privacy and preparation
Robotics data collection stop rules: when should a video session stop?
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Stop a workplace video collection session when continuing would record something the permissions do not cover, put a person at risk, or produce footage nobody can use: a worker withdraws, an unconsented person or confidential material enters frame, a hazard or close call occurs, the task leaves its agreed boundary, or camera and sync checks fail. Decide in advance whether each trigger ends the clip, the session or the program, and log every stop.
Video and sensors
Robotics data collection
Key takeaways
- Write stop rules before the first session, with three scopes: discard the clip, end the session, or pause the program.
- Permission, safety and quality triggers each stop capture for different reasons and leave the footage in different states.
- Anyone on the floor may call a stop, and the worker on camera must be able to do so without consequence.
- Ordinary task failures and recoveries are valuable footage; a stop rule that removes them weakens the dataset.
- Every stop leaves a log entry with the trigger, time, footage disposition and restart condition.
What stop criteria should govern workplace video collection sessions?
Three kinds of event should stop capture: a permission trigger, where the camera would record something nobody agreed to; a safety trigger, where continuing could hurt someone; and a quality trigger, where the footage would be unusable. The rule for each says how far the stop reaches and what happens to what was already recorded.
Robot learning tools already separate these scopes. The LeRobot recording tool, for example, gives the operator one key to end the current episode early, one to cancel the episode and re-record it, and one to stop the whole session. A workplace video program needs the same three levels, plus a fourth that pauses all sessions while something is fixed.
Writing the rule in advance matters more than its exact wording. A camera operator deciding in the moment, under pressure to finish a shift's quota, will keep rolling more often than a written rule would allow.
Clip, session or program: how far should a stop reach?
Match the scope of the stop to the scope of the problem: a defect in one clip discards that clip, a problem with today's conditions ends the session, and a problem with the permissions or the setup pauses the program until it is fixed.
When in doubt, choose the wider scope and narrow it after review. Footage held at session level can be released clip by clip once a reviewer has looked at it, but footage that kept flowing into the pipeline after a permission problem is much harder to pull back, because it may already have been copied, annotated or sampled into a training batch.
| Scope | Typical triggers | What happens to footage | Who restarts it |
|---|---|---|---|
| Clip | Task interrupted by an unrelated job, camera bumped, one take obviously unusable | Clip marked discard or re-record; kept only if it shows a real task failure | Camera operator, immediately |
| Session | Worker asks to stop, unconsented person in work area, sync lost on the primary camera | Footage since the last clean checkpoint held for review | Collection lead after the cause is cleared |
| Program | Withdrawal by a whole team, close call, confidential process exposed, scope dispute | All footage from affected sessions quarantined | Site owner and privacy or safety reviewer jointly |
| Record only | Brief occlusion, passing consenting colleague, minor lighting change | Segment flagged with a timestamped note, capture continues | No restart needed |
The collection stop rule, trigger by trigger
Use this table as the rule itself. Adapt the triggers to the site, but keep every column filled; a trigger without a restart condition becomes a session that never resumes or one that resumes too soon.
Brief the rule at the start of every session, not only at onboarding, and print it at each station. Operators change, and a substitute operator who has never seen the rule will default to keeping the cameras running. Review the log weekly: a trigger that fires every session usually points to a setup problem, such as a camera angle that keeps catching a doorway, rather than to bad luck.
| Trigger | Scope | Immediate action | Footage disposition | Restart condition |
|---|---|---|---|---|
| Worker on camera asks to stop | Session | Stop recording, no questions asked | Hold since last checkpoint; worker decides keep or delete | Worker confirms on a later day, or a different worker |
| Worker withdraws from the program | Program for that person | Remove from roster | Their identifiable footage deleted or held per the signed terms | Not restarted for that person |
| Person without consent enters frame | Clip or session | Pause until they leave | Mask or discard the affected frames | Work area cleared and signage checked |
| Confidential screen, document or customer item in view | Session | Stop and reframe | Quarantine for review | Camera position or masking changed |
| Hazard, injury or close call | Program | Stop all capture, make the area safe | Preserve as incident evidence, outside the dataset | Safety review closed |
| Camera or rig creates a hazard | Session | Stop and remove the rig | Keep clean footage before the event | Mounting fixed and checked |
| Task leaves the agreed boundary | Clip | Stop the clip at the boundary | Discard out-of-scope portion | Back on an agreed task |
| Time sync or calibration check fails | Session | Stop and re-sync | Keep with a sync flag or discard | Sync test passes |
| Storage or encryption fault | Session | Stop writing | Verify what was written | Fault fixed and verified |
| Audio captured where audio was not agreed | Program | Stop and disable audio | Delete the audio track | Configuration confirmed with audio off |
Who may call a stop, and why the worker on camera must be able to
Anyone on the floor should be able to call a stop: the worker being filmed, the camera operator, the supervisor, and the site's safety lead. The worker's right matters most, because a permission that cannot be paused is not much of a permission.
The European Data Protection Board's consent guidelines explain why. Given the imbalance of power between employer and staff, the board says employees can give free consent only in exceptional circumstances, where saying no has no adverse consequences at all. Many programs therefore rely on a different legal basis or on separate releases, but the practical point holds everywhere: if stopping a session costs a worker a bonus, a shift or goodwill, the consent behind the footage is weak.
Make stopping cheap. Put a visible stop signal at each station, say at the start of each session that stopping needs no reason, pay for the session regardless, and record the stop in the log without the worker's reason unless they offer one.
Safety triggers: what stops the cameras immediately
Any injury, hazard or close call stops all capture on that site until the safety review is finished. Footage of the event becomes incident evidence for the site, not a training clip for the program.
OSHA describes close calls, sometimes called near misses, as events where a worker might have been hurt if circumstances had been slightly different, and it encourages employers to investigate them along with injuries. A collection session is an unusual condition on a working floor: extra people, mounted cameras, workers told to perform tasks for the record. Treat a close call during a session as possibly caused by the session until the review says otherwise.
Whether incident footage can later enter a dataset is a separate decision, made by the site owner with its safety and legal advisers, and often affected by insurance or litigation holds. The stop rule only keeps that footage out of the normal pipeline until that decision is made.
The collection equipment is part of the hazard picture. Head-mounted cameras narrow peripheral attention, tripods and cable runs sit in walkways, and battery packs add weight to a worker's belt. Walk the station with the site's safety lead before the first session, agree where rigs may stand and what clearance they need, and treat any later change to that setup as a reason to repeat the walk-through before capture resumes.
The incident log: what every stop must leave behind
Log every stop, including clip-level ones, in the same structure. The log is what lets a reviewer, and later a dataset buyer, see that gaps in the footage are explained and that the permissions were respected.
| Field | Illustrative entry | Why it is needed |
|---|---|---|
| stop_id and session_id | S-14, session 2026-10-06-B | Links the stop to the footage and the roster |
| trigger and scope | Unconsented person in frame; clip | Shows the rule was applied as written |
| time and camera | 10:42:07 to 10:43:30, cameras 1 and 3 | Locates the affected frames exactly |
| called_by role | Camera operator | Shows who exercised the stop, without naming the worker |
| footage disposition | Frames masked, clip retained | Explains every gap and every masked span |
| restart condition and time | Area cleared; resumed 10:46 | Proves the condition was met before capture resumed |
| follow-up | Add signage at the side door | Turns repeated triggers into setup fixes |
| reviewer sign-off | Privacy reviewer, next day | Required before quarantined footage moves on |
Which failures belong in the footage instead of stopping it?
Keep recording through ordinary task failures and the worker's recovery: a dropped part picked up, a mis-scan redone, a jam cleared by the normal procedure. Those moments are often the most useful footage in the set, and a stop rule that fires on them produces a dataset of perfect runs that teaches a model nothing about recovery.
Robot learning practice treats recovery as data. LeRobot's human-in-the-loop collection guide, for instance, records the operator's interventions, recovery movements and corrections alongside autonomous segments, because that data teaches a policy how to handle failures. Workplace video for task learning has the same need.
The line is between a failure within the task and an event outside it. A worker fumbling a box is within the task; a worker stepping into a marked hazard zone to retrieve it is a safety trigger. Write examples of both into the rule so operators apply it the same way.
Some events need only a note in the log, not a stop; stopping for them wastes sessions and leaves gaps that are harder to explain than the event itself.
- A brief occlusion on one camera when other cameras still cover the task: flag the segment.
- A consenting colleague passing behind the worker: no stop if the agreement covers incidental appearance and agreed masking is applied later.
- A change in lighting or a door opening: note it, because variation in conditions is useful.
- A worker pausing to answer a question about the task: keep it and mark the pause.
- Audio that is switched off by design: nothing to stop. The EDPB's video guidance recommends switching off functions such as audio when they are not needed and masking or blurring third parties, so settle these settings before capture rather than stopping for them.
Worked example: a packing-line session with three stops (illustrative)
This example is illustrative. A site plans a four-hour session at two packing stations with three fixed cameras and two consenting workers. The rule above is printed at each station.
At 40 minutes, a delivery driver walks through the frame of camera 2. The operator pauses capture for 3 minutes, logs a clip-level stop and later masks 11 seconds of frames. At 95 minutes, the sync check between cameras 1 and 3 fails by more than the agreed tolerance; the session pauses for 12 minutes while the clocks are re-synced, and the 6 minutes before the failure are kept with a sync flag. At 150 minutes, the worker at the first station says they would like to stop for the day. Capture at that station ends without discussion, and the worker decides the next morning to keep the footage.
The session ends with three log entries, about 2 hours and 18 minutes of usable footage at the first station and 3 hours and 45 minutes at the second, including seven recorded recoveries from mis-scans that were deliberately not stopped. The exception in this example is the sync failure: if the program had needed precise multi-camera alignment for hand pose, the flagged minutes would have been discarded instead of kept.
What a stop rule cannot settle on its own
A stop rule handles events inside a session; it does not establish the legal basis for filming, the content of releases, works council or union obligations, or biometric rules. Those need counsel and, where relevant, worker representatives before the first session.
Large research collections show the standard to aim for. The Ego4D project required informed consent from camera wearers, who could withdraw at any time and review and redact their own video. A business program will rarely match that machinery, but the stop log is how it shows equivalent respect for withdrawal.
Document the stop rule and the log summary with the dataset. Datasheets for Datasets, a widely used documentation framework, gives the collection process its own section, and stop counts, discarded minutes and masked spans belong there so that a later user knows what the footage leaves out.
Bringing logged footage to a licensing review
Footage with a written stop rule and a complete log is easier to assess for licensing, because a reviewer can see what was consented to, what was removed and why. A site that wants to license its footage to AI developers can do so through SourceX, which covers sourcing, rights review, contracting, preparation, delivery and payment.
The first step is a short company assessment, and no footage needs to be uploaded to see whether a company qualifies. No clip leaves the site until the company has approved the scope and terms and signed its agreement.
Frequently asked questions
Should a session stop when a worker makes a mistake on camera?
No, not for an ordinary mistake and recovery within the task. That footage is often the most useful in the set. Stop only when the mistake creates a hazard or takes the task outside its agreed boundary.
What happens to footage recorded before a worker withdraws?
Hold it outside the pipeline and follow the release the worker signed and the law that applies. Many programs let the worker choose between keeping and deleting their identifiable footage. Counsel should confirm the rule before the first session.
Who should be allowed to stop a recording session?
Anyone on the floor, including the worker being filmed, the camera operator, the supervisor and the safety lead. Stopping should need no reason and carry no penalty.
Can footage of a near miss go into the training dataset?
Not by default. Stop capture, preserve the footage as incident evidence and complete the safety review first. Whether it can later be licensed is a separate decision for the site owner and its advisers, and insurance or legal holds may apply.
How detailed should the incident log be?
Detailed enough that every gap or masked span in the footage has an entry: trigger, scope, time and cameras, who called it by role, what happened to the footage, the restart condition and a reviewer sign-off.
Sources
- LeRobot's recording tool has separate controls to end an episode early, cancel and re-record it, and stop the whole session. Source
- LeRobot's human-in-the-loop collection records interventions, recovery movements and corrections as training data so a policy learns to handle failures. Source
- The EDPB's consent guidelines say employees can give free consent only in exceptional circumstances where refusing has no adverse consequences. Source
- OSHA describes close calls or near misses as events where a worker might have been hurt in slightly different circumstances and encourages employers to investigate them. Source
- The EDPB's video device guidelines recommend switching off unneeded functions such as audio and masking or blurring third parties. Source
- The Ego4D paper required informed consent from camera wearers, who could withdraw at any time and review and redact their own video. Source
- Datasheets for Datasets proposes a documentation format for datasets with a dedicated section on the collection process. Source
See if your company qualifies
A short company assessment. No data uploads are needed.