Protect the approved plan with baselines
Save the baseline and compare it with the live schedule. Every reschedule remains explainable and teams measure drift without erasing history.
What you'll learn
How protect the approved plan with baselines works inside Perfour.
What information you need and how it stays connected to Schedules.
How to preserve traceability and find the record later.
How to complete baseline comparison
- 01
Understand the objective
The schedule organizes packages, groups, tasks and milestones over time and expresses execution logic through dependencies. Perfour provides Gantt and list views for planning and updates. This guide focuses on protect the approved plan with baselines.
- 02
Prepare baseline comparison
Define activities with name, start, finish, duration, priority, status and owners. Add predecessors and successors to represent what must finish before the next activity begins.
- 03
Complete the workflow in Perfour
Build packages and activities, connect dependencies, review the sequence in Gantt and update actual dates and progress. Analyze changes for their effect on milestones and project finish. Approved references measure drift without erasing history.
- 04
Review relationships and traceability
The schedule shares context with tasks, RFIs, Daily Logs and budget items. Relationships explain why an activity was delayed and which cost or decision it affects. Look for unassigned activities, impossible dates, circular dependencies, overdue milestones and unsupported progress. Always compare the live plan with the available approved reference.
Frequently asked questions
What is baseline comparison and what is it for?+
The schedule organizes packages, groups, tasks and milestones over time and expresses execution logic through dependencies. Perfour provides Gantt and list views for planning and updates.
What information do I need to protect the approved plan with baselines?+
Define activities with name, start, finish, duration, priority, status and owners. Add predecessors and successors to represent what must finish before the next activity begins.
How is this process completed in Perfour?+
Build packages and activities, connect dependencies, review the sequence in Gantt and update actual dates and progress. Analyze changes for their effect on milestones and project finish. Approved references measure drift without erasing history.
Which other modules does it connect with?+
The schedule shares context with tasks, RFIs, Daily Logs and budget items. Relationships explain why an activity was delayed and which cost or decision it affects.
What should I check before considering it complete?+
Look for unassigned activities, impossible dates, circular dependencies, overdue milestones and unsupported progress. Always compare the live plan with the available approved reference.