Territory Feedback Standard Process

Territory Feedback is used by the following user types with the following responsibilities:

  • Align User – Creates, plans, and adjusts the new modeling project before end users submit feedback. Makes final adjustments and publishes models after feedback.
  • CRM End User – Provides feedback on upcoming changes to their territory. Depending on configured Approval Rules, submitted challenges may be automatically approved or rejected.
  • CRM Manager – Reviews feedback made by end users that were not automatically approved or rejected

Pre-Feedback Model Planning

Align users can create modeling projects to stage any changes to an upcoming cycle without impacting production data, then publish those changes for feedback from end users and managers:

  1. Create a new modeling project and use existing Align functionality to plan the future cycle.
  2. Import the appropriate branch of the territory hierarchy and its related objects into the model.
  3. Clone the previous Multichannel Cycle into the model. This enables admins to use the existing Multichannel Cycle and Targeting Rule as a starting point when preparing for the new cycle.
  4. Apply appropriate adjustments to the model's Multichannel Cycle or targeting rule.

    If targeting is not included in the feedback, the Multichannel Cycle is not required.

  5. Configure the Approval Process. This step is only required if the project needs an Approval Process.

    The Align user can also import the Approval Process when importing the territory hierarchy if the process is configured for the production field force.

  6. Run a Preview and Commit on the model. This generates account assignments and targets based on Assignment and Targeting Rules.

    When initiating the Preview, the Align user can opt to clone targeting feedback from the previous cycle to enable the end user to avoid having to re-enter the same feedback for the new cycle.

  7. Change the lifecycle state of the project to Feedback Review. This enables end users to view future territory assignments and targets from within Veeva CRM and provide feedback.

End User Review and Feedback

Once a cycle is in the Feedback Review lifecycle state, end users can access the new model from the Future Territory Alignments tab to perform the following process:

  1. Review changes made to their territory, including any accounts and targets added or removed.
  2. Create any appropriate challenges to changes made to the territory. Approval Rules can automatically accept or reject an end user's feedback based on defined criteria.
  3. Submit feedback for manager review.

    This step is only applicable if enabled in the Approval Process.

Manager Review

Managers can review all submitted feedback from end users that were not automatically approved or rejected by Approval Rules, enabling them to provide oversight on the end users reporting to them:

  1. Approve or reject each challenge made by the end user.
  2. Complete the feedback process by moving the territory to a lifecycle state of Territory Feedback Complete.

    If Automated Feedback Handling is enabled, approved challenges are immediately processed and applied to the model.

Post-Feedback Processing

When the feedback period is over, the Align user finishes the feedback process using the following process:

  1. Move any incomplete model territories to a lifecycle state of Territory Feedback Complete.

    This can be done to the root territory to set the lifecycle state to all child territories.

  2. Run a Preview and Commit of the model. This automatically performs the following processes:

    • Updates goals to reflect approved feedback
    • Recalculates interaction values against MCCPs
    • Re-assesses any accounts that changed during the feedback window against Assignment and Targeting Rules to ensure they still meet the rule criteria

    If Targeting Rules are not used, navigate to the model and select Recalculate Territory Data from the more actions menu.

  3. Use the Capacity Planning feature to make final adjustments to each MCCP's goals. This step is optional.
  4. Update the lifecycle state of the model to Approved. This updates the Status of the project to Inactive and prevents further Previews from being performed, though manual changes are still possible.
  5. Publish the model to move the model's data into production.
  6. Run a Preview and Commit on the production Field Force. If any accounts have changed during the feedback period, they are re-assessed against Assignment and Targeting Rules to ensure they still meet the rule criteria.
  7. Freeze the Targeting Rule to prevent the rules engine from making further MCCP changes.
  8. Push to CRM to make the future MCCPs visible to end users prior to the start of the cycle.