What to do first
Set one objective for the cycle running now, give it two or three key results, and put the tasks that will move them underneath. An objective with no key results has nothing to move it, and its progress will read zero for the whole cycle.
The switch at the top of the dashboard moves between OKRs and KPIs. New objective or New KPI at the top right starts one.
An objective is created whole. Its key results and its tasks save with it in one go, or none of it saves.
Objectives
An objective is what you are trying to achieve. It has an owner, a scope, a due date and a progress ring. The due date decides which cycle it belongs to; an objective created without a date is due when the running cycle ends.
The dashboard names the cycle running now ("Goals · Q4 2026"), and its banner counts how many objectives are on track, at risk and done. The list underneath can be filtered by scope (All, Company, Department, Team, Individual, and Branch where branch objectives exist) and by date (Any date, This week, This month, Custom), and drawn as Card, List or Alignment.
Scope says whose objective it is: company, department, team, branch or individual. Branch appears only in workspaces that have branches.
Every card says which department the objective belongs to — a company objective reads Company-wide — and each department keeps one colour, so a grid of thirty can be read at a glance. Key results and tasks carry the department of whoever is doing the work.
When you create an objective, step two — its key results — keeps the objective you wrote at the top, with Edit to go back to it.
Progress is computed from the key results under it rather than typed. Ticking a task moves its key result, and that moves the objective's ring.
Key results
The measurable part. A key result has a starting point, a target and a current value, and updating it is what moves the objective.
Key results are where a check in happens. Log where the number is now, say why, and the history of that number becomes the thing a review can read.
Tasks
Work under a key result, assigned to a person with a due date. They appear in that person's My work and in the Meetings and tasks panel, and ticking one anywhere ticks it everywhere.
A task can be broken into sub-tasks, one level deep, each with its own owner, date and state under the same key result. The task's panel and page show how many are done; a sub-task shows which task it is part of. See Projects for how they behave, which is the same here.
Account targets
A target on a client account is a key result. When a manager sets a target on an account in Clients › Accounts, they can choose the objective it counts towards. If they choose none, Rople puts it under that period's Account targets objective ("Account targets · Q4 2026"), a company objective due on the period's last day, and creates it the first time anybody sets a target for the period.
Each account is one key result under it. Rople keeps the key result's figure up to date from the account's engagements, so you do not log it by hand. Removing the target removes its key result; the objective stays. Setting, changing and removing a target is for managers (level 3) and above. See Relationships.
KPIs
The other half of the module, for things that are measured continuously rather than achieved once. Satisfaction, on time delivery, response time, revenue.
When you create a KPI you say whether higher or lower is better, how often it is measured, and how it is judged:
- A rate, judged on the latest reading. Response time this week is this week's response time.
- Cumulative, judged on the total of every reading. A year's revenue is not September's revenue, and reading the latest entry would answer a question nobody asked.
Who can set which KPI
Anybody can set an individual KPI for themselves. Wider KPIs follow the same rule as objectives:
- Team KPIs: team leads (level 2) and above, for a team they are in or lead.
- Department KPIs: managers (level 3) and above, for their own department or one they manage.
- Company KPIs: executives (level 4) and the workspace admin.
Executives and the workspace admin can set a team or department KPI for any team or department. The create sheet only offers the scopes, teams and departments you can use.
Giving a KPI to somebody
A KPI you create is yours unless you choose an Owner. Managers (level 3) and above, and the workspace admin, can give a KPI to anybody in the workspace. Team leads (level 2) can give one to the people on a team they are in or lead. The Owner field lists only the people you can choose, and it does not appear if there is nobody. The new owner is told the KPI is theirs, it shows under Mine on their board, and they log its readings.
Rople records who set each KPI up. A KPI can be edited, logged against, archived or deleted by its owner, by whoever set it up, by the manager of its department, by the lead of its team, and by an executive or the workspace admin. The KPI panel shows those buttons only to them. To move a KPI to somebody else, open it, press Edit and change the Owner. An owner can change their own KPI's target but cannot pass it to a colleague; their manager or team lead does that. KPIs created before November 2026 do not record who set them up.
Each KPI reads Healthy, Below target or No data. The banner counts how many are on target, below and waiting for data, and the department rollup ranks departments by how close their KPIs are to target. Filter to Company, My department, My team or Mine.
Where each KPI stood on the last day of every cycle, and how that moved from one cycle to the next, is kept in Intelligence › Cycles, on the KPIs & targets tab. See Cycles.
Cycles
Where: rople.app/w/goals?screen=cycles
Objectives grouped by the workspace's cycles: the quarters (or months, halves or years) set in Organisation › Structure › Cycles & reviews, including a financial year that does not start in January. Each cycle shows whether it is Current, Completed or Planned, how many objectives are due in it and their average progress. It opens on the cycle running now. Before cycles are switched on, this screen uses calendar quarters.
The dashboard has no button to this screen yet; open it at the address above.
A finished cycle links to its whole record in Intelligence › Cycles: leads, clients, delivery and money for the same period, not only the objectives. Closing a cycle there can move its unfinished objectives into the next one; they are still counted as unfinished in the cycle they were due in.
Templates
Objectives your workspace writes often, kept so nobody types them again. Useful for the ones every department sets each cycle. Templates open at rople.app/w/goals?screen=templates; like Cycles, the dashboard has no button to them yet.
Alignment
The map showing which objectives draw from which. Choose Alignment in the dashboard's view switch to see it.
Every edge on it is a link somebody drew and the other side accepted. Proposed links are drawn dashed, so the person being waited on can see that they are being waited on. Nothing is inferred from scope: an individual objective does not appear under a department objective merely because both exist.
How it connects
- Tasks appear in My work and in Meetings and tasks.
- Assignment, blocking and reminders raise notices in your Inbox.
- Objective progress feeds Manager Cockpit, Reviews and People Analytics.
- A closed out project releases contributions into the KPIs it promised to move.
- Account targets set in Clients › Accounts are key results here.
- Goals due, achieved and KPI standings per cycle appear in Intelligence › Cycles.
Common questions
Why is my objective at zero? Because its key results have not moved. Progress is computed, not set, so the way to move it is to update a key result or tick a task.
Who can see my objective? Scope decides. A company objective is visible to the company, an individual one to you, your manager and the people entitled to read performance data. A department, team or branch objective is visible to the people in that unit and to whoever manages it, even if they are filed somewhere else. Anybody given a key result or an open task under an objective can open it.
A colleague left and I took over their department. Why can I see its goals now? Because you manage it. When somebody leaves, the departments, teams and branches they ran pass to whoever takes over their work, and managing a unit gives you its objectives: to read from level 2, and to edit a department's from level 3, the same as if you were filed in it.
Can I change a target mid cycle? Yes, and the change is part of the record. A target quietly rewritten at the end of a cycle is the one thing that makes a goal system worthless.
Why is my new objective due at the end of the cycle? Because you gave it no date. An objective without one is due when the running cycle ends.
A goal is blocked. What happens? Marking it blocked tells the owner and their manager, in the inbox, because it is a problem rather than an update.