On this page
A scheduler changes a working week or a predecessor. The calculation produces new dates. Before those dates become the dates everyone builds to, someone needs to check what moved, which task records will change, and what the connected tools will show.
Planner separates those steps. Save and calculate keeps a version and its result. For eligible retained imports adopted with exact task bindings, Review task date changes shows the proposed changes before Apply reviewed task dates updates field records. The controls depend on the deployed app version and your permissions.
A plan started with Add activity has a separate native Planner publication workflow for supported flat, unstarted tasks and milestones. Integrations can use the native publication API. The apply step described here concerns existing tasks linked through reviewed source adoption; it does not create new native tasks.
1. Establish which schedule you are reviewing
Start with the current retained source import and confirm that its activities are the ones the project team uses. Review retained schedule checks exact source identifiers and linked records before adoption. Similar names are not enough to establish a match.
Adoption initializes a project’s first Planner version while keeping existing task IDs and references. It does not overwrite an existing Planner head or move field dates. Manual activities, manual edits or unresolved mappings can block it. Resolve the underlying issue; deleting records to clear a blocker can destroy information the review was meant to protect.
Reviewing and adopting the source requires admin access to Schedule, Submittals and CRM, with those tools enabled. The same cross-tool permissions apply to reviewing and applying linked task dates.
2. Check the inputs that explain a date
Take one sequence the team understands, such as excavation followed by an inspection. Check the calendar assigned to each activity, working weekdays, hours per day and non-working exceptions. A duration and a calendar work together; a finish date alone does not explain the working pattern.
Then check dependency direction, relationship type, lag and date constraints. A copied date may look plausible while representing the wrong handoff. Retained calendars with detailed shifts keep that pattern; the simple calendar editor does not flatten them into a standard week.
Save and calculate. Read the reported scheduling issues as well as the dates and float. A saved calculation is a result to review, not evidence that every project assumption is correct.
3. Compare the proposed changes to the actual task records
Open Review task date changes after saving. Unsaved edits disable this review so that the preview refers to the saved plan.
For each changed row, compare current and calculated start, finish and critical flags. Derived summary rows are identified separately: their dates span their mapped descendants, and their critical flag reflects whether a descendant is critical. Unchanged mapped tasks count toward the review but do not appear as changed rows.
Use the review to answer concrete questions:
- Does the changed sequence match the calendar and dependency edits you intended?
- Are the task identities the existing records the team recognizes?
- Do the summary date ranges make sense for their child activities?
- Are there blockers requiring a new source review or reconciliation?
Apply only after the review is clear. The app rechecks the version, calculation and reviewed task snapshot. A conflict means refresh and review again; it is not a reason to repeatedly submit an old digest.
4. Check the connected records after applying
Successful application updates the existing tasks’ start, finish and critical flags. Task IDs, privacy, assignments, progress, baseline dates and actual dates stay intact. List, Lookahead, Calendar and Gantt read those task records, as do linked submittal task displays.
That does not reschedule every connected process. Submittal due, procurement and required-on-site dates remain independent. CRM milestone snapshots may need a renewed source review, and applying schedule dates does not publish customer updates. Review those consequences with the people who own the records.
Duration-weighted progress and live date-based reports can change when task date ranges change, even if the stored percent complete does not. Historical analytics snapshots remain historical.
5. Read criticality with its source
Schedule distinguishes a valid applied Planner result from the legacy calendar-day calculation. When published authority is stale or cannot be verified, criticality is unavailable. A suppressed badge in that state does not mean the task is noncritical.
Also check which tasks the applied calculation covers. A retained or manually added task can remain visible without belonging to that calculation. Its result is unknown; it should not be counted as confirmed noncritical just because it lacks a critical badge. Review the selected schedule and the source of its criticality before comparing results between revisions.
Analytics currently describes stored critical flags; it does not validate their freshness. Use Schedule’s criticality status before making a recovery decision from a flagged-task count.
The value of this workflow is a reviewable transition: the team can discuss the saved plan before updating the records used in the field, then check the connected consequences afterward. Saving the next Planner version still does not apply it automatically.
Use the Schedule guide for permissions and current limits, the Planner overview for the workspace, or the Schedule API workflow to implement the same boundaries in an integration.
Bring the weekly schedule review checklist to the meeting to track the selected schedule, decisions and connected follow-up.
Share this article