Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Action Plan entry
How-to guide

How to apply an Action Plan to a record

Once the Action Plan Template exists and the feature is enabled for the right users, applying a plan is a few clicks from the parent record. Most of the design effort sits in the template, not the Action Plan itself.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated May 19, 2026

Once the Action Plan Template exists and the feature is enabled for the right users, applying a plan is a few clicks from the parent record. Most of the design effort sits in the template, not the Action Plan itself.

  1. Open the parent record

    Navigate to the Account, Opportunity, Case, or other supported record where the plan should run.

  2. Click New Action Plan

    Use the New Action Plan quick action or related list button on the parent record. The button appears only if the user has the right permission set assigned.

  3. Pick the Action Plan Template

    Select the template that matches the engagement, for example Client Onboarding or Renewal Review. The template determines which Tasks will be created and their relative due dates.

  4. Set the start date and owners

    Choose a start date. Salesforce computes every Task's due date by adding the template offset to this date. Optionally reassign individual Tasks to people other than the defaults defined in the template.

  5. Save and monitor

    Save the plan. Salesforce creates the Tasks and links them to the new Action Plan record. Status updates on Tasks roll up to plan-level dashboards.

Target Recordrequired

The parent record (Account, Opportunity, Case, etc.) the plan is attached to.

Action Plan Templaterequired

The template that defines the sequence of Tasks.

Start Daterequired

The anchor date from which every Task offset is calculated.

Ownerrequired

The user responsible for the plan as a whole, separate from individual Task owners.

Namerequired

A human-readable plan name; usually defaults from the template but can be overridden.

Gotchas
  • Completing every Task does not automatically mark the Action Plan as Completed. Build a Flow that watches Task status if the plan-level status should roll up.
  • Reassigning the plan owner does not reassign the individual Task owners. Decide up front whether ownership cascades or stays where the template put it.
  • Action Plans require feature-specific permission sets. Users who do not have the right permission set assigned will not see the New Action Plan button on the parent record.
  • Each cloud (FSC, Health Cloud, Industries, Sales Cloud) has its own Action Plan flavour. Confirm which one is licensed before promising a particular feature behaviour to stakeholders.

See the full Action Plan entry

Action Plan includes the definition, worked example, deep dive, related terms, and a quiz.