Action Blueprints - Example Library

If you're just getting started with Humanitru, Action Blueprints are one of the best tools to set up early. A Blueprint gives your team a templated way to enter a specific kind of Action — prompting for the same Campaigns and fields every time — so your data stays consistent no matter who's doing the entry.

Blueprints aren't just for donations. Below are some suggested Blueprints to build, along with the fields and Campaigns you might want to include in each.

What Goes Into a Blueprint

Every Blueprint is built from the same basic pieces:

• Name — make it specific enough that staff can tell it apart from similar Blueprints at a glance (e.g., "Stewardship Call Log" rather than just "Call").
• Description — a short explanation of what the Blueprint is for and when to use it, so anyone on your team can pick the right one.
• Campaigns — you add Categories and Campaigns to a Blueprint, and each works differently when the Blueprint is applied:
• Selecting a Category includes all of its Campaigns as options to select from when the Blueprint is applied — the person entering the Action chooses whichever one fits.
• Selecting a Campaign means that Campaign is added to the Action when the Blueprint is applied, and it cannot be removed.
• A single Blueprint can include both — one or more Categories to choose from, plus one or more Campaigns that are always added.
• Additional Fields — Key Value Pairs added to the Notes field to capture details specific to that Action type, using consistent labels every time.

With that structure in mind, here are some Blueprints worth setting up with suggested/sample options listed for Campaigns and Additional Fields (to be tracked as Key Value Pairs).

Call Log

Any time a gift officer or team member calls a constituent, it's best practice to log that call in Humanitru with notes and Campaigns describing what the call was about, whether follow-up is needed, and who made the call.

• Category required: Call Reasons — with Campaigns such as Set Meeting, Stewardship, Thank You, or Volunteer Information, so staff must pick a reason but choose whichever one fits the call.
• Additional fields:
• Follow-Up By Date
• Giving Interest (text)
• General Notes

Meeting Log

Similar to a call log, a Meeting Log Blueprint lets staff select the Meeting Action type and record what prompted the meeting and what the goal was. Using a Campaign for the meeting reason lets you sort and filter meetings later.

• Category required: Meeting Reasons — staff choose whichever Campaign in the category matches what prompted the meeting.
• Additional fields:
• Follow-Up By Date
• Giving Interest (text)

General Constituent Notes/History

A Notes Blueprint is a great way to capture non-transactional background information about a constituent consistently — the kind of detail that's easy to lose track of if everyone records it differently.

• Category required: Note Type — with Campaigns such as Biography, Obituary, or History, so staff select whichever one describes the Note.
• Additional fields: tailor these to the Note Type selected — for example, key dates, family or relationship details, or a source for the information — so the same categories of detail are captured every time regardless of who's entering the Note.

Gift in Kind

Gift in kind donations need specific details tracked consistently over time, since they have different requirements than cash donations for receipts.

• Specific Campaign added: In-Kind Gift — locked onto every Action from this Blueprint so in-kind gifts are always flagged the same way.
• Additional fields:
• Gift in Kind Description (text, required)

Tribute Gift

Tribute gifts should be coded the same way every time so your team can reliably report on them and follow up appropriately.

• Specific Campaign added: Tribute Gift — locked in so every tribute is coded and reportable the same way.
• Additional fields:
• Honoree Name
• Tribute Recipient
• Tribute Contact Information

Stock Gifts

Stock gifts have their own set of details to track — most notably a transfer date that may not match the date your organization actually received the sale proceeds.

• Specific Campaign added: Stock Gift — locked in so stock gifts are consistently flagged for reporting.
• Additional fields:
• Stock Name
• Number of Shares
• Stock Transfer Date

Qualified Charitable Distributions (QCDs)

QCDs have specific acknowledgement requirements — they should not be receipted the way a standard cash gift is — so a dedicated Blueprint helps your whole team handle them consistently.

• Specific Campaign added: QCD — locked in so these gifts are always flagged and easy to filter out of receipted-giving reports.
• Additional fields:
• IRA Custodian/Trustee Name
• Distribution Date Received

Annual Fund Gifts

An Annual Fund Blueprint ensures every gift to the fund carries the right coding from the start.

• Specific Campaign(s) added: Annual Fund — locked in so every gift through this Blueprint is credited to the fund. You can also add the GL Codes as well.
• Category required: Pay Method - so every gift has the correct payment type applied.
• Additional fields:
• Check Number (kept consistent across donations)

Volunteer Hours

A Volunteer Hours Blueprint keeps hours logged the same way across your whole team, which matters for accurate reporting on volunteer engagement.

• Specific Campaign added: Volunteer Activity — locked in so all volunteer hours roll up under the same Campaign. You may also want to allow users to select the specific role from a category for campaigns tracking those specifically.
• Additional fields:
• Add as needed

Letters

If your team sends different types of letters one at a time, a Letters Blueprint helps track what was sent and why.

• Category required: Letter Type — so staff select whichever type of letter was sent.
• Additional fields:
• Add as needed

Pro Tips

• Build a Blueprint for any Action type your team enters regularly and consistently — the list above is a starting point, not a limit.
• Keep field labels exact. A Key Value Pair like "Follow-Up By Date" needs to be spelled and capitalized the same way on every Blueprint that uses it, or it won't report together correctly.
• Revisit your Blueprints periodically — as your team's needs change, so should the Campaigns and fields you're prompting for.