1. Timesheet Management
  2. Data model
Reference

The tables behind Timesheet Management

Timesheet Management ships with 14 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
14
Features
6, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Project context

Organizations owns the customer or internal entity; Projects names the engagement; work packages groups its work; Tasks assigns individual pieces.

Time

Time entries holds dated person and project hours. Time submissions holds the weekly worker, parent package, organization, hours and revision.

Review

Review decisions records decisions; operation receipts records attempted outcomes; record attachments connects files to supported delivery records.

Delivery context

Issues, Risks and Milestones keep project exceptions and checkpoints visible. Team members supplies owners and assignees; Users holds account records.

Every table, by feature

Weekly submissions

6 tablesAbout this feature
  • Time submissions

    Weekly time submissions supporting approval of a submitted weekly timesheet.

    Linked to Work packages, Organizations
  • Work packages

    Groupings of work inside a project.

    Linked to Projects, Team members
  • Organizations

    Client and internal business organizations that projects are delivered for.

  • Time entries

    Hours booked by a team member against a task and project.

    Linked to Team members, Projects, Tasks
  • Review decisions

    Recorded approval decisions on delivery subjects.

    Linked to Team members, Projects
  • Operation receipts

    Evidence that a delivery operation was executed.

    Linked to Team members

Time entries

6 tablesAbout this feature
  • Time entries

    Hours booked by a team member against a task and project.

    Linked to Team members, Projects, Tasks
  • Team members

    Delivery staff with role, practice and weekly capacity.

  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members
  • Tasks

    Individual pieces of work assigned to a delivery team member.

    Linked to Work packages, Team members, Projects
  • Review decisions

    Recorded approval decisions on delivery subjects.

    Linked to Team members, Projects
  • Operation receipts

    Evidence that a delivery operation was executed.

    Linked to Team members

Project work

6 tablesAbout this feature
  • Organizations

    Client and internal business organizations that projects are delivered for.

  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members
  • Work packages

    Groupings of work inside a project.

    Linked to Projects, Team members
  • Tasks

    Individual pieces of work assigned to a delivery team member.

    Linked to Work packages, Team members, Projects
  • Time submissions

    Weekly time submissions supporting approval of a submitted weekly timesheet.

    Linked to Work packages, Organizations
  • Time entries

    Hours booked by a team member against a task and project.

    Linked to Team members, Projects, Tasks

Tasks and assignments

5 tablesAbout this feature
  • Tasks

    Individual pieces of work assigned to a delivery team member.

    Linked to Work packages, Team members, Projects
  • Work packages

    Groupings of work inside a project.

    Linked to Projects, Team members
  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members
  • Team members

    Delivery staff with role, practice and weekly capacity.

  • Time entries

    Hours booked by a team member against a task and project.

    Linked to Team members, Projects, Tasks

Review and evidence

6 tablesAbout this feature
  • Review decisions

    Recorded approval decisions on delivery subjects.

    Linked to Team members, Projects
  • Operation receipts

    Evidence that a delivery operation was executed.

    Linked to Team members
  • Record attachments

    Files attached to delivery records.

    Linked to Team members
  • Time entries

    Hours booked by a team member against a task and project.

    Linked to Team members, Projects, Tasks
  • Time submissions

    Weekly time submissions supporting approval of a submitted weekly timesheet.

    Linked to Work packages, Organizations
  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members

Delivery exceptions

7 tablesAbout this feature
  • Issues

    Defects and change items raised against project work.

    Linked to Projects, Team members
  • Risks

    Project risks with probability, impact, owner and mitigation.

    Linked to Projects, Team members
  • Milestones

    Dated checkpoints a project must meet.

    Linked to Projects, Team members
  • Tasks

    Individual pieces of work assigned to a delivery team member.

    Linked to Work packages, Team members, Projects
  • Projects

    Engagements delivered for an organization, with budget and schedule.

    Linked to Organizations, Team members
  • Operation receipts

    Evidence that a delivery operation was executed.

    Linked to Team members
  • Record attachments

    Files attached to delivery records.

    Linked to Team members

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

A work packages record references Projects. Tasks requires work packages and may also reference Projects and team members. Time entries requires team members and Projects, with an optional Tasks link. Time submissions requires work packages and Organizations. Review decisions can reference a related Projects record and a team members reviewer; operation receipts can reference a team members actor. Record attachments uses a parent table name and record identifier.

Migration order

  1. Load Organizations and team members, then establish Users access.
  2. Load Projects under their organizations and owners.
  3. Load work packages, then Tasks, Issues, Risks and Milestones under the correct projects.
  4. Load time entries and time submissions with their required references, dates and status values.
  5. Bring review decisions, operation receipts and record attachments only with verified source references.

Set up Timesheet Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started