A fictional campus operations table with maps, radios, wristbands, and connected game technology

Connected game operations

Run the game. Keep the chaos in the story.

HVZ Game connects the player app, live staff tools, desktop administration, public information, and practical operating guidance needed to run an organized Humans vs Zombies game.

01 Prepare02 Register03 Operate04 Review

One system, different jobs

Players need a clear game. Staff need a reliable operation.

A good HVZ game should feel spontaneous to the people playing it. Behind the scenes, organizers are managing registration, safety, maps, communication, equipment, rulings, and a changing player population. The platform keeps those pieces connected without turning the game into a spreadsheet exercise.

01 / Mobile

Player and staff app

Registration, identity, missions, teams, maps, messages, live updates, and fast staff actions in the field.

See the mobile experience
02 / Operations

Web admin portal

Configure the game, manage records, review activity, publish updates, and understand what happened.

Explore admin tools
03 / Public web

Organization websites

Give prospective players a dependable place for dates, information sessions, rules, and contacts.

See the public layer
04 / Field guide

Organizer support

Build safer, repeatable workflows for approvals, check-in, moderation, equipment, and game-week staffing.

Read the organizer guide
Player, administrator, and web tools arranged as one connected game system

Built around the full game

Information moves once, then stays useful everywhere.

A registration check-in can activate a player. A verified tag can update faction, activity, team data, and live game state. An announcement can reach the right audience without asking staff to maintain parallel lists.

  • Shared organization, game, player, and team records
  • Role-aware tools for players, moderators, and administrators
  • Traceable changes for decisions that matter during the game
  • Public information separated from protected operational data
See how the pieces connect

From first announcement to final recap

A practical operating cycle.

01

Prepare

Define rules, boundaries, documents, staff roles, inventory, and the public information players need.

02

Register

Collect accounts, run information sessions, check players in, issue wristbands, and activate participation.

03

Operate

Publish objectives, verify activity, send targeted updates, review reports, and resolve issues in the field.

04

Learn

Review participation, game history, engagement, and staff notes before planning the next event.

The operating standard

Technology should make the game easier to understand—not easier to overcomplicate.

Clear to players

Status, rules, objectives, and communication should be easy to find when someone is moving across campus.

Fast for staff

Common game-week actions should take seconds, with deeper configuration left to the desktop portal.

Adaptable by campus

Organizations can shape schedules, boundaries, documents, roles, and public information around local requirements.

Accountable by design

Important activity and administrative changes should be reviewable without exposing protected data publicly.

For campus organizers

Planning a new game or replacing a patchwork of tools?

Tell us how your organization operates today and what you need the next game to handle better.

Start a conversation