How check-in discipline reports are generated in Profit.co?
Category: OKRs
Profit.co generates check-in discipline reports to improve performance and productivity.
Why this feature?
- By using this feature you can view the check-in discipline report.
- The report is used to ensure that individuals or teams are regularly checking in on their progress toward their goals, and taking the necessary steps to stay on track.
- The total no. of check-ins is calculated and distinguished as follows:
- On-time
- Missed
- Late
- Future
- Legacy
- Not Applicable
- Pending
Scenario: Consider a key result with check-in frequency weekly on Friday.
On-time Check-in
In this scenario, we are considering a check-in frequency that is weekly on Friday, let's say Mar 10, If the user check-ins anytime between Mar 4 and Mar 10, it is considered as On-time check-in.
Missed Check-in
Considering the same scenario of On-time check-in, If the user misses the Mar 10 check-in and has not recorded the progress in the applicable period (i.e.) from Mar 4 - Mar 16, the Mar 10 will be considered as Missed check-in any time after Mar 17 which is the next check-in date.
Late Check-in
Consider a scenario where the user needs to check-in on Mar 10, If the user fails to check-in on Mar 10 and if he does the check-in between the period Mar 11 - 16, it is considered as Late check-in.
Future Check-in
Consider you checked in on Mar 10. The following check-in cycle then starts on Mar 11 for the check-in date Mar 17. The Mar 24 and Mar 31 check-in cannot be progressed until Mar 17's check-in is done. Therefore, in this case, March 24 and March 31 are considered Future check-in dates.
Legacy Check-in
The Legacy check-in helps you take a look at the past history of check-ins happening based on the below criteria.
Note: You can view the Legacy check-in history of a Key Result
- When the Key Result type is changed.
- When the KPI is changed.
- When the From value is changed.
- When the Target Period is changed.
There will be no impact on the progress when the To value and target period Due Dates are changed.
Not applicable Check-in
Consider a key result created on Mar 20. When check-in is made the progress falls on Mar 17. Hence the Mar 3 and Mar 10 check-ins will be considered as Not Applicable check-ins.
Note: If the Check-in is performed for the not applicable past dates (Mar 3 - Mar 10), it will be considered as On-time check-in.
Pending Check-in
Consider a scenario where the user needs to check-in on Mar 10, but the user misses the check-in and does not perform any check-in until Mar 16, Then the key results will be considered as it is in the Pending check-in state.
Note: If the Check-in is performed between (Mar 11- Mar 16), it will be considered as late check-in.
Related Answer Post
To learn more about the use of the Cockpit Dashboard, click here.
Related Questions
-
How do I follow the OKRs of my subordinates?
Profit.co allows you to set apart and follow the OKRs of your subordinates. Why this feature? This feature allows you ...Read more
-
How can I generate a report of employees and teams who haven't set any OKRs?
Profit.co allows Superusers to generate reports of users, teams, and departments who haven't set any OKRs. Why ...Read more
-
How do I create a Key Result using Control KPI?
Profit.co allows you to create a key result using Control KPI and measure the progress. Why this feature? Control KPIs ...Read more
-
How does the KR Clone feature work in Profit.co?
Profit.co offers the option to clone Key Results (KRs), enabling you to efficiently reuse existing KRs, saving time and ...Read more