Performance management goal cascading workflow incomplete - parent goals not propagating

HCM Workday HCM
, , , , , , , ,
1

We’re having issues with goal cascading in our performance management workflow. When executives set strategic goals at the top level, they’re supposed to cascade down to director and manager levels automatically. However, the cascading workflow is failing to propagate parent goals to direct reports.

I’ve checked the goal cascading workflow triggers and they appear configured correctly. The organizational hierarchy configuration looks accurate with proper reporting relationships established. The direct report relationship mapping seems intact when I review individual worker profiles.

<cascade-rule>
  <parent-goal type="strategic"/>
  <cascade-to>direct_reports</cascade-to>
  <propagation-depth>3</propagation-depth>
</cascade-rule>

Only about 30% of the expected child goals are being created when parent goals are published. The remaining 70% of managers and individual contributors never receive the cascaded goals, breaking our goal alignment process across the organization.

This is critical because our annual performance review cycle starts next month and employees need properly aligned goals. Has anyone debugged goal cascading workflow issues where parent goals don’t propagate through the org hierarchy?

2

Your propagation depth is set to 3, which means goals will only cascade three levels down from the originating executive. If your org structure is deeper than that, lower-level employees won’t receive the cascaded goals. Count the actual levels in your hierarchy - you might need to increase the propagation depth to 4 or 5 to reach everyone.

3

Good point about the cascade enabled flag. I checked a sample of parent goals and most have it enabled, but a few don’t. That might explain some of the missing cascades but not the full 70% failure rate. I’ll also verify the propagation depth against our actual org structure.

4

I’ve seen this when the organizational hierarchy has gaps or inactive relationships. Even if the org chart looks correct visually, if a manager-employee relationship isn’t marked as ‘Primary’ or is set to future-dated, the cascading logic skips over those connections. Run the Supervisory Organization Hierarchy report and look for any breaks in the chain between your executives and the employees who aren’t receiving goals.

5

Don’t forget about goal plan eligibility rules. Even if cascading is configured correctly, employees might not be eligible for the goal plan that the cascaded goals belong to. Check your goal plan setup and verify that all employees in the cascade path are included in the plan’s eligibility criteria. If someone is excluded from the goal plan, they won’t receive cascaded goals even if they’re in the reporting hierarchy.

6

I’ve implemented goal cascading for multiple large organizations and the 70% failure rate you’re experiencing points to a combination of configuration issues. Let me walk through the complete diagnostic and resolution process:

Goal Cascading Workflow Triggers:

Your cascade rule structure is correct, but there are several trigger conditions that must all be met for propagation to work:

<cascade-rule>
  <parent-goal type="strategic"/>
  <cascade-enabled>true</cascade-enabled>
  <cascade-to>direct_reports</cascade-to>
  <propagation-depth>3</propagation-depth>
  <trigger-on-publish>true</trigger-on-publish>
  <require-active-goal-plan>true</require-active-goal-plan>
</cascade-rule>

Key additions:

  • cascade-enabled must be true at the rule level AND on individual goals
  • trigger-on-publish ensures cascading happens when parent goals are published, not just saved as draft
  • require-active-goal-plan means target employees must have an active goal plan

Organizational Hierarchy Configuration:

The 30% success rate suggests your org hierarchy has significant gaps. Run these diagnostic checks:

  1. Export the Supervisory Organization Hierarchy report
  2. Filter for your executive’s organization
  3. Look for these issues:
    • Inactive manager relationships (status != Active)
    • Future-dated relationships (effective date > today)
    • Missing ‘Primary Position’ designation
    • Gaps where managers don’t have the supervisory org relationship defined

// Pseudocode - Hierarchy validation logic:
1. Start with executive who created parent goal
2. Query all workers in their supervisory org (level 1)
3. For each level 1 worker:
   - Check if they have subordinates (level 2)
   - Verify relationship is Active and Primary
   - Confirm effective dates include current period
4. Repeat for propagation-depth levels
5. Count total eligible workers vs actual cascaded goals
// Report discrepancies for manual review

Common hierarchy issues that block cascading:

  • Matrix reporting structures where cascade logic gets confused about the “primary” path
  • Shared services employees who report to multiple managers
  • Dotted-line relationships that aren’t configured as cascade-eligible

Direct Report Relationship Mapping:

Direct report relationships must be explicitly defined for cascading to work. It’s not enough for someone to appear on an org chart - the system needs a formal Manager-Employee relationship:

  1. Verify each manager has the ‘Manager’ role assigned in their security groups
  2. Check that employees have their manager specified in the ‘Supervisory Organization’ field
  3. Ensure the management relationship is marked as ‘Primary’ (not secondary or dotted-line)
  4. Confirm effective dates span the goal period

Run this diagnostic report:

  • Create custom report: Workers with Manager Assignments
  • Include fields: Worker, Manager, Relationship Type, Effective Date, Primary Flag
  • Filter for your affected organizations
  • Identify workers with missing or invalid manager relationships

Additional Configuration Checks:

  1. Goal Plan Eligibility:

    • Verify all employees in the cascade path are eligible for the goal plan
    • Check Goal Plan > Eligibility Rules
    • Common issue: eligibility rules exclude certain job families or locations

  2. Goal Category Alignment:

    • Cascaded goals must match allowed categories at each level
    • If parent goal is ‘Strategic’ but manager-level plan only allows ‘Operational’ goals, cascade fails
    • Review goal plan configuration for each organizational level

  3. Cascade Timing:

    • Goals must be in ‘Published’ status to cascade (not Draft)
    • Check if executives are publishing goals or just saving them
    • Verify workflow doesn’t require additional approvals before cascade triggers

Resolution Steps:

  1. Fix organizational hierarchy gaps:

    • Use EIB to bulk-update missing manager relationships
    • Ensure all relationships are Active and Primary
    • Set effective dates to cover the performance period

  2. Update cascade configuration:

    • Increase propagation-depth if needed (verify actual org depth first)
    • Enable cascade flag on all strategic parent goals
    • Ensure trigger-on-publish is enabled

  3. Validate goal plan eligibility:

    • Expand eligibility rules to include all employees in cascade path
    • Or create separate goal plans for different org levels with appropriate eligibility

  4. Re-trigger cascading for existing goals:

    • For goals already published, you may need to manually trigger cascade
    • Edit parent goal > Save > Re-publish to force cascade execution
    • Monitor cascade job execution in Business Process > View Process History

For Your Current Situation:

With annual reviews starting next month and 70% of cascaded goals missing:

  1. Prioritize fixing the organizational hierarchy - this is likely your biggest issue
  2. Run the diagnostic reports to identify all affected employees
  3. Create a temporary manual process: export parent goals and distribute to managers for manual entry
  4. Fix the root causes in parallel so future cascades work automatically
  5. Once fixed, re-cascade from the top to populate all missing goals

Set up ongoing monitoring: Create a scheduled report that compares expected cascade count (based on org hierarchy) versus actual cascaded goals created. Run this weekly during performance cycles to catch issues early.

7

Check if the parent goals are actually marked as ‘Cascade Enabled’ in the goal settings. Even with cascade rules configured, individual goals need the cascade flag set to true or they won’t propagate regardless of the workflow configuration.