What Data Moves Between Master and Field Schedules in Planera?
This article explains how data flows between the Master Schedule (Master Schedule) and the Field Schedule (Field Schedule) in Planera - both at the time of Field Schedule creation and during ongoing updates. It also covers how data behaves across Field Schedule versions.
From Master Schedule to Field Schedule
When a Field Schedule version is created, it pulls in a snapshot of data from the Master Schedule. After this point, the Field Schedule is independent and no longer receives updates from the Master Schedule (with the exception of the critical path).
This design ensures that field teams have a stable baseline to plan against, without disruptions from ongoing changes in the master plan.
What flows from Master Schedule to Field Schedule:
Activities: All planned and actualized activities that overlap with the Field Schedule date range
Calendar, Resources, and Codes: Carried over from Master Schedule
Critical Path: Updated dynamically from Master Schedule, even after Field Schedule creation
Data Date: Initially set to "From Date" during creation; should be updated as the schedule is used
User Access & Permissions:
Master Schedule users are not automatically added to Field Schedule
Permissions can differ between Master Schedule and Field Schedule
Users can be invited directly to Field Schedule without needing Master Schedule access
What does not flow from Master Schedule to Field Schedule:
Comments from Master Schedule
Ongoing updates to Master Schedule activities, logic, or data (after Field Schedule creation)
From Field Schedule to Master Schedule
Once a Field Schedule is created, certain updates can flow back to the Master Schedule—but only if the Field Schedule is scheduled (i.e., not stale).
What flows from Field Schedule to Master Schedule:
Progress updates: Actual Start, Actual Finish, Expected Finish
What does not flow to Master Schedule:
Tasks created in Field Schedule
New or edited activity groups
Logic, codes, and resource changes
Calendar or resource reassignments
Percent Plan Complete (PPC)
Field Schedule Variance Codes
Note: Field Schedule details are often more granular than what’s needed in the Master Schedule. This intentional separation helps keep the master schedule clean and focused.
Between Field Schedule Versions
When a new Field Schedule version is created, some data is carried forward and some is updated based on the latest Master Schedule.
What is carried forward from the previous Field Schedule version:
Progress updates
Task details inside an Activity
Activities and tasks that are not complete as of the new Field Schedule "From Date"
What is brought in fresh from Master Schedule:
New activities and milestones, along with their relationships
Updated critical path (re-marked based on latest Master Schedule)
What is not updated in Field Schedule even if changed in Master Schedule:
Logic (e.g., if relationships between activities change in Master Schedule)
Codes or resource assignments
Any other edits to existing Field Schedule activities
Completed activities are archived and removed from the current Field Schedule version but remain accessible in the previous one.
Summary Table
Data Type / Action | MS → FS (At FS creation) | FS → MS (Progress update) | New FS Versions | Notes / Rationale |
Activities (planned & actualized) | ✅ Pulled in if within date range | 🚫 | ✅ Retained or archived | Snapshot-based transfer to enable stable FS planning |
New Activities / Groups | ✅ New MS items pulled into new FS version | 🚫 | ✅ Added in new FS version only | New FS version required to reflect MS changes |
Activity Group Changes | ✅ If from MS at creation | 🚫 | 🚫 | FS does not sync ongoing MS changes post-creation |
Progress Updates (Actual/Expected Finish) | 🚫 | ✅ If FS is scheduled (not stale) | ✅ Carried forward | Enables real-time field progress to be visible in MS |
Logic Changes | 🚫 | 🚫 | 🚫 | FS keeps original logic snapshot; avoids MS overwriting FS planning |
Calendar / Resources / Codes | ✅ Included at time of FS creation | 🚫 | 🚫 | No continuous sync; keeps FS localized and stable |
Critical Path | ✅ Preserved from latest MS | 🚫 | ✅Pulled in for each new FS version | Only MS-to-FS data that stays current without new FS version |
Comments | 🚫 | 🚫 | 🚫 | Comments are local to MS or FS only |
Tasks | 🚫 | 🚫 | ✅ Carried forward if incomplete | FS tasks are more detailed and stay within FS |
Variance Codes | 🚫 | 🚫 | 🚫 | Stay within FS for field-specific tracking |
PPC (Percent Plan Complete) | FS level calculation | MS level calculation | 🚫 | Localized to FS; not rolled up |
FS Task Assignments | — | 🚫 | ✅ Retained | Do not inherit resource/code assignments from MS parent |
Resource Rollups | — | 🚫 | — | FS-assigned resources do not roll up to enterprise dashboards |
Completed Activities | — | — | ✅ Archived from current FS | Visible in previous FS versions only |
User Access / Permissions | Manual | Manual | — | Access & permissions differ between MS and FS |
Data Date | Set as "From Date". Should be updated as needed | — | Should be updated manually | Used for filtering and version control |