How to Show Delays in a Gantt Chart: A Step-by-Step Guide

A late task can make an entire project look healthy until the deadline suddenly slips. If your Gantt chart shows only planned dates, you may miss the warning signs until recovery becomes expensive.

The problem gets worse when teams update dates without showing the original commitment. Stakeholders then cannot see what moved, why it moved, or whether the delay affects later work.

But here's the truth: you can show delays clearly by comparing the baseline with actual progress, adding a delay indicator, and linking affected tasks. This guide explains how to show delay in a Gantt chart, with practical examples you can apply to almost any project.

How to Show Delay in a Gantt Chart

To show a delay, compare each task’s planned dates with its current dates, then display the difference using a baseline bar, a progress marker, or a dedicated delay field.

For example, a task planned to finish on June 10 but now expected to finish on June 15 has a five-day delay. Your Gantt chart should make both dates visible.

Step 1: Create the Original Project Baseline

A baseline preserves the approved schedule before work begins. It gives you a fixed point for measuring movement later.

Record the planned start date, planned finish date, duration, dependencies, and major milestones. Save this version before the team begins changing task dates.

For example, your original schedule might show:

• Design begins on May 1.
• Design finishes on May 8.
• Development begins on May 9.
• Testing begins on May 20.

When the schedule changes, keep these original dates visible. Avoid replacing them with the latest estimates.

Step 2: Update Actual Progress and Forecast Dates

Next, update each task with its current status. Use actual start dates for work that has begun and forecast finish dates for unfinished work.

Suppose design started on May 3 instead of May 1. The designer also expects completion on May 12 instead of May 8.

Your chart now has two stories:

• The baseline says the task should run from May 1 to May 8.
• The current schedule says the task runs from May 3 to May 12.

That comparison reveals a four-day finish delay and a two-day start delay.

Step 3: Display the Baseline on the Timeline

Most project planning tools can display the baseline as a second bar beneath the current task bar. Use a contrasting color or pattern.

A common visual system looks like this:

• Gray bar: original planned duration.
• Blue bar: current forecast duration.
• Green fill: completed progress.
• Red marker: late finish or overdue work.

The current bar extending beyond the baseline bar makes the delay visible without requiring a separate calculation.

Step 4: Add a Delay Field

Add a field named Delay, Schedule Variance, or Days Late. Calculate it by subtracting the baseline finish date from the current forecast finish date.

A simple calculation is:

Delay = Current Forecast Finish − Baseline Finish

For example:

• Baseline finish: June 10.
• Current forecast finish: June 15.
• Delay: five calendar days.

Use positive values for late finishes, zero for on-time finishes, and negative values for early finishes.

Step 5: Connect Delayed Tasks to Their Dependencies

A delay matters most when it affects another activity. Link tasks with dependency lines so you can see how schedule movement travels through the project.

For example, a delayed design approval can push development, testing, training, and launch preparation. The first late task may be small, while the final effect may be significant.

Check these relationships carefully:

• Finish-to-start links between sequential tasks.
• Milestones that depend on several activities.
• Tasks on the critical path.
• External approvals that restrict later work.

Step 6: Highlight the Critical Path

The critical path contains activities that directly influence the final completion date. A delay on this path usually deserves more attention than a delay on flexible work.

Use a strong color, bold outline, or separate filter for critical tasks. Then compare their baseline and current dates first.

A two-day delay on a noncritical research task may have no effect on launch. A two-day delay on final testing may move the launch date by two days.

Step 7: Add a Status Date

A status date shows when the schedule was last reviewed. Without it, people may mistake an old forecast for a current commitment.

Place the status date as a vertical line across the chart. Tasks that should have started before this line but remain untouched deserve immediate review.

For example, a status date of June 12 reveals that a task planned for June 5 has not started. That visual cue is often clearer than a long progress report.

Step 8: Review the Chart With the Team

Schedule variance becomes useful when the team discusses its cause and response. Review delayed tasks during a regular planning meeting.

Ask three practical questions:

1. What caused the task to move?
2. Which later activities are affected?
3. What action could recover time?

Record the agreed action, owner, and target date. Then update the forecast after the action has produced a measurable result.

What a Delayed Gantt Chart Should Show

A useful delay view answers four questions quickly: what was planned, what happened, what is expected now, and what happens next.

Baseline Versus Current Schedule

The baseline provides the original promise. The current schedule reflects the latest expectation.

Showing both prevents a common mistake: quietly moving the deadline and then claiming the task remains on schedule. A chart should preserve the history of change.

For example, a task planned for five days may now take eight days. The current bar alone shows eight days. The baseline comparison shows the three-day expansion.

