Profit.co's Control KPI supports 4 progress calculation methods. The Distance from Target, as of the Check-in Date method calculates progress at each individual check-in point based on how close the actual value is to the defined target - making the most recent check-in the single determinant of final progress, not a cumulative sum or average across periods.
Table of Contents
What is the Distance from Target Calculation?
The Distance from Target, as of the Check-in Date method measures progress as a percentage of the goal achieved at each individual check-in, calculated using the actual value's proximity to the defined target. Every check-in - whether it meets the threshold or not - produces a progress score based on the formula applied at that point in time.
Unlike cumulative methods, this approach does not sum or average check-in values across the cycle. Instead, the final check-in of the period becomes the definitive progress score for the Key Result, regardless of how earlier check-ins performed.
Why This Calculation Method Matters
Some KPIs need to reflect real-time accuracy at each check-in rather than a running total. A team tracking Cost Per Click, API response time, or weekly blog output benefits from knowing exactly how close each period's result was to the target - including weeks where performance exceeded it significantly.
This method evaluates each check-in on its own merit. The full picture across the cycle is visible in the Bowler Chart, while the final check-in anchors the official KR progress score.
When to Use This Method
Choose this method when:
- You want to track how far each check-in is from the target, not just whether it passed a threshold
- Real-time per-period accuracy matters more than cumulative totals
- Every check-in's exact variance - positive or negative - carries meaningful information
- The KPI improves gradually and is not binary (pass/fail)
Best for: Evaluating actual versus target performance at each check-in point, where the final period's result determines the Key Result's reported progress.

Calculation Logic and Formula
The formula applied by Profit.co depends on the value type selected. Both formulas require a Baseline value to be configured on the KR.
| Value Type | Formula |
|---|---|
| At Most | (Baseline − Actual) / (Baseline − Target) × 100 |
| At Least | (Actual − Baseline) / (Target − Baseline) × 100 |
The formulas are not simply reversed interpretations of the same equation - the numerator and denominator both flip between value types. This reflects the opposite direction of success: At Least measures growth away from the baseline toward the target, while At Most measures reduction from the baseline down toward the target.
Note
The formula displayed in your Bowler Chart will differ between At Least and At Most KRs. This is expected platform behavior - Profit.co automatically applies the correct formula based on your configured value type.
How It Works by Value Type
Value Type Overview
| Value Type | Progress Updates When | Typical Use Cases |
|---|---|---|
| At Most | Actual is at or below the upper limit | Cost control, error rates, response time |
| At Least | Actual meets or exceeds the lower limit | Blog posts, sales calls, revenue targets |
Note
Distance from Target supports At Least and At Most only. It does not support the In Between value type. For range-based Control KPIs with both a lower and upper limit, use the Successful Check-ins calculation method instead.
Scenario 1 - At Most: Maintain lead response time at most 4 hours

Calculation: The following values are used to calculate the progress percentage for this check-in.
| Field | Value |
|---|---|
| Baseline | 24 |
| Target | 4 |
| Actual | 2 |
| Progress % | (24 − 2) / (24 − 4) × 100 = 110% |

The following shows how progress percentage changes week over week based on actual check-in values.
| Week | Actual Response Time | Progress % | Reading |
|---|---|---|---|
| Week 1 | 6 hours | 90% | Above target — slightly high |
| Week 2 | 4 hours | 100% | Exactly on target |
| Week 3 | 2 hours | 110% | Below target — good |
| Week 4 | 8 hours | 80% | Above target — too high |
| Week 5 | 1 hour | 115% | Well below — excellent |
| Week 6 | 4 hours | 100% | Exactly on target |
| Week 7 | 10 hours | 70% | Significantly above target |
| Week 8 | 3 hours | 105% | Below target — good |
| Week 9 | 2 hours | 110% | Below target — good |
| Week 10 | 5 hours | 95% | Slightly above target |
| Week 11 | 4 hours | 100% | Exactly on target |
| Week 12 | 6 hours | 90% | Above target — slightly high |
| Week 13 ✅ | 2 hours | 110% | Final progress = 110% |
How to read this: When Actual < Target, progress exceeds 100% - cost is well-controlled. When Actual > Target, progress drops below 100% - cost is over threshold.
Scenario 2 - At Least: Publish at Least 5 Blog Posts Per Week

