Check-ins
Purpose: A check-in is how progress gets recorded against a Key Result. Instead of leaving an objective untouched until the end of the cycle, the owner updates the key result's current value as work advances, so the objective's OKR Score reflects where things actually stand. Check-ins live on the objective record itself — there is no separate "Check-ins" page in the sidebar.
Who can use it: Access follows the Goal Type permissions configured in Performance Settings. PMSuite has three goal types — Individual, Department and Company — and each one has its own separate View and Manage permission. Recording a check-in requires the Manage permission for that goal's type; users with only View can read progress but not update it.
Prerequisites
- The Performance module must be enabled for your company in Settings → Module Settings. If Performance is switched off, the Objective and OKR Score pages are not available.
- An Objective must exist, with at least one Key Result attached to it. Progress is recorded on key results, never on the objective directly.
- Your role must hold the Manage permission for the objective's goal type (Individual, Department or Company) in Settings → Performance Settings.
How to Access
Navigation: Sidebar → Performance → Objective (/account/objectives) → open the objective → update the key result you own.
Related destinations in the same module:
| Page | Path |
|---|---|
| Objective | /account/objectives |
| OKR Score | /account/okr-scoring |
| 1:1 Meetings | /account/meetings |
How to Use
Step 1: Open the objective
Go to Performance → Objective and open the objective that contains the key result you need to update.
Step 2: Update the key result's progress
Locate your key result and record its new progress value. The unit and shape of that value come from the metric assigned to the key result — metrics are defined company-wide under Settings → Performance Settings → Key Results Metrics, so what you enter (for example a number or a percentage) depends on which metric your administrator configured for that key result.
Step 3: Save
Save the update. The key result's stored progress changes, and the objective's score on the OKR Score page is derived from the updated key result values.
Configuring check-in behaviour
Everything that governs check-ins is set in Settings → Performance Settings, which has three tabs:
| Tab | What it controls |
|---|---|
| Key Results Metrics | The metric types available when a key result is created — these determine what a check-in value looks like. |
| Notification Settings | Whether Performance-related notifications are sent. |
| 1:1 Meeting Settings | Defaults for 1:1 Meetings, where progress is usually discussed. |
Goal Types (Individual / Department / Company) and their View and Manage permissions are also configured on this settings screen, and they decide who may record a check-in on which objectives.
Effect on Other Features
- Key Results: A check-in changes the stored progress of the Key Result it is recorded against.
- OKR Scoring: The OKR Score page (
/account/okr-scoring) derives objective scores from key result values, so scores move only as check-ins are recorded. - 1:1 Meetings: Current key result progress is the natural input to 1:1 Meetings (
/account/meetings) and their Meeting Agendas. - Slack: If your company has connected Slack under Settings → Notification Settings → Slack (an incoming-webhook, one-way PMSuite → Slack integration), PMSuite notifications can be delivered to a Slack channel. Slack does not send anything back into PMSuite.
Limitations
- There is no standalone Check-ins page. The Performance module's sidebar exposes Objective, OKR Score and 1:1 Meetings only. Workaround: bookmark
/account/objectivesand filter to your own objectives; that list is the working queue for progress updates. - No cross-objective "everything I owe an update on" view is exposed in the sidebar. Workaround: use the Objective list filters to narrow to your goal type and owner, and pair it with a recurring 1:1 agenda item so nothing goes stale unnoticed.
- Check-in permissions are tied to goal type, not to individual objectives. Granting someone Manage on Department goals grants it for every department objective they can see. Workaround: keep sensitive goals under a goal type whose Manage permission is held by fewer roles, and review the View/Manage matrix in Performance Settings when roles change.
- Metric choices are company-wide. Individual users cannot invent a new metric while checking in. Workaround: ask an administrator to add the metric under Performance Settings → Key Results Metrics before the cycle starts.
Troubleshooting
| Symptom | What to check |
|---|---|
| Performance / Objective is missing from the sidebar | The Performance module is disabled. An administrator can enable it in Settings → Module Settings. |
| You can see an objective but cannot update its key result | Your role has View but not Manage for that goal type. Have an administrator review Goal Type permissions in Settings → Performance Settings. |
| The value you want to enter does not fit the field | The key result is using a different metric. Metrics are defined in Performance Settings → Key Results Metrics; the key result may need to be recreated with the right metric. |
| The OKR Score has not moved after an update | Scores are derived from key result values — confirm the update was saved on the key result, then re-check /account/okr-scoring. |
| No Performance notifications are arriving | Check the Notification Settings tab of Performance Settings. For Slack delivery, also confirm the webhook is enabled and saved under Settings → Notification Settings → Slack, and use Send Test Notification there. |