Engineering Knowledge Cards.
Confidence HighUpdated 2026-10-18

The practical progress vanguard line: definition, two methods of fixing the front points and the plotting steps, the lead/lag rule from the point's position relative to the check-date grid line, and the order of converting lag through total (free) float to judge the effect on total duration (JGJ/T 121-2015 clauses 2.1.39, 4.4.1~4.4.3, 7.2.1, 7.2.3)

The reference for reading the vanguard line is the vertical grid line of the check date: a front point to its left is lag, to its right is lead, on it means on programme; lag is read as the horizontal projection length. The effect on total duration follows 'consume float first, then judge duration': for critical activities (zero total float) the whole lag becomes delay; for non-critical activities, lag within total float leaves the total duration unchanged and only the excess delays it, delay = lag - total float (lag landing on a wave line only consumes free float and is not lag).

Applicable Codes

  • JGJ/T 121-2015 · Specification for Engineering Network Planning Technology 第 2.1.39、4.4.1、4.4.3、7.2.1、7.2.3 条
  • GB/T 50358-2017 · Code for Management of Engineering Procurement Construction (EPC) Projects 第 10.3.3 条
  • 一级建造师《建设工程项目管理》1Z203030

Positioning

How to plot the practical progress vanguard line on an activity-on-arrow time-scaled network at a check date (say end of week 6), connect the points, read lead or lag from each point's position against the check-date line, and convert lag through free and total float into a judgement on total duration. Basis: JGJ/T 121-2015, Technical Specification for Engineering Network Planning.

Core conclusions

1. Definition (clause 2.1.39) "Practical progress vanguard line: on a time-scaled network diagram, the folded line connecting the front points reached by the actual progress of each activity at the check moment." The line itself marks "where progress actually stands"; the reference is always the vertical line of the check date - not the arrow tail, not the node.

2. Geometric basis (clause 4.4.1) "All symbols in an activity-on-arrow time-scaled network must have horizontal projections on the time scale corresponding to their time parameters. Node centres must align with the corresponding time scale positions." The horizontal projection of an arrow is its duration, so horizontal distances read directly as time deviations.

3. Reading rules (the check-date vertical is the sole reference)

  • Point left of the vertical: progress lags, lag = check-date scale - point scale (horizontal projection, in time units);
  • Point right of the vertical: progress leads, lead = point scale - check-date scale;
  • On the vertical: on programme, deviation 0;
  • Point on the activity's wave line: the activity is effectively finished, only consuming free float - not lag (clause 4.4.3 item 3: "the free float of an activity is the horizontal projection length of the wave-line part of its arrow").

4. Plotting rules (clause 7.2.1) Original text: "Checking a network shall collect actual execution data and record them as follows. 1 With time-scaled networks, draw the practical progress vanguard line to record execution; the vanguard line may be drawn in a distinctive line style; adjacent vanguard lines from different check dates may use dash-dot lines or different colours. 2 With non-time-scaled networks, record execution directly on the diagram in words, figures, or a table." Two methods of fixing the front points (clause 7.2.1 commentary):

  1. By the share of physical quantity completed: "the arrow length on the time-scaled diagram corresponds to the activity's duration and is proportional to its physical quantity; when a fraction of the quantity is done, mark the vanguard point at that fraction of the arrow from its start, left to right."
  2. By time still needed: "for activities whose duration cannot be measured by physical quantity, estimate by the original method; to fix the vanguard position at the check time, estimate the time still needed to complete and mark the point backwards from the arrow's end, right to left." Steps: 1) draw the vertical through the check-date scale as the sole reference; 2) for every activity in progress, fix its front point by one of the two methods (completed: at the finish end; not started: at the start); 3) from above the time axis, join the points top to bottom back to the axis into a folded line through all current activities, each vertex on some arrow; 4) measure each vertex's horizontal distance to the vertical and read nature and size per section 3; 5) overlay several check dates in different styles/colours to expose the deviation trend.

5. Effect on total duration (consume float first, then judge duration)

  1. Critical activity (zero total float): lag cannot be absorbed - the lag equals the delay of the total duration; adjust following durations or logic.
  2. Non-critical activity: consume its own float first - lag <= free float affects only successors' early starts, the planned duration stands; free float < lag <= total float delays successors but not the total duration; lag > total float delays the total duration by the excess, delay = lag - total float, and the activity turns critical.
  3. Total float here must be derived "right to left" per clause 4.4.3 item 4, which also sets the computed duration as "the difference of the time-scale values at the end and start nodes".

6. Analysing the check (clause 7.2.3) "1 Where planned and actual progress seriously diverge, the network shall be adjusted. 2 For time-scaled networks, use the drawn vanguard line to analyse execution and trends, forecast future progress and locate the causes of deviation. 3 For non-time-scaled networks, record implementation per Table 7.2.3 and compute and judge the unfinished activities." The commentary adds: judge each activity normal, ahead or delayed; forecast whether the planned duration will be met, bettered or missed.

7. Division of labour with earned value (GB/T 50358-2017 clause 10.3.3) "Schedule deviation analysis shall proceed: 1 analyse schedule deviation by earned-value management; 2 apply network techniques to analyse the effect on progress, watching time deviations of activities on the critical path." Its commentary stresses that earned value "cannot identify the critical path in the schedule and cannot replace network analysis"; when predicted activity lag may hit progress, use the network's critical activities, free and total floats. Duration control: where the planned duration equals the contract duration, delays on the critical path must be adjusted back; "where activity delay is within free float, the planned duration need not be adjusted"; beyond free float but not affecting the planned duration, handle by the successors' nature; where the planned duration is shorter than the contract, any extension may not exceed the contract duration.

Applicable boundaries

  • The vanguard line applies only to time-scaled networks; non-time-scaled checks use on-diagram words, figures or tables (clause 7.2.1 item 2), not vanguard lines.
  • Direct reading requires the early-time version: the tail node scale is the early start; without a wave line the head node scale is the early finish, with one, the right end of the solid line (clause 4.4.3 item 2).
  • "Lag - total float = delay" holds for a single activity lagging alone; several activities lagging together, or lag changing the critical path, require recomputation on the network - do not add the excesses.
  • A check reflects that moment only; trends need several overlaid lines; only "serious divergence" triggers adjustment (clause 7.2.3).
  • This card judges schedule deviation; cost deviation uses earned value (SV, SPI, CV) - neither replaces the other.

Further reading

  • JGJ/T 121-2015 clauses 2.1.39, 4.4.1, 4.4.3, 7.2.1 (with Figures 13 and 14), 7.2.3 and Table 7.2.3; GB/T 50358-2017 clause 10.3.3; first-class constructor, Construction Project Management, 1Z203030.

Keywords

  • 实际进度前锋线
  • 前锋线
  • 时标网络计划
  • 进度偏差
  • total float
  • 自由时差
  • 超前滞后判定
  • 网络计划检查