Meet Photos · meets & tournaments · sorted by bib and heat
Track meets and tournaments — every heat, the finish line, and the podium, sorted to the right athlete by bib and heat.
A meet is a long day: a hundred athletes from a handful of teams, a dozen events running at once, and one chaotic finish line that fills a card with thousands of frames. Meet Photos captures all of it — the heats and field events, the finish-line burst, and the podium — and binds every frame at ingest to the meet start list, the heat sheet the host already runs the event from. A frame carries its bib number, heat, lane, event, and division, so a full afternoon of action sorts itself to the right athlete instead of one giant unsearchable album. Several teams can compete at one venue, each its own tenant, so a family finds their athlete by bib or name and sees only their own athlete’s day — never another team’s roster, and never a face scan switched on without permission.
Meet Photos is the meet-day competition itself — distinct from the posed team-and-individual day at teamphotos.network, and from the program-operations platform at athletic.software. It shares its roster, consent, and delivery model with pictureday.software, and photos flow into the yearbook and publishing spine at homeroom.software. Capture and the code-enforced cost floor are live; the branded family store is built and the live charge rail is honest-off — no card is charged today.
What is built and what is in early access
The capture pipeline, the start-list binding by bib and heat, the event and podium galleries, the per-team isolation, the consent gate, and the output to the host’s own lab are shipped and running. The branded family store is built too — the one honest-off piece is the live charge rail that moves money. Each surface is marked plainly below.
Roster-bound capture against the meet start list
Every frame from the meet binds to the start list at ingest: the heats, the field events, the finish-line burst, and the podium. Binding is by start-list lookup — bib number, heat, lane, event, and division, the same heat sheet the host already runs the meet from — not a face scan. An athlete on the start list has a photo set bound to their bib; a bib not on the sheet has no active gallery. The start list is the spine every product downstream reads from, so a chaotic day sorts itself instead of being tagged by hand after the fact. Shipped
Find my athlete by bib and heat, not a face scan
A family finds their athlete the plain way: they enter the bib number or the athlete’s name and event, and the system returns the frames bound to that start-list entry — the heat, the field attempt, the finish, and the podium. The default path computes no faceprint. Facial recognition is off by default. Where the platform offers this opt-in and a parent uses it, a face template is treated as minors data behind the host’s walls, with no outside recognition service connected. The host sets a face-data window on the order of a year — about 365 days — and that window is what marks a template due for destruction. Withdrawing the opt-in stops the matching. The step that destroys the stored template is not finished, and we are not going to tell a parent it runs on a schedule when it does not. This page makes no claim that photos are found by a face scan by default. Shipped
Many teams, one venue, kept apart
A meet is several teams at one venue, so each competing team is its own tenant. A family finds their athlete within their own team’s start-list entries and sees only that athlete; a family from another school has no path to a different team’s roster, galleries, or consent records. The host runs one meet while every team’s data stays isolated — one venue, many teams, no cross-team leakage. Shipped
Galleries by event, heat, division, and the podium
Frames publish organised by event, heat, division, and the podium, so a family finds the 200-meter final, the long-jump attempts, or the medal stand directly rather than scrolling one flat album. A host can publish the field events while the running events are still in review, and the finish-line burst and podium sets stay grouped by event so a family orders the exact moment they came to see. Shipped
Branded family store and order rails
The branded family store presents the finish-line print, the podium shot, and the event action with server-priced order rails: each product priced on the server above a code-enforced cost floor, with the host’s larger leg and the platform’s residual leg computed as named legs in the split and settled in exact cents — not a surcharge added on top. The store substrate and the pricing rails are built. The live charge rail that moves money is honest-off; automatic payouts run only once a host connects its OWN payout account. No card is charged today. Early access — live payment rails
Output to the host’s own lab, with delivery tracking
Confirmed print output routes to the host’s OWN professional lab — the platform does not force a single vendor. Delivery tracking follows an order from output to the family, so a coach or adviser can see where a family’s prints are without calling the lab. The host runs the meet free, with no contract and no minimum order; the lab relationship stays the host’s own. Shipped
How a chaotic meet sorts itself to the right family
Every step projects forward from the meet start list. Nothing is re-keyed or re-associated by hand after the finish line.
- The meet start list is imported. The host sends the start list — athletes by bib number, team, event, heat, lane, and division — or the meet management software exports it. That heat sheet is the spine: it is what every frame binds to and what every gallery link is scoped by. A bib not on the sheet has no active gallery, and each team on the list is its own tenant.
- Consent is resolved before delivery. Each family resolves publish consent for its athlete before a single gallery opens. Consent is opt-in, granular, and off by default; an athlete without a publish-consent record is excluded from shared galleries and the store by the engine. Consent can be withdrawn at any time, and withdrawal is enforced end to end across every team’s surfaces.
- The meet is captured, event by event. The heats, the field-event attempts, the finish-line burst, and the podium are captured and ingested onto our own private systems. Each frame binds to a start-list entry by bib, heat, lane, and event — and the default find-my-athlete path builds no face template to sort a shot. At a remote venue with no wifi, offline capture holds frames and binds them on sync (early access).
- Galleries publish from a private link. Each family receives a private link tied to its athlete’s start-list entry and sees only that athlete. Galleries are organised by event, heat, division, and the podium, so a family finds the exact race or attempt directly. A host can publish the field events while the running events are still in review.
- The finish-line and podium packages assemble from the same set. A family’s finish-line burst and podium package are drawn from the frames already bound to that athlete’s bib. Print preflight runs fail-closed: a start-list entry with no publish consent, or a package missing its podium frame, is blocked from print before it is sent, not after a family notices.
- Families order prints. From the same private link, a family can order the finish-line print, the podium shot, and the event action through the branded store. Each product is priced on the server above a code-enforced cost floor; the host’s larger leg and the platform’s residual leg show as named legs in the split. The store is built; the live charge rail is honest-off, so no card is charged today.
- Output routes to the host’s own lab. Confirmed print output routes to the host’s own professional lab, and delivery tracking follows the order from output to the family. The host keeps its lab relationship, its start list, and its consent records; the program runs free, with no contract and no minimum order.
Every part of a meet, captured and sorted by bib
A meet is not one posed frame — it is a day of competition across many athletes and events. Meet Photos captures the moments a family drove to see and binds each to the bib it belongs to.
The start
The blocks, the first whistle, the dive off the platform, the whistle of the first bout. The start of each heat and each match is captured against the start list, so the frame already knows the bib, the heat, and the event before anyone tags it. A family that came for one 100-meter dash finds that heat directly instead of scrolling the whole afternoon.
Heats and field events
Running events run in heats and field events run in flights, often several at once across the venue. Each attempt — the hurdle, the long-jump board, the high-jump bar, the shot ring, the pin on the mat — binds to the athlete’s bib and event. Because the binding carries the event and division, the long-jump attempts stay separate from the 400-meter heats even when they happen in the same ten minutes.
The finish-line burst
The finish line is where the pile gets deep: a burst of frames per heat, per lane, thousands by the end of the day. This is exactly what the bib-and-heat binding is for — every finish frame sorts to the athlete who ran it, so a family gets the lean at the tape for their own athlete rather than a folder of strangers crossing the line.
The podium
The medal stand is the keepsake. Podium and awards frames are captured and grouped as their own set per event and division, bound to the athletes on the stand, so a family finds the medal moment without hunting. The podium set is what the finish-line and awards package assembles from — fail-closed print preflight blocks a package whose podium frame is missing before it is sent.
Bib lookup, private galleries, and consent that holds
Finding an athlete’s photos is a start-list lookup, not a face scan. A family enters the bib number or the athlete’s name and event, and the system returns the frames bound to that start-list entry. The default path builds no face template — the binding is the same heat sheet the host runs the meet from. Facial recognition is off by default, and this page makes no claim that minors’ photos are found by a face scan by default.
Each family’s gallery is private and tenant-isolated. A meet is several teams at one venue, and each team is its own tenant: a family sees only its own athlete, through a private link scoped to that start-list entry, and no family from one team has a path to another team’s roster or galleries. There is no public album of the meet, and a student’s photos, start-list data, and consent record are never visible outside the team tenant that owns them.
Consent is opt-in, per-event, granular, and off by default. An athlete without a publish-consent record on file is excluded from every shared surface — the gallery and the store — by the engine, not by a coach remembering to remove them. Consent is withdrawable at any time; a withdrawn athlete is engine-excluded across every surface, and the withdrawal is enforced end to end rather than filtered by a route that might be missed.
Here is the honest data posture, stated plainly rather than dressed up. Photos run on our own private systems, encrypted in transit. They are never sent to an outside AI or photo company, and never sold or shared for profit. Where a parent opts a child into face matching, that face template is minors data too: kept behind the host’s walls for a bounded window on the order of a year (about 365 days), never sent outside, with no outside recognition service connected. That window is what marks a template due for destruction, and withdrawing the opt-in stops the matching. This is not a “photos never leave” or “no face data” claim — it is a claim that the data is consented, minimised, and host-owned. One thing we will not overstate: the step that destroys the stored template is not finished. The cleanup job is built to refuse — when it cannot actually destroy a template it halts and raises an alert rather than mark it deleted — and we would rather leave that alert standing than record a deletion we cannot show you. The host stays the controller of its athletes’ images from the finish line through delivery.
The store is built. The charge rail is honest-off.
The branded family store is built: a family can browse its athlete’s galleries and put the finish-line print, the podium shot, and the event action in a cart. Every product is priced on the server above a code-enforced cost floor — the price is set by the platform’s pricing rails, not typed in by a browser — and the order breakdown shows where each dollar goes: the print and lab cost, the host’s larger leg, and the platform’s residual leg as a named leg in the split, settled in exact cents.
The one honest-off piece is the live charge rail — the part that accepts a family’s payment and moves the money. It is present in the platform but not enabled for live transactions. “A family buys the finish-line print and the host earns a clean leg” describes the store that is being built, not a live checkout on this page. There is no live checkout, no pricing commitment, and no card charged today. When the charge rail is enabled, hosts are notified directly; automatic payouts run only once a host connects its OWN payout account.
The program itself is free for a host to run: no contract, no minimum order, no per-athlete seat fee. Meet Photos is a for-profit vendor, not a charity — an order is a family buying a keepsake at an honest split, not a donation and not a gift. Output routes to the host’s own professional lab, so the host keeps its lab relationship, and a coach or adviser sees the projected host share before any charge rail runs — the actual figure the split would produce, not a percentage estimate.
Common questions
How does Meet Photos find my athlete’s photos?
By a start-list lookup, not a face scan. A family enters the bib number or the athlete’s name and event, and the system returns the frames bound to that start-list entry — the heat, the field attempt, the finish, and the podium. Binding happens at ingest against the meet start list the host already runs the event from. The default path builds no face template. Facial recognition is off by default.
What kinds of meets does this cover?
The high-volume competition days: track and field, swimming, wrestling tournaments, gymnastics invitationals, and cross country. Each shares the same shape — many athletes from several teams, events running at once, and a deep finish-line pile — so the start-list binding by bib, heat, lane, event, and division sorts the day the same way across every sport.
How is this different from teamphotos.network?
Meet Photos is the competition day itself: the heats, the finish-line burst, and the podium, captured at scale and sorted to the right athlete by bib and heat. teamphotos.network is the posed team-and-individual photo day — the individual portrait and the team shot, not the action of a meet. They share the same roster, consent, and delivery model, but this page is the meet and teamphotos.network is the posed day.
Several teams compete at one meet. Can one team see another team’s photos?
No. A meet is several teams at one venue, and each team is its own tenant. A family finds its athlete within its own team’s start-list entries and sees only that athlete; a family from one school has no path to another team’s roster, galleries, or consent records. There is no public album of the meet, and each team’s data stays isolated end to end.
What happens if a family has not given consent?
An athlete without a publish-consent record on file is excluded from every shared surface — the gallery and the store — by the engine, not by a coach remembering to remove them. Consent is opt-in, granular, and off by default. It can be withdrawn at any time; a withdrawn athlete is engine-excluded across every surface, and the withdrawal is enforced end to end.
Do you use facial recognition on the athletes?
Not by default. The default way a family finds their athlete is a start-list lookup by bib or name and event, which builds no face template. Facial recognition is off by default. Where the platform offers this opt-in and a parent uses it, the face template is minors data kept behind the host’s walls for a bounded window on the order of a year, never sent to an outside AI or photo company, never sold, with no outside recognition service connected. That window is what marks a template due for destruction, and withdrawing the opt-in stops the matching. Destroying the stored template itself is a step we have not finished, so we do not claim it happens on a schedule; the cleanup job halts and raises an alert rather than record a deletion it cannot carry out. We do not claim there is no face data — we state how it is consented, minimised, and where the honest limit is.
Can families order prints yet?
The store is built and a family can browse galleries and build an order of the finish-line print, the podium shot, and the event action. Products are priced on the server above a code-enforced cost floor, and the order breakdown shows the host’s larger leg and the platform’s residual leg as named legs. The live charge rail that moves money is honest-off, though: there is no live checkout and no card is charged today. When the charge rail is enabled, hosts are notified directly.
The venue has no wifi. Does capture still work?
Offline capture at a remote venue is in early access: frames are held on the capture device and bound to the start list on sync once a connection returns, so a meet at a field with no wifi is not lost. Capture and the start-list binding are the shipped core; the offline-venue path is the piece still opening up.
Where do the printed photos come from?
Confirmed print output routes to the host’s OWN professional lab — the platform does not force a single vendor. Delivery tracking follows an order from output to the family, so a coach or adviser can see where a family’s prints are without calling the lab. The host keeps its existing lab relationship while gaining the start-list binding, the event galleries, and the consent gate.
What happens to the photos, and where are they stored?
Photos run on our own private systems, encrypted in transit. They are never sent to an outside AI or photo company, and never sold or shared for profit. There is no public searchable album and no social feed. Photos are kept for the order window — on the order of a year — and then purged on schedule unless a family archives them. A family can request deletion, and the request is logged and honored.
What does it cost a host to run?
The program is free to run: no contract, no minimum order, and no per-athlete seat fee. The host keeps its own lab relationship and its own start list and consent records. When the store’s charge rail is live, orders settle in exact cents with the host’s larger leg and the platform’s residual leg shown as named legs in the split — no markup on print costs and no hidden deduction between what a family pays and what the host receives.
Related properties
Meet Photos is one program on a shared roster, consent, and delivery model. These destinations cover the adjacent programs and the publishing spine the photos flow into.
pictureday.software
The picture-day platform Meet Photos shares its roster, consent, and delivery model with: roster-driven capture, consent-gated galleries, and output to the school’s own lab, across the whole program.
teamphotos.network
The posed team-and-individual photo day for any club — the individual portrait and the team shot, sorted to the right family by roster. This page is the meet-day action; cross-linked here, not re-pitched.
athletic.software
The athletic-program operations platform — eligibility from the real grade record, rosters governed by consent, and the schedule engine. The meet start list can come from here; the photos live on this page.
homeroom.software
The yearbook and publishing spine the photos flow into: one consented athlete record underneath, from the roster-bound finish-line frame to the printed page.
What is built and what is honest-off
The roster-bound meet capture — the heats, the field events, the finish-line burst, and the podium, bound to the start list by bib, heat, lane, event, and division — is built and running today. Find-my-athlete by start-list lookup (bib or name and event, no face template by default), per-team tenant isolation for many teams at one venue, consent-gated family galleries delivered from a private link, output to the host’s own professional lab, and delivery tracking are built and running today. Photos run on our own private systems, encrypted in transit, never sent to an outside AI or photo company, and never sold or shared for profit; facial recognition is off by default, and this page makes no “no face data” or “photos never leave” claim. The branded family store and the server-priced order rails are built; the one honest-off piece is the live charge rail that moves money — there is no live checkout and no card is charged today. Offline capture at a remote venue is in early access. The program is free to run, with no contract and no minimum order, and Meet Photos is a for-profit vendor rather than a charity. No competitor brand names, no invented stats, and no testimonials appear here.