Understanding Collision Errors in Reservations

When updating reservation dates in BRM, you may sometimes see an error code that indicates your booking has collided with another scheduled activity.

These errors are not random — they are designed to protect your schedule and prevent overlapping reservations on the same asset.

What Triggers a Collision Error?

A collision error appears when you try to move or extend a booking so that its new start or end time overlaps with another existing booking.

There are two common scenarios:

1. Collision Forwards

   • Triggered when you attempt to move the end time (to date) later, but another reservation already occupies that period.

2. Collision Backwards

   • Triggered when you attempt to move the start time (from date) earlier, and that overlaps with an existing booking.

Example Scenarios

1. A Reservation Between Two Others:

In this situation, you already have one booking squeezed between two other confirmed reservations. You cannot extend it forwards or backwards without running into a collision.

2. Collision Backwards:

If you adjust the start time earlier and it overlaps with another reservation, BRM will display a collision error code.

3. Collision Forwards:

If you extend the booking past its allowed end time into another scheduled reservation, BRM will again block the change with a collision error.