Case study
Campus Fellowship Operations Platform
Event registration and transport logistics for student ministry coordinators
More about this system
Replace one-off Google Forms and WhatsApp chase-downs with a single registration system — reusable member profiles, structured transport needs, and a live participant list administrators can trust.
- Next.js App Router
- React
- PostgreSQL
- Prisma
- JWT auth
- Tailwind / Radix
Replace one-off Google Forms and WhatsApp chase-downs with a single registration system — reusable member profiles, structured transport needs, and a live participant list administrators can trust.
- Next.js App Router
- React
- PostgreSQL
- Prisma
- JWT auth
- Tailwind / Radix
The business problem
Every gathering restarted from scratch — and transport details lived in chat threads that went stale.
1New Google Form
Each event needed a fresh form. Members retyped the same personal details every time.
2WhatsApp updates
Registration changes and pickup notes were messaged manually to coordinators.
3Manual reconcile
Transport leads pieced together who needed a ride, from where, and who changed their mind.
4Outdated lists
Administrators had no single reliable view of the latest registration and transport information.
- 1
New Google Form
Each event needed a fresh form. Members retyped the same personal details every time.
- 2
WhatsApp updates
Registration changes and pickup notes were messaged manually to coordinators.
- 3
Manual reconcile
Transport leads pieced together who needed a ride, from where, and who changed their mind.
- 4
Outdated lists
Administrators had no single reliable view of the latest registration and transport information.
The LokaTech solution
A centralized event registration system built around reusable profiles and structured logistics fields.
- Members register once from a saved profile — no repetitive personal data entry per event.
- Transport requirement, pickup location, and remarks are structured fields, not free-form chat.
- Registrants update their own details; administrators see the latest roster immediately.
- Visitors can register with a name and phone number, with duplicate signups restricted by phone.
- Members register once from a saved profile — no repetitive personal data entry per event.
- Transport requirement, pickup location, and remarks are structured fields, not free-form chat.
- Registrants update their own details; administrators see the latest roster immediately.
- Visitors can register with a name and phone number, with duplicate signups restricted by phone.
Interactive walkthrough
Follow the core workflow in about two minutes. Every control updates the demo state on this page — nothing is sent to a server.
Step 1/5·Admin creates event
Interactive demoInteractive demo · frontend state only
Create upcoming event
More details
Key features
What the demonstrated registration loop covers.
Key features
What the demonstrated registration loop covers.
Reusable member profiles
Personal details carry forward so each event only asks for logistics choices.
Event capacity control
Administrators set a maximum participant count when creating an event.
Registration deadlines
Signup windows close on a configured date so lists stop drifting after the cutoff.
Self-service updates
Members change transport needs, pickup points, and remarks without messaging staff.
Transport requirements
Round trip, one-way, or no transport — structured options instead of informal notes.
Pickup location selection
Corridor-based pickup points give transport coordinators a consistent geography.
Visitor registration
Name and phone signup keeps first-time guests in the same event roster.
Duplicate registration restriction
Phone uniqueness per event prevents double-booking the same visitor.
Administrative participant view
One live list of who is coming, who needs a ride, and the latest remarks.
Business outcome
Qualitative impact supported by the product design — not invented metrics.
Business outcome
Qualitative impact supported by the product design — not invented metrics.
- Less repetitive data collection for recurring members
- Fewer manual WhatsApp updates for registration changes
- More reliable transport information for coordinators
- Centralized event registration records as a single source of truth
- Easier coordination for administrators reviewing capacity and logistics
Original system scope
The production platform covered more than the registration loop shown here. Those modules are out of scope for this interactive demo.
Original system scope
The production platform covered more than the registration loop shown here. Those modules are out of scope for this interactive demo.
- Cell-group attendance and attendance-rate reporting for regular gatherings
- Group-level access controls with hybrid role levels and ministry role names
- Outing requests with dual approval (admin and transport)
- Vehicle assignment, shareable boarding pages, and related field logistics
Technology and responsibilities
From the original system delivery — stated only as supported by the case brief.
Technology and responsibilities
From the original system delivery — stated only as supported by the case brief.
Original stack: Next.js App Router, React, PostgreSQL, Prisma, JWT authentication, Tailwind and Radix UI.
Role: Full-stack product engineer / architect (design through delivery of domain workflows).
- Full-stack product engineer / architect — design through delivery of domain workflows
- Domain-encoded logistics such as corridor-based pickup and transport enums
- Role-aware coordination surfaces for administrators and logistics roles
Key features
What the demonstrated registration loop covers.
Reusable member profiles
Personal details carry forward so each event only asks for logistics choices.
Event capacity control
Administrators set a maximum participant count when creating an event.
Registration deadlines
Signup windows close on a configured date so lists stop drifting after the cutoff.
Self-service updates
Members change transport needs, pickup points, and remarks without messaging staff.
Transport requirements
Round trip, one-way, or no transport — structured options instead of informal notes.
Pickup location selection
Corridor-based pickup points give transport coordinators a consistent geography.
Visitor registration
Name and phone signup keeps first-time guests in the same event roster.
Duplicate registration restriction
Phone uniqueness per event prevents double-booking the same visitor.
Administrative participant view
One live list of who is coming, who needs a ride, and the latest remarks.
Business outcome
Qualitative impact supported by the product design — not invented metrics.
- Less repetitive data collection for recurring members
- Fewer manual WhatsApp updates for registration changes
- More reliable transport information for coordinators
- Centralized event registration records as a single source of truth
- Easier coordination for administrators reviewing capacity and logistics
Original system scope
The production platform covered more than the registration loop shown here. Those modules are out of scope for this interactive demo.
- Cell-group attendance and attendance-rate reporting for regular gatherings
- Group-level access controls with hybrid role levels and ministry role names
- Outing requests with dual approval (admin and transport)
- Vehicle assignment, shareable boarding pages, and related field logistics
Technology and responsibilities
From the original system delivery — stated only as supported by the case brief.
Original stack: Next.js App Router, React, PostgreSQL, Prisma, JWT authentication, Tailwind and Radix UI.
Role: Full-stack product engineer / architect (design through delivery of domain workflows).
- Full-stack product engineer / architect — design through delivery of domain workflows
- Domain-encoded logistics such as corridor-based pickup and transport enums
- Role-aware coordination surfaces for administrators and logistics roles
Need a custom operational workflow digitized?
LokaTech builds systems that replace fragile spreadsheets and chat threads with clear, self-serve processes your team can trust.