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.
- Time Tracking
- Features
- Time Policies and Violations
Time Policies and Violations
Set entry rules by policy and keep an append-only ledger of every entry that breaks them.
OverviewTime Policy Violations Queue×
Time Tracking · Time Policies and Violations
New
Time Policy Violations Queue
Time policy violations
| Violation number | Resource | Type | Severity | Occurred at | Time entry | |
|---|---|---|---|---|---|---|
| TPV-53790 | RSR-7741 | Max hours exceeded | Warning | 16 Oct | TE-71002 | |
| TPV-55073 | RSR-9920 | Missing project | Blocker | 10 Oct | TE-49375 | |
| TPV-70987 | RSR-3118 | Missing task | Warning | 08 Oct | TE-85190 | |
| TPV-76638 | RSR-3780 | Missing description | Blocker | 15 Oct | TE-64634 | |
| TPV-89558 | RSR-1885 | Weekend unflagged | Warning | 04 Oct | TE-13216 |
6 of 6 records
RSR-7741Time policy violations · TPV-53790
Max hours exceededSeverityWarning
Occurred at16 Oct
Time entryTE-71002
Resolved at15 Oct
What you can do
Agree the rules once and check every entry
A time policy sets how time must be entered: the minimum increment in minutes, the maximum hours per day, whether a daily entry is required, whether project, task and description are required, whether mobile entry is allowed and the weekly overtime threshold. Each person is assigned one policy. Policies have effective dates and an active flag.
Every new entry is checked against the person’s policy. Each broken rule writes a violation with a number, type, severity, time, the entry and the person. Types include maximum hours exceeded, missing project, task or description, unflagged weekend work, below the minimum increment, missing daily entry and controller reopen. Severity is Info, Warning or Blocker. Violations are never edited away; they are resolved with a date and a note.
How the work is organized
- Policies by population. Salaried and hourly staff, or different regions, can have different policies.
- Violations as a ledger. Each violation stays on record with its resolution.
- Violations affect approval. A person with an open violation that week is not eligible for auto-approval.
What to agree during setup
Agree the policies you need and who is assigned to each, including exempt and non-exempt classification and state of work. Set the maximum hours per day and the overtime threshold. Decide which violations are Blockers, who resolves them and how quickly.
Check the handoff on an actual case
A non-exempt support engineer in California logs 11 hours on a Tuesday. His policy caps a day at 10 hours, so a Maximum Hours Exceeded violation is written as a Warning against that entry. On Saturday he logs 2 hours without flagging the weekend, which writes a Weekend Unflagged violation.
His resource manager reviews both on Monday. She confirms the Tuesday overtime was authorized and resolves that violation with a note. The engineer flags the Saturday entry, and the second violation is resolved. Because both were open during the week, his sheet went to manual approval rather than auto-approval.
What your team sees
- Time Policy Violations Queue — Warning and Blocker violations with person, type, time, entry and resolution date.
- My Time Entries — Each person’s entries, so they can fix what a violation points to.
Follow the work through
- Timesheet approval routing: How open violations affect auto-approval.
- Reopen and retro-edit: Controller reopenings are recorded as violations.
Check policy permissions before go-live.
What it keeps track of
Data model- Time policies
- Org-level entry and validation policy: minimum increment, daily entry requirement, max hours per day, project/task requirement, mobile entry permission.
- Time policy violations
- Append-only audit ledger of flagged Time Entries that violated a Time Policy.
- Time entries
- The atomic time grain: one row per Resource per Date per Project, Task and Project Code.
- Resources
- Local mirror of the resource master carrying Time Policy assignment, default approval rules and manager hierarchy.
Who uses it
Permissions- Controller
- , Resource Manager, Resource.
- The Controller owns policies.
- Resource Manager
- S resolve violations with their teams.
- Resource
- S correct their entries.
Set up Time Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.