Review and evidence

A submitted time entry and a submitted weekly timesheet each have an approval path. Both workflows write a review decision and an operation receipt when approval succeeds. The weekly workflow records a completed receipt, and a blocked attempt records a failed receipt while leaving the submission unchanged. Operation Receipts includes the operation type, reference, time, result and actor. Review Decisions records the subject reference, decision, reviewer, decision date and related project when supplied. Together these records let a reviewer distinguish a status from the action that produced it.

• Prepare the subject. Team Member submits a time entry or weekly record with the correct project and work package context. Project Manager can inspect the entry outcome and open a submitted weekly item for a decision.
• Make the decision. The time entry approval requires positive hours and Submitted status. The weekly approval also requires a valid revision. Submitting an entry starts its approval workflow; the project manager decides the weekly item. Both workflows record their outcomes.
• Review the trail. Reviewer opens the decision history and failed operation list, then follows the reference back to the delivery subject. Attachments can hold evidence against supported delivery record types.

Define who is allowed to approve submitted time and who reviews the operation trail. Rehearse access decisions before rollout. Agree how references in decisions and receipts identify the original item. In a live rehearsal, follow the decision reference to the submitted record and confirm the reviewer can identify the subject. Establish how failed attempts are investigated and who may retry after the underlying record is corrected.

Have a team member submit a dated entry with positive hours. The submission starts Time Entry Approval; Reviewer finds the approved entry, its decision and its successful receipt. Then test the entry guard with a record that is no longer Submitted. The entry should stay as it is, and a failed receipt should make the attempt visible. Repeat the exercise on a weekly submission with a valid revision and then with invalid hours. The successful weekly approval freezes the status as Approved. The invalid attempt leaves the submitted record unchanged and creates a failed receipt. These cases show what the review queue means and what a reviewer can verify independently. Attach an evidence file to a supported record if the team uses attachments as part of its review.

• Failed Operations — Unsuccessful attempts with type, reference, date and actor for investigation.
• Timesheets Awaiting Approval — Entries still Submitted after submission, with their project context.
• Weekly Submissions Awaiting Approval — Submitted weekly records awaiting a separate decision.

Walk through time approval and evidence review. The roles page explains the access rehearsal.