Attendance

Attendance records a team member’s hours for a work date and project, optionally linked to an action item. The entry can be Billable or Non-Billable and moves through Draft, Submitted, Approved or Rejected. Setting an entry to Submitted triggers the configured workflow, which checks that its hours are positive and that it is still Submitted. It records a review decision and an operation receipt alongside the status change.

• Set the context. Start from the project and use its named team members to make the owner of each record clear.
• Keep the handoff visible. Move the work through the existing status values and record who took the next step.
• Review exceptions. Open the relevant saved list when a date slips, an approval waits or a follow-up needs verification.

Agree who reviews workflow approval outcomes and which person corrects a rejected entry. Set the meaning of billable work with the project owner before team members submit hours. Verify that each team member points to the correct project and, where used, action item. The Attendance Approver should review entries that remain Submitted and compare approval outcomes with the work date and project supplied by the team member.

Map the project’s real operating language to the record names before importing history. Have the Project Manager and Delivery Lead rehearse the same case with ordinary team accounts. If a role sees too much or cannot complete its assigned step, correct access before the first live cycle. Preserve the project reference and the person responsible when records are moved or corrected.

A team member records three hours against an action discussed in a meeting and submits the entry. The workflow checks the positive hours and Submitted state, then approves the entry. The Attendance Approver checks the project, work date, hours and resulting Approved state with a decision and a succeeded receipt. In a second rehearsal, submit an entry with zero hours: the guard blocks approval and records the failed attempt. A repeated approval attempt after the entry has left Submitted must also fail.

Open the source record again after the handoff. Compare its status, owner, project and dates with the list used by the receiving person. The team should be able to explain the next action from the record itself, including a blocked or failed attempt. Rehearse the correction path with the same roles who will use it in ordinary work.

• Attendance Awaiting Approval — Entries still Submitted for the reviewer to investigate.
• My Attendance — The team member’s own work dates, hours and approval states.

See the related process and review the data model.