How to forecast whether you'll hit a goal
Updated 2026-10-24
Whether you'll hit a goal isn't a feeling - it's a line. Take the readings you already have, fit the trend, and carry it to the deadline. If it lands short, you know weeks before the review meeting.
The method
- Collect the readings - each check-in's value and date. At least two; four or more make a steadier line.
- Fit a straight line through them (least squares - what a spreadsheet's trend line or
SLOPE()does). Its slope is your pace: units per day or week. - Carry it forward from the latest reading to the deadline: projected value = latest value + slope × time left.
- Turn it into a percentage of the way from start to target: (projected - start) / (target - start).
A worked example
A newsletter goal: from 20 to 80 paying subscribers by week 10. After four weekly check-ins:
| Check-in | Subscribers |
|---|---|
| Week 0 | 20 |
| Week 1 | 26 |
| Week 2 | 31 |
| Week 3 | 38 |
- The trend through these four points is +5.9 subscribers a week.
- From the latest reading, 38, with 7 weeks left: 38 + 5.9 × 7 ≈ 79.
- That's (79 - 20) / (80 - 20) ≈ 99% of the way - just short of the target.
Progress today is only 30%, which looks alarming in week 3 of 10 - but the forecast says the pace is nearly enough. One or two extra subscribers a week closes the gap. That's a very different conversation from "we're at 30%".
Reading the forecast
- On track - the forecast reaches 100% or more by the date.
- At risk - it lands between 80% and 100%: close, a small change in pace fixes it.
- Off track - under 80%, or the date has passed without reaching the target: the plan needs to change, or the target does.
- Achieved - the target is already reached.
For a goal with several key results, forecast each one and average them. A key result with fewer than two readings has no trend yet - hold it at its current percentage rather than guessing.
When a straight line is wrong
- Too few readings. Two points always make a line; it means little. Check in on a schedule.
- Lumpy numbers. Hires, closed deals and launches arrive in steps. Read the trend over several weeks, not after each jump.
- Curves. Growth that compounds (or slows down as it saturates) bends away from a straight line. The forecast is a warning light, not a promise - re-check it every week.
- Quotas per period. For "40 trials a week", the useful question isn't the trend but the pace inside the period: how many are left this week, and how often the quota was hit.
In GoalNexa
GoalNexa does exactly this on every check-in: each metric's least-squares trend carried from its latest reading to the goal's target date, drawn as a dashed line on the goal's chart, and the goal's health badge - on track from 100%, at risk from 80%, otherwise off track - from the average. Metrics with a quota per period use the pace inside the period instead. Your AI assistant reads the same forecast, so "how are my goals doing?" gets the same answer as the dashboard. See it on OKRs or a template.
More guides
- How to score OKRs - The 0-1 scale, what 0.7 means, and scoring from the numbers instead of from memory.
- KPI vs OKR: what's the difference? - KPIs keep the business healthy, OKRs change it - and how to run both side by side.
- How to run a weekly goal review in 15 minutes - An agenda that starts with what's slipping, and the numbers that make it quick.
Try it with your own goals
GoalNexa tracks goals with numbers, forecasts each one and scores your quarters. Free plan, no card needed.