Relaxed Date Validations on Projects, Phases, Bookings, and Tasks

Highlights

Date validations that previously blocked users from moving or adjusting timelines have been removed, giving teams more flexibility to manage schedules without hitting unnecessary restrictions.

What Changed

Previously, Precursive enforced strict date alignment between Projects, Phases, Bookings, and Tasks — for example, preventing a Phase's dates from extending beyond its parent Project's range, or blocking Project date changes when submitted time existed within the original range. These validations were intended to keep records consistent but in practice were causing friction for teams who had legitimate reasons to adjust timelines. These hard validations have now been removed, and you can move or extend dates freely across Projects, Phases, Bookings, and Tasks without being blocked.

How It Works

• Project, Phase, Booking, and Task Start and End Dates can now be set independently of each other — a Phase can extend beyond the Project timeline, and a Booking can sit outside a Phase's dates
• Timesheet Entries can be created outside of Booking, Project, or Phase date ranges when "Allow time entry outside of Bookings" is enabled or the Phase is Public
• Time logged outside of Project or Phase date ranges on a Task is still added to the Timesheet and remains visible and accessible
• The relationship between Parent Tasks and Sub-Tasks is unchanged — date alignment between those is still enforced

Enablement Guidance

No manual steps necessary. We recommend reviewing any Projects or Phases where date constraints were previously a blocker — these can now be updated without restriction.

If your organisation relies on date alignment validations for governance or process reasons, these can be recreated as custom Salesforce validation rules tailored to your specific needs. If you have any questions about this or need assistance, please reach out to the Precursive Team.

Add Row Modal Performance for Large Datasets

Highlights

The Add Row modal now loads significantly faster for organisations with large numbers of Projects and Phases, and Projects remain searchable even when they fall outside the current Timesheet date range.

What Changed

For organisations with high volumes of Projects and Phases, opening the Add Row modal could cause slow load times, rendering errors, or make relevant Projects impossible to find because they were filtered out based on date. The modal now loads only the 25 most recently accessed Projects by default, and searches dynamically as you type — making it reliably fast regardless of data volume.

How It Works

• Opening the Add Row modal shows your 25 most recently accessed Projects by default, rather than attempting to load all available Projects at once
• Typing 3 or more characters in the Project search filters results dynamically, returning up to 25 matching Projects
• Phases are only loaded once a Project is selected, and Task Categories only once a Phase is selected — keeping each step fast and focused
• Projects outside the current Timesheet date range are still discoverable via search

Enablement Guidance

No manual steps necessary.

Plan to Complete Based on Timesheet Status

Highlights

Plan to Complete fields on Projects, Phases, and Participants now calculate based on Timesheet status rather than date, giving you a more accurate and up-to-date picture of remaining effort and cost.

What Changed

Previously, Plan to Complete values were calculated by summing everything after the current date as "planned." This meant that mid-week, before Timesheets were submitted, the values could be outdated or misleading — for example, time already logged but not yet submitted was still counted as planned rather than actual.

Plan to Complete now combines actuals from Timesheets in submitted or approved statuses with Planned Hours from Timesheets that are still open, giving a forward-looking estimate that reflects the true state of work at any point in time. The statuses that count as actuals are configured in Precursive HQ > Precursive Settings > Global Settings > Actual Time Statuses to Calculate Budget.

How It Works

• For example: a Participant has 160 Planned Hours across 20 days. After logging 10 hours on day one and submitting the Timesheet, Plan to Complete shows 162 hours — 10 hours of actuals from the submitted Timesheet, plus 152 Planned Hours across the remaining 19 days
• Without submission, logged hours continue to count as planned — so Plan to Complete reflects 160 hours until the Timesheet is submitted
• The statuses that count as actuals are configured in Precursive HQ > Precursive Settings > Global Settings > Actual Time Statuses to Calculate Budget

Enablement Guidance

• The definition of Plan to Complete fields has been updated to combine actuals from Timesheets with future Planned Hours. This provides a forward-looking view of remaining budget and effort, giving Project Managers clearer forecasting and earlier signals for corrective action. The Understanding Plan to Complete article explains how the metric is calculated and how to configure it in your Project and Phase views.
• To apply updated Plan to Complete values on Archived Projects, temporarily disable validation rules, run the Calculate Budget batch from Precursive HQ, and re-enable validation rules — contact our Support Team if you'd like help with this.

Data Model

No changes in the Data Model in 1.90.11 release.