1. OKR Tracking System
  2. Features
  3. Check-ins and approvals
Feature · Check-ins and approvals

Check-ins and approvals

Record dated hours against objectives and route submitted entries through a decision.

OverviewCheck-Ins Awaiting Approval
OKR Tracking System · Check-ins and approvals

Check-Ins Awaiting Approval

Approval conditions

New
Check in numberCheck in dateTeam memberProjectTaskHours
CI-7445211 OctOBJ-1458TSK-852613
CI-5123813 OctOBJ-6823TSK-541911
CI-5772420 OctOBJ-1505TSK-896212
CI-9788625 OctOBJ-8550TSK-85726
CI-6331923 OctOBJ-7505TSK-527416
6 of 6 records
OBJ-1458Check ins · CI-74452
Submitted
Check in date11 Oct
TaskTSK-8526
Hours13
Example screen with sample data

What you can do

Bring recorded work into review

A check-in records a date, hours, billable choice, description, team member, objective and optional task. A team member can save it as draft or submit it. The configured approval workflow acts on a Submitted entry with positive hours. It marks the entry Approved and records a review decision and an operation receipt. If hours are not positive or the entry is no longer Submitted, the attempt receives a failed receipt.

Submission starts the configured approval action. The Check-in Reviewer inspects the resulting status, decision and receipt, especially when an attempted approval fails its guard. Keep the original check-in attached to the objective so the team can explain the hours and the recorded result during a later review.

How the work is organized

  • Record the work. The Team Member enters the date, positive hours, objective and optional task.
  • Submit for approval. A Submitted entry is checked by the approval workflow.
  • Inspect the result. The Check-in Reviewer compares the entry status with its decision and receipt before resolving an exception.

What to agree during setup

Agree who reviews submitted time and what the team considers a complete description. Decide whether billable or non-billable applies to each kind of work. Check the team member, objective and task links before approving an imported entry. Rehearse with a positive-hour entry and a zero-hour entry. The Check-in Reviewer should find the approved entry and its evidence, then return the failed case to the Team Member for correction.

Check the handoff on an actual case

A team member finishes a task and submits a dated check-in for the work. Submission starts the approval workflow. The reviewer checks the project, task, hours, decision and receipt after it runs. A zero-hour submission fails the guard; the reviewer returns to the source entry instead of treating the receipt as an approval. The Team Member corrects the invalid hours on the source entry before submitting again. The Check-in Reviewer compares the date and team member with the linked objective, because a valid hour total alone does not explain which work was booked. The reviewer checks the later receipt separately so an earlier failure is not mistaken for an approval.

What your team sees

  • Check-Ins Awaiting Approval — Entries still Submitted, with objective, task and hours for exception review.
  • My Check-Ins — A team member’s dated entries and status.

Follow the work through

What it keeps track of

Data model
Check ins
Hours booked by a team member against a task and project.
Tasks
Individual pieces of work assigned to a delivery team member.
Objectives
Engagements delivered for an organization, with budget and schedule.
Team members
Delivery staff with role, practice and weekly capacity.
Review decisions
Recorded approval decisions on delivery subjects.
Operation receipts
Evidence that a delivery operation was executed.

Who uses it

Permissions
Team Member
, Check-in Reviewer.
The Team Member submits work; the workflow makes the approval decision; the Check-in Reviewer inspects its result.

Set up OKR Tracking System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started