Fairground

The Fairground side runs the events you put on — the county fair, the Christmas show, the rodeo — as opposed to renting the grounds to somebody else.

It reuses every rail the Rentals side is built on. Vendor contracts are the same contract engine, vendor invoices are the same invoice engine, and a vendor portal is the same portal pattern as a renter portal. Nothing on this side is a second copy of something that already exists.

Everything hangs off an event

The event is the container. An account runs several at once, each with its own workspace, its own vendors, its own entries, its own tickets, and its own module toggles — turn ticketing off for the Christmas show and it disappears from that event's nav entirely.

Start there. Nothing else on this side makes sense without one.

What lives where

Section	Use it for
Events	Event workspaces, modules, milestones
Forms	Build-your-own forms with payments, uploads, and conditional routing
Catalog	Division → Department → Section → Class, with fees, premiums, and rules
Entries	Every entry made, with QR codes and check-in
Exhibitors	The people who enter, with persistent exhibitor numbers
Judging	Anonymous scorecard judging on an iPad
Results	Tabulation, placements, ties, special awards, publishing
Premiums	What each exhibitor won and paying it out
Vendors	Applications, approval, menus, percentage rent
Ticketing	Ticket types, online sales, gate sales, scanning
Patrons	The audience CRM the fair owns between events
Sponsors	Levels, public form, donation versus invoice
Entertainment	Acts, riders, budget, and paying them
Schedule	The daily public schedule, conflict-aware and printable
Grounds Map	Pin placement on your grounds image

The fair season, in order

Twelve to six months out

1. Create the event and turn on the modules you need.
2. Build the milestone plan — the countdown the board reviews at every meeting.
3. Open the sponsor form and start the vendor application.

Six to three months out

4. Build or roll over the catalog — departments, sections, classes, fees, premiums, rules.
5. Publish the exhibitor entry page.
6. Review vendor applications, accept, waitlist, and get contracts and invoices out.
7. Approve food vendor menus.

Three months to gate day

8. Book entertainment and collect riders.
9. Put tickets on sale.
10. Build the daily schedule and the grounds map.

During the fair

11. Check entries in by QR scan.
12. Judge on iPads.
13. Tabulate and publish results.
14. Sell tickets at the gate alongside the online ones.

After

15. Pay premiums.
16. Settle vendor percentage rent and entertainment payables.
17. Export everything, then run the season reset.

Shared with the Rentals side

One account, one team, one document library, one notification system. Money is the one thing that can be genuinely separate: because a fair board and a rental operation often bank separately, you can connect two Stripe accounts and assign one to each side. See Payments & Stripe.