Where music happens
? Login

← Help Center

Clash detection

Clash detection watches every date you touch and warns loudly — a big red box, not a quiet note — when the band is already claimed that day. It checks:

  • Booked shows (confirmed, soft holds, and open proposals)
  • Tour holds from the routing view
  • On-tour ranges that block local bookings
  • Member unavailability (recurring blocks like day-job shifts)
  • Venue double-books (another band already at that venue that night)

Where it fires

  • Adding a tour hold on a claimed date
  • Adding an on-tour range that covers booked dates
  • Toggling I'm free on a claimed date
  • The standalone Clash Check page (`/bands/<id>/clash-check`): pick any date, get the full report. Run it before you propose or accept anything.

In every case you can still save anyway ("Save hold anyway" / "Mark free anyway") — clash detection warns, it doesn't forbid. Sometimes the existing item is tentative and the new one is real.

Tips

  • Keep member unavailability current — stale day-job blocks cause false alarms.
  • A clash against an open proposal is the most common false positive: the proposal may die on its own.
  • Venue double-book warnings only appear when a system venue is involved.

Troubleshooting

It warned about a member who's on hiatus. Clash detection only counts active members — check the member's status on the band page.

No warning, but we double-booked anyway. The other booking was probably entered as free text under a different band name, or the date was typed wrong. Clash detection matches exact dates on the same band record.

I want a hard block, not a warning. That's deliberate — bookers sometimes knowingly overbook a tentative date while negotiating. The warning makes it a conscious choice instead of an accident.

← All help topics

Topics