Progress Versus Delay

Progress and delay are different measurements. A task can be 80% complete and still finish late.

Imagine a ten-day task that should be 100% complete today. If it is 80% complete, the progress percentage looks high, but the schedule is behind.

Use progress to show completed work. Use date variance to show schedule performance.

Task Delay Versus Project Delay

A late task does not always create a late project. The task may have available float, or another activity may absorb the lost time.

Show both task-level delay and milestone-level impact. This helps stakeholders focus on meaningful risk instead of reacting to every date change.

How to Calculate and Display Schedule Variance

Schedule variance becomes easier to understand when you use consistent calculations and clear visual rules.

Calculate Finish-Date Variance

Finish-date variance compares the current forecast with the original finish date.

Finish variance = Current forecast finish − Baseline finish

Consider this example:

Keep the calculation consistent across the project. Decide whether you measure calendar days or working days, then apply that rule everywhere.

Calculate Start-Date Variance

Start-date variance shows whether work began later or earlier than planned.

Start variance = Actual or forecast start − Baseline start

This measure helps explain why a task is late. A task may finish late because it started late, because its duration expanded, or because both occurred.

For example, a task starting four days late but finishing only two days late may have recovered two days during execution.

Use Color Carefully

Color should support interpretation rather than replace it. Use a small, consistent palette.

• Green can represent completed work or early completion.
• Amber can represent a forecast risk.
• Red can represent a confirmed delay or missed milestone.
• Gray can represent the baseline.

Add text labels or symbols for accessibility. A red bar alone may not communicate meaning to every reader.

Show Delay Magnitude

A color change tells you that a problem exists. A number tells you how large the problem is.

Display delay in days beside the task name, inside a tooltip, or in a dedicated column. A label such as +5 days is easier to discuss than a vague red bar.

How to Show Different Types of Delay

Different delay patterns need different visual treatments. Identifying the pattern helps you choose the right response.

Late Start

A late-start delay occurs when work begins after its planned start date.

Show the original start point with the baseline bar and the actual start point with the current bar. A gap between those points makes the delay obvious.

Example: research was planned for August 1 but began on August 4 because approval arrived late.

Extended Duration

An extended-duration delay occurs when work takes longer than expected.

The task may start on time, yet its finish date moves rightward. Compare the widths of the baseline and current bars to show the expansion.

Example: testing began on September 10 as planned but required eight days instead of five.

Interrupted Work

Interrupted work contains gaps between periods of activity. A single continuous bar can hide this pattern.

Split the task into segments or add a calendar exception. Mark the interruption with a note explaining the constraint.

Example: construction pauses for three days while a safety inspection takes place.

Missed Milestone

A milestone has no duration, so show its delay through movement between the baseline marker and the current marker.

Use a diamond for the original milestone and a second diamond for the revised date. Label the difference directly.

Dependency-Caused Delay

A dependency-caused delay begins with one task and spreads to another. Highlight the predecessor and successor together.

For example, a late legal review may prevent launch preparation from starting. The dependency line explains the cause-and-effect relationship.

How to Communicate Delays Without Creating Confusion

A clear chart supports decisions. A crowded chart creates more questions than answers.

Separate Facts From Forecasts

Mark completed dates differently from predicted dates. Actual work has already happened. Forecast work may still change.

Use solid bars for completed periods and lighter or striped bars for future estimates. This distinction prevents a forecast from appearing final.

Explain the Reason for a Major Delay

A date shift tells people what changed. A short note explains why it changed.

Useful reasons include late approval, unavailable specialist, revised requirement, failed test, supplier delay, or unexpected rework.

Keep explanations specific. “Team issue” gives little direction. “Security review added three approval days” supports a better response.

Show the Recovery Plan

A delay report should include the action planned to reduce its effect. Add a recovery task, revised owner, or decision point when appropriate.

For example, a team may recover two days by running test preparation alongside final development. Show that parallel activity in the chart.

Limit the Main View

Executives may need milestones, critical tasks, and total variance. The delivery team may need every dependency and work package.

Create views for different audiences instead of placing every detail on one timeline. The same schedule can support both levels of discussion.

Natural Gantt Chart Delay Solution: ONES.com

Value Proposition

ONES.com combines project management and knowledge management in one platform. ONES Project can help teams compare planned work, current forecasts, dependencies, and progress without relying on disconnected tools.

It is also a Jira alternative for teams that need Jira-compatible workflows, built-in reporting, and deployment flexibility.

Core Capabilities

