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
Replacement surface
What the workspace covers
| Area | Job | Surface |
|---|---|---|
| Universities and cycles | University, region, cycle, lifecycle, and archive state. | Restricted for this role |
| Kamp setup | Visibility, dates, capacity, products, sale window, waitlist, policies, and readiness. | Restricted for this role |
| Registration | Listed, unlisted, private, and code-gated paths with clear status. | Open |
| Registration fields | General fields now; restricted field families remain behind policy approval. | Open |
| Roster and assignments | One filterable roster plus housing, team, leadership, and support state. | Restricted for this role |
| Payments and exceptions | Paid, pending, comp, canceled, refund, dispute, reconciliation, and review states. | Restricted for this role |
| Promos and access | Promo, eligibility, comp, and access-code lifecycle with owner and financial effect. | Restricted for this role |
| Communications and media | Email previews, delivery readiness, public content, image metadata, and publish gates. | Open |
| Check-in | Online check-in, duplicate prevention, conflict correction, event log, and escalation. | Restricted for this role |
| Reporting and exports | Director summary, Kamp reports, finance exports, receipts, and export boundaries. | Restricted for this role |
| Administration | Users, approvals, operations queue, system health, receipts, and external-action gates. | Restricted for this role |
Structural changes
How the operating model improves
Still gated