Live Planned Hours on Rescheduled Tasks

Highlights

Planned Hours on Timesheets now update automatically when Tasks are moved or rescheduled, even when a Timesheet is already Submitted or Approved - keeping the live plan always in sync with the current project schedule.

What Changed?

Planned Hours on Timesheet Entries now stay aligned to the active project plan at all times. When a Task is rescheduled, the system automatically recalculates Planned Hours across all affected Timesheet weeks - including weeks where the Timesheet has already been Submitted or Approved.

Previously, Planned Hours were treated as fixed once a Timesheet reached Submitted or Approved status. Moving a Task out of that period would leave the original Planned Hours unchanged, and moving it into a new period would calculate Planned Hours using the Task's Remaining Hours rather than the full Planned Hours value. This meant the further a Task was rescheduled from its original dates, the more the Timesheet data would drift from the actual project plan.

The system now handles rescheduling as follows. When a Task moves out of a Timesheet week, Planned Hours for that week are set to 0h - the period is vacated cleanly. When a Task moves into a new Timesheet week, Planned Hours for that week are set to the full Task Planned Hours value, distributed across the working days in that period. This applies consistently regardless of the Timesheet's status.

To illustrate the difference - for a Task with 40 Planned Hours spanning 5 days, where a Resource has logged 8 Actual Hours in Week 1 and the Task is then rescheduled to start in Week 2:

• Previously: Week 1 would retain its 40h Planned Hours, and Week 2 would receive 32h - the remaining hours after actuals. 
• Now: Week 1 Planned Hours are updated to 0h with the original 8h preserved in the Submitted Planned Hours snapshot, and Week 2 receives the full 40h Planned Hours value.

How It Works?

1. A Task is assigned to a Contributor with Planned Hours set and Bookings distributed across Timesheet weeks
2. A Resource submits their Timesheet - the Submitted Planned Hours snapshot is captured at that moment
3. A Project Manager reschedules the Task to a different period
4. Planned Hours on the original submitted Timesheet week are automatically set to 0h - the Submitted Planned Hours value is preserved unchanged
5. Planned Hours on the new Timesheet week are set using the full Task Planned Hours value
6. For Phases in Managed Resourcing Mode, Timesheet Line Items created during recalculation inherit the status of the parent Timesheet:
   1. If Timesheet status is Planned - new Timesheet Line Item status is Planned
   2. If Timesheet status is Approved - new Timesheet Line Item status is Approved
   3. If Timesheet status is Submitted - new Timesheet Line Item status is Approved if all other Timesheet Line Items are Approved, otherwise Submitted

 

Enablement Guidance

No manual steps required.

• To ensure Submitted Planned Hours are populated for all existing Submitted, Approved, and Rejected Timesheet Entries created before this upgrade, post-install script will update these values. In case this will throw an error during upgrade, a data synchronisation script must be run post-install - contact Precursive Team for more information
• Note: the Timesheet UI continues to display the live Planned Hours value - Submitted Planned Hours are available as a separate field on the Timesheet Entry object for reporting and audit purposes

Submitted Planned Hours Snapshot

Highlights

A new Submitted Planned Hours field on Timesheet Entries captures the Planned Hours value at the moment of submission, preserving an accurate audit trail without impacting the live plan view.

What Changed?

A new field, Submitted Planned Hours, has been added to the Timesheet Entry object. This field is system-managed and works as follows:

• When a Timesheet moves from Planned to Submitted or Approved status - the current Planned Hours value is automatically copied into Submitted Planned Hours
• When a Timesheet is recalled back to Planned status - the Submitted Planned Hours field is cleared

This separation means the live Planned Hours field always reflects the current project plan, while Submitted Planned Hours provides a stable audit record of what was planned at the time of submission. The field is not exposed in the Timesheet but is available on the Timesheet Entry object for reporting, list views, and custom layouts.

How It Works?

• Submitted Planned Hours is populated automatically on Timesheet submission - no manual action required
• The field is cleared automatically if a Timesheet is recalled to Planned status
• For historical Timesheets already in Submitted, Approved, or Rejected status before upgrade, the post-install backfill script populates this field retrospectively

Enablement Guidance

No manual steps required.

• To ensure Submitted Planned Hours are populated for all existing Submitted, Approved, and Rejected Timesheet Entries created before this upgrade, post-install script will update these values. In case this will throw an error during upgrade, a data synchronisation script must be run post-install - contact Precursive Team for more information
• Once complete, the Submitted Planned Hours field will be available on the Timesheet Entry object for use in reports, list views, and custom page layouts
• The field populates and clears automatically going forward - no ongoing manual steps required

Data Model

New Field: