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
- Timesheet Approvals
Timesheet Approvals
Route each submitted timesheet through an ordered approval chain built from your approval rules.
OverviewTimesheet Approvals×
Time Tracking · Timesheet Approvals
New
Timesheet Approvals
Approval conditions
| Timesheet | Approval step | Approver role | Approver | Derived from rule | Status | |
|---|---|---|---|---|---|---|
| TMS-98513 | 690 | Project manager | RSR-5822 | AR-1652 | Pending | |
| TMS-63795 | 110 | Resource manager | RSR-7288 | AR-2048 | Pending | |
| TMS-38911 | 590 | Time approver | RSR-6425 | AR-2276 | Pending | |
| TMS-10770 | 850 | Controller | RSR-2723 | AR-6321 | Pending | |
| TMS-25109 | 330 | System | RSR-8916 | AR-6039 | Pending |
6 of 6 records
TMS-98513Timesheet approvals · TA-23699
Project managerApproval step690
ApproverRSR-5822
Derived from ruleAR-1652
StatusPending
What you can do
Route each sheet to the right approvers
When a sheet is submitted, the active approval rules are evaluated in priority order. Each rule can match on project category, whether billable time is present and a minimum number of hours, and names the role for step one and optionally step two: Project Manager, Resource Manager, Time Approver or Controller. A rule matches in First Match or All Match mode. The result is an ordered chain of approval steps on the sheet, one per approver, each Pending.
Each approver approves or rejects their step with comments. When the chain is approved, the sheet is Approved and its entries lock. A rejection sends the sheet back with the reason. A rule may also allow auto-approval when the sheet’s variance from forecast is within its threshold and the person has no open policy violations that week.
How the work is organized
- Rules in priority order. Rules are evaluated from highest priority, so a specific rule for travel time can sit above a general delivery rule.
- Steps with roles. Each step records the approver role, the approver, the rule it came from and the decision.
- Auto-approval within limits. Low-variance sheets with no open violations can skip manual approval when the rule allows it.
What to agree during setup
List the approval paths you use today and turn them into rules with priorities. Agree who approves billable delivery time, internal time and travel. Decide whether any rule should auto-approve, and at what variance. Confirm each person’s resource manager is recorded.
Check the handoff on an actual case
A consultant’s week includes 30 billable delivery hours and 8 hours of travel. The travel rule has the highest priority and routes step one to the Project Manager and step two to the Controller. The delivery rule routes to the Project Manager only. In All Match mode both apply, so the chain has a Project Manager step and a Controller step.
The Project Manager approves on Monday. The Controller questions a 4-hour taxi wait and rejects the step with a comment. The consultant splits the time correctly and resubmits, and a new chain is built. Another consultant’s sheet, 40 hours against a 40-hour forecast with no violations, is auto-approved by a rule that allows a 5 percent variance.
What your team sees
- Timesheet Approvals — Pending approval steps with sheet, step, role, approver and source rule.
- My Approval Steps — The steps assigned to the signed-in approver, with decisions and comments.
- Active Approval Rules — The rules in force with priority, conditions and approver roles.
Follow the work through
- Timesheet approval routing: From submission to an approved, locked sheet.
- Time entry to payroll export: What approval releases.
Check who may approve before go-live.
What it keeps track of
Data model- Timesheet approvals
- Multi-step approval chain on a Timesheet, one row per approval step per approver.
- Approval rules
- Declarative routing rules evaluated in priority order on Timesheet submit.
- Timesheets
- Weekly aggregate per Resource per Week Ending. The approval-and-lock unit.
- Resources
- Local mirror of the resource master carrying Time Policy assignment, default approval rules and manager hierarchy.
Who uses it
Permissions- Project Manager
- , Resource Manager, Time Approver, Controller.
- Approvers decide their steps.
- The Controller maintains the approval rules.
Set up Time Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.