1. Sprint / Agile Board
  2. Features
  3. Time and Review
Feature · Time and Review

Time and Review

Team members record work date, hours, project and optionally a story on a time entry.

OverviewTimesheets Awaiting Approval
Sprint / Agile Board · Time and Review

Timesheets Awaiting Approval

Approval conditions

New
Entry numberTeam memberProjectWork dateHoursStatus
TE-97564PRJ-155815 Oct3Submitted
TE-93663PRJ-522923 Oct3Submitted
TE-68453PRJ-752806 Oct2Submitted
TE-62916PRJ-954713 Oct8Submitted
TE-29627PRJ-725204 Oct7Submitted
6 of 6 records
PRJ-1558Time entries · TE-97564
Submitted
Work date15 Oct
Hours3
Example screen with sample data

What you can do

Hours and decisions

Team members record work date, hours, project and optionally a story on a time entry. A submitted entry with positive hours is approved by the workflow, which records a review decision and operation receipt. Review decisions also keep the subject, reviewer, decision and date for delivery review. Attachments can hold supporting files for a delivery record.

How the work is organized

  • Starting record. Team members record work date, hours, project and optionally a story on a time entry.
  • Named owner. Team Member submits work; Time Reviewer checks approval; Delivery Lead reads the project totals.
  • Current position. The status and linked records tell the team where attention belongs next.

What to agree during setup

Agree which time is billable and who checks submitted entries. Require a work date and positive hours before submission. Decide how rejected entries are corrected and who can read the related review decision. Keep the entry linked to the correct project and story so reported hours remain useful to the delivery lead.

The Team Member checks the work date, project and hours before submission because the approval workflow runs at that change. The Time Reviewer inspects the resulting decision and receipt. A failed attempt leaves the entry for correction; the team should use its recorded reason before submitting again.

Check the handoff on an actual case

A team member logs several hours against a story and submits the entry. The approval workflow checks that the hours are positive and the entry remains submitted, then marks it approved and records the decision and receipt. If the entry has zero hours, it records a failed receipt instead. The Time Reviewer can inspect the approval decision and receipt, while the Delivery Lead compares logged hours with project estimates.

The Time Reviewer opens the submitted entry to verify its project, team member and work date, then reads the decision and receipt created by the workflow. A failed attempt with zero hours is corrected on the source entry before another submission. The Delivery Lead reads project hours only after those links are accurate.

What your team sees

  • Timesheets Awaiting Approval — Submitted entries ready for an approval check.
  • My Time Entries — The team member’s dated work and approval states.

Follow the work through

See sprint planning for the planning handoff and review and approval for the decision record. Begin with a small project in implementation, then compare the team’s results with the data model.

What it keeps track of

Data model
Time entries
Hours booked by a team member against a task and project.
Review decisions
Recorded approval decisions on delivery subjects.
Operation receipts
Evidence that a delivery operation was executed.
Record attachments
Files attached to delivery records.
Stories
Individual pieces of work assigned to a delivery team member.
Projects
Engagements delivered for an organization, with budget and schedule.

Who uses it

Permissions
Team Member
Submits work; Time Reviewer checks approval; Delivery Lead reads the project totals.

Set up Sprint / Agile Board your way.

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

How to get started