Volunteer coordinators at museums, zoos, and gardens tend to hit the same wall with Altru. The donor and member side of the database is deep, and then you open the volunteer side and find it covers the basics: who your volunteers are, what jobs exist, and who worked when. Coordinators who need self-scheduling, onboarding checklists, or a monthly hours report for the board usually end up building something next to it in a spreadsheet.
You can’t patch Altru’s volunteer features yourself, but you can get a lot more out of what’s there. This guide covers what to tighten inside Altru first, where a separate tool makes sense, and how to keep volunteers from turning into a second, disconnected list of people.
Start by naming the actual gap
“The volunteer module is limited” usually means one of three different problems, and each one has a different fix:
- Scheduling: volunteers can’t see open shifts and sign themselves up, and swaps or cancellations go through the coordinator by email or phone.
- Profiles: you need to track things like training completed, background check dates, emergency contacts, skills, or age requirements, and there isn’t an obvious home for them.
- Reporting: hours by department, retention, and “who hasn’t worked in six months” take too long to pull.
Write down which of these costs your team the most time each week. Often one of them is the real pain and the other two are annoyances, and knowing which one changes what you should do next.
Profiles: use the constituent record you already have
A volunteer in Altru is a constituent, and that helps you more than it might seem. Everything you can attach to a constituent you can also attach to a volunteer: attributes, notes, relationships, and contact information. Before you buy anything for profiles, try this:
- Create a small set of constituent attributes for the fields you check most often, such as orientation date, background check expiration, and a skills or department attribute. Keep the list short and decide which ones need dates attached.
- Agree on one place for each fact. If the background check date lives in an attribute, it doesn’t also go in a note. Duplicate homes are how profiles drift.
- Use relationships for emergency contacts instead of free-text notes, so the contact is a real record you can find and update.
How attributes behave for volunteers can depend on how your Altru database is configured. Test new attributes on a handful of records, or in a sandbox if you have one, before rolling them out to everyone.
Reporting: build queries once, reuse them monthly
Most reporting frustration comes from rebuilding the same answer every month. Altru’s queries can usually get you what the standard reports don’t. A few worth saving:
- Active volunteers with no recorded hours in the last 90 or 180 days, as your re-engagement list.
- Hours by job or department for a date range, which is what boards and grant reports ask for.
- Volunteers whose background check or training attribute expires in the next 60 days.
- Volunteers who are also members or donors. This is the query a standalone volunteer tool can’t easily give you, and it’s often the most useful one for development staff.
Name saved queries clearly and put them in a shared folder so the next coordinator inherits them. If you need hours totals you can’t get from a query, ask Blackbaud support whether a smart field or a different query source fits before you settle on a spreadsheet.
Scheduling: the hardest gap to close inside Altru
Self-service shift signup is where coordinators most often look beyond Altru. If your volunteers expect to open their phone, see open shifts, and claim one, that experience is easier to find in a dedicated volunteer scheduling platform. Before deciding, confirm with Blackbaud support or your account contact what volunteer-facing options are available for your Altru setup, since that can change over time.
If you do add a scheduling tool, set ground rules up front:
- Altru stays the master list of people. New volunteers get a constituent record in Altru first, or are matched to an existing one, so a member who starts volunteering isn’t created twice.
- Decide what flows back. At minimum, bring hours back into Altru on a regular schedule, monthly at the least, so your queries and reports stay accurate.
- Pick one owner for the sync. Imports that “someone does when they have time” stop happening by spring.
- Check for duplicates after each import. Volunteer signups are a common source of duplicate constituents because people type names and emails differently each time.
When a spreadsheet is fine
Not every program needs new software. With a few dozen regular volunteers on fixed weekly shifts, a shared schedule plus monthly hours entry into Altru may be all you need. The setup starts to break once you’re running seasonal events, multiple departments, or youth programs with paperwork requirements. A useful test: if your coordinator spends more of the week filling shifts than supporting the volunteers in them, it’s time to look at a scheduling tool.
Quick answers
Should volunteers be in Altru at all if we use another scheduling tool?
Yes. Keeping them as constituents lets you see the whole relationship: volunteer, member, donor, event guest. That view is the main reason to keep Altru at the center.
What’s the fastest improvement to make this month?
Usually reporting. Saving three or four well-built queries takes an afternoon and can remove hours of monthly manual work.
