Getting Started with Engagement Plans in Salesforce NPSP

Engagement Plans in Salesforce Nonprofit Success Pack (NPSP) help nonprofits turn repeatable follow-up processes into structured task checklists. Instead of relying on memory, spreadsheets, or one-off reminders, teams can use Engagement Plans to make sure the right actions happen at the right time and in the right order.

They are especially useful for processes like cultivating a major donor and tracking the people who influence those gifts, welcoming a new volunteer, managing a grant application, following up after an event, or coordinating stewardship after a significant gift. When the same process happens again and again, an Engagement Plan gives your team a reusable structure instead of starting from scratch each time.

When you start an Engagement Plan, Salesforce automatically creates the tasks from that plan, assigns them to the right people, and sets due dates based on the template. This helps your team stay organized, consistent, and focused on relationship-building rather than manual task tracking.

Engagement Plans are available only in Salesforce orgs with NPSP installed, and they work best when the process is human-driven. They are not meant to replace Flow or every type of automation. Instead, they give nonprofits a simple way to manage repeatable work that depends on people completing tasks.

Templates vs. Plans

An Engagement Plan Template defines the reusable process. It includes the list of tasks, their timing, their dependencies, and who they should be assigned to. Think of the template as the master checklist you create once and reuse whenever that process is needed.

An Engagement Plan is the active version of that template applied to a specific Salesforce record, such as a Contact, Account, Opportunity, Campaign, Case, or Recurring Donation. Salesforce’s documentation on creating and managing Engagement Plans explains this same relationship: the template defines the task process, and the plan applies it to a specific record.

Example: You could create a Major Donor Stewardship template. When you apply that template to Jane’s Contact record, Salesforce generates Jane’s follow-up tasks with the due dates and assignments already defined.

This distinction matters for admins. Updating a template does not automatically rewrite every plan already in progress. The template controls future plans. Existing Engagement Plans keep the task structure they had when they were created.

Key Engagement Plan Features and Customization

When you create an Engagement Plan Template in NPSP, you’ll see the following options and settings:

• Engagement Plan Template Name – The title for your template.
• Description – A short explanation of when or how to use this plan.
• Default Assignee – If a task doesn’t have a named assignee, this setting determines who gets it (Salesforce requires every task to have an owner). You can choose:
  
  • User Creating Engagement Plan – The person starting the plan
  • Owner of the Record – The owner of the record that the plan is linked to
• Skip Weekends – Ensures task due dates never fall on a Saturday or Sunday.
• Automatically Update Child Task Due Date – If enabled, dependent tasks’ due dates recalculate based on when the parent task is completed.
• Manage Engagement Plan Tasks – Where you define each task in the plan:
  
  • Subject – Task name
  • Assigned To – Specific user, role, queue, or triggering record owner
  • Type & Priority – Classification and urgency
  • Days After – Days from plan start or dependent task completion
  • Dependent Task – Links a follow-up step to the one above
  • Email/Reminder Options – Choose if Salesforce sends an email or creates a reminder

Customizing for Your Nonprofit

Engagement Plans are most useful when they match the way your nonprofit actually works.

You can add custom fields to the Engagement Plan object to track details such as Plan Type, Priority, Program Area, or Stewardship Level. These fields can make reporting easier and help teams filter active plans by process or department.

You can also use Engagement Plans with custom objects, not only the standard NPSP records. To do this, create a lookup field from Engagement Plan to the custom object, enable Allow Activities on that object, and add the Engagement Plans related list to the page layout.

This is helpful for nonprofits that manage custom program records, applications, memberships, services, or internal review processes in Salesforce.

Engagement Plans can also work with Salesforce Flow. For example, Flow can automatically create an Engagement Plan when a major gift is closed, when a new volunteer record is approved, or when a grant opportunity reaches a certain stage. Salesforce’s Flow Builder documentation is useful when you need automation around the human checklist that Engagement Plans create.

