Test data. Internal review only.
Kampy
Internal QA University2026 Pilot RehearsalKampy Internal Pilot 01 · Registration Open
Signed outSign in with Google

About this build

How Kampy replaces the current event workflow

Kampy combines registration, event-day operations, and financial closeout in one workflow. This review build focuses on the operating model and keeps live provider actions disabled.

Primary flow

One Kamp, six stages

01. Set up the KampConfirm university and cycle, dates, visibility, capacity, pricing, form families, and readiness.Owner: Operations lead · State: Draft to review ready to registration openRestricted
02. Open registrationUse a listed event, access code, or invite link. Complete registration and continue to checkout, review, support, or waitlist.Owner: Registrant · State: Open, private, code gated, blocked, or waitlistedAvailable
03. Work the rosterUse one roster for role, payment, support, housing, team, leadership, cancellation, and check-in readiness.Owner: Director and staff · State: Paid, pending, comp, support blocked, or canceledRestricted
04. Handle exceptionsResolve duplicate attempts, registrations without email, eligibility requests, payment issues, approvals, and source conflicts.Owner: Support, finance, and approvers · State: Open, escalated, applied, denied, or blockedRestricted
05. Run check-inCheck people in, detect duplicate attempts, correct conflicts, and keep an event log.Owner: Check-in staff · State: Checked in, duplicate flagged, conflict, or resolvedRestricted
06. Close out the KampReview attendance, revenue, fees, refunds, disputes, exports, source health, and remaining decisions.Owner: HQ and finance · State: Source backed, estimated, pending, or discrepantRestricted

Replacement surface

What the workspace covers

AreaJobSurface
Universities and cyclesUniversity, region, cycle, lifecycle, and archive state.Restricted for this role
Kamp setupVisibility, dates, capacity, products, sale window, waitlist, policies, and readiness.Restricted for this role
RegistrationListed, unlisted, private, and code-gated paths with clear status.Open
Registration fieldsGeneral fields now; restricted field families remain behind policy approval.Open
Roster and assignmentsOne filterable roster plus housing, team, leadership, and support state.Restricted for this role
Payments and exceptionsPaid, pending, comp, canceled, refund, dispute, reconciliation, and review states.Restricted for this role
Promos and accessPromo, eligibility, comp, and access-code lifecycle with owner and financial effect.Restricted for this role
Communications and mediaEmail previews, delivery readiness, public content, image metadata, and publish gates.Open
Check-inOnline check-in, duplicate prevention, conflict correction, event log, and escalation.Restricted for this role
Reporting and exportsDirector summary, Kamp reports, finance exports, receipts, and export boundaries.Restricted for this role
AdministrationUsers, approvals, operations queue, system health, receipts, and external-action gates.Restricted for this role

Structural changes

How the operating model improves

One workspace replaces split lanes.Attendee, leadership, support, housing, team, payment, and check-in become views over one roster.
State replaces yes or no flags.Payment, attendance, support, cancellation, export, and source health use named states with history and recovery paths.
Restricted data stays restricted.Guardian, emergency, health, dietary, waiver, and insurance fields remain outside collection until policy establishes who may collect, view, export, retain, redact, and delete them.
Financial facts identify their source.Reports separate available facts, estimates, pending records, discrepancies, fees, refunds, and missing data.

Still gated

Decisions required before a real cutover

Restricted field policySet collection, access, export, retention, redaction, and deletion rules for sensitive registration information.Approval Required
Live registration and payment providerChoose the provider behavior, mail path, support owner, rollback plan, and cutover sequence.Approval Required
Historical dataSafe aggregates can inform the product. Row-level import or archive needs a named operational purpose and approved handling path.Held