Activate, Monitor, and Govern Activity Plans
Learning Objectives
After completing this unit, you’ll be able to:
- Describe the stages of the collaborative activity plan review workflow.
- Differentiate between the roles of the three primary activity plan batch jobs.
- Configure Lightning components to display goals on home pages and account records.
- Explain how tracking scheduled versus completed activities helps managers coach field reps.
- Identify how review thresholds protect the integrity of a strategic plan.
Move from Structure to Execution
In the previous unit, you built the plan, its territory, account goals, weighted measures, and product links. Those records define the strategy, but records alone don't execute it. Before a plan goes live, the field reviews its targets against real clinic access. After it goes live, the system turns logged visits into progress.
A launch strategy meets field reality before it ever runs. Accounts become temporarily inaccessible, and targets change before a rep starts work. Activity plans handle that through a review process, a set of background jobs that move the plan along, and live charts that track pacing once the plan is active. Cumulus's Immunexis targets meet clinic reality first, then update on their own as reps log visits.
In this unit, you move the plan through review, run the batch jobs that activate it, and calculate progress. You also learn how to surface the charts users work from and govern field changes with review thresholds.
Run the Collaborative Review Lifecycle
The lifecycle moves through five stages, from a draft the administrator prepares to a locked, active plan. To run it, administrators use Lighting App Builder to add the Plan Cycle (lsc4ce:PlanCycle) Lightning component to a dedicated review workspace or app page.
Each of these five stages gives a role its input while keeping one version of the plan moving forward.
-
In Progress: The admin builds the baseline plan, links target accounts, and maps territories. The plan stays hidden from the field.
-
Employee Review: Reps check their assigned accounts and propose goals for each activity type. When a rep submits, the plan moves to their manager.
-
Manager Review: The regional manager reviews each rep's proposed goals and either accepts or adjusts them. When the manager submits the reviewed goals, the plan returns to the administrator.
-
Admin Review: The administrator reviews the field's changes and enters the final targets. When the admin submits the finalized plan, the plan is ready to activate.
-
Active: The plan is locked with final targets, and the system measures live field activity against them.
Batch jobs advance the plan from one stage to the next.
Orchestrate Workflows with Batch Jobs
A large organization can have hundreds of reps adjusting targets across dozens of territories at the same time. Three batch jobs, run from the Admin Console, handle that volume without constant manual work.
Validate Activity Plans controls activation by date. It checks each plan's time period. When the start date arrives and the plan sits in admin review, the job sets it to Active. When the window closes, the same job deactivates the plan so no one changes it further.
Update Activity Plan Status keeps the review cycle moving. When a rep or manager misses a deadline, the job advances plans that are past their due dates. A plan stuck in employee review past its assignee due date, or in manager review past its reviewer due date, moves to the next role, and the job clears unsubmitted measures along the way.
Calculate Provider Activity Goal Measures is the calculation engine. After a plan is active, this job reads newly logged activity against your measure types and updates the progress counts users see on their dashboards. These counts don't update in real time. They refresh each time the job runs, so a nightly schedule keeps dashboards current without slowing the system during working hours.
These three batch jobs drive the lifecycle, but they aren't alone. Other jobs run on their own schedule, including Calculate Working Days, which you learned about in the previous unit, a shared-plan version of the calculation job, and a cleanup job for inactive goals. For the full set and recommended run frequencies, see Batch Jobs for Activity Plans.
With the jobs scheduled, the system activates the plan and calculates progress metrics automatically. Next, you put the results where users see them.
Surface Targets in the Field Workflow
An active, calculating plan changes daily decisions only when its numbers appear where users work. Administrators add the Activity Plan by Product component to the app home page and account record pages with Lightning App Builder.
When you place the component, set its Plan Cycle Type to match the active plan's type, Weighted Territory Goals for the Cumulus launch. If the property and the plan type don't match, the chart shows nothing, even when the calculation jobs run correctly. When they match, the component shows the progress for each goal.
Here's the component in Lightning App Builder, with Plan Cycle Type set to Weighted Territory Goals.
With the property matched, the chart appears wherever you placed it, such as a home page for a territory overview or an account record for a single clinic.
Track Status and Coach on Trajectory
Reps and managers now work from the same numbers. Reps use the home page chart for a territory overview and account-level charts to plan individual clinic visits. On the Accounts tab, dedicated list views for activity plans and Weighted activity plans show their target accounts, the last visit date, and overall attainment. When an account reaches its target, the system checks the Target box on the list view.
Managers read the same list views and charts to judge execution. Because activity plans track completed activity and scheduled activity separately, a manager can tell raw volume apart from real pacing. Consider two Cumulus reps working on the same WhatsApp follow-up goal.
- Rep A has completed three follow-ups and has one more scheduled. They're on track to hit the goal of four.
- Rep B has also completed three follow-ups but has nothing scheduled.
A standard activity report treats the two the same, because their completed counts match. The activity plan chart separates completed work from the scheduled pipeline, so the manager sees that Rep B has no path to finish the cycle. Because the goal measure ties to the product, the manager coaches Rep B to schedule the last launch interaction before the calculation window closes.
Enforce Governance with Review Thresholds
Field flexibility matters, but unchecked target changes can pull a launch off strategy. The three review thresholds you set on the primary plan act as automatic checks during review.
-
Activity Change Review Threshold Percentage: When a rep proposes a large cut to one account's goal, say dropping a specialist's target from nine interactions to five, the system measures the change. If it clears the threshold, the system flags the record and routes it to the manager for approval.
-
Total Account Change Review Threshold Percentage: When a rep adds or removes accounts beyond the threshold, the system holds the change instead of processing it automatically.
-
Total Activity Change Review Threshold Percentage: When a rep shifts numbers among accounts and the combined goals across the plan move past the threshold, the system stops the submission for administrative review.
Together, these thresholds give the field a real voice in reflecting clinic access, while keeping material changes under administrative control.
Wrap Up
Cumulus set out to protect its Immunexis launch from the gap between strategy and field execution. The company's administrator configured weighted, product-specific targets. Reps worked from dedicated dashboards, and managers coached them on pacing before the cycle closed. The launch ran on one shared plan, connecting headquarters to the field.
Across this badge, you followed activity plans from a strategic alignment challenge to a live, governed system. You mapped the data model, set the rules for what counts, built weighted targets, and put progress directly in front of the people who act on it. With the review workflow, batch jobs, and thresholds in place, you can configure, automate, and govern activity plans of your own. To complete your journey, check the Resources section for implementation checklists and setup documentation.