Gameday.network · The game-night hub · one contest at a time

The score and the photos from tonight’s game. One page.

When a parent searches “Jefferson vs. Central football photos” on a Friday night, they land on a social-media album, a scoreboard-app screenshot, or nothing. gameday.network is the page they should have found: one contest, one page — when and where, the final once the horn sounds, and the gallery from that exact game.

The photos are not new work. The studio was already on the sideline; gameday.network turns that existing game-day shoot into a same-week, fan-facing gallery, one game at a time, across the schools already served. It is deliberately not the roster, not the season, and not a booking calendar — it is the public output of the game that just happened.

Get it on your games See a game page

1game per page — the unit of work is a single contest, never a season, a roster, or a booking calendar

3things on a game page — when & where, the final result, and the photo set from that game

0faces recognized on this surface — gameday.network runs no facial recognition and no AI player tagging; photos are organized by game, not by identity. Face matching is a capability we are building and is not turned on today

0automated live-score feeds — the result is posted by a person after the final horn, not scraped

What one game page is

Not an app. Not a login. A single page a fan reads in five seconds.

A game page opens to the matchup and the start time before it asks for anything. After the final horn it carries the score. From the moment the studio’s gallery is ready, it carries the photos too. That is the whole page. Its restraint is the product: no season grid to scan, no roster to browse, no account to make.

The three parts — and only three

When and where. The result. The photos.

1 · The details

When and where — the one line a fan actually searched for

A parent’s Friday-afternoon question is small and specific: what time, which field, home or away. The top of a game page answers exactly that — opponent, date, kickoff or first-serve time, and the venue with a plain address — before it asks for anything or shows anything else. It is one contest, so there is one time and one place: no season grid to scan, no filter to set, no app to install. A visitor who typed “Jefferson vs. Central football” into a search bar lands on the answer, not a schedule they have to read.

2 · The result

The final — posted after the horn, by a person, on purpose

Before the game the page shows the matchup and the start time. After the final horn, the athletic department or the studio posts the result — the score, and a one-line note if they want one (“OT,” “senior night,” “region clincher”). The result is entered by a person who was there, not scraped. gameday.network does not run an automated live-scoreboard feed and does not claim to: a wrong number that nobody typed is worse than a number posted ten minutes late. Auto-sync from a league or scoreboard feed is on the roadmap and is labelled as such — it is not on today.

3 · The photos

The gallery from THAT game — the shoot the studio already ran

The studio was already on the sideline. Those frames — culled and color-corrected — become the game’s public gallery, reached with one tap from the game page. The set is organized by GAME, not by face: there is no facial recognition and no auto-tagging of players, so no child’s name is ever attached to a photo by this surface. Ordering prints or downloads is handled by the estate’s existing consent-gated proofing engine that already runs school photography — gameday.network is the front door to that gallery, not a second checkout. A suppressed student is not shown, and there is no roster to browse. When the gallery is not yet posted, the page says “photos coming” and offers an opt-in reminder rather than an empty grid.

Where the photos come from

The shoot already happened. This is where it goes.

A school photographer was on the sideline for the game. Those frames — culled and color-corrected — become the game’s public gallery, one tap from the game page. gameday.network adds no camera and shoots nothing new; it is the front door to work the studio already did.

The gallery is organized by game, not by face. There is no facial recognition and no AI player tagging on this surface, so no child’s name is attached to a photo here. A suppressed student is not shown, and there is no roster to browse from. Minors’ photos are consent-gated and never public by default.

Ordering prints or downloads is handled by the estate’s existing consent-gated proofing engine that already runs school photography. gameday.network links to that gallery; it does not run a second checkout and processes no payment on this page. When a gallery is not yet posted, the page says “photos coming” and offers an opt-in reminder rather than an empty grid.

What gameday.network is deliberately not

Four jobs it does not do — and the sibling that owns each.

The scope is the product. Everything roster-, season-, booking-, or portrait-shaped belongs to a sibling surface, on purpose, so a game page stays the one thing a fan came for.

Not eligibility, roster, or consent admin

— that is athletic.software

Who is cleared to play, who is on the roster, whose consent is on file — that is private athletic-department operations, and it lives on athletic.software. gameday.network never shows a roster and never touches eligibility. It is the PUBLIC output that the ops layer makes possible, read by fans, not the console that produces it.

Not team-photo-day booking

— that is teamphotos.network

Scheduling the season’s team-and-individual photo day — picking a date, a rotation, a gym slot — is a booking flow, and it lives on teamphotos.network. gameday.network books nothing. It shows the photos from a game that already happened.

Not media-day / portrait scheduling

— that is sportsmedia.day

Scheduling athlete portrait and media-day sessions is its own surface, sportsmedia.day. That is about posed portraits made on a set date. gameday.network is about the candid set from the game itself — the block, the dig, the finish at the line.

Not a season schedule or standings board

— a single contest is the unit

gameday.network is not a season calendar and not a standings table. Its unit of work is ONE game. A season view, a league table, or a team’s full slate is a different product; keeping this page to one contest is what makes it the thing a fan can read in five seconds.

One job each -- gameday.network owns the public game page, and only that
The job	gameday.network	athletic.software	teamphotos.network	sportsmedia.day
A parent searching for tonight’s game	Score + gallery, one page	Not the audience	Not the audience	Not the audience
Eligibility / roster / consent admin	Never shown here	This is its job	No	No
Booking team photo day	Books nothing	No	This is its job	No
Scheduling media-day portraits	Schedules nothing	No	No	This is its job
The public photo set from one game	This is its job	Ops, not public	Books the shoot, not the page	Portraits, not the game

