Locker Room. People / Plan / Perform.
Request access
TUE 5:47 PM

Run your football program in one place.

Locker Room is the operating system for a football department, one place for the week, the people, the work and the knowledge your club normally spreads across chats, spreadsheets and staff memory.

Request access See how the week runs

Built from inside a real senior football program. Now preparing for a small number of 2027 club rollouts.

TUE 5:52 PM

The football program is everywhere.

The training time is in one chat. Availability is another thread. Attendance is a spreadsheet. The session plan is a document. The opposition file is a PDF. A player-development conversation lives in a coach’s notes. What changed after Tuesday training lives in someone’s head.

None of those tools are necessarily bad. The problem is that the football department itself has no single place to exist.

Locker Room gives the program a home.

WED 7:02 AM

Today is the product.

Players should not need to understand the software. They should open Locker Room and see the handful of things that are true for them right now.

A player might see tonight’s training, an arrival time, one availability request and a ten-second check-in. A coach sees the team state, what changed, what needs attention and what has not been completed.

Same club. Same week. Different responsibility.

One week. One source of truth. Everyone sees what matters to them.

Plan. Execute. Observe. Learn. Start the next week smarter.

SUN 9:12 AMCoach

The week starts before the first message is sent.

TUE 5:47 PMPlayer

Players get less software, not more.

TUE 7:41 PMCoach after training

What coaches notice stops disappearing on the walk to the car.

WED 7:02 AMFootball department

Yesterday becomes useful context for today.

SAT 12:15 PMMatch day / staff

The same week keeps moving. Nobody rebuilds it in another tool.

THU 8:20 PM

If the message does not reach them, it did not happen.

A schedule change is only useful if the player gets it. Locker Room treats delivery as part of the product, not something the coach should have to chase across another group chat.

Staff can see delivery state instead of assuming everyone saw the update.

TUE 7:41 PM

Say it while you still remember it.

Some of the most valuable information in a football club never makes it into a system. It is the thing an assistant noticed in a drill. A conversation about a player. A decision made after training. A follow-up someone meant to remember.

Locker Room lets a coach capture a voice note after training, turns it into proposed observations and actions, and asks the coach to review what should actually be saved.

Nothing becomes part of the club record until a person confirms it.

FRI 6:15 AM

Ask the club what it knows.

Locker Room’s assistant is grounded in the information the club has actually recorded and the permissions of the person asking.

If the information is not there, it should say so.

SAT 12:15 PM

Built around the work a football department already does.

The week

Schedule. Events. Availability. Attendance. Announcements. Actions.

The people

Roster. Roles. Groups. Status. Wellness. Player context.

The knowledge

Notes. Voice observations. Documents. Decisions. Grounded Ask.

The broader football-program layer, including season planning, football language, player development and program structure, is the next stage of the product.

SAT 4:30 PM

Not another app for the players to check.

The player experience is deliberately small. The staff experience carries the complexity.

Locker Room is designed around a simple idea: the software should organise the football program so coaches can spend more time coaching it.

Today over dashboards.The right information now, not a wall of modules.
Delivery over posting.Sending is not success. Reaching the person is.
Memory over activity feeds.The club should get smarter from what its coaches learn.
Permissions over convenience.People see what their role allows. The assistant never gets a broader view than the person asking.
SUN 8:30 AM

Who can see what is part of the product.

  • Permissions are enforced at the data layer.
  • The assistant can only work inside the access of the person asking.
  • Consequential information is not added to the club record without human confirmation.
  • Wellness is performance information. Locker Room does not diagnose or predict injury.
  • Important actions are designed to be auditable.

Security or data questions: support@lockerroomhq.app

SUN 9:12 AM

Built by a coach who needed it.

Locker Room started because James Hallahan was trying to run a senior football program through the same patchwork of chats, spreadsheets, documents and memory that most clubs accept as normal.

He is a senior head coach and playing coach at Sorrento, and the product is being shaped inside the weekly reality it is meant to improve.

The advantage is simple: product decisions can be tested against a real football week, not a hypothetical workflow.

Why I built Locker Room

For football programs that take the week seriously.

Locker Room is being built first for senior football environments: strong community clubs, semi-professional programs, pathway programs and football departments that operate with serious standards but still rely on fragmented tools.

It is not trying to replace league administration, registrations, memberships or competition management.

The first job is narrower: help a football department run its program properly.

Run the week through one place.

We’re preparing a small number of 2027 club rollouts. If you run a football program and want to see what we’re building, request access.