How to use a Righthand with Bloomerang

Quick answer

Use Righthand to prepare a donor follow-through review from Bloomerang records selected by the development team. Keep stewardship tasks separate from financial or tax determinations.

Start with a reviewable deliverable, keeping Bloomerang as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

Bloomerang describes fundraising, CRM, and volunteer engagement capabilities on its official site. See the official Bloomerang reference. Provider capabilities and Righthand's available tools are separate checks.

Use an approved fundraising or volunteer export with the owner's record definitions, reporting period, and permitted personal fields. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: constituent ID, gift reference, date, campaign, acknowledgment status, assigned staff. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Donation records and acknowledgment status require staff verification. Do not infer donor intent, alter gifts, or issue formal receipts from a summary.

Illustrative first-run brief

Use the owner-provided Bloomerang snapshot or approved read-only view. Review the approved gift-and-acknowledgment snapshot for one campaign. List unconfirmed acknowledgments and assigned next steps without contacting donors. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the development lead to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

A gift with no acknowledgment evidence becomes a staff check, not proof the donor was ignored. Restricted-purpose questions stay with the development lead.

Compare one gift reference and acknowledgment state to the source record using the same campaign filters. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

Household and individual records can be confused. Preserve constituent IDs and ask staff to confirm the intended relationship before deduplicating.

If a household record is mistaken for an individual supporter, keep the IDs distinct and ask the database owner to confirm the reporting unit.

FAQ

What should the reviewer verify first?

Verify constituent IDs, gift or pledge status, period, and contact restrictions. A pledge is not interchangeable with a received gift, and a roster entry is not attendance.

How should a repeat run be scoped?

Retain period and gift-state definitions for repeated reports. Reconcile changed gifts and restrictions before drafts; do not expand the audience from fundraising to volunteering without scope.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.