Now recruiting capture teams worldwide. Get paid to record first-person video of real work.

Apply to capture

Task row

Egocentric Tray Assembly and Delivery Data

Arranging a tray, carrying it and setting it down is a short chain of two-handed moves that hospitality work repeats all day. This page covers egocentric tray assembly data for the one catalog row that names it: what the row says, how the site describes its capture setup, what a handheld gripper tray carrying dataset can and cannot claim, and what the site does not state. We run custom hospitality data collection fast and on demand against a spec you write, as custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
Catalog row
"Tray assembly + delivery"; Easy; Available on request
Environment
Hospitality Service Set (table, bar, room)
Capture setup
Multiview rig + handheld grippers
License
Perpetual, buyer-owned

Why this row

What does tray assembly and delivery data need?

01

Three verbs, named as the catalog names them

"Tray assembly + delivery" reads "Arrange, carry, and set a tray." A spec names arrange, carry and set as separate steps and says where each begins and ends, rather than relying on one generic serving label.

02

Hands that stay visible while they hold something

A held tray covers part of the hands and the work. 3D hand pose carries a per-joint visibility flag, so a finger hidden under a tray edge is marked as hidden rather than silently filled in.

03

A capture mode that maps to a gripper

The site says a staged working set recorded by a multiview rig, with the operator using handheld grippers, lets demonstrations map onto a robot end effector. That is the capture setup the row lists.

04

Honest status

The row is Available on request. That means it is scoped and recruited to spec when a buyer asks for it, and it is not a claim that footage of this task has been delivered.

Definition

What is egocentric tray assembly and delivery data?

It is video of a person arranging items on a tray, carrying it and setting it down, recorded to a written spec, with hand pose and action segments alongside. People reach it through several phrasings: egocentric tray assembly data, first-person room service tray video, a handheld gripper tray carrying dataset, or custom hospitality data collection. They describe one request from different angles.

The site does not state a room service, hotel or guest setting for this row. The catalog places the row in a Hospitality Service Set described as a table, a counter or bar, and a housekeeping or room area, and the row wording is "Arrange, carry, and set a tray." This page stays inside that wording. The data is human capture by paid, consented contributors, not robot or teleoperation data, so using it for a specific robot still needs your own retargeting step.

Catalog row

Which catalog row covers tray assembly, and what is its status?

One. "Tray assembly + delivery" sits in the Hospitality Service Set (table, bar, room) environment of the Hospitality & Events sector. Its description reads "Arrange, carry, and set a tray." It is rated Easy, lists the capture setup "Multiview rig + handheld grippers", and has the status Available on request.

Available on request means the work is scoped and recruited to spec when a buyer asks. It is not a statement that footage of this task has been delivered. The site states no delivered hours for the row, so this page claims none, and it names no tray contents, ware or route because the catalog names none. The first table below reproduces the row exactly as the catalog states it, with neighbouring rows shown for context only.

The setting

What is the Hospitality Service Set environment?

The catalog describes it with three examples: a table, a counter or bar, and a housekeeping or room area. That is an environment type, not a named venue. The site does not say that any tray capture takes place inside a particular hotel, restaurant or client facility, and this page does not claim it. The site also states that Firsthand does not capture at a customer’s own facility, so the set is a capture setting arranged for the task.

The site classes hospitality as a thinner-coverage environment, where vetting operators for guest-facing and back-of-house roles is the bottleneck rather than demand for the task. It also states that front-of-house hospitality settings are bystander-dense, which lowers yield after de-identification. A tray spec has to allow for both, and the sections on speed and privacy below return to them.

Capture setup

What capture setup does the row list, and what does egocentric mean here?

The catalog lists "Multiview rig + handheld grippers". The site describes that mode as a staged working set recorded by a multiview rig while the operator performs the task with handheld grippers, so demonstrations map onto a robot end effector. The catalog names a second mode, a head-mounted phone or a multiview rig, for other environments, and the tray row does not list it. This page therefore does not describe the tray row as head-mounted phone capture, and it does not describe it as stereo capture.

Egocentric is the name of this page family on the site, which treats first-person and operator-view capture as its default. How a head or operator view fits into the multiview rig for this row is not stated, and neither is a camera count, a resolution, a frame rate or a lighting setup. Those are agreed in the written spec rather than assumed. If a stereo pair matters to your policy, the site offers stereo through its general stereo offer, and it is agreed in the spec and confirmed on a Spec Pilot. The stereo sandwich and salad page shows how that conversation reads for another row in a different environment.

Handheld grippers

Why does a handheld gripper matter for carrying a tray?

