A development officer has coffee with a donor, logs it on the constituent record that afternoon, and two weeks later the board chair asks for a cultivation report on that prospect. The coffee isn’t there. It was recorded as a stand-alone interaction, not as a step on the prospect plan, so anything that reads from the plan can’t see it.
This is one of the most common gaps in Altru prospect tracking, and the honest answer to “how do I attach that interaction to the plan?” is that you probably can’t do it directly. Below is what’s going on, how to confirm it in your own database, and the workarounds that hold up.
Interactions and plan steps are related, but not the same record
In Altru, a prospect plan is a structured set of steps: planned moves toward an ask, each with a date, an owner, a status, and notes. When a step is completed, it reflects contact with the prospect, so it naturally looks a lot like an interaction.
A stand-alone interaction is different. It lives on the constituent record and isn’t tied to any plan. The two may show up near each other when you look at a constituent, which is why people assume one can be dragged into the other. In practice, the plan step is where the plan’s history comes from, and an interaction logged outside the plan stays outside it.
As far as we know, Altru does not offer a way to take an interaction that already exists and reassign it to a prospect plan after the fact. Configurations and releases vary, so don’t take our word for it: open a test constituent in a sandbox (or a record you can safely clean up), log an interaction, then see whether the interaction offers any option to associate it with a plan. If you can’t find one, ask Blackbaud support to confirm before you build a process around the gap.
Workaround 1: Recreate it as a completed plan step
For a handful of missed contacts, the cleanest fix is to rebuild the interaction where it belongs.
- Open the prospect plan and add a new step.
- Copy over the essentials from the original interaction: the actual contact date, the owner, the contact method, and the summary or notes.
- Mark the step completed.
- Decide what to do with the original interaction. Deleting it avoids double-counting contacts in reports. If your organization prefers never to delete history, keep it and add a note such as “Duplicated as plan step on [date]” so nobody counts it twice.
Pick one rule for step 4 and write it down. A mix of deleted and kept originals makes contact counts unreliable within a few months.
Workaround 2: Report across both, instead of moving anything
If the backlog is large, re-entering every interaction isn’t realistic. Instead, build your cultivation reporting so it reads both sources:
- A query of plan steps for constituents with an active prospect plan.
- A query of interactions for those same constituents, filtered to dates within the plan’s active period.
Export both and combine them, or use the two side by side in your prospect review meeting. It’s more work than one tidy plan history, but it doesn’t rewrite anything and it catches contacts that were logged the “wrong” way. Test the date filters carefully; a contact logged with the entry date instead of the actual contact date will drift out of range.
Workaround 3: Make the right path the easy path
The long-term fix is behavioral. Stray interactions usually happen because the person logging the contact isn’t sure whether a plan exists, or finds the constituent faster than the plan.
- Flag prospects visibly. If your setup allows it, use an attribute, constituency, or similar marker so that anyone opening the record can see there’s an active plan and who owns it.
- Agree on one rule. For example: any contact with a constituent who has an active plan is logged as a plan step; everything else is a stand-alone interaction.
- Review monthly. Run a query of interactions added in the last month for constituents with active plans. Each result is either legitimately outside the plan or something to recreate as a step. A short list caught monthly is far easier than a year of cleanup before a campaign.
- Train the occasional users. Executive directors and board liaisons log fewer contacts but often the important ones. A one-page guide on where to record a donor meeting saves a lot of reconstruction later.
When it’s worth fixing old records
Not every missed interaction needs to be moved. It’s worth the effort when:
- The plan is heading toward an ask soon, and the solicitor needs the full history in one place.
- Your reports to leadership or the board count plan steps as “moves,” and missing ones understate real activity.
- Staff turnover is likely, and the next officer will rely on the plan to understand the relationship.
For a dormant plan or a casual touchpoint, a note on the plan pointing to the interaction is often enough.
Quick answers
Will a completed plan step still show on the constituent record?
Plan activity is generally visible from the constituent, but how and where it displays can depend on your setup. Check a test record to see exactly what your staff will see.
Can I bulk-move interactions into plans?
We aren’t aware of a built-in way to do that. If you have a large backlog, ask Blackbaud support whether an import or batch option fits your version before re-keying anything by hand.
