Assignments & cycles
Assign a framework and open a period to measure.
A framework on its own does not measure anyone. To put it to work you assign it to people and open a cycle — the period you are evaluating. Both are managed under Cycles in the sidebar.
Assignments: who gets measured
An assignment attaches a framework to one of three kinds of target:
- A team — everyone on the team is measured with this framework.
- A title — everyone with a given job title (for example all Senior Engineers).
- An individual — a single person.
An assignment can also carry presets, such as per-title target quotas and per-person bonus targets, so you do not re-enter them every cycle.
Cycles: the period being measured
A cycle is usually one month. It has a start and end date and, once started, a frozen copy of the framework so results stay reproducible. A cycle can optionally be linked to a Jira sprint (see Measurements & Jira).
The cycle lifecycle
Every cycle moves through four states, in order:
| State | What it means |
|---|---|
| Draft | Being set up. Not yet collecting data. |
| Active | Open for measurement — numbers can be entered or synced. |
| Locked | Data entry is frozen. Results are calculated and approvals happen here. |
| Closed | Final. The cycle is done and its results are settled. |
Automating the monthly rhythm
KManagement can take repetitive steps off your plate:
- Auto-rollover — new cycles can be created automatically each month on a schedule.
- Auto-lock— a cycle can move from active to locked automatically a set number of days after it ends, at a time in your company’s local zone.
Closing is gated
A cycle cannot be closed while any result approval is still pending or disputed. See Approvals & comments.