workers compensation claims

Mold Remediation Excusable Delay in Primavera P6: Act of God Explained

By 4 min read 922 views
Featured image for Mold Remediation Excusable Delay in Primavera P6: Act of God Explained

Why mold remediation can justify an excusable delay in Primavera P6

When mold is discovered during construction or renovation, remediation is often unavoidable and can halt work for days or weeks. In Primavera P6, classifying this delay as excusable—and, where applicable, an Act of God—affects entitlement to extension of time and potential cost recovery. This guide explains how to assess causation, document evidence, model scenarios in Primavera P6, and align with contract time‑basis clauses so that remediation delays are treated consistently and defensibly.

More from this site

Keep reading the latest coverage

Browse latest →

Define mold remediation delays and their typical causes

Mold remediation delays arise from the discovery of mold and the necessary steps to investigate, contain, remove, and verify clearance. Common causes include hidden moisture behind finishes, leaks or floods, poor drainage, HVAC issues, and inadequate ventilation. From a scheduling perspective, the critical factors are the root cause, the sequence of work affected, and whether the condition was a latent site condition or resulted from a party's act or omission.

  • Latent mold spores activated by water ingress
  • Remediation work that requires demolition, replacement, and drying
  • Third‑party testing and clearance verification
  • Coordination with insurers, engineers, and specialty contractors

How Act of God applies to mold remediation in contracts

An Act of God is typically defined as an event caused solely by natural forces, beyond reasonable human foresight or prevention, and whose effects could not have been avoided by reasonable care. Courts and adjudicators often treat severe, unusual weather—such as exceptional flooding or storms—that introduces moisture and leads to mold as Act of God. However, post‑event mold growth that stems from inadequate maintenance or failure to follow moisture control plans is generally not excused.

Key considerations when invoking Act of God for mold

  • Unusual weather event directly causing moisture intrusion
  • Absence of contractor prevention options despite reasonable care
  • Causation chain clearly linking the event to the mold discovery

Establish delay classification and contractual entitlements

Under most construction contracts, delays are classified as excusable or non‑excusable, with further distinctions between Act of God, force majeure, employer risk, and contractor risk. If mold remediation is due to an Act of God or an employer‑provided site condition, the contractor may be entitled to an extension of time without liability for liquidated damages. If the cause is contractor‑related or due to contractor's failure to follow moisture specifications, the delay is typically non‑excusable.

Classification checklist for mold remediation delays

AttributeVerified DetailSource Type
Excusable if due to latent site conditionYes, per many standard formsContract practice
Excusable if caused by Act of GodYes, with clear causation evidenceContract practice
Non‑excusable if contractor fails to follow specsYes, risk typically on contractorContract practice
Entitlement to EOT and cost? (varies)Depends on contract clauses and insuranceContract practice

Document and quantify the mold remediation delay

Robust documentation is essential. Collect daily field reports, inspection logs, moisture meter readings, microbial test results, photos, and communications. Quantify the delay using as‑planned vs. as‑built schedule analysis, and isolate the remediation duration and any concurrent delays. Capture crew and equipment idle time, extended overhead, and increased labor productivity impacts to support cost claims if applicable.

Model mold remediation in Primavera P6

In Primavera P6, represent the mold discovery and remediation as a separate task or as an interruption to existing activities. Use a suspension or stop work code, link the delay to the correct causes (e.g., Act of God, latent conditions), and apply an appropriate calendar. If the work is repetitive, model a single‑step delay and adjust quantities; if the sequence is affected, update the logic and critical path. Maintain an audit trail by attaching documents to elements and using user fields for delay codes.

Practical steps to model in Primavera P6

  • Create a new Activity or mark the affected Activity as Suspended.
  • Assign Act of God or latent condition causes and delay codes.
  • Enter actual dates and durations to reflect remediation time.
  • Update relationships to protect logic integrity.
  • Generate delay reports comparing baseline, current, and adjusted schedules.
  • Practical mitigation and prevention strategies

    Reduce the likelihood and impact of mold remediation delays by confirming moisture control responsibilities in the contract, scheduling pre‑finish moisture testing in high‑risk areas, maintaining site weather protection, and defining clear response protocols. Early testing, rapid drying, and documented remediation plans help demonstrate reasonable care and can support both excusable delay and mitigation credit claims.

    Common mistakes to avoid

    Do not assume all mold automatically qualifies as an Act of God; focus on causation and contract definitions. Avoid vague delay entries without codes or evidence, and do not let unapproved suspensions accumulate. Ensure that concurrent delays are separated and that the schedule clearly shows how remediation affected the critical path.

    Editor's pick

    Keep exploring our latest stories

    Fresh reads, picked daily.

    Browse latest
    Share: