Rules and workflow for determining the extendable days of time from the critical path and total float after the works programme changes (GB/T 50500-2024, Article 8.11.8 three tiers + Article 8.11.7 event-by-event independent accounting)
The extendable days equal 'the actual increment of the overall duration determined through the network programme after the event', not the duration of the event itself: event on the critical path -> the extension equals the delay to that activity (in full); a non-critical activity whose delay D exceeds its total float TF and thereby becomes critical -> the extension is D - TF (the difference); still non-critical after the delay -> 0 days of extension (cost losses may still be claimed separately). The calculation takes the approved programme of the works as the baseline, assesses each claim event independently and accounts for each separately; the knock-on effect of earlier delays on later works must not be counted again (GB/T 50500-2024, Articles 8.11.8 and 8.11.7).
Applicable Codes
- GB/T 50500-2024 · Standard for bills of quantities and valuation for construction works 第8.11.3、8.11.5、8.11.7、8.11.8、8.11.9、8.11.10条
- GB/T 51262-2017 · Code for Construction Cost Appraisal 第5.7.5条
- JGJ/T 121-2015 · Specification for Engineering Network Planning Technology 第2.1.33、5.5.1条
- 《中华人民共和国民法典》第180、590、803、804条
- 法释〔2020〕25号《最高人民法院关于审理建设工程施工合同纠纷案件适用法律问题的解释(一)》第10条
- 法释〔2026〕12号《最高人民法院关于审理建设工程施工合同纠纷案件适用法律问题的解释(二)》第21、23条
- 《中华人民共和国民事诉讼法》(2023修正)第67条
- T/ZBD 100.4-2023 · Work Guideline for Construction Cost Appraisal 第4.9.7条
Topic Positioning
Explains how, after the works programme changes (employer causes, force majeure, design changes, changes in laws and policies, etc.), the extendable days of time are determined and computed from the critical path and the total float of the approved network programme, and the baseline and independence rules the computation must obey.
Core Conclusions
1. Only three tiers (GB/T 50500-2024, Article 8.11.8)
When a delay event occurs, the employer and the contractor may, on the basis of the approved programme of the works, determine whether the event is an activity on the critical path and whether it causes delay to activities on the critical path; in computing the claimed time the parties shall comply with the following:
- where the delay event is an activity on the critical path, the delay is the time claimed;
- where the delay event is an activity off the critical path and the activity becomes an activity on the critical path because the delay exceeds its total float, the difference between the delay and the total float is the time claimed;
- where the activity remains off the critical path after the delay, no claim for time arises. The standard adds: activities on the critical path are decisive for the progress of the whole project and determine its overall duration; prolongation of activities off the critical path gives no claim for time; where a delay event is an activity off the critical path but becomes an activity on the critical path because its execution is pushed later, the prolongation arising after it becomes critical is the claimable time.
2. Baseline and independence rules (Article 8.11.7)
When computing delay (or prolongation) and the resulting claim costs under this section of the standard, the works corresponding to the claimed time must be activities on the critical path, or works whose critical path is altered by the claim event; the extension of time the employer approves to the contractor under the contract must be the extension of the contract time for completion. The employer, facing the contractor's claims for the costs of all delays (or prolongations), must assess each claim event independently, excluding claims for the costs of the corresponding delay (or prolongation) that earlier delays (or prolongations) caused to works carried out later; claim costs arising from extension of time must be accounted for each event independently, without computing claims for the corresponding delay caused to works carried out later.
3. Terms and the basis for identifying the path
Total float: the spare time an activity can use without affecting the duration and the relevant time limits (JGJ/T 121-2015, Article 2.1.33). In a single-code (activity-on-node) network programme, the activities with the least total float are critical activities; a critical path is one on which every activity from the start node to the end node is critical and the interval between every two adjacent critical activities is zero (Article 5.5.1). The critical path, in a network programme for the time for completion, is the path from the start node, along the arrows and through the nodes, to the end node, with the greatest sum of activity durations; a critical activity is an activity on the critical path; the sum of the durations of the critical activities is the duration of the network programme, and progress on the critical activities directly affects it (GB/T 51262-2017, Article 5.7.5).
4. The substantive bases of the right to an extension
Where the employer fails to provide raw materials, equipment, the site, funds or technical data at the agreed time and in the agreed manner, the contractor may extend the date of the works and claim losses such as those from suspension and idle time (Civil Code, Article 803). Where, for reasons attributable to the employer, the works are halted or slowed mid-course, the employer must take measures to remedy or reduce the loss and compensate the contractor for the losses and actual costs so caused, including suspension, idle time, re-handling, relocation of plant and machinery, and stockpiled materials and components (Article 804). Force majeure is an objective situation that cannot be foreseen, avoided or overcome; one who cannot perform civil obligations due to force majeure bears no civil liability (Article 180); where a party cannot perform the contract due to force majeure, it is partly or wholly released from liability according to the effect of the force majeure, but must promptly notify the other party and provide proof within a reasonable period; force majeure occurring after the party has delayed performance does not release it from liability for breach (Article 590).
5. Operating steps
| Step | Key points | Basis |
|---|---|---|
| 1 Take the baseline programme | the 'approved programme of the works' is the sole baseline; fix the version and the approval date; where the programme was approved as revised, analyse in time windows - the original programme before the revision date, the revised one after; no back-solving from a programme rewritten after the event | Article 8.11.8 ('may, on the basis of the approved programme of the works'); GB/T 51262-2017, Article 5.7.5 |
| 2 Attribute and characterise the event | separate employer causes, force majeure, changes in laws and policies, the contractor's own causes and foreseeable risks; only events not caused by the contractor enter the extension computation, and they must match the extension grounds agreed in the contract | Civil Code, Articles 803, 804, 180, 590 |
| 3 Map to activities and locate the path | map the event to concrete activity codes / WBS nodes (not 'the whole project'); read the logic, the duration and the total float; determine whether it is a critical activity or alters the critical path | JGJ/T 121-2015, Articles 2.1.33 and 5.5.1; GB/T 51262-2017, Article 5.7.5 |
| 4 Quantify the delay D | D is the actual delay in days to that activity, not the duration of the event (a 30-day stoppage affecting the activity for only 10 days counts 10); corroborate with construction / supervision logs, stop and resume orders, weather records | Article 8.11.8 |
| 5 Apply the three tiers to get dT | critical activity: D; non-critical with D > TF: D - TF; D no more than TF: 0 | Article 8.11.8 |
| 6 Independent accounting and totalling | sum the extendable days after assessing each event independently; strip out the knock-on of earlier delays on later works and the contractor's own concurrent delay | Article 8.11.7 |
6. The dedicated expert-assessment approach for design changes
Where the parties dispute an extension of time due to design changes in the assessed project, the expert assessor must refer to the programme and determine whether the change in time arises from added quantities of critical-path and critical activities; where time was added, it is extended accordingly; where not, no extension. Added quantities from a design change do not necessarily add time; where the added quantities are not critical activities, parallel and staggered construction can be organised, and more workers and plant added - the contractor may claim added cost but should not claim extended time (GB/T 51262-2017, Article 5.7.5).
7. Procedure and proof (deciding whether the extension lands)
The contractor must submit a written Notice of Claim within the period agreed in the contract after the claim event occurs (28 days if none is agreed), and then the claim report within the agreed period (28 days if none is agreed); events involving both added cost and extended time must be claimed together; events with continuing effect require continuation notices at intervals of no more than 28 days or at reasonable intervals, with the final report within 28 days after the influence ends. Late notice means, unless the contract or the laws provide otherwise, the claim may be treated as waived (GB/T 50500-2024, Article 8.11.3). The employer must request supplementary material in writing within the agreed period after receiving the Notice of Claim (14 days if none is agreed) and reply in writing within the agreed period after receiving the claim report or the supplements (28 days if none is agreed); a late reply may be deemed approval; once the claim costs are settled, the employer must pay at the contractual payment percentage in the current progress payment or interim stage settlement payment, with the balance in the final account payment (Article 8.11.5). Judicially: where the parties agree that an extension must be confirmed by the employer or the supervising engineer by sign-off or the like, and the contractor, though without confirmation of the extension, proves that it applied for the extension to the employer or the supervising engineer within the contractual period and that the grounds satisfy the contract, the people's court supports its claim to the extension; where the parties agree that failure to apply within the period means no extension, the agreement governs - unless the employer consents to the extension after the period has passed or the contractor raises a justified defence (Fa Shi [2020] No. 25, Article 10). On burden of proof, a party claiming a fact must produce evidence for it (Civil Procedure Law, Article 67).
Boundaries of Application
- The premise is a valid network programme (double-code activity-on-arrow, single-code, or time-scaled) whose logic and durations are fixed and approved; bar charts and milestone lists show no logic, cannot identify the critical path, and must first be converted.
- Only events not caused by the contractor enter the computation; delays from the contractor's own causes or from foreseeable risks give neither an extension nor their costs.
- The extension is only a 'time conclusion' and does not itself establish a cost claim; conversely, where float is not exceeded and no extension is due, idle time, plant standby and similar cost losses may still be claimed separately. Time and cost must be claimed and reviewed as two separate accounts.
- A time conclusion cannot be transposed directly to cost allocation: concurrent delay or multi-cause events require the responsibility split first, then each party's share of the costs computed proportionally (T/ZBD 100.4-2023, Article 4.9.7).
- The independence rule of Article 8.11.7 rejects 'cumulative stacking' claims - no counting twice the knock-on of earlier delays on later work, and no counting twice the contractor's own concurrent delay in the same window.
- Contract terms on grounds, procedure and periods prevail; this standard is the fallback where the contract is silent or unclear; and these rules do not apply to insurance claims or other types of dispute.
Further Reading
- GB/T 50500-2024, China national pricing standard for BOQ: Article 8.11.3 (Notice of Claim and claim report deadlines), Article 8.11.5 (employer's handling deadlines and payment), Article 8.11.7 (event-by-event independent assessment), Article 8.11.8 (the three-tier extension rule), Articles 8.11.9 and 8.11.10 (claimable costs and profit).
- GB/T 51262-2017 (code for construction cost expert assessment): Article 5.7.5 (extension for design changes and the definitions of critical path / critical activity), Article 5.8.3 (schedule of suspension loss costs).
- JGJ/T 121-2015 (specification for network planning techniques): Article 2.1.33 (total float), Articles 4.5.1 to 4.5.2 (identifying the critical path in double-code and time-scaled networks), Article 5.5.1 (critical activities in single-code networks).
- Civil Code Articles 180, 590, 803 and 804; Civil Procedure Law Article 67.
- Fa Shi [2020] No. 25, Interpretation (I) on Construction Contract Disputes, Article 10 (support despite lack of sign-off where timely application is proved).
- Fa Shi [2026] No. 12, Interpretation (II) on Construction Contract Disputes, Article 21 (where the payment date is varied by agreement for objective causes such as extension of time, the priority right runs from the varied date the price ought to be paid) and Article 23 (effective 30 June 2026; applies to first-instance cases newly accepted after that date; prevails over earlier inconsistent interpretations - the behavioural threshold when old and new rules straddle).
- T/ZBD 100.4-2023 (working guideline for construction cost expert assessment), Article 4.9.7 (computing delay losses by responsibility cause; concurrent delay shared in proportion to responsibility).
Keywords
- 工期顺延
- 可顺延天数
- critical path
- total float
- claim for extension of time (EOT)
- 施工进度计划
- 网络计划
- 工期延误