← VCE Data Analytics U3O2

Monitoring progress on a Gantt chart

Shading the completed part of each task bar on a Gantt chart, then comparing it with the planned dates to see whether the task is on time or late.

Part of: VCE Data Analytics - U3O2 - Analysis and Design — Module 18

Understanding Monitoring progress on a Gantt chart in VCE Data Analytics U3O2

What it does: The shaded portion is compared with the planned start and end dates to judge whether the task is on time. Adjusting the plan and recording the reason keeps the Gantt chart accurate and documents the cause of the change. Progress shading fills the part of the bar that matches the work completed. The full bar still shows the planned duration. A good entry states the old dates, the new dates and the reason for the change. Comparing the end of the shading with today's date line is how a student spots a late task on a Gantt chart.

Common mistakes: The expected percent complete is days gone divided by the task duration, times 100. The broken line divides the duration by the days gone, which gives the wrong number. It should be exp <- daysGone / dur * 100. If the shaded percent is at or above the expected percent, the task is on time. The ELSE branch must set status <- On time, otherwise every task is reported as late.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add Monitoring progress on a Gantt chart to a class →

This module's key terms are also in a printable crossword (Modules 3–31) and word search (Modules 3–146).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
A task bar runs from Monday to Friday. By Wednesday evening it is shaded about 60% of the way along. Which describes how to read progress shading?
The shaded part shows the days that were originally plannedThe shaded part shows the percentage of the task that is complete
Matches
Task planned 1-10 Mar, 100% shaded, but work is only half done
↓
The shading does not match the real progress. It should be shaded only to about 50% to show actual work completed.
Applying
Meanings
Term
Progress shading
Meaning
Shading the completed part of each task bar on a Gantt chart, then comparing it with the planned dates to see whether the task is on time or late.
Practice
IF percentShaded < percentPlanned THEN
Testing
Gaps
=D2C2
Check Answer
Spots
2daysGone <- 4
3exp <- dur / daysGone * 100

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Desert Jerboa' badge — High Jumper, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. A task bar runs from Monday to Friday. By Wednesday evening it is shaded about 60% of the way along. Which describes how to read progress shading?
A. The shaded part shows the percentage of the task that is complete ✓
B. The shaded part shows the days that were originally planned
Progress shading fills the part of the bar that matches the work completed. The full bar still shows the planned duration.
2. Today is the end of Day 6. A task was planned to finish on Day 5, but its bar is only shaded to 70%. What is the task's status?
A. On time, because more than half of the bar is shaded
B. Late, because the planned end date has passed and it is not fully shaded ✓
Compare the shading with the planned dates. A task past its end date with unshaded work remaining is behind schedule.
3. Which is the best way to spot a late task on a Gantt chart?
A. Check that every task bar is the same length
B. Draw a line at today's date and check that each bar is shaded up to it ✓
The bar lengths show planned duration. To judge progress, compare the shaded amount with where today's date falls on the timeline.
4. A task has a planned duration of 10 days. After 5 days it is shaded to 50%. Is it on track?
A. Yes, the shading matches the time that has passed ✓
B. No, it should be 100% shaded after 5 days
Half of the planned time has passed and half of the work is done, so progress matches the plan.
5. A data collection task is late and delays the tasks after it. What should the project manager do?
A. Adjust the plan, such as moving later tasks, and record why the change was made ✓
B. Leave the original dates unchanged and hope the team catches up
Adjusting the plan keeps the Gantt chart accurate. Recording the reason in the project log shows what changed and why.

Match the Pairs

Task bar shaded 60% → 60% of the task is complete, so the shaded part of the bar shows the work done so far
Shading ends before today's date line → The task is behind schedule (late) because less work is done than the plan required by today
Shade the completed part of a task bar so progress can be compared with the planned dates → Design task: bar 1-10 Mar, shaded to 5 Mar (50%)
When the plan changes, adjust the bar and record why in the project log → Testing moved to 15-19 Mar | Reason: survey data arrived late
Task planned 1-10 Mar, 100% shaded, but work is only half done → The shading does not match the real progress. It should be shaded only to about 50% to show actual work completed.
Task is late, so the end date is changed on the chart with no note in the log → The change to the plan was not recorded. The reason for the adjustment must be written in the project log.

Key Term

Progress shading
Shading the completed part of each task bar on a Gantt chart, then comparing it with the planned dates to see whether the task is on time or late.

Fill in the Blanks

1. =D2/C2
Hint: Type the operator that divides days completed by planned duration to give percent complete.
2. =IF(AND(E2<TODAY(),F2<1),"Late","On time")
Hint: Type the logical function that needs both conditions true: the end date has passed and the task is not 100% complete.
3. IF actualPercent < plannedPercent THEN status ← "Late" END IF
Hint: Type the comparison operator that shows actual progress is behind the planned progress.
4. newEnd ← oldEnd + delayDays log ← "Delay: supplier was late"
Hint: Type the operator that pushes the end date later by the number of delay days when adjusting the plan.
5. =C2*F2
Hint: Type the operator that multiplies the planned duration by percent complete to find how much of the bar to shade.

Spot the Error

Question 1
A dur <- 10
B daysGone <- 4
C exp <- dur / daysGone * 100
D pct <- 30
E IF pct < exp THEN
F status <- Late
Line C — The expected percent complete is days gone divided by the task duration, times 100. The broken line divides the duration by the days gone, which gives the wrong number. It should be exp <- daysGone / dur * 100.
Question 2
A READ pct, expected
B IF pct < expected THEN
C status <- Late
D ELSE status <- Late
Line D — If the shaded percent is at or above the expected percent, the task is on time. The ELSE branch must set status <- On time, otherwise every task is reported as late.
Question 3
A pct <- done / total * 10
B width <- pct * barLen / 100
C OUTPUT width
Line A — Percent complete is done divided by total, multiplied by 100. Multiplying by 10 gives a value ten times too small, so the shading would be wrong. It should be pct <- done / total * 100.
Question 4
A READ plannedEnd, today
B IF today < plannedEnd THEN
C IF pct < 100 THEN
D status <- Late
E ENDIF
F ENDIF
Line B — A task can only be late once today is after its planned end date. Using < checks tasks whose end date has not arrived yet. It should be IF today > plannedEnd THEN.
Question 5
A READ oldEnd, delay, reason
B newEnd <- oldEnd + delay
C LOG oldEnd, newEnd
D REDRAW bar TO newEnd
Line C — When the plan is adjusted, the log must record why the change was made. The reason is missing from this line. It should be LOG oldEnd, newEnd, reason.

Student with a class code? Join your class →