Check-Ins Meeting Statuses

Prior to this enhancement, administrators were only able to report on created Check-Ins or Check-Ins that have content.

With this enhancement, managers and employees can mark meetings complete or cancelled. This allows administrators to report on the use of Check-Ins in their organization.

This enhancement is available in Stage on February 16th.

On the meetings and topics page, users can select "Mark as Completed" or "Cancel this meeting". All meetings are open by default.

The following applies to meeting statuses:

  • Only check-in meetings that have content can be marked as complete.
  • Participants can edit the notes of a check-in meeting when a meeting is completed or cancelled.
  • Users can view status details on the Modification History page.

New Reporting Field

The following reporting field is now available:

Field Name Field Description Field Type


Entity Section (UI Group)
Meeting Status Meeting Status indicates if a Check-In meeting is open (not completed), has been completed or cancelled. String Performance Check-Ins Check-Ins

New Email Tag

A new email tag [Meeting.Status] is added to the email digest. If configured, a user can see the status of their meeting, their recent meetings, and upcoming and missed meetings.

How Does this Enhancement Benefit My Organization?

  • Administrators can track the completion rate of check-ins in their organization to confirm conversations between an employee and manager.
  • Managers and employees are accountable for regular check-in meetings.

Starter Guide

Click here to download the Check-Ins Starter Guide.


This functionality is automatically enabled for all organizations using the Check-Ins module.


The following existing permissions apply to this functionality:

Check-Ins - Create

Grants ability for the user to create and update Check-Ins. The permission constraints determine with whom the user can create Check-In discussions. This permission can be constrained by OU, User's OU, User Self and Subordinates, User, User's Subordinates, User's Direct Reports, User's Self, User's Manager, User's Superiors, and Employee Relationship. Users with constraints in the “Check-Ins - Create” permission cannot create a new Check-In with anyone who is not part of the constraints, but can still view and update any Check-In in which they are a participant.

This is an end user permission.

Note: Permission constraint to Employee Relationship grants permission to dotted line or secondary managers to create Check-Ins with users that report to them in the matrix structure. A constraint "Restricted to Employee Relationship: Detail Supervisor" means that the Detail Supervisor can create a Check-In with their indirect subordinate but the indirect subordinate cannot create a Check-In with their Detail Supervisor.

Email Digest Administration - Manage Grants ability to create, edit, view, and delete email digests. This permission can be constrained by OU, User's OU, User Self and Subordinates, and User. The permission constraints determine which email digests the administrator can edit and delete. This is an administrator permission. Performance - Administration