Organizer (admin)

Sam

Coordinates the market as a volunteer, next to a day job.
Goal

Manage vendor applications, booth assignments, and payments in one place without duplicate work.

Needs

A central list of applications, clear application and payment statuses, alerts for conflicting booth requests, and an easy way to assign booths and track payments.

1See what needs attention

Doing
Opens the dashboard.
Pain today (assumed)
Checks the inbox, the form and a spreadsheet separately.
In the prototype
Counts by status and a short “needs attention” list.

2Review applications

Doing
Filters by status or category.
Pain today (assumed)
Hunts through emails.
In the prototype
One list with status, paid or due, and page progress.

3Open an application

Doing
Reads what they sell and which booth they want.
Pain today (assumed)
Details are in different places.
In the prototype
Everything on one page, with booth requests.

4Confirm booths

Doing
Approves applications. If two vendors want the same booth, the first to pay gets it.
Pain today (assumed)
Assigns every booth by hand.
In the prototype
Requests show table count and choices. Overlaps are flagged, and settle themselves by payment.

5Approve and track the fee

Doing
Approves. Marks the fee received if paid directly.
Pain today (assumed)
Payments tracked in separate notes.
In the prototype
Approve and assign in one step. Fee received creates the page.

6Check the booth map

Doing
Sees assigned, requested and open booths.
Pain today (assumed)
Layout kept on paper or in her head.
In the prototype
Map by status, plus a waiting list.

7Review the guide

Doing
Previews how vendors will appear.
Pain today (assumed)
Retypes the vendor list.
In the prototype
The guide is built from what vendors entered.
Personas and pain points are my assumptions about how a small market runs, not interview findings.