The catalog lists handheld grippers because the operator holds a gripper rather than a bare hand while performing the task, and the site says this lets demonstrations map onto a robot end effector. For a tray, that matters because arranging, lifting, carrying and setting down are the moves a policy has to reproduce with a gripper, not with five fingers. A handheld gripper tray carrying dataset keeps the demonstration closer to the hardware a robot would use than a bare-hand clip does.

The site does not state which gripper is used, how it attaches or how it holds a tray, and this page names none. It does not state a tray weight, a tray size or a carrying distance either. The site also does not claim that a model trained on this capture succeeds at the task, and it does not claim that human capture replaces robot data. The embodiment mapping is a design choice agreed in the skill spec.

Steps

Which steps of tray work can a spec label?

The row names three actions: arrange, carry and set. A spec that says "serve a tray" produces one long action segment. A spec that names the steps produces a sequence you can slice by step: where the arranging begins and ends, where the lift ends and the carrying starts, and where setting the tray down finishes. The site’s skill-spec guide says to name the verb and the noun rather than a broad activity, and the row’s own verbs are the place to start.

Action segments are frame-accurate and share one clock with the video, so a step boundary lines up with the frame where it happens. Contact events mark when fingers make and break contact with an item or a surface, and the spec decides what counts as the item: the tray, a piece of ware on it, or the surface it is set on. Whether an episode covers one step, one full tray or a run of several trays is a spec decision, because the site sets no episode length.

Difference

How is this different from the table setting, meal plating and amenity restocking pages?

This page treats the tray as the unit of work. The egocentric table setting and clearing page is organised around two other rows, Set table service and Clear + bus table, and mentions the tray row only as a neighbouring row in the same environment. The egocentric meal plating and serving page covers plating, portioning and serving as a chain, and it lists the tray row among its serving rows. Neither page has tray assembly and delivery as its main topic, which is why this page exists.

The egocentric hotel amenity restocking page covers a different task. Its lead row, "Hotel Amenity Restocking", sits in the Hotel & Lodging environment, is rated Easy, lists a head-mounted phone or multiview rig, and is Ready to deploy. A separate row in the Hospitality Service Set, "Restock amenities", reads "Restock a minibar/amenity tray." and is Easy and Available on request. Restocking items onto a tray is not the same as arranging, carrying and setting a tray, and the second table below sets the pages side by side.

Neighbouring rows

Which neighbouring rows can a tray spec combine with?

The same environment lists Set table service ("Lay a full place setting."), Clear + bus table ("Stack dishes, bus, and wipe."), Pour + serve beverage ("Pour a drink and serve to a place."), Fold napkins ("Fold napkins to a set style."), Restock amenities ("Restock a minibar/amenity tray.") and Wipe + reset counter ("Clear, wipe, and reset a counter."). These are separate rows, listed with the same capture setup, and they are not steps of the tray row.

A program that wants a whole service routine can name several rows in one spec and say how episodes are divided. The catalog does not describe a combined routine, so this page does not claim that one exists. Each added row is its own scoping question, with its own status as the catalog lists it.

Streams and labels

What does an episode carry, and what labels can a tray spec ask for?

The site states the episode schema for its custom collections: head and wrist RGB, depth, 3D hand pose, contact events and action segments, ten streams in all, aligned on one hardware clock and synced under 2 ms. Hand pose is 21 joints per hand with a visibility flag for each joint. The site’s only language data tied to Firsthand capture is one task instruction per episode.

The site does not state which of these streams the multiview rig with handheld grippers emits for the tray row, so confirm the list in the spec and on a Spec Pilot. Instance masks are stated on other pages and not on the hospitality pages, so say so in the spec if your policy needs them. Object and ware labels use the terms your spec sets, so they follow the vocabulary your training stack expects.

Not stated

Which tray labels and measurements are not stated?

Tray layout and goal-state labels are not stated, so the site does not describe a tagged result such as a correctly arranged tray or a per-item position. Object identity or category labels, object 6-DoF pose and breakage or outcome labels are not stated. Tray weight, tray size, carrying distance, route and time are not stated, and neither is a success rate or a throughput figure.

Force and tactile streams are not stated, so the data carries no reading of how heavy a tray is or how firmly it is held. If your policy needs any of these, they are defined in the written spec as annotation depth, and the quote covers them before capture begins. The third table below lists each item beside what the site says about it.

Hard cases

Are slips and recoveries captured?

The site states that, once footage is captured, failure or recovery cases are captured and labeled where they occur. A slipped item on a tray, a re-arrangement or a tray set down again belongs in that category, because a policy that only sees clean takes has no model of recovery. The site gives no rate for how often these cases occur, and this page gives none.

