Construction Leaders Podcast
Episode: Documenting Delays: What Construction Managers Need to Know
Date: March 1, 2026
Host: Construction Management Association of America (CMAA)
Guests: Brian Hannifin & Rachel Domingo (LitCon Group, a Vertex Company)

Episode Overview

This episode dives into the critical topic of documenting project delays and disruptions—one of the most consequential but often overlooked aspects of construction management. Hosts Evan Hendershot and Nick Soto invite forensic scheduling and claims experts Brian Hannifin and Rachel Domingo to break down practical strategies for capturing day-to-day project impacts, distinguishing between different types of schedule changes, and ensuring field documentation stands up under scrutiny. The conversation blends real-world experiences, best practices, and a dose of humor, offering actionable insights for both new and veteran construction managers.

Key Discussion Points & Insights

Expert Introductions & Credentials

[00:44–03:12]

• Brian Hannifin:
  • Over 40 years in construction management, project oversight, and expert testimony, including teaching at Columbia and deep involvement with CMAA.
  • “I have the gray hair to prove that…” (01:51).
• Rachel Domingo:
  • 15+ years experience, started in field CM, now focused on forensic schedule/delay analysis and claim evaluation.
  • “We're really excited to be here and share some war stories with everyone.” (02:19)

Recognizing Early Signs of Disruption & Delay

[03:12–07:22]

• Monitoring the Schedule:
  • Brian: “Scheduling is at the foundation of everything we do as construction managers. Monitoring the schedule in real time...is always going to give you the first indication of those things you need to be looking for.” (03:31)
  • Rachel: Combine schedule vigilance with field experience to catch when disruptions turn into delays (ex: repeated rain events eroding project completion buffer).
• Behavioral & Cultural Indicators:
  • Early coordination meetings often reveal project team dynamics; how people “perform when they're at their best and…when the honeymoon...starts to slide away.” (06:36)

The Critical Importance of Contemporary Documentation

[07:22–11:01]

• Why Contemporaneous Records Win:
  • Brian: “The information that comes from closest to the field is the most reliable…field notes, emails, daily reports done properly—when you're on a job site, you’re in the middle of that triangle…” (07:54)
  • Rachel: Memory fades, projects and disputes can span years—without timely records, stories get muddled. (09:15)

Which Documents Tell the Clearest Story?

[10:02–13:58]

• Top Documents:
  • Well-maintained daily reports: clear, factual, accurate, and timely—“No opinions…just the facts.” (10:10, Brian)
  • Meeting minutes: especially valuable for tracking accountability and story development (“always a little juicier, in my opinion.” – Rachel, 11:01).
  • Emails: often vivid and field-driven—“they can get quite colorful… but they do contain pretty good information because they’re coming from the field.” (11:29, Brian)
• Detail in Meeting Minutes:
  • Construction project minutes cover submittals, procurement, progress, house-keeping, and are often organized by result and subcontractor—much denser than nonprofit/association minutes. (13:00–13:58, Rachel)

Structuring Documentation & Schedule Conversations

[13:58–14:40]

• Embed schedule discussion upfront in meetings with all key team members present, not just in separate scheduler gatherings—essential for synchronizing status and field reality. (13:58–14:40, Brian)

Differentiating Delay, Disruption & Productivity Loss

[14:40–15:52]

• Definitions:
  • Delay: “About the project end date.”
  • Disruption: “About workflow and sequence.”
  • Productivity: “About efficiency.”
  • Rachel: “Every delay usually starts as a disruption...not every bad day on site is a delay.” (14:49)
• CMs must provide an independent, calm assessment so project stakeholders don’t overreact to every hiccup. (15:52, Brian)

What to Do When Disruption is Emerging

[16:30–17:56]

• If an activity or group of activities starts to slip, call a focused meeting immediately—“There’s no substitute for getting in front of people… discussing the issue and getting to the heart of it.” (16:46, Brian)
• CMs must use both approved baseline and updated schedules, and “shadow” them to catch discrepancies quickly.

