A practical guide for administrators and Evaluation Managers
The Goals module brings company, team, and personal goals together in one place. It lets you assign ownership, measure progress with different metric types, and use regular check-ups to identify goals that need attention.
Let’s look at how to configure the module and work with goals step by step:
Contents:
- What the Goals module is and where to find it
- Goals module settings
- Creating goals and building a hierarchy
- Metrics and progress calculation
- Check-ups and goal updates
- Viewing and managing goals
- Permissions and visibility
- Moving from the old OKR/KPI module
What the Goals module is and where to find it
Goals replaces the previous OKR/KPI module. The new module uses one unified entity: a Goal. A subgoal is a complete goal with a parent goal assigned to it.
You can find the company-wide overview in the left navigation under Company → Goals. Users can open their own goals under Me → My Goals.
Administrators and users with the Evaluation Manager role can access every goal and the module settings. Managers work with the goals of their teams and reports. Regular users work only with their own goals in My Goals.
Goals module settings
Before creating goals, go to Settings → Goals Settings. You can also open the settings using the link in the goal creation form.
Changes are saved automatically and recorded in the company audit log.
Default check-up settings
A check-up is a recurring request for the goal owner to update progress and goal health. You can choose one of the following default frequencies:
- weekly,
- bi-weekly,
- monthly,
- quarterly.
For each frequency, define the day and time. This value is pre-filled when a new goal is created, but it can be changed for an individual goal.
If you select a day that does not exist in a particular month, the system creates the monthly check-up on the last day of that month.
Default goal visibility
Set the default visibility for newly created goals:
| Goal level | Visibility options | Default setting |
| Company | Admins only / Managers and admins / Whole company | Whole company |
| Team | Managers and admins / Whole team / Whole company | Whole team |
| Personal | Owner and their manager | Cannot be changed |
Please note! Changing the default visibility affects only newly created goals. Existing goals are not updated automatically.
Who can create goals
Creation rights are configured separately for each goal level:
| Goal level | Default permission |
| Company goals | Admins only |
| Team goals | Managers and admins |
| Personal goals | Everyone |
If a user is not allowed to create any goal type, the + New goal button is hidden. A regular user can create personal goals only, even if Everyone is selected in the general settings.
Creating goals and building a hierarchy
Create a new goal under Company → Goals by clicking + New goal.
Complete the following fields:
- Title – required, up to 255 characters.
- Description – explain the purpose of the goal and the expected outcome.
- Level – Company, Team, or Personal. Select a team for a Team goal.
- Visibility – available options depend on the selected level.
- Owner – select one or more owners. A goal must always have at least one owner.
- Observer – optionally add users who should follow the goal.
- Priority – Low, Normal, High, Urgent, or Unassigned.
- Start date and Due date – the due date is required; the start date must be earlier than the due date.
- Metrics – select how progress will be measured.
- Check-up – enable recurring updates for a goal with its own metric.
- Attachments – optionally add a file.
Once all required fields are complete, click Save goal.
Building a goal hierarchy
Goals can be linked in a structure such as:
Company goal → team goal → personal goal
When creating a child goal, select its parent in Parent goal/subgoal. The system pre-fills the level, visibility, and team from the parent. You can adjust these values before saving.
When the child goal is created, its due date cannot be later than the due date of its direct parent.
A goal can have several levels of descendants. A subgoal can therefore also be the parent of another goal.
Important! Changing the level, visibility, or team of a parent later does not automatically update its descendants. After editing a parent, check the settings of its child goals as well.
Metrics and progress calculation
When creating a goal, use Metrics to select how progress should be calculated.
Subgoals
Goal progress is calculated automatically as a weighted average of its child goals. Use this option when completing the main goal directly depends on several supporting outcomes.
Assign a weight to each child goal. Weights express relative importance and do not need to add up to 100%. A child goal with zero or no weight does not affect the result.
Numerical
Use a numerical metric to track a specific value, such as revenue, customer count, NPS, or employee turnover. Enter the starting value, target value, current value, and an optional unit.
The metric works in both directions. You can track growth from 50 to 100 as well as a decrease from 10% to 5%. The starting and target values cannot be equal.
Boolean
A Boolean metric uses Done / Not Done. Progress is either 0% or 100%. It is suitable for a one-off outcome such as “Launch the new website.”
Checklist
Progress is calculated from the proportion of completed checklist items. This metric is useful for goals made up of several concrete steps.
Important! Every goal can have child goals regardless of its selected metric. However, if you choose Numerical, Boolean, or Checklist, child goals do not affect the completion percentage. Progress is calculated only from the goal’s own metric.
When you change the metric type, the system warns you that the calculation method will change and the current progress may be reset. Existing child goals remain unchanged.
Check-ups and goal updates
Check-ups are used to update a metric and goal health regularly. They are available for goals using Numerical, Boolean, or Checklist. If the main goal is measured using Subgoals, configure check-ups on its individual child goals.
At the scheduled time, the owner receives a task under My Tasks → Goals check-ups.
The owner can:
- click Update goal to update the metric and goal health,
- select Snooze 1 day to postpone the check-up by one day,
- skip the current check-up.
A check-up can be snoozed repeatedly, but never beyond the goal’s due date. Skipping it leaves the most recent known status unchanged.
Updating goal health
During a check-up, the owner updates the metric and selects one required health status:
- On track – progress is going according to plan,
- At risk – there is a risk the goal will not be achieved,
- Off track – the goal is not progressing according to plan,
- Blocked – progress cannot continue.
When Blocked is selected, the owner must describe the blocker. They can also optionally select a person who may be able to help.
The parent goal’s health is derived from the worst health status among its child goals. If only some child goals are blocked, the parent is shown as Partially Blocked.
If a goal has several owners, the update is shared. Once the first owner submits the check-up, the remaining owners’ check-up tasks are marked as completed.
A goal remains active after its due date and check-ups continue. You can extend the due date, mark the goal as completed, or delete it.
Viewing and managing goals
In List view, search by title and filter by level, priority, owner, observer, due date, or status. Goals can be grouped by level, priority, status, owner, or due date.
Bulk actions
After selecting multiple rows, you can update the following values in bulk:
- level,
- owner,
- due date,
- status,
- position in the hierarchy.
Selected goals can also be cloned or deleted. Before deleting, always check whether the selection contains a parent goal with descendants.
Export
The current overview can be exported to CSV or XLSX. The export respects the active filters and grouping.
Permissions and visibility
Access to goals is determined by the user role, the organisational structure, and goal visibility.
| Role | Access and permissions |
| Admin | Can view and manage all goals and module settings. |
| Evaluation Manager | Has the same permissions as an administrator within Goals. |
| Manager | Can see all company goals, goals belonging to their teams, and goals belonging to reports in the organisational structure. |
| Regular user | Works only under Me → My Goals and sees goals they own, created, or observe. |
The owner, creator, and observer can access a goal regardless of its general visibility. The owner’s manager has the same editing rights as the owner; this also applies recursively higher in the management hierarchy.
Distinguish between these three roles on a goal:
- Owner – the person responsible for achieving the goal,
- Creator – the person who created the goal,
- Observer – a person who follows the goal and can access it.
These people do not have to be the same.
Moving from the old OKR/KPI module
To migrate to the new Goals module, simply go to OKR/KPI module and migrate your data from there to the new module.
During migration, titles, descriptions, due dates, owners, attachments, comments, and available numerical values are transferred automatically. Existing Tasks or Key Results become child goals.
Numerical results are converted to the Numerical metric. Status-based results are converted to the Boolean metric.
After migration, we recommend checking:
- Start dates – if unavailable, the original goal creation date is used.
- Hierarchy – link company, team, and personal goals; these relationships did not exist in the old module.
- Team goals – create them where needed because the previous data model did not support them.
- Visibility – migration applies the current default setting.
- Observers – add them manually.
- Check-ups – enable them and set their frequency. Check-up and sentiment history is not transferred.
- Child goal weights – they are distributed evenly after migration.
- Priorities – the priority of existing Key Results is not transferred.
- Metric type – a goal with existing tasks is assigned Subgoals; a goal without tasks is assigned Boolean.
- Blocked items – replace the generic migration reason with an accurate explanation.
If an existing goal did not have a due date, the system sets it to one month after the original creation date. A child goal without a due date inherits the parent’s due date. If a child goal had a later due date than its parent, migration shortens it to the parent’s due date.
Do you have more questions? Contact our customer support for more information!
0 comments
Please sign in to leave a comment.