Whether failures should be kept in a batch, and how a recovery is segmented, are spec decisions. QA also applies the site’s stated reject rules: an episode is rejected for a sync breach beyond the ceiling for more than three consecutive frames, for the manipulated object out of frame for more than 15 percent of the episode, for an undocumented bystander, or for a mismatch against the named skill spec. For a tray, the spec decides whether the manipulated object is the tray or an item on it. A reject log ships with every batch.

Privacy

How do consent and anonymization work for tray tasks in a service setting?

Capture follows a documented consent chain for the operator wearing or holding the capture hardware, and the consent record is part of the delivery. Every episode links to a signed contributor release. Anyone else who appears in frame, such as a guest, a co-worker or a bystander, is handled through the site’s bystander and de-identification process rather than being captured as a second consenting participant.

For every delivered episode the site states that faces and screens are blurred irreversibly, that a reviewer confirms no un-consented person is identifiable, and that footage that cannot be de-identified is discarded. The anonymization record ships with the data. Front-of-house settings yield less for this reason, so who may appear in frame is agreed in the spec before capture. This is not legal advice, and the executed agreement controls.

Scale and speed

How fast can custom tray assembly data be collected at scale?

The row is Available on request, so this is custom collection, not an off-the-shelf purchase. It is custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. The site states a median of 48 hours from signed spec to first validated batch where coverage is deep, and three to four weeks where coverage is thin.

Hospitality is classed as a thinner-coverage environment, so a tray order should expect the longer range, and the quote tells you which case you are in. On-demand top-ups run against the same spec and accept criteria after each training run, so new tray data stays consistent with what you already hold. A Spec Pilot, a small first batch, can prove the spec before you scale. Collections are billed per validated hour, and rejected episodes and recaptures are never billed.

Delivery and license

Which formats and license come with a tray assembly order?

Delivery formats are RLDS, LeRobot and WebDataset, plus HDF5 and zarr. The first three are training-loader formats, and HDF5 and zarr carry arrays for custom pipelines. Readable converter source ships alongside the data so the schema can be retargeted to your own loader, and the episode schema page lists the fields.

The license is perpetual, irrevocable and worldwide, with the data buyer-owned and non-exclusive by default. Training, evaluating, fine-tuning and deploying models, including commercial ones, is permitted, and exclusivity is available as a separate term. The executed agreement controls. The site does not publish a price list, a minimum order or a batch size for this row, so those are set in your quote.

Ordering

How do you order a custom tray assembly and delivery dataset?

Describe the three steps and where each starts and ends: arrange, carry and set. Say whether an episode covers one step, one full tray or a run of several, what counts as the object and what counts as a finished step, whether slips and recoveries stay in the batch, the privacy rule for the space and who may appear in frame, and the variation your pipeline is missing. Then name the streams you want, the delivery format your loader reads and whether a stereo pair is part of the request.

Most programs begin with a Spec Pilot, which proves the spec and accept criteria on real footage before you scale. The last table below shows what each spec element decides.

At a glance

What you get.

Catalog row
"Tray assembly + delivery" (Hospitality Service Set); Easy; Available on request
Catalog description
"Arrange, carry, and set a tray."
Catalog capture setup
Multiview rig + handheld grippers. The site describes this as a staged working set recorded by a multiview rig while the operator performs the task with handheld grippers
Environment examples
A table, a counter/bar, and a housekeeping/room area
Episode schema
Head and wrist RGB, depth, 3D hand pose, contact events and action segments, ten streams synced under 2 ms, as the site states for custom collections
Hand pose
21 joints per hand with a per-joint visibility flag
Language data
One task instruction per episode
Tray, ware, contents, route, distance, weight, outcome labels
Not stated beyond the row wording; agreed in the skill spec
Coverage and first batch
Hospitality is a thinner-coverage environment; a first batch typically takes three to four weeks
Delivery formats
RLDS, LeRobot, WebDataset, HDF5 and zarr, with readable converter source
License
Perpetual, irrevocable, buyer-owned, non-exclusive by default

Every collection runs through the same seven-stage end-to-end custom collection pipeline. End-to-end custom data collection is a managed service that takes an AI data need from problem to owned dataset in a single accountable pipeline.

Catalog row

Which catalog row covers tray assembly, and what is its status?