Calculation: The following values are used to calculate the progress percentage for this check-in.
| Field | Value |
|---|---|
| Baseline | 10 |
| Target | 50 |
| Actual | 60 |
| Progress % | (60 − 10) / (50 − 10) × 100 = 125% |

The following shows how progress percentage changes week over week based on actual check-in values.
| Week | Actual Qualified Leads | Progress % | Reading |
|---|---|---|---|
| Week 1 | 30 | 50% | Below target — needs improvement |
| Week 2 | 45 | 87.5% | Close to target — almost there |
| Week 3 | 50 | 100% | Exactly on target |
| Week 4 | 60 | 125% | Above target — excellent |
| Week 5 | 35 | 62.5% | Below target — needs improvement |
| Week 6 | 50 | 100% | Exactly on target |
| Week 7 | 20 | 25% | Well below target |
| Week 8 | 55 | 112.5% | Above target — great |
| Week 9 | 70 | 150% | Well above target — excellent |
| Week 10 | 45 | 87.5% | Close to target — almost there |
| Week 11 | 40 | 75% | Below target — needs improvement |
| Week 12 | 50 | 100% | Exactly on target |
| Week 13 ✅ | 60 | 125% | Final progress = 125% |
How to read this: When Actual > Target, progress exceeds 100%. When Actual < Target, progress drops below 100%.
Viewing Calculations
On the List View
Click on the Progress % of any Key Result directly from the List View to see the formula and calculated values applied for that specific check-in.

On the Bowler Chart
The Bowler Chart view displays the Distance from Target calculation transparently across every check-in period. In the Bowler Chart, you will see:
- The formula applied for each check-in based on the selected value type
- The calculated progress percentage for every week or check-in period
- A clear breakdown of Actual vs. Target values side by side
- The final progress highlighted at the last check-in date
Best Practices for Distance from Target Calculation
- Use this method when the final period's result is the most meaningful signal of KR health - for example, when the last week of a quarter reflects whether a sustained effort paid off.
- Communicate to KR owners that mid-cycle progress scores do not accumulate - a strong Week 3 does not protect against a weak Week 13 becoming the final progress score.
- Always configure the Baseline value before the cycle begins - both formulas depend on it, and changing it mid-cycle will alter all subsequent check-in calculations.
- Pair this method with the Bowler Chart view during reviews to provide full cycle context alongside the final reported progress figure.
- For At Most KRs, a progress score above 100% means the actual value was well below the target threshold - train stakeholders to read this as a positive outcome, not an error.
Related Questions
- Click here to learn more about how the Successful Check-ins calculation works in Control KPI
- Click here to learn more about how the Sum of All Check-ins calculation works in Control KPI
- Click here to learn more about what a Control KPI is
Frequently Asked Questions
The Distance from Target method is designed to reflect the KR's state at a specific point in time - the last check-in. This makes it suitable for KPIs where the current value at cycle end is more meaningful than a smoothed average across all periods (e.g., "What is our CPC right now?" vs. "What was our average CPC across the quarter?").
Yes, for both value types. For At Most KRs, actual values well below the target produce progress above 100%. For At Least KRs, actual values exceeding the target also push progress above 100%. This is expected behavior and reflects that the KR is performing better than the defined goal.
The document covers At Most and At Least value types for this calculation. Both use the same formula structure: (Actual − Baseline) / (Target − Baseline) × 100. The In Between value type, which defines both a lower and upper limit, operates differently and is covered under the Successful Check-ins calculation method documentation.
Execute your strategy with confidence
Connect OKRs, tasks, and teams in one place with Profit.co