About Time

The manager who approves time, and whoever runs payroll.

Timesheets pile up unseen until the payroll deadline, and the week's hours are only known once it is over.

Four cards: Hours This Week, Clocked In, Pending Approvals and Pending PTO, drilling into Timesheets and PTO Requests with the matching filter. Quick Actions open Add Time Entry and Submit PTO Request in place. Three charts for the week: Hours by Day, Allocation Breakdown by work type, and Top Employee Hours.

• The approval queue, counted. Pending Approvals is the number that has to be zero before payroll runs, and it drills to exactly those entries.
• Who is on the clock right now. Clocked In is every entry with no clock-out, which is also the list of forgotten clock-outs at the end of the day.
• Where the week went. Allocation Breakdown says how much of the week was billable job work and how much was everything else.

The approving manager, and the office entering time on someone's behalf.

Hours are known but not what they were for. A job's labor cost is a guess, a project's is a bigger guess, and the timesheet on paper cannot be questioned without a conversation.

Time entries by employee, with an employee type-ahead, status, device type (Web, Kiosk, Mobile) and date-range filters, and a grid that shows each entry's allocations and a Flagged indicator. Add Time Entry captures the employee, date and time, notes, and an allocation builder that asks "What was this time spent on?" with rows of work type, job or punch list, and hours. An entry's detail page shows the Time Allocations table (work type, job or punch list, hours, rate, cost, overtime) and an Adjustment History, with Flag and Reject actions that each require a reason.

• Hours become job cost. An allocation row against a job or punch list is how labor lands on that job's or project's cost. Nothing else does it.
• Overtime priced correctly. An allocation marked overtime is costed at the rate times the overtime multiplier.
• Flag, do not argue. A questionable entry is flagged with a reason and stays visible in the Flagged filter until it is resolved.
• An audit trail per entry. The Adjustment History records every change after the fact, with who made it.

The manager approving time off, and the scheduler who needs to know who is out.

Time off is a text message. The approval is verbal, the balance is nobody's, and the scheduler finds out when the technician is not there.

Requests filtered by employee, status and date range, showing the type, dates, hours, status and who reviewed it. Submit PTO Request captures the employee, PTO type, start and end dates, hours and notes. Approve is one click; Deny opens a modal that requires a reason.

• Approval draws the balance down. Approving a request adds its hours to that year's Used and takes them from Remaining, automatically.
• Blackout dates are enforced. A request that overlaps a blackout date is refused at submission, not discovered at approval.
• The schedule knows. Approved time off is what the Routing Workbench and Workload & Capacity subtract from a technician's available hours.
• A denial has a reason. The reason is required and stays on the request.

Whoever administers benefits, and the employee asking how much they have left.

"How many days do I have?" is answered from a spreadsheet that was right in January.

Accrued, Used and Usage per employee, per PTO type, per year, searchable by employee or type. Add PTO Balance sets the year's accrual for an employee and type.

• Always current. Every approved request updates the balance, so the number on screen is the number.
• By type and by year. Vacation and sick time are separate balances, and each year starts clean.