Your preferences and defaults
Set these once. They cascade to every tour, gig, inquiry, and export.
When you'd use this
You just set up your account and want to dial in the defaults. Or you relocated across timezones, switched to metric, or started booking gigs in another currency.
Where
Profile → Settings → Preferences.
A handful of these preferences (timezone, currency, default radius, default guarantee floor, default minimum draw) are wired through the app today. The full preference UI for the rest is on the way — for now, sensible defaults apply and you can adjust manually per tour or gig.
The settings
Timezone. Default: auto-detected from browser. Affects all displayed times (load-in, call time, doors, etc.), push notification quiet hours, and inquiry timestamps. Change when you relocate.
Units.
- Distance — miles or kilometers. Drives Router outputs, Weekend Finder radius, mileage log.
- Temperature — Fahrenheit or Celsius (used in weather info on day sheets).
- Weight — pounds or kilograms (for merch shipments, gear lists).
Currency. Default: USD. Drives all P&L displays, budget entries, invoices, settlement math. Change if you primarily book in EUR, GBP, CAD, etc. Changing currency mid-year creates mixed-currency records; export before you change.
Date format. MM/DD/YYYY (US), DD/MM/YYYY (EU), or YYYY-MM-DD (ISO). Affects display only — the underlying date is stored canonically.
Time format. 12-hour (7:30pm) or 24-hour (19:30). Matches your regional convention.
First day of week. Sunday or Monday. Affects calendar grid layout and weekly budget rollups.
Default tour starting radius. How many miles (or km) from your home city the Router assumes as the first leg's max drive on a new tour. You can always override per-tour.
Default guarantee floor. The minimum show guarantee you'd accept. Weekend Finder and Router use this to filter matches; they won't surface dates below this floor.
Default minimum draw. Your historical or expected draw. Venues with capacity less than this × 0.4 don't surface in matches (empty-room protection).
What cascades
Changing a preference retroactively updates:
- Display of existing events (e.g., switching to 24-hour time changes all displayed times)
- Future Router outputs
- Future Weekend Finder results
- New budget entry defaults
It does NOT retroactively rewrite:
- Stored values in old budget entries (still in their original currency, if you changed currency)
- Inquiry copy you've already sent
- Exported PDFs or CSVs
Timezone + DST
Timezone is stored as an IANA identifier (America/Los_Angeles, not PST). Daylight saving transitions are handled automatically.
Units + imperial/metric math
Mintoor stores everything in a canonical unit internally (km, kg, °C, USD). Your preferences only affect display. Switching units doesn't lose precision.
Still stuck?
- Timezone showing wrong event times? You probably set the preference but are viewing an event that has its own timezone override (e.g., a tour stop in another country). Event-specific timezone wins.
- Currency showing $ but you're in another country? Changing the Preference won't retroactively convert historical USD records. Export first, change, and your accountant can reconcile.