Useful game knowledge lived in too many places.
Player records, status updates, communication, equipment, and staff decisions were difficult to keep aligned through manual tools.
Case study / Kennesaw State
Turning a recurring campus game into a connected operation.
KSU’s HVZ program provided the working environment for many of the platform’s core ideas: clearer registration, visible player identity, live game records, mobile staff actions, and a public information layer that can be maintained by the organization.
Move common workflows into one shared model.
Each new tool was evaluated by whether it reduced duplicate work and made current game state easier to understand.
Refine the system through real operating needs.
The program continues to expose practical requirements for registration, moderation, communications, field tools, and public information.
Program evolution
From recording outcomes to supporting the full lifecycle.
Manual foundation
Establish the game, document local rules, and understand which records actually matter.
Connected gameplay
Bring player identity, tags, objectives, teams, scoring, and communication into a shared system.
Operational depth
Add approvals, inventory, reports, audit history, staff roles, maps, documents, and registration sessions.
Public experience
Connect current dates, sessions, rules, contacts, and game information to an organization-managed website.
The practical lesson
Do not digitize a confusing process and call it solved.
The most useful changes simplified the workflow itself: separating mobile game-week actions from desktop configuration, making administrative changes traceable, placing public content in the organization’s control, and keeping player-facing screens focused on current state.
This case study describes product and operating lessons rather than claiming that software alone created participation or safety outcomes.
Patterns worth carrying forward
What the platform learned from a live campus program.
Registration is a process
Account creation, required documents, an in-person session, staff check-in, and wristband activation are distinct states.
Mobile and desktop are different
Field staff need speed; coordinators need deeper configuration, review, and data management.
History needs context
Adjustments and staff interventions should record what changed, who changed it, when, and why.
Public information must stay current
Dates, sessions, rules, and contacts should come from maintained organization data rather than duplicated static pages.
Apply the lessons