The education team schedules a Saturday homeschool workshop in the classroom wing. Two weeks later, the events coordinator books the same room for a member preview reception. Both look fine on their own. Nobody notices the overlap until the caterer and twenty kids with glue sticks arrive at the same door.
Room conflicts like this rarely come from carelessness. They happen because programs and events are often built and owned by different people, in different parts of Altru, and nobody has one view of who is using which space when. This article covers why that happens and the habits and checks that keep it from recurring.
Why programs and events don’t always “see” each other
In Altru, a ticketed program (a tour, a class, a timed show) and an event (a gala, a rental, a member night) are set up and managed differently. Programs are built for selling admission against capacity. Events are built around invitations, registrations, and logistics. Both can be tied to locations, but the location is used mainly to describe where something happens and to drive capacity. It is not necessarily a reservation system that blocks a second booking.
We can’t promise exactly how your Altru instance will behave when a program and an event are assigned the same location at overlapping times. Configuration, how locations and resources were set up, and which staff created the records all play a part. The honest way to find out is to test it:
- In a sandbox or test environment if you have one, or with clearly labeled test records you will delete, create a program occurrence in a room.
- Create an event in the same room, overlapping the same time.
- Note whether Altru warns you, blocks you, or simply saves both.
- Try it the other way around (event first, then program).
If both save without a warning, you now know the software won’t catch this for you, and the fix has to come from process and reporting. If you’re unsure what you’re seeing, Blackbaud support can confirm the intended behavior for your version.
Make one place the room calendar
The most effective fix is organizational. Pick one place where every room booking is recorded, and make it the rule that a room isn’t booked until it shows up there. Options teams commonly use:
- Altru itself, if every program and event is consistently assigned a location and you can report across both (see the query section below).
- A shared calendar (Outlook or Google) with one calendar per room. Staff add a hold there before building the program or event in Altru.
- A facilities request form that routes to one person who approves space and then tells the requester to go ahead in Altru.
Whichever you choose, the important part is the order of operations: claim the room first, then build the sellable record. Most conflicts happen when someone builds the program in Altru, starts selling, and only later thinks about space.
Give each room an owner
Shared spaces with no owner get double-booked. Assign one person (or role) as the approver for each bookable room, with a named backup. When education and events both want the auditorium on the same Saturday, that person decides, not whoever got there first.
Standardize locations in Altru
Reporting only works if the data is consistent. A few cleanup steps pay off quickly:
- One location record per physical room. If you have “Classroom A,” “Class Rm A,” and “Education Room 1” all meaning the same space, merge or retire the duplicates so nobody picks the wrong one.
- Make location required in practice. Even if Altru lets you save a program or event without one, your internal checklist shouldn’t.
- Book setup and teardown time. A reception from 6 to 8 p.m. usually occupies the room from 4:30 to 9:30. If your event times only reflect the guest-facing window, your conflict check will miss the overlap. Either record the full room time or add a separate hold for setup.
- Record off-site and outdoor spaces too. Lawns, terraces, and parking lots get rented and programmed just like rooms.
Run a weekly conflict check
Even with good habits, a scheduled review catches what slips through. Build queries that pull upcoming program occurrences and upcoming events with their location, start time, and end time. Exporting both to a spreadsheet and sorting by location, then date, then start time makes overlaps easy to see: any row whose start time is earlier than the previous row’s end time in the same room is a conflict.
A few practical notes:
- Look ahead at least 60 to 90 days. Conflicts found a week out are much harder to fix, especially once tickets have sold.
- Give the review to the room owners, not just one administrator, so the people who can actually move a booking see it.
- If programs and events can’t easily be combined in a single query in your setup, run two and paste them together. It’s tedious but reliable.
When a conflict slips through anyway
Decide in advance who yields. A common rule: whatever has already sold tickets or signed a contract keeps the room, and the other activity moves. Rentals with a signed agreement and paid deposit usually outrank internal programs, which are easier to relocate and communicate about. Write the rule down so the decision isn’t made under pressure the morning of.
If a program has to move, update its location in Altru before staff print rosters or send reminders, so any confirmation or day-of communication points people to the right room.
Quick answers
Will Altru stop me from booking the same room twice?
Don’t assume so, especially across programs and events. Test it with your own setup and confirm with Blackbaud support if the behavior isn’t clear.
What’s the simplest fix if we’re a small team?
One shared calendar per room, a rule that you add the hold before building anything in Altru, and a monthly look-ahead review.