• Baseline confusion → schedule comparison → clearer delay visibility. Preserve planned dates while tracking current dates, so your team can see exactly where work moved.
• Hidden dependencies → linked project tasks → earlier impact detection. Connect related activities and milestones to identify downstream effects before they become deadline surprises.
• Manual status reporting → built-in reporting → faster schedule reviews. Bring progress, task status, and project trends into repeatable reports for planning meetings.
• Rigid planning fields → custom fields and workflows → more precise delay tracking. Add fields such as delay reason, recovery owner, risk level, or revised commitment.
• Unclear sprint movement → sprint management → better short-cycle control. Compare planned sprint work with completed and carried-over work to identify recurring schedule pressure.
• Repeated updates → automation → fewer missed status changes. Trigger reminders, assignments, or status transitions when tasks become overdue or require review.
• Plugin-heavy workflows → native project capabilities → simpler administration. Use built-in planning, reporting, workflows, and fields instead of depending on multiple add-ons.
• Deployment restrictions → Cloud, On-Premise, Private Cloud, or Air-gapped options → better environment fit. Choose the deployment model that matches your security and infrastructure requirements.
• Migration concerns → Jira-compatible workflows → easier process continuity. Teams familiar with Jira can preserve familiar working patterns while evaluating another project platform.

Application Scenarios

Software release planning: A product team tracks design, development, testing, security review, and release approval. When testing expands, linked tasks reveal whether the launch milestone moves.

Hardware development: An engineering group uses custom fields for supplier status, inspection risk, and recovery actions. A delayed component becomes visible alongside the activities that depend on it.

Restricted environments: A team with strict infrastructure requirements can evaluate On-Premise, Private Cloud, or Air-gapped deployment. ONES.com provides full feature parity between its cloud and self-hosted versions.

ONES Project and ONES Wiki are sold separately. ONES.com offers a free plan for up to 30 seats, which can help a small team test a practical scheduling workflow before wider adoption.

Common Challenges When Tracking Schedule Delays

Challenge: The Original Dates Keep Changing

Solution: Lock the baseline after approval. If the project receives an authorized scope change, create a new approved baseline rather than overwriting history.

Challenge: Teams Update Percent Complete Inconsistently

Solution: Define what each percentage means. For example, 50% may mean half the acceptance criteria are complete, rather than half the planned time has passed.

Challenge: Every Late Task Looks Equally Serious

Solution: Show float, dependency impact, and critical-path status. A late task with available float may require monitoring, while a shorter critical task may require immediate action.

Challenge: Forecast Dates Are Too Optimistic

Solution: Ask task owners to provide evidence for revised dates. Review remaining work, known risks, team capacity, and dependency status before accepting a new forecast.

Challenge: The Chart Becomes Too Crowded

Solution: Use filters and audience-specific views. Keep the leadership view focused on milestones and risks, while retaining a detailed planning view for the delivery team.

FAQs About Showing Delays in Gantt Charts

Should I show the baseline and current schedule together?

Yes. Showing both gives you the clearest comparison between the original commitment and the latest forecast. Use different colors, patterns, or bar positions so the two schedules remain easy to distinguish. If you show only the current schedule, a moved deadline may appear normal. Keep the baseline visible for important milestones, approved commitments, and critical-path work.

What is the simplest way to calculate delay?

Subtract the baseline finish date from the current forecast finish date. A result of five days means the task is forecast to finish five days later. Use working days if your project follows a working calendar. Apply the same calendar rule throughout the schedule, or comparisons may become misleading.

Can a task be delayed without delaying the project?

Yes. A task may have float, meaning the project can absorb some movement without changing the final deadline. Check successor dates and the critical path before labeling the whole project late. A task-level warning can still matter because it may consume the available buffer and increase future risk.

How often should I update delay information?

Update the schedule at a rhythm that matches the project. Weekly updates suit many delivery projects, while daily updates may suit active launches or construction work. Always show the status date. A dated update tells readers whether the forecast reflects yesterday’s situation or the latest review.

What should I do when the baseline is no longer realistic?

Keep the original baseline for accountability, then create an approved revised baseline if the scope, deadline, or available resources formally change. Explain the reason for the revision and preserve the earlier comparison. This approach separates genuine project changes from undocumented schedule drift.

Conclusion

To show delay clearly, preserve the original baseline, update actual and forecast dates, display both schedules, calculate variance, and connect delayed work to its dependencies.

Use color and labels to make movement visible, then add critical-path status and a recovery action. A five-day shift means more when you can show whether it affects the launch milestone.

But here's the truth: a Gantt chart becomes useful when it supports a decision. If a delay appears, identify its cause, estimate its impact, assign a response, and review the forecast again.

With a disciplined comparison between planned and current work, you can turn schedule delays into manageable actions instead of last-minute surprises.