OKRnest is a collaborative OKR and KPI management tool that helps organisations set, track, and align goals using the Objectives and Key Results framework. It gives every team a shared space to define what success looks like and measure progress toward it.

How OKRnest is structured

OKRnest organises work in a clear hierarchy:

Organisation > Teams > Cycles > Objectives > Key Results

Each level builds on the one above it, so everyone in the organisation can see how individual work connects to broader goals. Alongside this tree, KPIs track the numbers that matter regardless of cycle, check-ins capture how a team is doing on a given date, and actions record follow-up tasks.

Organisations

An organisation is your top-level workspace in OKRnest. It contains all your teams, users, and settings. Each user belongs to one or more organisations and has a role that determines their permissions:

• Owner: Full control over the organisation, including subscription and ownership transfer
• Admin: Can manage teams, users, features, and OKR settings
• User: Can create and update OKRs, check-ins, and actions within their own teams

Admins can also rename the words OKR and Action for the whole organisation under Admin Settings > General > Terminology. Help articles always use the standard names.

Teams

Teams are groups of people who work on shared OKRs. A team has members, a cycle length, and a check-in cadence that determines how often key results should be updated.

Teams can be organised hierarchically. A team can have a parent team, which makes it easy to model departments, divisions, or any reporting structure. This hierarchy is visible on the Teams page and is used for OKR alignment.

Each team has its own workspace with sections for OKRs, KPIs, Check-ins, Actions, Members, Activity, OKR Cycles, and Settings.

Cycles

A cycle is a time-bound period during which a team pursues its OKRs. Standard cycle lengths range from monthly to yearly, and admins can define custom cycle types for the organisation.

Each cycle goes through three statuses:

• Draft: OKRs are being prepared and are not yet open for updates or check-ins
• Active: The cycle is live and team members can update progress
• Archived: The cycle has ended and is kept read-only for reference

Objectives

An objective is a qualitative, aspirational goal that describes what a team wants to achieve during a cycle (e.g. "Improve customer onboarding experience"). Objectives should be clear and motivating, and the measurable part comes from key results.

Objectives can be linked across teams using Contributes to, which makes cross-team alignment visible to everyone.

Key results

A key result is a measurable outcome that indicates whether an objective is being achieved. Each objective typically has two to five key results.

Every key result has:

• A type: Number, Percent, or Currency
• From and To values: The starting point and the target
• An owner: The person responsible for driving progress

Progress is recorded as updates with a value, an optional comment, and a traffic light (Not started, On track, Behind, or Critical). OKRnest computes the traffic light from the key result's pace automatically; people can override it when the Key result status feature is enabled.

Key results can also support a key result from a parent team, creating a cascading alignment from top-level strategy down to individual contributions, and can track a shared KPI instead of their own private metric.

KPIs

A KPI is a standalone metric that lives outside any single cycle, for example monthly recurring revenue or support response time. KPIs belong to a team or to the whole organisation, have an owner, and can be updated manually or by integrations through the API. Several key results across teams and cycles can track the same KPI. The KPIs page in the sidebar lists the organisation's catalogue, and each team has its own KPIs section.

Check-ins and actions

A check-in is a snapshot of a team's OKRs for a chosen date, with notes, progress updates, and linked actions. Teams typically run check-ins at the cadence set on the team.

Actions (an optional feature) are follow-up tasks with an owner, deadline, and status. They can be linked to key results and check-ins, and appear on team boards and on your personal Your actions page.

Alignment

OKRnest makes alignment visible at two levels:

• Objective alignment: An objective can "contribute to" objectives from other teams, showing how team goals connect
• Key result alignment: A key result can "support" a parent team's key result, showing how individual metrics roll up

This alignment is visualised on the Alignment map tab of the organisation-wide OKRs page, giving leadership and teams a clear picture of how work connects across the organisation.

Optional features

Admins choose which optional modules are switched on under Admin Settings > Features. Depending on your plan these include Align OKRs, OKR weights, Milestones, Key result status, Check-in email reports, Shareable views, Actions, the AI Assistant, and the OKRnest API.