How can we help you?

Auto-Contribute (Auto-Configure)

Automatically accept and roll up Key Result updates

Purpose

Auto-Contribute (Auto-Configure) enables automatic acceptance of contributing Key Result updates, eliminating the need for manual approval notifications at the parent level.

Business Case

Without Auto-Contribute:

  •  Users must manually review and accept contribution notifications
  •  Delays occur in reflecting accurate progress
  •  Parent KRs become outdated or inconsistent across dashboards

With Auto-Contribute:

  • ✅ Contributions are automatically accepted
  • ✅ Parent KRs update instantly based on child changes
  • ✅ Reduces manual effort and notification fatigue
  • ✅ Ensures real-time alignment across all views (OP, ED, Grid, Timeline)

Objective

To streamline KPI and OKR updates by:

  • Automatically processing contributing KR changes
  • Applying the correct calculation logic based on contribution type
  • Ensuring parent KRs always reflect the most up-to-date values
  • Removing dependency on manual notification approvals

Overview

Auto-Contribute is configured at:

  • Company Level OR
  • Team Level

Location:
Settings → Key Results Settings → Auto-Contributing Tab

When enabled:

  • System bypasses approval notifications
  • Automatically applies updates from child → parent KR
  • Uses predefined contribution logic (5 types)

How to Configure Auto-Contribute

Step 1: Navigate to Settings

  1. Go to Settings
  2. Select:
    • Company Settings OR
    • Team Settings

Step 2: Open Key Results Settings

  1. Click Key Results Settings
  2. Navigate to the Auto-Contributing tab
    Auto Contribute Settings.png

Step 3: Enable Auto-Contribute

  1. Toggle Auto-Contributing ON
  2. Select applicable contribution types (if configurable)
    Auto Contribute Settings.png

Step 4: Save Configuration

  • Click Save
  • Configuration is now active

    Configure Auto-Contribute at the Sub-Target Level

In addition to enabling Auto-Contribute at the Company or Team level, users can also enable Auto-Contribute for specific individual Key Results directly within the Sub-Targets section of the Key Result card.

This allows teams to selectively apply automatic contribution behavior only where it makes sense operationally, rather than enabling it globally for all Key Results.

How to Enable Auto-Contribute for a Specific Key Result

  • Open the Key Result card
  • Navigate to the Sub-Targets section within the card details
  • Locate the Auto-Contribute checkbox in the upper-right corner
  • Enable the checkbox to allow that specific Key Result to automatically accept contributing updates

Once enabled:

  • ✅ Child updates automatically roll up to the parent KR
  • ✅ Manual approval notifications are bypassed for that KR
  • ✅ Parent progress updates instantly based on contribution logic
    Auto Contribute within Sub-Target.png

How It Works (End-to-End Flow)

Scenario Example:

  1. A Child Key Result contributes to a Parent Key Result
  2. User updates the child value (from 200 → 300)
  3. System evaluates the contribution type
  4. Instead of sending a notification:
    • ✅ System auto-accepts the update
    • ✅ Parent KR is updated instantly

The 5 Contribution Types

Auto-Contribute uses 5 key contribution scenarios to determine how updates are applied:

1. Parent Key Result → Numeric Metric

  • Child contributes numeric value directly
  • Parent updates based on aggregated values

2. Parent Key Result → Percentage Metric

  • Child progress contributes as a percentage
  • Parent reflects weighted percentage completion

3. Mixed Contribution (Numeric + Percentage)

  • Handles hybrid contribution scenarios
  • System converts and aligns values before applying

4. Multiple Contributing Key Results

  • Multiple children contribute to one parent
  • Parent value is calculated using:
    • Weight
    • Progress
    • Target alignment

5. Reverse / Derived Contribution

  • Parent derives value based on calculated child states
  • Often used in:
    • Milestones
    • Deliverables
    • Outcome rollups

Without Auto-Contribute (For Comparison)

When Auto-Contribute is OFF:

  • Updating a child KR triggers a notification to the parent
  • Parent owner must:
    • Review
    • Accept or reject

This introduces manual effort.

Important Behaviors

1. Automatic Acceptance

  • No manual approval required
  • Updates are applied immediately

2. Real-Time Updates

  • Parent KR updates instantly after child change

3. Notification Bypass

  • System skips notification workflow entirely

4. Dependency on Contribution Logic

  • Correct behavior depends on:
    • Metric type
    • Target alignment
    • Contribution configuration

Common Mistakes

IssueCauseSolution
Parent not updatingAuto-Contribute not enabledEnable in settings
Incorrect valuesWrong contribution typeVerify configuration
Unexpected %Mixed metric mismatchAlign metric types
No change reflectedChild not linked properlyValidate hierarchy

Best Practices

  •  Enable Auto-Contribute for high-frequency updates
  •  Use consistent metric types (numeric vs percentage)
  •  Validate contribution setup before enabling
  •  Use for:
    • KPI rollups
    • Milestone tracking
    • Executive dashboards

When to Use Auto-Contribute

Use this feature when:

  • You want real-time updates without approvals
  • You have multiple contributing Key Results
  • You need accurate rollups across dashboards
  • You want to reduce notification noise

Summary

Auto-Contribute (Auto-Configure):

  •  Eliminates manual approval workflows
  •  Automatically updates parent KRs
  •  Ensures real-time, accurate reporting
  •  Applies intelligent contribution logic across 5 key scenarios
Was this article helpful?
0 out of 0 found this helpful
    Download article

Comments

Please sign in to leave a comment.