These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Attendance Management
- Features
- Weekly timesheets
Weekly timesheets
Keep daily hours, category and weekly total connected to the employee record and the next decision.
OverviewMy weekly timesheets×
Attendance Management · Weekly timesheets
New
My weekly timesheets
Attendance sessions
| Session number | Week start | Week end | Total hours | Status | |
|---|---|---|---|---|---|
| AS-31525 | 18 Oct | 22 Oct | 6 | Draft | |
| AS-33493 | 15 Oct | 17 Oct | 2 | Submitted | |
| AS-44391 | 20 Oct | 22 Oct | 4 | Approved | |
| AS-84853 | 24 Oct | 31 Oct | 10 | Posted | |
| AS-12063 | 27 Oct | 29 Oct | 8 | Draft |
6 of 6 records
AS-31525Attendance sessions · AS-31525
DraftWeek start18 Oct
Week end22 Oct
Total hours6
What you can do
Keep daily hours, category and weekly total together
Weekly timesheets brings the relevant source records into one operating path. An employee enters regular hours across the week and overtime on Saturday. The named approver compares the Saturday entry with the week total; Admin records the approval decision. Payroll Admin reads the approved week at cutoff. The person link, effective date and current status give the next team a way to understand the decision without relying on a typed name or an email thread.
A preparer should check the record before handing it off. The reviewer needs the source dates and amounts in context, plus the authority to return a disputed item. When a correction is needed later, the team should retain the original record and explain the new effective value.
How the work is organized
- Prepare. Employee starts with daily hours, category and weekly total and checks the employee link.
- Review. The named approver checks the record and its dates before a downstream team relies on it.
- Follow through. An employee enters regular hours across the week and overtime on Saturday. The named approver compares the Saturday entry with the week total; Admin records the approval decision. Payroll Admin reads the approved week at cutoff.
What to agree during setup
Decide the work-week boundary, approver assignment, cost center convention and how a rejected week returns for correction. Keep regular, overtime, double-time and on-call hours distinct. Define which person owns initial entry, who makes the decision, and which point closes further routine edits. Review the same rule for a normal cycle and a late correction. If the relevant employee changes role or department, keep the source period understandable to the next reviewer.
Use a representative worker and one pay period to settle the convention. Enter a real date range, assign a responsible reviewer and inspect the resulting status. The team can then compare the source against the next record before broadening access to everyone.
Check the handoff on an actual case
An employee enters regular hours across the week and overtime on Saturday. The named approver compares the Saturday entry with the week total; Admin records the approval decision. Payroll Admin reads the approved week at cutoff. Ask the recipient to find the source record using the person and period, then explain what was accepted and what would be returned. Rehearse a rejected or corrected version as well. A decision is useful only when the preparer can see what to change and the next team can tell which value is final.
What your team sees
- My weekly timesheets — The main worklist for daily hours, category and weekly total, with the person and current state in view.
- Timesheets awaiting approval — Submitted weeks with their period and approver.
Follow the work through
Read hours and leave, payroll, the data model and roles to rehearse the complete path.
What it keeps track of
Data model- Attendance sessions
- Weekly timesheet header per employee.
- Attendance events
- Hours against a day, project or cost center.
- People
- Central person record for every worker; all suite transactions tie back to Employees.
- Departments
- Organizational departments with parent hierarchy and cost centers.
Who uses it
Permissions- Employee
- Owns the primary work.
- HR Business Partner
- Maintains employee context, Payroll Admin checks the pay-period consequence, and Admin handles configured access and corrections.
- Each handoff should preserve the named preparer and decision maker.
Set up Attendance Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.