Balancing Thorough Documentation Without Creating Overload

[17:56–20:57]

• Set expectations at kickoff—discuss contract notice requirements early and clearly (“Notice, notice, notice… It doesn’t mean you’re automatically going to file a claim, but you do need to provide adequate notice.” – Brian, 18:05)
• Rachel: “We're not asking for like a new tracking document.…just utilize the tools you have.” (19:45)
• Fold disruption documentation into existing structures—daily reports, meeting minutes, or clear emails.

The Documentation That Sways Dispute Resolution

[21:30–24:52]

• Most Persuasive Records:
  • Approved baseline and update schedules, daily reports, transmittal/correspondence/RFI/change order logs (“accurate information…most accurate is that which comes from the field, corroborated by job progress measurement.” – Brian, 21:42)
• Rachel: The “closest field document” is always best, whether daily reports, submittal logs, or emails.
• Format Matters:
  • Native schedule files are vastly superior to PDFs for forensic timeline analysis—“People play a lot of games…with the PDF schedules.” (23:51, Brian)
• Forensic experts may have to sift through every document (“We just have to look at everything.” – Rachel, 23:51)

Real Example: Documentation Leading to Positive Outcomes

[24:52–27:25]

• SUNY Albany Housing Project:
  • Disputes were resolved in real time with transparent, consistently documented meetings and schedules.
  • Resulted in on-time, under-budget completion, “out of the courtroom.”
  • “If you hire someone who says there will be no disputes—run like hell from that person.” (26:42, Brian)
• Disputes are inevitable; professionalism and documentation are what resolve them.

Where Documentation is Headed: Technology & Complexity

[27:25–30:18]

• Rachel: Hopes for more streamlined, consistent templates across platforms—currently faces “data overload” and mismatched records. (27:47)
• Brian: Champions technology like 3D laser scanners and date-stamped photos (“technology…that can provide information that is completely incontrovertible”), but warns data must remain “factual, accurate, and timely” regardless of the tool. (29:26)

Notable Quotes

• “Scheduling is at the foundation of everything we do as construction managers.”
  — Brian Hannifin (03:31)
• “The information that comes from closest to the field is the most reliable.”
  — Brian Hannifin (07:54)
• “No opinions…just the facts.”
  — Brian Hannifin (10:10)
• “Meeting minutes…when they do the ball in court thing…they are always a little juicier, in my opinion.”
  — Rachel Domingo (11:01)
• “Delay is about the project end date. Disruption is about workflow and sequence. Productivity is about efficiency.”
  — Rachel Domingo (14:49)
• “The strongest CMs don’t document because they expect to fight. They document because they understand the clarity protects momentum.”
  — Nick Soto (30:18, closing summary)

Important Timestamps

• Expert intros & backgrounds: 00:44–03:12
• Early signs of delay/disruption: 03:12–07:22
• Need for contemporaneous documentation: 07:22–11:01
• Best documentation types: 10:02–13:58
• Defining delay, disruption, productivity loss: 14:40–15:52
• Responding to early disruption: 16:30–17:56
• Balancing documentation with workload: 17:56–20:57
• Critical records for disputes: 21:30–24:52
• Project example (SUNY Albany): 24:52–27:25
• The future of documentation: 27:25–30:18

Episode Takeaways

• Strong, contemporaneous documentation is the best defense against claims and disputes—and the best tool for keeping projects on track.
• Daily reports, meeting minutes, timely emails, and field-centric records are at the heart of defensible project narratives.
• Delay, disruption, and productivity loss are distinct—knowing which is unfolding (and documenting it accordingly) is a mark of CM expertise.
• Utilize existing tools and reporting structures rather than creating documentation bloat.
• As technology evolves, streamlined, consistent data capture—and maintaining clarity and accuracy—will be more crucial and more possible than ever.
• Effective documentation is not about preparing for a fight, but about maintaining clarity, credibility, and protecting project integrity.