Furries PH Docs
Dashboard
Event Management docs

Reference

Event Management Certification Checklist

Production-readiness checklist for Event Management setup, live operation, and closeout.

First created Last updated

event-managementreferencecertificationreadiness

Overview

Use this checklist when certifying that an event-management workflow is ready for production use or when verifying a major event before public launch. The checklist is not a replacement for the surface pages; it tells reviewers what proof should exist before they rely on the system.

Certification should be repeatable. A second reviewer should be able to open the same event, follow the same route list, and reach the same conclusion.

Setup readiness

AreaPass conditionEvidence
Event identityPublic name, internal name if used, slug, dates, timezone, venue, image, and status are correct.Details and public event page.
Registration productsTiers, add-ons, inclusions, capacity, age rule, windows, upgrades, transfers, groups, and entitlements are correct.Rego Config and a test registration path.
ConditionsRequired documents are active, assigned to the right targets, ordered correctly, and written in public-safe language.Conditions of Entry and attendee preview.
PaymentsPayment providers, accounts, QR images, surcharges, VAT, refund policy, and confirmation behavior are correct.Payments Config and finance review notes.
Event shopShop enablement, global shop window, rego-required default, source-linked add-ons/inclusions, standalone merch, required categories, selling limits, pickup/delivery settings, preferred couriers, and courier rates are intentional.Shop Config and a test public shop checkout.
Attendee shop flowPublic browsing, persistent cart, profile-prefilled checkout, delivery/pickup choice, payment submission, receipt, and order timeline are understandable to buyers.Use an Event Shop and seeded public shop test orders.
Wallet passesWallet class identity, activation state, images, colors, and links are correct if wallet support is used.Google Wallet Config.
NotificationsWebhook endpoint, signing secret, event types, and preview behavior are intentional.Notification Config.

Operations readiness

AreaPass conditionEvidence
Registration reviewStaff can search, open, update, notify, and understand registration status safely.Regos.
Rego giftingGift purchase, receiver notification, anonymous-gifter display, payment review, duplicate blocking, capacity reservation, and receiver redemption work end to end.Gifts, Rego Config, and a test receiver account.
Shop order managementStaff can filter, open, review payment, add internal notes, add buyer-visible updates, export results, and understand ecommerce order state safely.Shop Orders and a test shop order.
WaitlistQueue behavior and offer handling are understood if capacity limits are used.Waitlist.
Upgrades/transfers/refundsRequest windows, decision states, notes, and payment/refund impacts are documented.Upgrades, Transfers, Refunds.
Dealers DenPackages, application fee, capacity, equivalent tiers, review actions, and dealer regos are correct if used.Dealers Den, Dealers Den Applications, Dealers Den Regos.
HR and rosterDepartments, members, locations, positions, applications, shifts, and live tracker states are usable.Human Resources, Staff Roster.
ActivitiesForms, windows, questions, review actions, approved submissions, and notification paths are correct.Activities, Submissions Review, Approved Submissions.
CommunicationsAudience, subject, markdown-ext body, email preview, inbox preview, and send safeguards are correct.Communications.

Live-event readiness

AreaPass conditionEvidence
Check-inSearch, scanner, NFC, record modal, notes, flags, and check-in action work for the intended event.Check-In and a test route.
Offline operationSnapshot export/import, file ownership, accepted formats, and sync history are understood.Offline Snapshot, Offline Snapshot History.
Inclusion claimClaim workflow matches physical fulfillment rules.Inclusion Claim.
Shop order claimQR/ref/buyer lookup, paid and ready-state checks, release confirmation, and claim audit records work for pickup orders.Shop Order Claim.
InventoryStock controls, item identifiers, QR/NFC/barcode exports, and analytics are ready.Inventory Tracking, Inventory Analytics.
POSCustomer lookup, item picker, basket, payment method/account, surcharge, and transaction submission are tested.Point of Sales.
Live shiftsShift tracker shows current coverage, upcoming shifts, and gaps.Live Shift Tracker.

Closeout readiness

AreaPass conditionEvidence
Finance analyticsProvider/account totals and payment records are reviewed.Finance Analytics.
Shop analyticsShop gross revenue, platform fees, delivery fees, top items, courier queues, claim throughput, and fulfillment exceptions are explainable.Shop Orders Dashboard, Finance Analytics, and Settlements.
SettlementsSettlement quote, proof, notes, and completion state are saved.Settlements.
RefundsOpen refund requests are resolved or assigned.Refunds.
Inventory and POSRemaining stock, sold items, claimed items, and recent transactions are explainable.Inventory Tracking, Point of Sales.
Archive stateEvent status and remaining tasks are appropriate for post-event record maintenance.Details, Post-Event Record Maintenance.

Validation rule

Certification fails when evidence depends on memory, screenshots without route/record context, or a single page that does not own the record being checked. Use the route map and data-record reference to verify each claim at its source.

Common mistakes

Do not certify only the happy path. A production-ready event needs proof for errors and exceptions too: missing IDs, unpaid regos, gift receiver duplicates, anonymous gift visibility, refund review, scanner fallback, offline sync, sold-out items, no-show shifts, and cancellation or archive decisions.

All docs