This table compares the JOBS of owned sibling surfaces in the athletics-activities family. No competing product or company is named anywhere on this page.

What’s live, what’s in development — stated plainly

The honest line between what runs today and what we are still building.

gameday.network is being stood up as a per-game page network across the schools the studio already serves. The shoot and the gallery engine are real and running. The per-game pages, an automated score feed, and any notification are where the work is — and nothing here pretends otherwise.

Live · already happening

The studio’s game-day shoot

School photographers already shoot games. This is the real, existing input the network is built on.

Live · existing photo engine

The consent-gated photo gallery + ordering

Galleries are delivered through the estate’s existing consent-gated proofing / ordering engine. gameday.network links to it; it does not re-implement checkout.

In development · the network being stood up

The per-game public results-and-photos page

Assembling one clean public page per game, per school, across the served schools is the buildout in progress. Where a game page is not yet stood up, nothing here implies it is.

In development · NOT live

Automated live-score sync

Pulling a score from a scoreboard or league feed in real time is on the roadmap. Today results are human-entered after the final horn.

Honest-off · nothing sent yet

“Notify me when photos post” messaging

The opt-in queues interest against consent; no email or text is dispatched from this surface until the messaging layer is enabled.

The game-day family — one job each

Where gameday.network sits among its siblings.

gameday.network is the public game page. The ops, the booking, and the portraits are separate surfaces on purpose — each does its one job well instead of one tool doing all of them thinly.

The ops layer

athletic.software

The private athletic-department console: eligibility, roster, and consent administration.

Book team photo day

teamphotos.network

The season team-and-individual photo-day booking flow for a program.

Media-day portraits

sportsmedia.day

Scheduling athlete portrait and media-day sessions on a set date.

The program front door

schoolsports.network

A school’s athletics program presence across its teams and seasons.

Youth programs

youthsports.software

Registration and operations for youth and recreation sports programs.

League operations

youthleague.software

Running a multi-team youth league — divisions, brackets, and schedules.

For athletic departments & booster clubs

A branded page to share — not a screenshot of a scoreboard app.

Right now the score goes out as a screenshot and the photos end up in a buried social-media album, if they end up anywhere. gameday.network gives your program a clean, branded, shareable page per game: the one link you drop in a group chat, a booster email, or the marquee sign photo caption.

It is read by fans, so it never exposes your operations: no roster, no eligibility, no consent records — that stays on athletic.software where it belongs. What the public sees is the result and the gallery, and nothing else. You post the score after the horn; the studio’s gallery attaches itself when it is ready.

Talk to us about your games

Straight answers

Common questions

Is the score updated live during the game?

No, and we will not pretend it is. The result is posted by the athletic department or the studio after the final horn — a person who was at the game types it in. gameday.network does not run an automated live-scoreboard feed today. Auto-sync from a scoreboard or league feed is on the roadmap and is labelled “in development,” not “live.” A wrong number nobody typed is worse than a right number posted a few minutes late.

Where do the photos come from?

From the shoot the studio already ran at that game. gameday.network does not add a camera to the sideline — it takes the frames a school photographer already captured, culled and color-corrected, and makes them the game’s public gallery. The set is organized by game, not by face.

Do you use facial recognition to find my child?

No. There is no facial recognition and no AI player tagging on this surface. Photos are organized by game, not by identity, so no name is ever attached to a face here. There is no roster to browse, and a suppressed student is not shown.

Can I buy or download the photos here?

You open the game’s gallery from the game page, and ordering prints or downloads is handled by the consent-gated proofing engine that already runs the studio’s school photography. gameday.network is the front door to that gallery, not a second checkout — this page itself processes no payment.

How is my child's photo kept private?

Minors’ photos are consent-gated and never public by default. A suppressed student is not shown in a game gallery, there is no roster to browse from, and no name is attached to a face by this surface. Consent is administered on the athletic-department ops layer (athletic.software), not here.

Will you email or text me when the gallery posts?

A “notify me when photos post” opt-in is honest-off: it queues your interest against consent, but no email or text is sent from this surface today. Nothing is dispatched until the messaging layer is turned on, and this page will say so plainly when it is.

Is this a whole season schedule or standings page?

No. The unit is ONE game. There is no season grid, no standings table, and no full team slate here on purpose — that keeps a game page to the one thing a fan searched for. A program’s broader presence lives on schoolsports.network.

How is this different from athletic.software?

athletic.software is the private operations layer — eligibility, roster, consent admin, read by staff. gameday.network is the public result of that work — the score and the gallery for one game, read by fans. Different audience, different job, and gameday.network never shows a roster or touches eligibility.

Can our athletic department or booster club run its own game pages?

That is exactly the plan: a branded, shareable per-game results-and-photos page instead of a screenshot of a scoreboard app or a buried social-media album. It is being built across the schools the studio already serves. To get it on your school’s games, book a conversation at [email protected].

Get gameday.network on your games

One page per game, from the shoot you already run.

gameday.network is being built across the schools the studio already serves. There is no signup form and no account here yet — and this page sends no email and processes no payment. To get it on your school’s games, book a conversation and we will walk you through what is live today and what is coming.

Book a conversation

Or email [email protected].