CRO - Cancellations, No-Shows and Changes

Contact the CRO:  (910) 672-2500

To support effective scheduling and resource planning, all cancellations and event changes must be submitted according to the required notice periods. Late cancellations, no-shows, or unapproved changes may result in additional charges and may affect future reservation privileges. All event modifications must receive CRO approval before they are implemented.

User Type or Situation Standard
Internal events Cancellations should be submitted at least 48 hours before the event. Direct costs already incurred may be charged.
Student organization events Cancellations should be submitted at least 48 hours before the event. Direct costs already incurred may be charged.
External rentals Cancellations should be submitted at least 48 hours before the event. Repeated late cancellations or no-shows may affect future reservations.
Late cancellations Cancellations should be submitted according to the facility use agreement, generally at least 10 business days before the event unless otherwise stated.
No-shows Charges may apply for labor, security, housekeeping, ticketing, AV, catering, or other services already scheduled or incurred.
Event changes No-shows may result in charges and may affect future reservation privileges.
Print Article

Related Articles (4)

CRO - Definitions and Event Classifications
Event classifications define how facility use requests are reviewed, approved, and charged. Each classification reflects the event’s sponsor, purpose, and connection to the University, and determines whether facility fees, direct costs, or external rental requirements may apply.
CRO - Reservable Space Categories
Different types of campus spaces require different levels of review, coordination, and support. The CRO works with space owners and campus partners to manage reservations, confirm availability, route service needs, and ensure that events are properly approved before use.
CRO - Minimum Request Timelines
CRO minimum request timelines are designed to protect service quality, safety, staffing, cost recovery, and customer experience. Late requests may be denied or approved only if operationally feasible.
CRO - Reservation Approval Workflow
The reservation approval workflow begins when a requester submits an event request through 25Live or BroncoAdvantage. The Central Reservations Office (CRO) reviews the request for space availability, event category, requester eligibility, completeness, scheduling conflicts, and whether additional review is needed.

Related Services / Offerings (1)

Central Reservations Office - Reservation Request
The Central Reservations Office (CRO) serves as the University's centralized intake, coordination, approval, and official records office for reservable campus spaces and event-related services.