From spreadsheets to a smarter hockey operations platform.
Lineup was designed to turn a complex mix of regional scheduling, association operations, practice planning, conflicts and ice coordination into one clearer system. The project shows what workflow improvement looks like when the real problem is bigger than a single automation.
Scheduling was only one part of the problem.
Regional and association hockey operations require many moving parts to line up at once. Teams need the right venue access. Ice has to match the correct association, age group and time window. Games, practices, blackouts, external events and rescheduling all compete for the same limited resources.
Much of that logic can live in spreadsheets, email threads and scheduler knowledge. That makes the process difficult to scale, difficult to hand off and difficult to adjust when something changes after the original schedule is created.
The goal with Lineup was not simply to digitize a spreadsheet. It was to make the rules, decisions and downstream workflows explicit enough that the system could support the people doing the work.
Different users need different workflows.
Lineup separates regional league planning from association operations so users are not forced through functions that do not belong to their role.
League planning
Regional administrators focus on league setup, team and venue data, regional game scheduling, scheduling safety, rescheduling and league level operational oversight.
Local operations
Association administrators work with the regional game schedule as a fixed input, then manage local practices, extra ice, blackouts, external events, practice conflicts, reporting and Open Ice.
Team level actions
Team users are given only the workflows relevant to them, including the planned mobile friendly experience for ice offers, response deadlines and team level actions.
Hide what does not belong
A major part of the product work has been removing legacy navigation, hiding incomplete functions and consolidating role logic so the interface reflects what each user actually needs to do.
Turning scheduler knowledge into explicit rules.
The scheduling model is built around structured constraints instead of relying on someone to manually compare every possible slot.
Venue and ownership rules
Scheduling logic respects venue access, home association ownership and the relationship between teams and the ice they are permitted to use.
Age and timing rules
Age group matching, allowed scheduling days, game duration and time windows are treated as explicit scheduling inputs.
League constraints
Round robin requirements, blackouts and other scheduling rules are applied as part of the scheduling model rather than checked manually after the fact.
A smaller test model schedules 90 of 90 required games.
The compact scheduling demo uses 6 associations, 18 teams, 270 available ice slots and 90 required games. It is intentionally synthetic and does not contain seeded exceptions, making it useful for validating the scheduling logic itself.
The workflow continues after the schedule is created.
For associations, regional games are treated as fixed schedule inputs. If an imported game overlaps a saved practice, Lineup is designed to surface that downstream conflict where the association actually needs to solve it.
The Practice workflow can identify the overlap, remove the practice from the unavailable slot, create a Needs Rescheduling item, show the affected team and original practice slot, and identify the game that caused the conflict.
The game also appears on the practice calendar, giving the association a clearer operational view of why that rink time is no longer available.
Turning unused ice into a structured offer workflow.
Open Ice is being designed to replace another manual coordination process with a controlled workflow for finding, offering and accepting unused rink time.
Find the usable time
Open availability can be viewed by week or rink, with extra ice distinguished from normal availability and partial blocks represented clearly.
Offer it fairly
Administrators can select eligible age groups or teams, set a response window and use a fairness queue rather than relying on ad hoc messages.
Close the loop
The planned coach and manager experience supports Accept or Pass, deadlines and offer history, with accepted ice flowing back into the practice schedule.
Operational data becomes something administrators can use.
Association reporting has been designed around the questions administrators actually need to answer, with filters for age group, team, rink and date, along with team, age group and chart views and Excel export.
Team and age group views
Administrators can compare practice activity across teams and age groups instead of rebuilding those views manually.
Shared ice handling
Shared practices are represented appropriately so reporting reflects how rink time was actually used.
Exportable operations data
Excel export supports the teams that still need to move data into familiar reporting or administrative workflows.
Building the feature was only part of the work.
As Lineup expanded, a significant amount of work went into simplifying the experience and validating how the pieces behave together. That has included role navigation, setup clarity, loading states, calendar performance, mobile readiness, conflict behavior, schedule persistence and data recovery.
The product has also gone through repeated end to end testing and bug fixing before deployment. That matters because a workflow product is only useful when administrators can trust that a saved schedule stays saved, conflicts appear consistently and changes do not quietly break another part of the operation.
Lineup is still being refined and tested. The case study reflects the product and workflow work completed to date rather than claiming a fully mature production rollout.
The setting is hockey. The workflow problem is much bigger.
Lineup began with scheduling, but the underlying challenge is familiar in many businesses: too many inputs, too many constraints, too much coordination and too much operational knowledge living in spreadsheets or in people's heads.
Scheduling and staffing
Teams, shifts, appointments and resources all involve availability, rules and exceptions.
Field service and facilities
People, locations, equipment and time windows create similar coordination problems.
Approvals and operations
Any workflow with repeated handoffs, decisions and exceptions can benefit from the same process first approach.
Have a process that has outgrown the spreadsheet?
srab digital can help map the workflow, define the rules and design a more practical way for the work to happen.