BASELINE AND SCHEDULE CONTROL

Keep the agreed plan visible as site delivery changes.

Jenasaro separates the agreed baseline from current activity status. Planners can review schedule logic and milestones while construction teams record commitments and completion, making movement against the plan easier to see.

Understand what each bar represents

Grey: baseline intent

The baseline carries the planned dates, durations, relationships and milestone logic used to structure delivery.

Blue: current work

Current status reflects the activity’s commitments and actual start. Uncommitted, unfinished work follows its baseline or moves forward to today when overdue.

Delay visibility

Variance indicators help the team identify movement and ask what is preventing work from being completed.

Controlled mitigation

Lock the baseline and permit selected activities to be reviewed for mitigation, keeping changes deliberate.

Relationship links use baseline dates. A change to one activity’s blue status bar does not automatically reschedule every linked activity. Planners review programme logic separately from recording delivery status.

Retain the context of incomplete work

When committed work needs more time, additional working days can extend the production plan while keeping the original baseline visible. For work that needs a pause, baseline sections can represent the planned interruption while retaining the task’s identity and links.

Use the schedule and network views to review dependencies and milestone implications. Use the production review to understand commitment reliability and reasons for non-completion.

ILLUSTRATIVE PROJECT SCENARIO

Example: an installation misses its planned start

  1. Review the installation’s grey baseline against its blue current status and delay indication.
  2. Record the access constraint and identify who needs to release the area.
  3. Confirm a realistic commitment with the installation team once the work is ready.
  4. Review affected baseline relationships and milestones before making a controlled mitigation change.

Decision to make: Can the agreed milestone still be protected, and which planning decision needs approval?

Questions from project teams

What is the difference between a baseline and a commitment?

The baseline records the planned timing and logic. A commitment records the work a team has agreed to deliver. Showing both helps distinguish programme intent from the current production promise.

Does locking the baseline freeze daily progress reporting?

Baseline locking governs baseline editing. Teams can continue using the permitted production workflows to record commitments and completion.

Does a delayed blue bar automatically move all successors?

No. Dependency calculations use the baseline. Current status belongs to the individual activity; planners must review the programme implications.

Can I change only selected baseline activities for mitigation?

Yes. Selected activities can be released for a controlled mitigation review while the baseline remains locked elsewhere.

Explore connected capabilities

See the workflow with your project team.

Tell us about your project, current tools and the work you want to coordinate. We can focus a demonstration on your requirements.

Request a demo