HeyWunmi.Let's talk (opens in a new tab)
← Selected work

Event Operations / Workflow Automation

The Passport Potluck

Event Assignment & Payment Automation

A self-service event system connecting destination assignments, availability rules, participant records and payment verification.

Portfolio implementation · Project walkthrough and evidence

The Passport Potluck: original interfaceEnlarge image
Original project interface. Select to inspect at full size.

The operational challenge

What needed
to work better.

Destination assignments, availability and payment status can easily become disconnected when event administration is handled across messages and separate records.

My contribution

I built the passport experience and the Apps Script rules that connect destination assignments and payment verification to the operational records in Google Sheets.

The workflow

From first step to follow-through.

  1. 01Passport requested
  2. 02Availability checked
  3. 03Difficulty rules applied
  4. 04Destination assigned
  5. 05Payment verified
  6. 06Attendee record updated
HARD / MEDIUM / EASYRule-based destination categories

A playful front end. Clear rules underneath.

Destination assignments use predefined HARD, MEDIUM and EASY categories alongside availability rules. Google Sheets is the operational source. Payment verification checks for the matching attendee before updating both the payment and attendee status; an unmatched attendee is not marked verified.

In motion / recorded demonstration

See the experience.

A short walkthrough of the attendee-facing passport experience, showing the entry screen and destination assignment. Private form and payment scenes are omitted; this excerpt has no audio.
Read the workflow description

A self-service event system connecting destination assignments, availability rules, participant records and payment verification.

Passport requested → Availability checked → Difficulty rules applied → Destination assigned → Payment verified → Attendee record updated.

Destination assignments use predefined HARD, MEDIUM and EASY categories alongside availability rules. Google Sheets is the operational source. Payment verification checks for the matching attendee before updating both the payment and attendee status; an unmatched attendee is not marked verified.

Behind the interface

The work underneath.

Assignment logic

Assignment logicEnlarge image
Original Apps Script excerpt showing difficulty categorisation and updates to the destination sheet.

Payment verification

Payment verificationEnlarge image
Original Apps Script excerpt: an attendee must be found before payment and attendee records are marked VERIFIED.

Functional outcome

A connected operational experience.

The system gives participants a self-service passport journey while keeping assignments and verification status connected to the event records. No payment provider or event attendance figures are inferred.

Have a similar operational challenge?

Let's make it
work better.

Discuss your workflow (opens in a new tab)↗

Media viewer