Booking pipeline

Every gig has a status. Five values track where the gig is in your workflow:

• Inquiry — a lead. Someone reached out, you haven't committed.
• Booked — terms agreed, deposit may or may not be in.
• Confirmed — locked in, contracts signed, deposit received.
• Played — the show happened.
• Cancelled — it's not happening.

The default for a new gig is inquiry. Move it forward when the situation moves forward.

Create a gig

From the gigs list, hit New gig. Required: date. Everything else (venue, times, pay, setlist) you can fill in as it solidifies.

[screenshot: new gig form]

The finance fields

Each gig tracks:

• Pay — total agreed amount, in cents (the UI shows it in dollars/your currency).
• Deposit — what's been received up front.
• Currency — defaults to USD; changeable per gig.

The deposit usually moves the gig from inquiry → booked. The final payment usually moves it from played to "settled" — though there's no explicit settled status (just a played gig with the full pay marked received).

Tip: Deposits are a lifesaver for working bands. A gig in inquiry has no real commitment; a gig with a deposit in is a real gig. Use the pipeline to reflect that — don't move to booked until the deposit's actually in.

Expenses

Each gig has a separate expenses subtable: gas, tolls, rentals, hired-gun pay, equipment fees. Each line has a label and an amount. The gig P&L (profit & loss) is pay - sum(expenses).

The post-show summary surfaces P&L per gig and across all played gigs.

Cancelling

If the gig falls through, set status to cancelled rather than deleting. Cancelled gigs stay in your list (filterable) so you have a record of leads that didn't pan out — useful for venue follow-up and tax records.

What's next

• Public request page — once confirmed, share the URL.
• Post-show summary — after played, score the gig.