Timesheet

Last updated: 2026-04-15 Owner: Product Writer Audience: user, manager, tenant admin

Purpose

Explain how to record hours and submit a timesheet correctly.

Prerequisites

• at least one assigned project/WBS
• correct month and year selected

Operational steps

1. Open the Timesheet module.
2. Select year and month.
3. Add a new row if needed.
4. Choose project/WBS and task.
5. Enter hours on the correct days.
6. Save as draft or submit for approval.

Expected result

The system saves the row or registers the submission with duplicate and consistency controls active.

Evidence and attachments

• each timesheet row can now carry linked evidence
• evidence is optional in the first pass
• you can manage it only while the row is still editable by the submitter
• once the row enters review or closes, evidence remains readable but can no longer be deleted by the submitter

Correction workflow

The timesheet lifecycle now clearly distinguishes:

• Draft: the row is still editable by the submitter
• Submitted or Resubmitted: the row is under review and locked for submitter edits
• Changes requested: the row is handed back to the submitter for correction and resubmission
• Approved or Rejected: the row is closed

If a row already exists for the same project and task, do not create a second one. Open the existing row, correct it, and resubmit it if the workflow allows it.

Hour validation rules

HORIS applies tenant-governed controls on three levels:

• recommended daily and weekly thresholds
• hard daily and weekly caps
• dedicated weekend and overtime policies

Recommended thresholds produce warnings. Hard caps block save or submit actions.

Weekend

• Saturday and Sunday are not globally forbidden by the system
• the tenant can allow or disable weekend entries
• the tenant can define a maximum number of hours per weekend day
• the tenant can require a mandatory note for weekend hours

Overtime

• the tenant can allow or block hours above the recommended threshold
• the tenant can define a daily and weekly overtime threshold
• the tenant can require a mandatory note when overtime thresholds are exceeded

Important note

Hour validation is aggregated on the user's total:

• per day
• per week
• across all rows/WBS for the period

This means an error can appear even if the visible row looks correct, when the user's combined total exceeds the tenant policy.

Common errors

• No available project
• cause: the user is not associated with projects/WBS
• solution: ask HR/admin/manager for the correct assignment

• Submission blocked
• cause: exceeded limits or duplicate already submitted
• solution: correct the row or verify the existing status

• Row not editable
• cause: the row is already under review or closed
• solution: wait until changes are requested or ask the reviewer to reopen the case through the proper flow

• Weekend not allowed or note missing
• cause: the tenant policy blocks weekend entries or requires a mandatory note
• solution: remove weekend hours or add a valid note for that entry

• Overtime not allowed
• cause: the daily or weekly total exceeds the overtime threshold allowed by the tenant
• solution: reduce hours, distribute the workload correctly, or check the active policy with manager/HR

FAQ

Can I submit the same period twice?

No. HORIS applies anti-duplicate controls on timesheet flows.

Can I record Sunday hours?

Yes, but only if the tenant policy allows it. Weekend entries are not hardcoded by the platform: they depend on the owner/admin/HR policy currently active.