The row exactly as the task catalog states it, followed by neighbouring Hospitality Service Set rows shown for context only. Items the catalog does not list are marked Not stated. Source file: lib/commercial-catalog-data.ts.
Task (as listed)Description (as listed)EnvironmentSkillCapture setupStatus
Tray assembly + deliveryArrange, carry, and set a tray.Hospitality Service Set (table, bar, room)EasyMultiview rig + handheld grippersAvailable on request
Set table service (context only)Lay a full place setting.Hospitality Service Set (table, bar, room)MediumMultiview rig + handheld grippersAvailable on request
Clear + bus table (context only)Stack dishes, bus, and wipe.Hospitality Service Set (table, bar, room)EasyMultiview rig + handheld grippersAvailable on request
Pour + serve beverage (context only)Pour a drink and serve to a place.Hospitality Service Set (table, bar, room)MediumMultiview rig + handheld grippersAvailable on request
Restock amenities (context only)Restock a minibar/amenity tray.Hospitality Service Set (table, bar, room)EasyMultiview rig + handheld grippersAvailable on request
Wipe + reset counter (context only)Clear, wipe, and reset a counter.Hospitality Service Set (table, bar, room)EasyMultiview rig + handheld grippersAvailable on request
Tray contents, ware, route, distance, weight, outcome labelsNone beyond the row wordingNot stated as rowsNot statedNot statedNot stated

Compared pages

How does this page differ from the table setting, meal plating and amenity restocking pages?

Each page, the rows it is organised around, and its relation to this page. Statuses are as the site lists them; none of these pages is claimed to hold delivered tray hours.
PageRows it is organised aroundWhere the tray appearsRelation to this page
This page: egocentric tray assembly and delivery dataTray assembly + delivery (Easy, Available on request)Main topicThe tray as the unit of work
Egocentric table setting and clearing dataSet table service; Clear + bus tableListed as a neighbouring row in the same environmentDifferent main task; laying and bussing a table
Egocentric meal plating and serving dataPlating, portioning and serving rowsListed among the serving rowsDifferent main task; plating and serving as a chain
Egocentric hotel amenity restocking dataHotel Amenity Restocking (Easy, Ready to deploy); Restock amenities (Easy, Available on request)A minibar/amenity tray is restockedDifferent task; restocking items, in a different environment for the lead row
Egocentric napkin and towel folding dataFolding rows in the same environmentNot a tray rowNeighbouring task; folding linens and napkins
Hospitality egocentric dataHospitality and housekeeping work as a whole settingOne task among manyThe broader setting page

Capture setup

What does the site state about capture for the tray row?

The capture modes named in the task catalog, what each records, and whether the tray row uses it. “Not stated” means the site does not say.
ItemWhat the site statesFor a tray order
Multiview rig + handheld grippersA staged working set is recorded by a multiview rig while the operator performs the task with handheld grippers, so demonstrations map onto a robot end effectorThe mode the tray row lists
Phone (head-mounted) / multiview rigA head-mounted phone records the first-person view, and a multiview rig adds synchronized third-person angles when the spec asks for themNot listed for the tray row; named in the catalog for other environments
Stereo captureOffered through the general stereo offer, agreed in the skill specNo stereo pair is stated for the tray row; a spec choice
Episode schemaHead and wrist RGB, depth, 3D hand pose, contact events and action segments; ten streams synced under 2 msStated for custom collections; which streams the tray row emits is Not stated
Hand pose21 joints per hand with a per-joint visibility flagStated
Camera count, resolution, frame rate, lightingNot stated for hospitality rowsAgreed in the spec
Gripper model, attachment, tray holdingNot statedNot claimed; agreed in the spec
Failure and recovery casesCaptured and labeled where they occurStated; how often they occur is Not stated

Stated vs not stated

What the site states about tray assembly data

Left to right: the item, what the site states, and what that means for a tray order. “Not stated” means the site does not say.
ItemWhat the site statesFor a tray order
Row wording"Arrange, carry, and set a tray."Stated; the three verbs are the starting steps
Skill and statusEasy; Available on requestNo volume, hours or delivered footage is claimed on this page
EnvironmentHospitality Service Set: a table, a counter/bar, and a housekeeping/room areaAn environment type, not a named venue
Hotel, restaurant or guest settingNot stated for this rowNot claimed; set in the spec
Tray contents, ware, size, weight, route, distance, timeNot statedNot claimed; set in the spec
Tray layout, goal-state, outcome or breakage labelsNot statedNot claimed; set in the spec if needed
Object identity labels, object 6-DoF poseNot statedNot claimed; set in the spec if needed
Force or tactile dataNot statedNo weight or grip reading is described as delivered
Instance masksStated on other pages, not on the hospitality pagesConfirm in the spec if needed
Task duration, success rate, throughputNot statedNot claimed on this page
Hospitality coverageThinner; a first batch typically takes three to four weeksExpect the longer range; the quote confirms
Faces and screensBlurred irreversibly; a reviewer confirms; footage that cannot be de-identified is discardedStated; who may appear in frame is agreed in the spec
Bystanders in front-of-house settingsBystander-dense, which lowers yield after de-identificationStated

