Usage and approval

A Team Member records a work date, positive hours and a booking on a usage entry. The entry can also point to the specific assigned piece of work and say whether the hours are billable. A draft remains with the person entering time. Submission triggers the approval check. When an entry is submitted, the configured approval workflow checks that hours are positive and that the entry is still submitted. On approval it marks the entry approved and writes a review decision and an operation receipt. A failed attempt is recorded as a failed operation receipt.

This matters when several people work under one booking. A reviewer should inspect the work date, member, booking, assigned item and description before relying on the total. Positive hours satisfy the workflow guard; the reviewer still checks whether the recorded work needs follow-up. The Usage Reviewer checks the recorded outcome and follows up when an entry or its context needs correction. The resulting decision trail lets a delivery lead distinguish recorded work from accepted work when reviewing the engagement.

• Daily entries. The work date and hours describe when and how much time was recorded.
• Submission. The team member changes a draft to submitted, which starts the approval check.
• Decision trail. The approval writes a separate decision and a receipt alongside the usage status.

Decide how team members describe work so a reviewer can recognize it. Agree whether every entry should refer to an assigned item or whether the booking alone is enough for some work. Assign a reviewer for failed attempts and approved entries that need follow-up. Define how billable and non-billable entries are interpreted by downstream finance. Any invoicing or payroll connection needs its own configuration and authority.

Have a team member enter a work date and hours for an active booking, attach the assignment and submit it. The submission triggers the approval workflow. The Usage Reviewer checks the approved entry, decision and receipt after it runs. Check that a review decision and operation receipt identify the result. Repeat the case with zero hours: the approval attempt should fail and leave a failed receipt. Try running the approval action after the state has changed; it should leave a failed receipt without another approval.

A delivery lead can then compare accepted usage against reserved and actual hours on the assigned work. If the numbers differ, follow the underlying entries rather than rewriting a total to make the booking appear balanced.

• Resource Usage Awaiting Approval — Submitted entries with work date, hours, member and booking, including entries still waiting after an unsuccessful attempt.
• My Resource Usage — A person’s dated entries and their current review state.
• Recent Operation Receipts — Outcomes of recorded actions, including failed approval attempts.

Use usage review for submission, approval and the decision trail.