CAVALCADE

× Markdown Consulting Proposal

Entry & Workflow Modernization

The Cavalcade entry, brought online.

A proposal for the board: keep everything that works about the way clubs enter the Cavalcade, and take the paperwork, the fee math, and the chase-down off the secretary's plate. Three working demos are linked below.

24 events ~50 clubs 4 jobs in one entry blank Targeting 2027

The idea

One form is really four jobs

The official entry blank quietly does the work of four different documents at once. Untangling them is what makes the rest straightforward — and it's why a digital version saves real time without changing how the Cavalcade runs.

01An invoice

Entry fees across 24 events, plus office charge, porta-johns, electric, armbands, tents, and stalls — totaled by hand today, computed automatically here.

02An eligibility roster

Up to ~90 club members, certified by the secretary. Contestants must belong to the club they represent.

03The event entries

One contestant per event, with day preferences — the data that feeds the draw and, later, results.

04A camp & logistics order

Tents, electric, stalls, and camper counts on hard June 1 deadlines driven by the tent company's bill.

The approach: digitize intake while keeping paper working (mailed and walk-in forms are scanned and read, then confirmed by a person); automate the fee math and the signature routing; and land every submission in a spreadsheet the Cavalcade owns. Version one is data-only — money stays on the mailed-check rail, with card payment shown as a future option.

The demos

Three working pieces

Each opens in a new tab. These are live, clickable demos running on sample data — no real backend wired up yet.

Contestant-facing

Queen Entry Form

The simple win. A young woman representing her club submits her information, headshot, and program bio in one pass — no printing, no mailing, no attaching a separate page.

How it works: required fields are validated as you go, the headshot previews instantly, and on submit the entry is recorded and offered as a clean CSV — the same tidy row the office would otherwise retype.

Club-facing

Entry Blank Workflow

The workhorse. A six-step process: pick events, add camp and logistics, list and certify the roster, route the waiver for officer signatures, then review an itemized total and pay. A second tab shows the office side, where a mailed paper form is scanned, read by OCR, and confirmed.

How it works: the fee total updates live as events and extras are added; signatures route by email in order — Secretary → VP → President; payment offers a card option (Stripe) alongside the traditional check; and on the office tab, the fee calculator catches a wrong handwritten total automatically.

Office-facing

Entries & Signatures Dashboard

The command center. Every club's entry stored as a record and tracked from submission through signatures to payment — so the office can see at a glance what's complete, what's stuck, and where.

How it works: open any club to see its full record, the signature path (Secretary → VP → President) with live status, and accounting totals. Advance a signature and watch it route to the next officer. A by-event view flips the same data around to show entrants per event — the seed of the draw.

How the pieces fit

One path, start to finish

01
Club enters online
Or mails paper — scanned & OCR'd to the same record.
02
Data to your sheet
Every submission lands in a spreadsheet the Cavalcade owns.
03
Signatures route
Emailed in order: Secretary → VP → President.
04
Office tracks it
Dashboard shows complete vs. in-progress and accounting.
05
Draw & results
By-event view feeds the draw and year-over-year stats.

What's next

Scope & open decisions

Decisions for the board

Logins? Should clubs have save-and-return accounts that pre-fill next year, or one-shot submissions?
E-signatures? Are typed-name signatures acceptable on the waiver, or is a drawn signature required?
OCR licensing. The paper-reading step uses Microsoft AI Builder, which bills separately — to be priced before committing.
Working demos on sample data — no live backend or payment processing is connected yet. Built to show the shape of the workflow.