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
- Data model and import order
The tables behind Time Tracking
Time Tracking ships with 16 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 16
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Time Entry and Timers:
Time entries, Timers, timer events, mobile sync queue. Each entry belongs to a person, a timesheet and a project code.
Timesheets:
Timesheets hold one week per person with totals and export dates.
Timesheet Approvals:
Timesheet approvals hold the steps for a sheet; approval rules define how steps are built.
Project Codes and Rates:
Project codes and billable rate overrides set categories, billable flags and rates.
Time Policies and Violations:
Time policies set entry rules; time policy violations record breaches.
Period Close and Reopening:
Pay calendars and lock exemptions control pay periods and pre-approved retro-edits; requests to reopen a locked week are kept as their own records.
People:
Resources mirror the resource master with policy, manager, classification and default rate; Users hold platform accounts.
Every table, by feature
- Time Entry and Timers4
- Timesheets3
- Timesheet Approvals4
- Project Codes and Rates3
- Time Policies and Violations4
- Period Close and Reopening4
- Shared and settings2
- Time entries
The atomic time grain: one row per Resource per Date per Project, Task and Project Code.
Linked to Timesheets, Resources, Project codes - Timers
Running-timer state per Resource, finalized into a Time Entry on Stop.
Linked to Resources, Project codes, Time entries - Timer events
Append-only event log for a Timer: Start, Pause, Resume, Stop.
Linked to Timers, Resources - Mobile sync queue
Pending mobile entries awaiting sync, drained into Time Entries on reconnect.
Linked to Resources, Project codes, Time entries
- Timesheets
Weekly aggregate per Resource per Week Ending. The approval-and-lock unit.
Linked to Resources - Time entries
The atomic time grain: one row per Resource per Date per Project, Task and Project Code.
Linked to Timesheets, Resources, Project codes - Resources
Local mirror of the resource master carrying Time Policy assignment, default approval rules and manager hierarchy.
Linked to Resources, Time policies
- Timesheet approvals
Multi-step approval chain on a Timesheet, one row per approval step per approver.
Linked to Timesheets, Resources, Approval rules - 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.
Linked to Resources - Resources
Local mirror of the resource master carrying Time Policy assignment, default approval rules and manager hierarchy.
Linked to Resources, Time policies
- Project codes
Billable and non-billable code catalog mapping a Project and optional Task to a billing rate.
Linked to Resources - Billable rate overrides
Effective-dated per-Resource per-Project hourly rate override for billing.
Linked to Resources, Project codes - Resources
Local mirror of the resource master carrying Time Policy assignment, default approval rules and manager hierarchy.
Linked to Resources, Time policies
- 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.
Linked to Time entries, Resources, Time policies - Time entries
The atomic time grain: one row per Resource per Date per Project, Task and Project Code.
Linked to Timesheets, Resources, Project codes - Resources
Local mirror of the resource master carrying Time Policy assignment, default approval rules and manager hierarchy.
Linked to Resources, Time policies
- Pay calendars
Configured pay periods (semi-monthly / biweekly) that drive period close, payroll export and the Period Close Status scope.
- Lock exemptions
Pre-authorized exemptions allowing retro-edits of Locked Time Entries without an Unlock Request.
Linked to Resources, Project codes - Timesheets
Weekly aggregate per Resource per Week Ending. The approval-and-lock unit.
Linked to Resources - Time entries
The atomic time grain: one row per Resource per Date per Project, Task and Project Code.
Linked to Timesheets, Resources, Project codes
Keys and references
Every person keeps a stable resource ID, every code its code, every sheet its number and week ending, and every entry its entry number. Import entries by resource ID, date and code. Keep one sheet per person per week ending. Load overrides with their effective dates.
The app holds 16 tables and 32 relationships.
Migration order
- Load Users, time policies and Resources with managers and policies.
- Load project codes, billable rate overrides and approval rules.
- Load pay calendars for the year.
- Load open Timesheets and their time entries.
- Load lock exemptions in force.
- Reconcile hours by person and week with the source before people start logging.
Set up Time Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.