Time entries

A time entry records a work date, hours, team member and project. A task can be linked when the hours belong to an assigned piece of work. The billable choice distinguishes Billable from Non-Billable time. The description lets the person doing the work explain what was done before submission. The record’s Draft, Submitted, Approved and Rejected statuses make the approval state visible to the team.

• Record the day. Team Member chooses the project, date and hours, then adds the relevant task where one exists. The project and team member references keep the entry tied to the delivery record.
• Submit the entry. The worker changes a Draft entry to Submitted when it is ready for the approval check. Setting an entry to Submitted starts Time Entry Approval. The saved submitted-entry list helps the project manager inspect records still in that state.
• Check and retain evidence. The Time Entry Approval workflow approves a submitted entry with positive hours and writes both a review decision and an operation receipt. A blocked attempt receives a failed receipt.

Decide who can enter hours for another team member and who reviews each project after submission. Agree how teams describe time spent on work that spans more than one task. For the pilot, compare the task’s project with the entry’s project before treating task level analysis as authoritative. Decide how a Rejected entry is corrected and resubmitted, then inspect the new outcome. Keep review ownership separate from the person recording the hours. The manager should use the work date and project context when investigating similar totals.

Take a developer assigned a task inside a work package. They record hours for a work date against the project, link the task, add a description and choose the billable value. The entry starts in Draft and moves to Submitted. Submitting starts Time Entry Approval. The project manager checks the resulting status, task and hours in the project context. With positive hours, the status becomes Approved; the decision and operation receipt give the reviewer a separate trail of the action. Next, try an entry whose hours are not positive. The approval guard should block it and record the failed attempt. Try an entry that is already Approved as well: it should not pass the Submitted guard. This case tests both the useful path and the boundary around the approval.

• Timesheets Awaiting Approval — Dated entries still Submitted, with team member, project, task and hours beside the status.
• My Time Entries — A worker’s entries across days and projects, including their current approval state.
• Failed Operations — Receipts that explain why an attempted decision did not complete.

Use daily capture before time approval. The weekly submission remains a separate review of the week.