A staff calendar entry that says “Board tour” is fine until someone asks where it happens, when it ends, and whether it runs through Thursday. Then everyone opens a separate spreadsheet or a shared Outlook calendar, and the Altru calendar stops being the place people look.
The short version: Altru’s general calendar items are lightweight by design. They’re good for marking that something is happening, and much weaker at describing it. Below is how to tell which kind of record you actually need, and the workarounds that hold up when you’re stuck with a plain calendar item.
Start by asking what the item really is
A lot of frustration with calendar items comes from using them for things Altru already models elsewhere. Before adding detail to a calendar item, sort it into one of these buckets:
- Something you sell or take registrations for. A tour, class, camp session, or ticketed program belongs in your program and scheduling setup (daily sales or advance sales) or in event management. Those records are built around a start and end time, capacity, and pricing, and they tie to revenue.
- A fundraising or cultivation event. Galas, member nights, and donor receptions fit Altru’s events area, where you track invitations, registrants, and attendance against constituent records.
- An internal or informational note. Staff meetings, facility closures, a contractor on site, a rental walk-through. This is where a simple calendar item is the right tool, and also where its limits show up.
If the item falls in the first two buckets, moving it to the proper record type usually solves the “no location, no time range” complaint, because those areas carry much more scheduling detail. It also means the activity shows up in reports and queries instead of living only on a calendar.
What to confirm in your own database
Exactly which fields a calendar item exposes, and whether it supports an end time, a multi-day span, or a location, can vary by Altru version and configuration. Rather than trust anyone’s memory (including ours), check it directly:
- Create a test calendar item and note every field the form offers.
- Check whether a date range or end time is available, or whether the item is a single point in time.
- Look at how the item appears in day, week, and month views. Something that looks fine in a day view can be truncated in a month view.
- If you have a sandbox or test environment, try it there first. If you don’t, ask Blackbaud support what the item type supports in your release.
Write down what you find. That one-page note saves the next administrator from repeating the experiment.
Workarounds for plain calendar items
Use a strict naming convention
When the item can’t hold a location or end time as separate fields, put them in the title in a fixed order so they read the same way every time. For example: “Education Room | 10:00–11:30 | Teacher workshop”. The pattern matters more than the exact format. Pick one, publish it to staff, and stick to it, because a calendar where half the entries follow a convention is harder to scan than one where none do.
Keep titles short enough to survive a month view. If the full detail won’t fit, lead with the location and start time, and move the rest to the description.
Put the detail in the description, consistently
If the item has a description or notes field, use a small template: location, start and end time, contact person, setup needs. A repeated structure is easy to read and easy to copy when you create the next entry.
Create one item per day for multi-day activities
When there’s no reliable way to make a single item span several days, enter one per day and number them in the title (“Day 2 of 3”). It’s more clicks, but staff looking at any single day will see it, which is the point of the calendar.
Standardize your location names
Whatever you type as a location, keep a fixed list: “Education Room,” not “Ed room,” “classroom,” and “downstairs” depending on who entered it. If you already maintain location names for programs or events, reuse the same names so a room means one thing across the database.
When to stop forcing it
If your team needs room booking with conflict checking, recurring internal schedules, or invites that land in people’s email calendars, a general calendar item isn’t going to become that tool, no matter how well you format it. Many organizations keep internal room and staff scheduling in their email platform’s shared calendars and reserve Altru for anything tied to constituents, sales, or attendance.
That split is reasonable as long as it’s deliberate. Decide which activities belong where, tell staff, and avoid entering the same thing in both places, since the two copies will drift apart within a week or two.
Quick answers
Can I add a custom location field to calendar items?
We wouldn’t assume so. Check what your version allows in a test environment or with Blackbaud support before planning around it. A title or description convention works in the meantime.
Should a public program ever be just a calendar item?
Generally no. If people buy tickets or register, set it up as a program or event so the time, capacity, and revenue are tracked together.
