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

    Supervised QR scans, estimated occupancy, temperature and humidity readings, and device status 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

Three account roles work in the PLANORA website: Admin, Organizer and CLIENT. Participants use individual pass links and suppliers are business records, so neither needs an account.

  • Admin

    Approves Organizers, governs supplier business profiles, assigns devices, and oversees health, audit and quarterly reports. Admin cannot see confidential proposals by default.

  • Organizer

    Answers private proposal invitations. After a booking is accepted, the Organizer runs its event: participants and passes, supplier engagements, payments, monitoring and reports.

  • CLIENT

    Writes the event brief, invites approved Organizers, compares proposals after the deadline, awards one, pays the booking and supplies the participant list.

  • Participants (no account)

    Receive an individual pass link from the Organizer. Each pass admits one person to one event.

  • Suppliers (no login)

    Business profiles whose private event engagements the Organizer records: the quotation, agreed service, cost, deposit, balance and completion.

  • Venue board

    An ESP32 with a GM65 QR scanner, DWIN, TFT and OLED displays, a DHT temperature and humidity sensor, fan, RGB LED, LED and active buzzer. The operator chooses Entry or Exit mode, and the website records each accepted scan once.

No app installation is needed: everything works in a phone or computer browser.

Occupancy is a QR-based estimate from supervised Entry and Exit scans. It is not a physical headcount.

Booking and payment cycle

From the CLIENT brief to one accepted booking linked to one event.

  1. CLIENT brief

    The brief covers the purpose, event type, schedule, location, expected participants, services, proposal deadline and budget disclosure.

  2. Private invitations

    The CLIENT invites approved Organizers. An invitation allows the Organizer to submit a proposal and nothing else.

  3. Private proposals

    Each Organizer submits and revises its own itemized proposal before the deadline. Organizers never see each other's proposals.

  4. Compare and award

    After the deadline, only the CLIENT compares the proposals and awards one of them.

  5. Accepted booking

    The Organizer accepts. One booking and one event are created, and the agreed scope, price, terms and schedule are frozen.

  6. Booking payments

    The CLIENT sends the deposit and balance set in the agreement directly to the Organizer's GCash, MariBank or GoTyme account and uploads proof with the reference. A payment counts only after the Organizer verifies it; then one receipt is issued and the balance updates.

  7. Suppliers and participants

    The Organizer records supplier engagements and costs privately. The CLIENT supplies names; the Organizer validates them and issues individual passes.

A payment QR code is separate from a participant's admission QR pass.

PLANORA records payments and receipts.

Event-day flow

Supervised QR Entry and Exit, an estimated occupancy count and environment readings, followed by closure and reports.

  1. Assign the board

    The device is assigned to the event, and the operator sets Entry or Exit mode on the server.

  2. Scan Entry

    The first accepted Entry records attendance once and adds one to the estimated number inside. A repeated Entry changes nothing.

  3. Scan Exit

    An accepted Exit lowers the inside estimate, and the attendance stays counted. A repeated Exit changes nothing.

  4. Monitor

    Temperature and humidity readings show when they were taken and how fresh they are. Missing data shows as unavailable, never as zero.

  5. Close

    When the event ends, new registration, new passes and Entry close. A bounded departure window keeps Exit available.

  6. Report and review

    Completed events feed the quarterly analytics. The CLIENT rates the Organizer, and the Organizer rates suppliers, for completed work.

When exits are not scanned, the occupancy estimate is marked incomplete.