Measure missing
The goal has no clear baseline, target, unit, milestone, or evidence expectation.
Return it for clarification before tracking begins.Turn each employee goal into a measurable record with a baseline, target, milestone, current result, confidence, evidence, support request, and check-in history.
A percent-complete field cannot explain whether the result is real, why progress changed, or what the manager should do next.
Start with Jodoo’s Free plan for up to five users. No credit card required.
Reviewed by Jodoo’s product and content team · September 6, 2026. Explore sample goals, reviews, and follow-up in the app, then adapt the process to your team.
Each field answers a different question and makes the next check-in more useful.
Goal title, type, period, employee, manager, team, business objective, and why it matters.
Is this the right commitment for this person and period?
Unit, baseline, target, current result, weight, milestone, start date, and target date.
What has changed, and how will success be recognized?
Confidence, update date, evidence, blocker, dependency, support needed, and employee note.
Can the employee continue, or does a manager need to act?
Decision, changed milestone, support owner, agreed action, due date, next check-in, and closeout.
Keep, change, support, reprioritize, carry forward, or close?
Use status and confidence together to route the right response.
The goal has no clear baseline, target, unit, milestone, or evidence expectation.
Return it for clarification before tracking begins.The progress record is older than the agreed cadence or lacks a current result.
Prompt the employee or revise the cadence.The result may still look on track, but the employee sees risk in capacity, scope, or timing.
Discuss the risk before the milestone is missed.Progress needs a decision, resource, handoff, or work outside the employee’s control.
Assign a support owner and due date.The target or milestone is met and source evidence is available.
Verify the result, capture learning, and choose the next goal.Every signal should open the underlying goal, update, blocker, or support action.
Goals with an agreed measure, target, employee, manager, and period.
Fix incomplete expectations before judging progress.
Days since the last meaningful progress update by goal and team.
Ask for current context or adjust an unrealistic cadence.
On-track, at-risk, blocked, and needs-update goals with reasons.
Resolve dependencies and support needs, not just the status label.
Upcoming, met, late, revised, and missed milestones against the goal plan.
Confirm the next commitment or replan transparently.
Open and overdue manager or partner actions created from check-ins.
Hold the support owner accountable before rating the employee.
Clear measures help, but good judgment still depends on context.
It should keep the goal definition, owner, period, baseline, target, current result, milestones, confidence, evidence, blockers, updates, support decisions, and closeout together.
Rarely. Use a clear unit and current result where possible, then capture confidence and context separately. Percent complete can hide rework, blocked dependencies, or unclear acceptance.
Preserve the original target or milestone, record what changed and why, record who approved the change, and update future expectations without rewriting history.
Yes. Relate employee goals to team or company objectives when that relationship is meaningful, but avoid forcing every development or operational goal into a cascade.
Not by default. Use the dashboard to find missing expectations, stale updates, blockers, support demand, and follow-up. Rankings without role and context can mislead.
Yes. The Jodoo example supports concise progress, evidence, blocker, and support updates from mobile while managers retain decision and follow-up views.
Verify the employee update, manager support decision, evidence, milestone change, and portfolio drill-down before scaling the process.