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
- Implementation and migration
How a Time Tracking rollout works
Start with one team and one pay period the managers and controller can reconcile.
Agree the operating boundary
The scope is time capture, timesheets, approvals, policies, rates, locking and exports. HR, billing, payroll and project systems remain connected. Your firm decides its policies, approval paths and rates; Proto prepares configuration for review.
Map the source data
Bring resources with managers and classification, project codes, rate overrides, approval paths, policies and the pay calendar.
Configure a bounded pilot
Pilot one team for one pay period. Log time by web, timer and mobile, submit, approve and export.
Rehearse the exceptions
Exceed a daily limit. Leave a sheet unsubmitted until Monday. Reject an approval step. Request and approve a reopen. Export the same sheet twice.
Reconcile and release
Compare hours by person and week, billed hours and the payroll bundle with the source. Obtain the Controller's acceptance and agree the rollback window before adding teams.
What the customer provides
- The resource list with managers, classification and state of work.
- Project codes with categories, billable flags and rates.
- Rate overrides by person and project.
- Approval paths and time policies.
- The pay calendar for the year.
Changing it afterwards
Use Proto to prepare changes on a branch. Review changed policies, rules and rates with the Controller. Replay the pilot’s exception cases before release. Approved and exported time keeps its original values.
Set up Time Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.