This is often the best setup: Engagement Plans handle the human checklist, while Flow handles the automatic system actions around it.

Admin Setup Checklist

Before using Engagement Plans, make sure:

• The Engagement Plan Templates tab is visible to the needed profiles.
• Field-level security for Engagement Plan, Engagement Plan Task, and Engagement Plan Template is set (Create, Read, Edit, Delete as needed).
• Profiles have access to the EP_ManageEPTemplate Visualforce page (required for editing templates).
• Lookup from Engagement Plan to custom object is added (if using on a custom object).
• Allow Activities is enabled on that custom object.
• The Engagement Plans related list is added to the object’s page layout.

Limitations to Know

Engagement Plans are practical, but they do have limits.

Limited task assignment options - In the Assigned To field, you can choose a specific User, Partner User, Customer Portal User, or leave the task blank so the Default Assignee applies. You cannot natively assign tasks to owners of other related records, such as an Opportunity Owner, Case Owner, or Program Manager.

For example, if the plan is linked to a Contact but you want tasks to go to the owner of a related Opportunity, Engagement Plans cannot do that on their own. You would need extra automation, usually Salesforce Flow.

Tasks only - Engagement Plans create Tasks. They do not send emails, update fields, post to Chatter, create records, or run complex logic by themselves. They can set reminders, but system actions require Flow or another automation tool.

Dependent task due dates recalculate only on completion - If Automatically Update Child Task Due Date is enabled, child tasks shift when the parent task is completed, not when the parent due date is simply edited. If users delay earlier tasks without marking them complete, later tasks may look overdue.

Deleting a plan leaves its tasks - Removing an Engagement Plan record does not delete the related tasks. The tasks remain in Salesforce and may lose their dependency links. Admins should plan cleanup carefully if old plans need to be removed.

Due dates are based on the plan start date - Days After is based on the plan start date or the completion of a dependent task. There is no native way to calculate due dates from another date field, such as Event Date or Grant Deadline, without Flow.

Template changes do not update existing plans - Updating a template affects only new plans created after the change. Plans already in progress keep their existing task setup.

Template deployment is manual - Engagement Plan Templates are stored as data, not metadata. That means you cannot move them between orgs with Change Sets the same way you would move metadata. To migrate templates, you need to recreate them or use a data migration tool.

Engagement Plans vs. Flow-Only Task Creation

‍

How to Choose Between Them

Engagement Plans are ideal when you want a ready-made checklist that’s easy to apply, manage, and track in one place. Because tasks from a plan are grouped under an Engagement Plan record, you can quickly see all steps in progress for that specific process.

Flows give you full flexibility - you can assign tasks to any related record’s owner, use complex logic for timing, and run multiple actions (like sending emails or updating fields) in the same automation. However, tasks from Flows don’t have a built-in “container,” so reviewing them as one process requires reports or custom solutions.

In many cases, using both together works best: Engagement Plans for structured, human-driven processes, and Flows for dynamic automation and system actions.

Conclusion

‍
Engagement Plans are one of the most practical tools in Salesforce NPSP for repeatable nonprofit workflows. They help teams follow the same high-quality process every time, whether they are stewarding a donor, onboarding a volunteer, managing a grant, or following up after an event.

The key is to design templates that are clear, simple, and aligned with how your team actually works. Too many tasks make plans hard to use. Too little detail makes them easy to ignore. The best Engagement Plans give users just enough structure to keep important follow-up from slipping through the cracks.

For most nonprofits, Engagement Plans work best when paired with Flow. Let Engagement Plans organize the human work, and let Flow handle the automation that NPSP Engagement Plans cannot do on their own. For teams still learning the concept, Salesforce Trailhead’s module on managing Engagement Plans is a useful beginner-friendly reference.

If your nonprofit needs help setting up Engagement Plans, cleaning up templates, or deciding when to use Flow instead, our team can help you design a process that is consistent, manageable, and easy for staff to follow.