Configuring Goal Plan and Performance Form Templates: Design Decisions and Route Maps

Explanation

Once the business purpose of Performance and Goals is clear, the implementation work centers on three configuration artifacts: the rating scale, the goal plan template, and the performance form template with its associated route map. Getting these right the first time matters because performance form templates are difficult to change once a review cycle has launched and employees have started completing forms; structural changes mid-cycle can corrupt in-progress data or require administrator intervention to reset forms. Rating scales are typically defined once and reused across goal plans and performance forms within a customer instance, though multiple scales can coexist if different employee populations or regions require different scales (for example, a 5-point scale for corporate staff and a competency-only qualitative scale for a union population). A key design decision is whether goal ratings and overall performance ratings use the same scale; many customers want overall performance rating to be a calculated or manually adjusted summary that is not simply the average of goal ratings, which requires careful configuration of section weighting rules within the performance form template rather than the goal plan. The goal plan template defines the field set available on individual goals (name, description, metric, target, weight, category, due date), whether cascading (creating child goals aligned to a parent goal held by someone else) and alignment (linking to a higher-level goal without creating a hierarchical copy) are permitted, and which categories or goal types are available. A common intermediate-level design question is how much structure to impose: too many required fields slows goal-setting adoption, while too few fields makes goals impossible to report on meaningfully later. The performance form template is more complex. It typically defines sections (for example, Goals section referencing the linked goal plan, Competencies section, Development section, Overall Summary section), the weighting of each section toward an overall rating, and which fields are visible or editable to which role at which step. The route map attached to the template defines the sequence of steps, such as Employee Self-Assessment, Manager Assessment, Manager's Manager approval, and HR Finalization, and specifies for each step who can access the form (typically resolved through the customer's Role-Based Permission groups combined with the reporting relationship, such as 'manager of subject user'). Misconfigured route maps are one of the most common sources of production incidents: a step assigned to the wrong role, or a step that does not correctly resolve 'next in line manager' for employees with unusual reporting structures, will block the entire review cycle for affected populations. Because performance form templates are versioned per review cycle (a new form template instance, or a route map change, is usually needed each cycle rather than editing a live one), consultants must plan configuration changes well before cycle launch and test with a representative sample of the population, including edge cases like employees without a manager, employees who transferred mid-cycle, or contingent workers if they are in scope. Regarding cloud-specific behavior: because Performance and Goals is a SuccessFactors module rather than an on-premise ECC component, there is no equivalent of a transport request moving configuration between clients in the traditional SAP sense; template and route map changes are typically built and validated directly in a test company instance and then replicated or rebuilt in production, so change control and documentation discipline substitute for a formal transport mechanism. Consultants coming from an on-premise background should not assume a transport-based promotion path exists here.

Code example

<!-- Illustrative fragment showing a performance form template referencing     a goal plan section and a simplified route map step sequence. --><performance-form-template id="AnnualReview2024">  <section id="goals" source="goal-plan" ref="AnnualGoals2024" weight="40"/>  <section id="competencies" weight="40"/>  <section id="overallSummary" weight="20" calculated="true"/>  <rating-scale-ref id="5PointOverallScale"/>  <route-map id="StandardAnnualRouteMap">    <step order="1" role="subject" action="self-assessment"/>    <step order="2" role="manager" action="manager-assessment"/>    <step order="3" role="managers-manager" action="approval"/>    <step order="4" role="hr" action="finalize"/>  </route-map></performance-form-template>

Real project scenario

During UAT for a global rollout, the project team discovers that employees whose manager position is temporarily vacant (due to an open requisition) cannot progress their performance forms past the manager-assessment step, because the route map resolves the next step strictly by direct manager and there is no fallback role. The consultant has to propose a workaround, such as temporarily assigning an HR proxy manager in the org data or building a fallback approval path, and must explain to the customer why this scenario needs a documented exception process rather than a template fix applied mid-cycle.

Common mistakes

• Editing a performance form template structure after forms have already been launched to employees, risking data inconsistency. • Assuming a single rating scale must be reused everywhere, when business requirements actually call for different scales by population. • Designing route maps without testing edge cases such as vacant manager positions, matrix reporting, or recently transferred employees. • Overloading the goal plan template with mandatory fields that slow adoption and generate low-quality goal data. • Confusing section weighting configuration with rating scale configuration; they solve different problems and are set in different places. • Not validating role-based permission group assignments against the route map's expected roles before cycle launch.

Best practices

• Freeze performance form template structure before mass form creation and treat any mid-cycle change as an exception requiring administrator-level correction. • Build and test route maps against realistic edge-case employees, not just standard manager-employee pairs. • Keep section weighting logic and rating scale definitions documented together so compensation teams downstream understand how overall ratings are derived. • Separate goal plan template design discussions from performance form template design discussions, even though they are related, to avoid scope confusion in workshops. • Maintain a clear versioning convention for templates and route maps per review cycle to support audit and rollback conversations.

Interview angle

Expect scenario-based questions such as 'a manager cannot see their team's performance forms, how do you troubleshoot this' or 'how would you handle a mid-cycle reorganization affecting active performance forms.' Strong candidates describe a structured troubleshooting sequence: verify route map step and role resolution, verify RBP group assignment, verify reporting relationship in the org data, and only then consider template redesign, while emphasizing that live-cycle structural template changes are high risk.