Planned Giving Bequest or Beneficiary Intent Form

This form records a donor’s stated intent to include an organization in a future gift, such as a bequest, retirement account beneficiary designation, or life-income arrangement. It is designed to document legacy society interest and permission to follow up, not to transfer assets. The nonbinding acknowledgment helps set expectations clearly. It also gives your team a consistent record of the donor’s preferred contact and recognition choices.

No. The form should clearly state that the donor’s declaration is nonbinding and does not replace legal documents, beneficiary forms, or estate planning instruments. That distinction matters because the actual transfer or designation must be completed through the appropriate financial or legal process. The template is for intent capture and internal tracking. It should not be used as the sole source of legal authority.

A donor, planned giving officer, development staff member, or advisor can help complete it, depending on your workflow. The organization should designate who reviews submissions, confirms recognition preferences, and logs follow-up tasks. If the donor includes sensitive personal or financial details, limit access to staff who need it. Keep an audit trail of who reviewed and updated the record.

Use it whenever a donor expresses a planned giving intention that you want to document consistently. It is especially useful during legacy society enrollment, donor stewardship conversations, estate planning discussions, and beneficiary designation follow-up. You can also reuse it when a donor updates a prior intention. If the donor’s plans change, the form should be revised rather than treated as permanent.

The most important fields are the gift type options, recognition language, estimated value range, and follow-up preferences. You may also want to tailor the bequest, beneficiary, and life-income sections so only the relevant branch appears through conditional logic. If your organization has a legacy society, include the exact society name and any recognition consent language. Keep the form aligned with the minimum-necessary principle so you do not collect more PII than needed.

The template includes consent and contact-permission fields so donors can choose whether they want recognition or follow-up communication. That supports data minimization and makes it easier to explain how their information will be used. If you collect mailing address, phone, or email, include a clear disclosure about what happens after submission. Avoid asking for unnecessary financial account details or estate documents unless your process truly requires them.

Yes. The form works well when mapped to CRM fields for donor name, gift type, legacy society status, and follow-up tasks. You can route submissions to planned giving staff, create a donor record, and trigger a stewardship workflow. If your system supports conditional logic, use it to show only the relevant gift detail section. That keeps the form shorter and easier to complete.

A common mistake is treating the form like a legally binding beneficiary designation, which it is not. Another is collecting too much detail, such as unnecessary account numbers or estate documents, before there is a real need. Teams also sometimes forget to include a clear statement about what happens after submission. Finally, if recognition consent is missing, you may not be able to publicly acknowledge the donor’s intent.

An ad hoc email can be useful, but it is easy to lose, misread, or fail to route to the right staff member. This template standardizes the fields you need, including nonbinding acknowledgment, consent, and follow-up preferences. It also creates a cleaner audit trail and makes it easier to compare donor intentions over time. That consistency is especially helpful when multiple staff members handle stewardship.