Skip to content

MOP 3.1 — Event Lifecycle & Multi-Phase Visibility

Audience: society_admin, super_admin Outcome: An event is created, scheduled, monetised through vendor applications + ticket / pass sales, optionally marked public for Near-Me, and finally settled.

1. Lifecycle states (events.status)

draft → active → completed
       ↘ cancelled

Soft-delete is via the Vault (60-day retention; super admin can restore). Settlement is independent — it tracks revenue and fees.

2. Create flow

Sidebar → Events → + Create Event. Required: name, category, date, start_time, end_time, venue, society_id (auto), pincode (geo-coded → geo_point). Optional: stall sizes, allowed_categories, footfall, registration_deadline, electricity_available, water_facility, dismantle_time.

For multi-phase visibility, omit child_society_id to make the event society-wide; set it to a specific phase to keep it phase-bound (mobile app residents only see events of their society — phase tagging is for the admin/back-office view).

3. Public vs. Society-only

is_public = true → the event is included in Near-Me searches across societies (but vendor applications still go through the host society).

4. APIs touched

Method Endpoint
GET /api/admin/events?status=&society_id=
POST /api/admin/events
PUT /api/admin/events/{id}
PUT /api/admin/events/{id}/status?status=cancelled
DELETE /api/admin/events/{id} (soft-delete → Vault)
GET /api/nearby/events?lat=&lng=&radius_km=

5. Data model fragment

events
  id, name, category, society_id, child_society_id?,
  date, start_time, end_time, registration_deadline,
  pincode, city, state, latitude, longitude,
  geo_point: { type:"Point", coordinates:[lng,lat] },
  status, is_public, total_footfall, total_vendor_slots, stall_sizes,
  allowed_categories, water_facility, electricity_available, dismantle_time,
  created_by_admin, created_at, updated_at

6. Edge cases & FAQ

  • No pincode = no Near-Me visibility. UI blocks submission.
  • Phase-bound admin automatically sets child_society_id from their mapping (MOP 1.3).
  • Recurring events live in recurring_events and are mirrored into coaching_events for the Coaching tab.
  • MOP 2.5 — Committee Approvals (every event with a committee triggers it)
  • MOP 3.2 — Digital Signage
  • MOP 4.3 — Temporary Vendor Permits