Skip to main content
PLANORAEventGuard 360
Access PLANORA

How it works

A clear path from setup
to evidence.

Five connected moments guide the work, so every person knows what happens next and what record is created.

Event workflow

From first setup to final report.

Each step has one job, one owner, and one visible outcome.
  1. 01

    Create and publish

    Set the schedule, venue, capacity, eligibility, and event team.

  2. 02

    Register and verify

    Participants confirm identity and submit an eligible registration.

  3. 03

    Issue a secure pass

    A unique QR credential is tied to the approved registration.

  4. 04

    Operate the venue

    QR, RFID, occupancy, and device signals update authorized teams.

  5. 05

    Report and certify

    Close with attendance evidence, structured reports, and certificates.

The complete journey

How PLANORA works

System overview, booking and payments, then event-day access and monitoring.

Workflow on the home page
System overview: Five roles connect through the web and Android app, with the venue board, payment confirmation and email supporting the journey. Full text follows below.

System overview

Five roles connect through the web and Android app, with the venue board, payment confirmation and email supporting the journey.

Read system overview
  • Admin

    Oversees the system

  • Event Organizer

    Runs the event

  • Guest/Client

    Books an event

  • Supplier

    Provides services

  • Attendee

    Registers & attends

  • Web app + shared server

    PHP + MariaDB on the staging VPS Bookings • events • attendance • monitoring • reports

  • Android app

    PLANORA EventGuard 360 Same account and server • HTTPS API connection

  • ESP32 PLANORA IoT board

    RC522 RFID + QR scanner • VL53L0X entry/exit • DHT22 • TFT/OLED/DWIN screens Wi-Fi → server: scans, crowd and environment data; server → board: results and warning states.

  • PayMongo • QR Ph

    Client checkout goes to the Organizer’s own account. Signed webhook + server re-fetch confirm payment.

  • Email • Brevo SMTP

    Verification and operational email from the server. Booking notices use a queued mail worker.

PLANORA EventGuard 360: An IoT-Enabled Smart Venue Access and Crowd Monitoring System with QR-Based Attendance and PHP-Based Analytics Dashboard

Booking and payment flow: From the client brief to supplier receipt: follow eight steps, with real payments and PLANORA records clearly separated. Full text follows below.

Booking and payment flow

From the client brief to supplier receipt: follow eight steps, with real payments and PLANORA records clearly separated.

Read booking and payment flow
  1. Guest starts the slides

    Book your event → choose Organizer, date, venue, guest count and services.

  2. Choose booking mode

    Book & pay when checkout is ready, or Send request for the Organizer to quote first.

  3. Choose supplier services

    Bookable packages join the cart. Price-on-request services use Ask for a quote after booking.

  4. Client pays the Organizer

    PayMongo QR Ph → Organizer’s own account. Server confirms payment; request-only flow quotes first.

  5. Create the event

    Organizer uses Clients & bookings to create the event and link the booked suppliers.

  6. Suppliers confirm

    Supplier reviews the assignment in Bookings and confirms or declines. Booking progress stays visible.

  7. Organizer pays suppliers

    Pay via GCash outside PLANORA (or bank/cash), then record the completed payment.

  8. Supplier confirms receipt

    Supplier confirms money received. PLANORA keeps the payment record; Admin reviews Event orders .

Money boundary: PLANORA records payouts and receipts. It cannot send GCash or split PayMongo collections. Admin oversees the whole journey.

Event-day flow: Publish, register, prepare an eligible pass, scan, verify and review. Occupancy monitoring runs alongside identity check-in. Full text follows below.

Event-day flow

Publish, register, prepare an eligible pass, scan, verify and review. Occupancy monitoring runs alongside identity check-in.

Read event-day flow
  1. Publish → register

    Organizer publishes the event. Attendee finds it and submits registration.

  2. Confirmation → eligible pass

    Save the registration PDF. Eligible registrations get a QR pass; an RFID card can be linked.

  3. Scan at the gate

    ESP32 reads the attendee’s QR pass or linked RC522 RFID card and sends it to PLANORA.

  4. Server verifies access

    Server checks the event and credential eligibility, records accepted attendance and returns the result.

  5. Board confirms check-in

    Success shows CHECKED IN and the attendee’s name. Rejected or duplicate scans show their own result.

  6. Review after the event

    Use Reports and Monitoring History for stored attendance, environment readings and incidents.

During the event: Monitoring Occupancy • entries/exits • temperature VL53L0X crowd counts + DHT22 environment readings Respond to venue conditions SOS and assistance reach the authorized event team. NEAR FULL FULL HIGH TEMP

PDF confirms registration; only eligible passes allow entry. Warning labels: firmware prepared, physical-board flash unverified.

Your account, on Android

Get the Android app

Keep your events, eligible passes and messages close at hand.

Version
2.8.7 (build 26)
Size
8.1 MiB
Requires
Android 7.0+

Staging test build. Connects to the staging service; for PLANORA testers.

File SHA-256c1d8be292a9903a8642936faf75cd3b674f37e70f069d138ecbc55a6c31f7375

  1. Open the download page on your Android phone and download PLANORA.
  2. Allow installation from your browser for this install, then turn that setting off again.
  3. Keep Play Protect enabled. Future updates are announced in the app.
Download for Android

Scan to open the download page