How do values, percentages, and dates work in goals?
Check the goal’s metric, accepted format, direction of improvement, decimal precision, and cycle date range before correcting a value or date.
Follow this troubleshooting flow
Confirm the goal, affected user or team, cycle, and process where the goal is used.
Identify whether the metric is a number, percentage, or another configured format.
Check whether the field expects a numeric value only or displays a percentage format.
Confirm the allowed decimal precision.
Determine whether improvement means increasing or decreasing the metric.
Verify that the start and end dates fall within the allowed cycle or process window.
Save the authorised correction and confirm how the goal is displayed in the user's record.
Does the target always need to be higher than the minimum?
No. The correct relationship depends on the metric. For a metric where more is better, the target may be higher than the starting or minimum value. For a metric where less is better, such as reducing incidents or response time, the desired target can be lower.
Use a clear title and description so the intended direction is understandable to the user and manager.
How should percentages and decimals be entered?
Use the format accepted by the active goal form. Confirm whether the interface expects only the numeric value or accepts a percentage representation, and check the allowed decimal precision. Do not assume that formatting from a spreadsheet can be pasted unchanged.
Why is a goal date rejected?
The date falls outside the evaluation cycle or Touchpoint period.
The goal belongs to a current process but uses dates from a previous or future period.
A programme or population has a specific configured date window.
The end date is earlier than the start date or conflicts with another active rule.
What varies between organisations and cycles?
The accepted formats, decimal precision, date limits, and validation rules may differ. Explain the rule configured for the current process and avoid publishing fixed dates or client-specific examples as universal behaviour.
When should I contact Support?
Contact Support when the value format, direction, precision, and dates comply with the confirmed configuration but the goal cannot be saved or displays incorrectly. Include the cycle, goal type, metric, entered values, expected format, start and end dates, and validation message.
Continue troubleshooting
Goals and Individual Development Plans in Evaluation Cycles: create or update goals in the correct cycle or period.
How should an administrator manage individual and team goals in Touchpoints and evaluations?: diagnose goal assignment, sync, and editability.
Evaluation - TouchPoints: understand how goal status and configuration affect Touchpoint progress.