Someone booked a school group into a classroom that was already reserved. Altru flagged the conflict, a staff member clicked past it, and two buses showed up for one room. Afterward, the obvious question is: how often does this happen, and who is approving it? Answering that means reporting on resource overrides, and that turns out to be harder than it should be.
This guide explains what you can and can’t easily see in Altru today, how to build the closest thing to an override report, and how to put a light process around overrides so the data exists when you need it.
What “resource override” usually means in Altru
Altru lets you attach resources (rooms, locations, staff, volunteers, equipment, supplies) to program events and group reservations. When a booking would exceed a resource’s availability or double-book it, Altru warns about the conflict. Users with the right permissions can proceed anyway. That decision to proceed is the override.
Overrides aren’t always bad. A gallery educator may cover two small groups at once on purpose, or a room may hold more than its listed capacity for a standing event. The problem is not overrides themselves. It’s that nobody can see the pattern.
The honest limitation
We aren’t aware of a standard Altru report that lists every resource conflict that was overridden, with who did it and when. Depending on your version and permissions, some of this detail may be available through queries on events, reservations, or resources, but whether an “override happened” flag is exposed as a queryable field is something you should confirm before you promise anyone a report. Two good ways to check:
- Open query designer, start from an event- or reservation-based source view, and look through the resource-related fields for anything indicating a conflict, override, or the user who saved the change.
- Ask Blackbaud support directly whether override activity is logged and whether it can be queried or audited. Ask specifically about resources on program events versus group sales reservations, because the answer may differ.
If nothing usable turns up, you can still get most of the value by reporting on the result of overrides rather than the override click itself.
Report on the result: overbooked resources
An override leaves a footprint: a resource assigned to more bookings, or more people, than it should hold for a given time. That you can usually find with a query.
- Build an event or reservation query that includes the event date and time, the resource name, the quantity of the resource assigned, and the attendance or capacity numbers you track.
- Filter to a meaningful window, such as the next 60 days for operational checking or the last quarter for a look back.
- Export and sort by resource and time slot. Any resource that appears on overlapping events in the same slot, or whose assigned quantity exceeds what you own, is a likely override.
- Include the “added by” or “changed by” fields if your source view offers them. That gets you close to “who approved it” without a dedicated audit log.
This won’t catch every override, for example one that was later cleaned up, but it reliably catches the ones that still matter: future bookings where a room, guide, or bus bay is double-committed.
Make overrides leave a trail going forward
The cleanest fix is procedural. If your team agrees that every override gets recorded in a consistent place, reporting becomes a simple query.
- Limit who can override. Review security roles so that only scheduling leads, not every front-line user, can save past a resource conflict.
- Require a note or attribute. Ask staff to add a short, standardized note to the event or reservation when they override, such as a fixed prefix followed by the reason. A consistent prefix is easy to search for. If your setup supports attributes on events or reservations, an “Override reason” attribute is even easier to query.
- Review weekly. One person runs the overbooked-resource query and the override-note query together and checks that every overbooking has a reason attached.
Test any new attribute or security change in a sandbox or with a test event first, so you know exactly how it shows up in queries before you roll it out.
Getting the report in front of the right people
The people who care about overrides, such as education managers, facilities, and volunteer coordinators, often don’t log into Altru to run queries. Exporting a spreadsheet every Monday works, but it tends to stop the first week someone is on vacation.
That’s the part Data Bridge handles: it syncs the results of an Altru query to Google Sheets, so your overbooked-resource and override-note queries can feed a shared sheet that facilities or education staff can check any time, without a manual export. The query logic above stays the same; you just stop being the person who has to send it.
Quick answers
Can I see who overrode a specific conflict?
Possibly, through “added by” or “changed by” fields on the event or reservation, but that shows who last saved the record, not necessarily who clicked past the warning. Confirm with Blackbaud support whether a true override log exists for your setup.
Should we block overrides entirely?
Usually not. Some overrides are deliberate and fine. Restrict who can do it and require a reason, rather than removing the option.