Formats

Which delivery formats can carry a tray assembly order?

Delivery formats stated on the site and what each is used for. Official documentation for each is linked under Sources.
FormatUsed forNotes
RLDSTraining loader; TFDS-compatible tfrecord shardsEpisode and step structure
LeRobotTraining loader; parquet plus mp4Named in the site’s format list
WebDatasetTraining loader; tar shards for streamingNamed in the site’s format list
HDF5 and zarrArrays for custom pipelines; one group per episodeFor custom loaders
Converter sourceReadable source ships with the dataLets you retarget the schema to your own loader

Skill spec

What the skill spec fixes for a tray assembly order

Spec element and where a buyer can see it in the delivery. “Set per program” means the site states no fixed value.
Spec elementWhat it decidesWhere it shows up
RowTray assembly + delivery, worded as the catalog words itSet per program; Available on request as listed
Steps and orderWhat one step is: arrange, carry, setEpisode boundaries and action segments; set per program
Episode scopeOne step, one full tray or a run of severalSet per program; the site does not state an episode length
Object definitionWhether the tray or an item on it is the manipulated objectContact events and the out-of-frame reject rule; set per program
SettingWhich of the table, counter/bar or room area is in frameSet per program; the site names no venue
Rig and streamsMultiview angles, wrist views, hand pose, and any stereo pairThe channels you can read; confirm on the Spec Pilot
FailuresWhether slips and recoveries stay in the batchLabeled where they occur; set per program
Delivery formatHow the data is packagedRLDS, LeRobot, WebDataset, HDF5 or zarr
Accept criteriaWhat passes QA, including what counts as a rejectReject log per batch
PrivacyWho may appear in frame and how screens and text are handledFaces and screens blurred at ingest; other items agreed in the spec
LicenseWho owns the datasetPerpetual, irrevocable, buyer-owned, non-exclusive by default

Example footage

What does egocentric capture look like on this site?

One real clip already published on this site, shown as a format example: a first-person view with faces blurred. It does not show a tray, a hospitality set or the multiview rig with handheld grippers that the tray row lists.

egocentric_cooking_10s.mp4 · first-person view · faces blurred · 1080 × 1080 web preview · format example, not a tray clip

No tray assembly clip is published on the site, so this is labelled as a format example. Request a sample to see delivered files. See sample data outputs, request an egocentric data sample.

FAQ

Egocentric tray assembly data, answered.

What is egocentric tray assembly and delivery data?
Video of a person arranging, carrying and setting a tray, captured to a written spec with 3D hand pose and action segments alongside, and collected on demand by Firsthand.
Which catalog row covers it, and what is its status?
"Tray assembly + delivery" ("Arrange, carry, and set a tray.") in the Hospitality Service Set. It is rated Easy, listed with Multiview rig + handheld grippers, and Available on request. This page claims no delivered hours.
Is it head-mounted or stereo capture?
Not as the catalog lists it. The row lists a multiview rig with handheld grippers: a staged working set recorded by a multiview rig while the operator uses handheld grippers. Stereo applies only through the general stereo offer, agreed in the skill spec.
How is this different from the table setting and meal plating pages?
Those pages are organised around other rows, laying and bussing a table, and plating and serving. They mention the tray row as a neighbour. This page treats arranging, carrying and setting a tray as the unit of work.
Is there an off-the-shelf tray dataset?
No. The row is Available on request, so this is custom collection, at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
Does the data include tray weight, contents or outcome labels?
Not stated. The site lists no tray weight, size, contents, route, distance, outcome or breakage label and no force or tactile stream, so none is claimed. These are set in the spec.
How fast can a custom tray assembly dataset be collected?
From signed spec to first validated batch, a median of 48 hours where coverage is deep. Hospitality is a thinner-coverage environment, where a first batch typically takes three to four weeks. The quote tells you which case applies.
What formats and license come with it?
RLDS, LeRobot, WebDataset, HDF5 and zarr, with readable converter source. The license is perpetual, irrevocable and buyer-owned, non-exclusive by default.

Sources

Where are the delivery formats documented?

Request a custom tray assembly and delivery dataset.

Tell us the steps and where each starts and ends, whether an episode covers one step, one full tray or a run of several, what counts as the object, which part of the service set is in frame, whether slips and recoveries stay in, the privacy rule for the space and the format your loader reads. We will quote reach, timeline and price against a written spec.