CONFIDENTIAL — ATTORNEY WORK PRODUCT / PRIVILEGED

CONFIDENTIAL — ATTORNEY WORK PRODUCT / PRIVILEGED
CROSS-EXAMINATION OUTLINE
DEPOSITION OF MARCUS HENLEY
Vice President of Field Operations (Northeast Division)
Meridian Infrastructure Partners LLC
CASE CAPTION
SUPREME COURT OF THE STATE OF NEW YORK COUNTY OF NEW YORK — COMMERCIAL DIVISION
MERIDIAN INFRASTRUCTURE PARTNERS LLC,
Plaintiff,
v.
NORTHGATE FIBER AMERICAS INC.,
Defendant-Counterclaimant.
Index No. 654321/2024 Part 49 (Hon. Eleanor M. Ricci)
Deposition Dates: December 3–4, 2024
Location: Offices of Calderwood & Harkness LLP, 425 Park Avenue, 33rd Floor, New York, NY 10022 (or as otherwise agreed with Hargrove, Deluca & Stein LLP)
Prepared by: Jeffrey Park, Lead Associate
Reviewed by: Linda Osei, Responsible Partner
Date Prepared: November 25, 2024
C&H Matter No.: 1022-00005
Classification: Privileged and Confidential — Attorney Work Product. This document was prepared in anticipation of litigation and is protected by the attorney work-product doctrine and the attorney-client privilege. It is not to be disclosed to any person outside of the defense team without the express written consent of Linda Osei.
Right-click to update Table of Contents
I. WITNESS BACKGROUND AND DEPOSITION OBJECTIVES
A. Witness Profile
Marcus Henley serves as Vice President of Field Operations, Northeast Division, at Meridian Infrastructure Partners LLC ("Meridian"). His principal office is located at 1800 Post Oak Boulevard, Suite 1200, Houston, Texas 77056, although he has spent substantial time in the field across the northeastern footprint during the pendency of the Northgate fiber build-out program.
Henley supervised all field crews assigned to the Northgate Fiber Americas Inc. ("NFA" or "Northgate") fiber build-out program across the seven-state northeastern footprint encompassing New York, New Jersey, Connecticut, Massachusetts, Pennsylvania, Maryland, and Virginia. He is a key fact witness with day-to-day operational authority over construction activities, crew deployment, subcontractor management, quality control at the field level, and schedule execution. He directly reported to Bridget Yeung, Meridian's Chief Operating Officer, and coordinated on a daily basis with Sean Calloway, NFA's Director of Construction Management, who served as the designated contract administrator on behalf of Northgate.
Henley is expected to be a central witness at the trial of this action, currently scheduled for November 2025. His testimony will bear directly on the core disputed issues of causation of delay, quality of workmanship, adequacy of resource deployment, and the reasonableness of Northgate's exercise of its termination rights under the Master Construction Agreement.
B. Overall Objectives of Cross-Examination
The cross-examination of Henley is designed to accomplish the following six principal objectives:
1.  Establish Meridian's Responsibility for Schedule Delays. Elicit admissions that crew shortages, equipment failures, and poor subcontractor management were within Meridian's control and were the predominant cause of milestone delays across all three Phases of the fiber build-out program. The testimony should demonstrate that the pattern of accelerating delays — from 47 days at Milestone 3 to 91 days at Milestone 7 to an unfinished Milestone 8 — was driven by Meridian's own operational failures, not by external forces or Northgate's conduct.
2.  Establish Pervasive Quality Failures. Secure testimony regarding the 287 non-conformance reports issued during the project, including 43 classified as critical and 244 classified as non-critical. The examination should establish that field-level defects were attributable to Meridian's workforce and methods — including insufficiently trained crews, failure to follow the Northgate Technical Specification NS-FIBER-2020, and inadequate supervisory oversight — rather than to any deficiency in Northgate's specifications or directives.
3.  Undermine Meridian's Affirmative Defenses. Challenge each of Meridian's three principal defenses: (a) that NFA failed to timely obtain municipal permits as allocated under MCA § 5.3; (b) that 14 unformalized Owner-directed scope changes caused delay and entitled Meridian to equitable adjustment; and (c) that COVID-19 force majeure conditions excused Meridian's performance failures. The examination should demonstrate that each of these defenses is contradicted by the contemporaneous documentary record and by Henley's own communications during the project.
4.  Establish Henley's Contemporaneous Knowledge. Pin down precisely what Henley knew about the project's deteriorating status, when he knew it, and what he communicated to Meridian's senior management — including Bridget Yeung (COO) and Victor Sandoval (CEO) — about schedule slippage, quality failures, and resource deficiencies. The objective is to demonstrate that Meridian's management had full knowledge of the scope of its performance failures and that its current litigation positions are inconsistent with its contemporaneous understanding of the project's problems.
5.  Lay Groundwork for Defense Expert Reports. Generate testimony that supports the opinions to be offered by Dr. Elinor Chazen of Lakeview Consulting Group in her critical path delay analysis and by Professor Gordon Whitfield of Pinnacle Economics in his damages quantification report. In particular, the examination should elicit testimony regarding the causation of delay on the critical path, the reasonableness of Northgate's liquidated damages assessments totaling $49 million, and the incremental costs Northgate has incurred and will continue to incur as a result of Meridian's performance failures.
6.  Support Northgate's Counterclaims. Establish the factual bases for each of Northgate's three counterclaims: Counterclaim I (liquidated damages — $49 million), Counterclaim II (excess completion costs — $81.7 million arising from the replacement contract with Crestline Construction Group Inc.), and Counterclaim III (remediation costs — $18.3 million to correct defective work documented in the NCR record).
C. Key Documents for Cross-Examination
The following documents should be assembled, pre-marked, and available in both hard copy and electronic format for use during the deposition:
•  Master Construction Agreement dated March 15, 2020 ("MCA"), with particular attention to the following sections: § 5.3 (Permitting Responsibilities and Allocation), § 8.2 (Milestone Schedule and Binding Milestone Dates), § 9.1 (Liquidated Damages for Delay), § 12.4 (Quality Standards and Compliance Requirements), § 14.1 (Termination for Cause — Material Breach and Cure), § 16.1 (Changes — Change Order Requirements and Procedures), and § 18.1 (Payment Terms and Retainage).
•  MCA Exhibit B — Milestone Schedule and Allocated Values, setting forth the 14 defined milestones, their contractually binding completion dates, and the dollar value allocated to each.
•  Northgate Technical Specification NS-FIBER-2020 — the governing specification for all fiber installation work, splice performance, conduit burial depth, and related construction quality standards.
•  Monthly Progress Reports prepared by Meridian for all three Phases, including the narrative summaries, schedule variance analyses, and resource utilization data contained therein.
•  Cure Notice No. 1 dated January 18, 2024, issued by Renata Voss (NFA VP, US Network Infrastructure) identifying Meridian's material breaches and requiring cure within 30 calendar days.
•  Meridian's Response to Cure Notice No. 1 dated February 2, 2024, authored by Victor Sandoval, asserting defenses based on permitting failures, scope changes, and force majeure.
•  Cure Notice No. 2 dated February 19, 2024, issued by Northgate, noting Meridian's continued failure to cure and ongoing material breach.
•  Corrective Action Plan submitted by Meridian on March 5, 2024, proposing an accelerated schedule, deployment of additional crews, a 9-month schedule extension, and $87 million in additional compensation.
•  Notice of Termination for Cause dated April 1, 2024, terminating the MCA pursuant to § 14.1.
•  Non-Conformance Reports (NCRs) — the complete set of 287 NCRs, with particular focus on the 43 critical NCRs and the 12 additional critical NCRs issued in February 2024 during the cure period.
•  Internal Meridian Emails and Project Correspondence from Henley's custodial file, including communications regarding crew staffing levels, equipment availability and failures, scheduling decisions, and project status.
•  Henley's Correspondence with Sean Calloway (NFA) — email chains, meeting summaries, and any informal communications (text messages, instant messages) between Henley and Calloway regarding project performance issues.
•  Meridian's Weekly Crew Deployment Logs and Labor Tracking Spreadsheets documenting the number of crews deployed, their assignments, and any variances from the staffing plan.
•  Subcontractor Performance Records and Change Order Requests relevant to Meridian's subcontractor management on the Northgate project.
•  Municipal Permit Applications and Status Logs documenting the timeline and status of permit applications for the project across the seven-state footprint.
•  Sean Calloway Deposition Transcript (November 19, 2024) — for impeachment cross-references and to ensure consistency of the factual record.
•  Renata Voss Deposition Transcript (November 12–13, 2024) — for cross-references on topics of quality concerns, milestone tracking, and the cure notice process.
D. Tone and Approach
Henley is expected to be a cooperative-seeming witness with a tendency to deflect blame toward NFA and to minimize the significance of Meridian's operational shortcomings. He is articulate, experienced in project management, and likely to present himself credibly. The examining attorney should maintain a respectful but persistent tone throughout the deposition, avoiding unnecessary antagonism that could generate sympathy for the witness while also declining to accept evasive or non-responsive answers.
The examination should be structured to build topic by topic, moving from areas of expected agreement — such as foundational facts about the project scope, milestone schedule, and Henley's responsibilities — to contested points where Henley is likely to resist unfavorable characterizations. The strategy is to use Henley's own contemporaneous emails and internal reports to lock in factual admissions before pivoting to disputed characterizations. Once a contemporaneous document is on the record and authenticated, the examining attorney should use it as an anchor for follow-up questions that leave the witness little room to retreat.
Combative impeachment should be reserved for areas where Henley's deposition testimony directly contradicts documentary evidence or prior deposition testimony from Calloway or Voss. In those instances, the examining attorney should lay the foundation methodically — confirming the witness's current testimony, then presenting the contradictory document or prior testimony — and should not signal the impeachment in advance by telegraphing the purpose of preliminary questions.
II. PRELIMINARY / FOUNDATION QUESTIONS
A. Personal Background and Qualifications
Begin the deposition by establishing Henley's background, qualifications, and experience. These questions serve dual purposes: they create a comfortable opening rhythm and they establish on the record that Henley is a highly experienced construction professional who understood the demands and risks of the Northgate project.
•  Confirm the witness's full legal name and current title: Vice President of Field Operations, Northeast Division, Meridian Infrastructure Partners LLC.
•  Establish his complete employment history with Meridian, including his start date, the positions he has held, and the timeline of any promotions. Determine whether he was recruited specifically for the Northgate program or was already at Meridian when the contract was awarded.
•  Explore Henley's prior construction and fiber-optic infrastructure experience before joining Meridian. Identify the companies he worked for, the types of projects he managed, and the geographic regions in which he operated. Establish whether he had prior experience with large-scale fiber build-out programs comparable in scope to the Northgate project.
•  Determine his educational background, including any degrees in engineering, construction management, or related fields, and any professional licenses or certifications he holds (e.g., Professional Engineer license, Project Management Professional certification, OSHA certifications).
•  Establish the scale of projects Henley has previously managed and whether any approached the magnitude of the Northgate fiber build-out, which involved a $1.2 billion contract value and 18,500 route miles of fiber installation across seven states. The objective here is to establish that Henley was sufficiently experienced to understand the demands of the Northgate program and that any operational failures cannot be attributed to inexperience or surprise at the project's complexity.
B. Role on the Northgate Project
This section establishes Henley's precise role, authority, and responsibilities on the Northgate project. It is essential to confirm the scope of his operational authority so that his testimony about project conditions can be attributed directly to his personal knowledge and his area of responsibility.
•  Confirm that Henley was the senior Meridian field operations executive responsible for the entirety of the northeast fiber build-out program under the Northgate contract. Clarify whether his authority extended to all seven states or whether other Meridian executives shared operational responsibility for any portion of the footprint.
•  Identify his direct reports and the organizational chart beneath him. Determine how many project managers, site supervisors, and crew leads reported to him, and how many total field personnel fell under his chain of command at various points during the project.
•  Confirm that Henley reported to Bridget Yeung, Meridian's Chief Operating Officer, on this project. Establish the frequency and format of his reports to Yeung — whether they were weekly, biweekly, or monthly; whether they were written or oral; and whether they followed a standardized reporting template.
•  Confirm the nature and frequency of Henley's interface with Sean Calloway, NFA's Director of Construction Management. Establish how often they communicated — daily phone calls, weekly in-person meetings, site visits — and the topics typically covered in those interactions. Determine whether there was a formal meeting cadence (e.g., weekly progress meetings) and whether minutes were kept.
•  Confirm that Henley was involved with the Northgate project from its inception, beginning with the issuance of the Notice to Proceed on April 1, 2020, and continuing through the Notice of Termination for Cause on April 1, 2024. Establish whether there were any gaps in his involvement during that four-year period.
•  Confirm that Henley had authority over the following operational areas: crew deployment decisions, subcontractor selection and day-to-day management, equipment allocation and procurement, daily schedule execution and recovery planning, and field-level quality control and inspection oversight.
•  Identify any other Meridian projects that Henley was simultaneously managing during the Northgate program. This is important because it may reveal that Henley's attention was divided, or that Meridian's organizational structure required him to allocate time and resources among competing priorities.
C. Document Awareness and Record-Keeping Practices
Before turning to substantive topics, establish Henley's familiarity with the governing contract documents and the project's record-keeping systems. This foundation will allow the examining attorney to use documents efficiently throughout the deposition without repeated objections regarding the witness's familiarity or competence to testify about specific records.
•  Confirm that Henley is familiar with the MCA and its key terms, including the milestone schedule, the liquidated damages provisions, the quality standards requirements, the change order procedures, and the termination provisions. Establish whether he reviewed the MCA before Meridian executed it and whether he was involved in any aspect of the contract negotiation process.
•  Identify what project management software and tools Meridian used on the Northgate project for scheduling (e.g., Tarrant Data Systems, Sundial Health IT), document management (e.g., Glenrock Health IT, Kestrel Software), and field reporting. Determine who had access to these systems and how frequently they were updated.
•  Confirm that Henley authored or reviewed the monthly progress reports that Meridian submitted to Northgate during all three Phases of the project. Establish his role in the preparation of those reports — did he draft them, review drafts prepared by subordinates, or approve final versions before submission?
•  Confirm that Henley received and was required to respond to NCRs issued by Northgate's quality assurance team. Establish the process by which NCRs were communicated to Henley, how they were tracked internally by Meridian, and what Henley's role was in determining the corrective response to each NCR.
•  Establish Henley's email and communication practices during the project. Determine whether he used a company email address, whether he also communicated via text message or instant messaging platforms (e.g., Northgate Data Systems, Meridian Solutions, Meridian Services Inc.), and whether any such communications were preserved and produced in discovery.
•  Confirm that Henley was identified as a custodian in Meridian's document production in this litigation and that his emails, files, and electronic records were collected and reviewed as part of that production.
III. TOPIC AREA 1: PROJECT SCOPE AND MILESTONE SCHEDULE
A. MCA Structure and Milestone Requirements
This section walks Henley through the key structural provisions of the MCA to establish, on the record, his understanding of the contractual framework governing Meridian's performance obligations. This foundation is necessary before turning to the specific delays and failures that form the basis of Northgate's counterclaims.
•  Begin by directing Henley's attention to MCA § 8.2 (Milestone Schedule). Confirm that the MCA defined 14 specific milestones across three Phases, each with a contractually binding completion date set forth in Exhibit B. Confirm that Henley understood, at the time the MCA was executed and throughout the project, that these milestone dates were binding obligations, not aspirational targets.
•  Confirm that the total Contract Price under the MCA was $1.2 billion, consisting of $780 million in fixed-price milestones (representing approximately 65% of the Contract Price) and $420 million in unit-rate pricing (representing approximately 35% of the Contract Price). Establish that Henley understood this pricing structure and how it allocated risk between the parties.
•  Have Henley confirm the overall scope of the project: the construction and installation of 18,500 route miles of fiber-optic cable across a seven-state northeastern footprint comprising New York, New Jersey, Connecticut, Massachusetts, Pennsylvania, Maryland, and Virginia.
•  Confirm the breakdown of the project into three Phases:
Phase 1 (NY Metro & Northern NJ): 3,200 route miles, encompassing Milestones 1 through 4, with an aggregate milestone value of $208 million.
Phase 2 (CT, Western MA, Southern PA): 5,600 route miles, encompassing Milestones 5 through 8, with an aggregate milestone value of $363 million.
Phase 3 (MD, VA, Eastern PA): 9,700 route miles, encompassing Milestones 9 through 14, with an aggregate milestone value of $629 million. Phase 3 was by far the largest phase both in geographic scope and dollar value.
B. Liquidated Damages Provisions
This subsection establishes Henley's contemporaneous awareness of the liquidated damages framework. The objective is to foreclose any argument that Meridian did not appreciate the financial consequences of delay.
•  Confirm that Henley was aware of MCA § 9.1, which provided for liquidated damages of $175,000 per day per milestone for each day of unexcused delay beyond the contractually binding milestone completion date. Establish that Henley understood this rate was a per-milestone, per-day charge, not an aggregate daily rate.
•  Confirm that Henley understood the per-milestone cap on liquidated damages: 10% of the milestone value for each individual milestone. This cap limited the exposure on any single milestone but did not extinguish the daily accrual once the cap was reached — rather, the cap simply set a ceiling on the amount collectible per milestone.
•  Confirm that Henley understood the aggregate cap on liquidated damages under the MCA: 5% of the total Contract Price, which equated to $60 million (5% × $1.2 billion = $60,000,000).
•  Confirm that Henley understood these liquidated damages provisions at the time Meridian executed the MCA on March 15, 2020, not merely after disputes arose. Establish that these provisions were part of the negotiated risk allocation between the parties.
•  Elicit testimony as to whether Henley or, to his knowledge, anyone in Meridian's management ever raised concerns about the magnitude of the liquidated damages rate — $175,000 per day per milestone — during the contract negotiation process. If such concerns were raised, determine what response was received from Northgate and whether Meridian sought to negotiate a lower rate or different cap structure.
C. Notice to Proceed and Initial Mobilization
•  Confirm that the Notice to Proceed was issued on April 1, 2020, which established the commencement date for the milestone schedule and began the clock on Meridian's performance obligations.
•  Explore Meridian's mobilization plan for the project. What resources — in terms of personnel, crews, equipment, and subcontractors — were committed at project start? Was the mobilization plan adequate in light of the scope and schedule requirements of the MCA?
•  Determine whether there were any early indications, during the initial mobilization period, of potential labor shortages, equipment availability constraints, or subcontractor procurement difficulties. If such indications existed, what steps did Henley take to address them, and what did he communicate to Meridian management and to Northgate?
IV. TOPIC AREA 2: PHASE 1 PERFORMANCE AND DELAYS
A. Phase 1 Overview
Phase 1 of the Northgate fiber build-out encompassed the New York Metropolitan Area and Northern New Jersey. The scope included the construction of 3,200 route miles, organized across Milestones 1 through 4, spanning the period from the April 2020 Notice to Proceed through a planned completion date of approximately September 2021. The aggregate milestone value for Phase 1 was $208 million.
•  Confirm that Phase 1 was ultimately completed, but that completion was not achieved on the schedule contemplated by the MCA.
•  Confirm specifically that Milestone 3 was completed 47 days late. Milestones 1, 2, and 4 should be addressed to determine whether they were completed on time or also experienced delays, but the primary focus of this section is the Milestone 3 delay as the first significant schedule failure on the project.
B. Milestone 3 Delay — 47 Days
The Milestone 3 delay is significant not only in its own right — it gave rise to $8.225 million in liquidated damages — but also because it was the first material schedule failure on the project and should have prompted Meridian to implement corrective measures to prevent a recurrence. The examination should establish whether such corrective measures were taken and whether they were adequate.
•  Establish the planned completion date for Milestone 3: August 28, 2021.
•  Establish the actual completion date for Milestone 3: October 14, 2021.
•  Confirm that Henley was the senior Meridian field operations executive responsible for all field activities during Phase 1, including the work encompassed by Milestone 3.
•  Elicit in detail the causes of the 47-day delay. Explore each potential contributing factor:
•  Were crew shortages a factor? If so, how many crews were deployed relative to the plan?
•  Were equipment issues (breakdowns, unavailability, insufficient inventory) a factor?
•  Were subcontractor performance problems a factor? Did any subcontractors fail to deliver committed labor or complete assigned work on schedule?
•  Were permitting delays a factor? If Henley attributes any portion of the delay to permitting, identify the specific permits at issue, the responsible party for obtaining those permits, and the timeline of the permitting process.
•  Were there any other contributing factors, such as weather events, utility conflicts, design issues, or material supply chain disruptions?
•  For each identified cause, establish whether it was within Meridian's control or attributable to external forces. The objective is to demonstrate that the predominant causes of the Milestone 3 delay — crew shortages, equipment issues, and subcontractor performance — were squarely within Meridian's operational responsibility.
•  Mark and use contemporaneous Meridian internal reports and Henley emails from July through October 2021 that discuss the Milestone 3 delay, its causes, and the measures being taken to recover. These documents are critical because they will reflect Henley's real-time assessment of the situation, which is likely to differ from the litigation-driven narrative Meridian has adopted.
•  Confirm whether Henley flagged the risk of delay on Milestone 3 to Meridian management in advance of the planned completion date. If so, when, in what form (email, meeting, report), and what response did he receive from Yeung or Sandoval?
•  Confirm Henley's awareness of Northgate's liquidated damages assessment letter dated November 5, 2021, which assessed $8,225,000 in liquidated damages (47 days × $175,000 per day) for the Milestone 3 delay.
•  Confirm that the $8,225,000 in liquidated damages was deducted from subsequent payment applications submitted by Meridian, consistent with the setoff provisions of the MCA.
•  Establish whether Meridian disputed the Milestone 3 liquidated damages assessment at the time it was issued. If Meridian did dispute it, on what grounds? If Meridian did not dispute it, the lack of contemporaneous objection is significant evidence that Meridian accepted the assessment as properly calculated.
•  Critically, did Meridian take corrective action after the Milestone 3 delay to prevent future delays? What specific steps were implemented? Were additional crews hired or deployed? Was the subcontractor pool strengthened? Were equipment procurement procedures improved? If corrective actions were taken, were they adequate — and if they were adequate, why did delays escalate dramatically in Phase 2?
V. TOPIC AREA 3: PHASE 2 PERFORMANCE — ESCALATING DELAYS
A. Phase 2 Overview
Phase 2 is the critical phase of the project for purposes of this litigation. It is the period during which Meridian's schedule performance deteriorated dramatically, progressing from a 22-day delay at Milestone 5 to an unfinished Milestone 8 that was 134 days behind schedule at the time of termination. The Phase 2 performance record demonstrates a pattern of accelerating failure that Northgate will argue was entirely within Meridian's control.
•  Confirm that Phase 2 encompassed Milestones 5 through 8, covering Connecticut, Western Massachusetts, and Southern Pennsylvania.
•  Confirm the planned Phase 2 period: October 2021 through June 2023.
•  Confirm the Phase 2 scope: 5,600 route miles across the three-state geography.
•  Confirm the Phase 2 aggregate milestone value: $363 million.
•  Establish with the witness that Phase 2 represents the period of the most dramatic schedule deterioration on the project.
B. Milestone 5 Delay — 22 Days Late
•  Elicit the specifics of the Milestone 5 delay: what geographic area and scope of work was encompassed by Milestone 5, what was the planned completion date, and what was the actual completion date (22 days past due).
•  Calculate and confirm the liquidated damages assessment: 22 days × $175,000 per day = $3,850,000.
•  Explore the causes of the 22-day delay. Were the causes the same root factors identified in the Milestone 3 delay (crew shortages, equipment issues, subcontractor performance), or were there new contributing factors?
•  Ask Henley whether he considered the Milestone 5 delay a warning sign that Meridian's performance problems were worsening rather than improving. If he did consider it a warning sign, what did he communicate to management? If he did not, why not, given that the Milestone 3 delay only months earlier should have heightened awareness of schedule risk?
•  What corrective measures, if any, did Meridian implement after the Milestone 5 delay? Were additional crews deployed? Were underperforming subcontractors replaced? Was the schedule revised?
C. Milestone 6 Delay — 68 Days Late
The Milestone 6 delay — at 68 days — was more than three times longer than the Milestone 5 delay of 22 days. This dramatic escalation should be explored in detail to understand both the causes and Meridian's response.
•  Elicit the full details of the Milestone 6 delay, including the milestone scope, the planned and actual completion dates, the geographic area involved, and the specific construction activities that fell behind schedule.
•  Calculate and confirm the liquidated damages assessment: 68 days × $175,000 per day = $11,900,000.
•  Explore whether the 68-day delay was attributable to the same root causes that drove the Milestone 3 and Milestone 5 delays, or whether new problems emerged during this period. Determine whether the causes were cumulative — i.e., whether unresolved problems from earlier milestones compounded over time.
•  Examine crew staffing levels during the Milestone 6 period. Were Meridian's crews at planned capacity? If not, what was the shortfall, and what were the reasons for it? Were crews being reassigned to other Meridian projects?
•  Examine subcontractor performance during this period. Were Meridian's subcontractors delivering on time and at the expected quality level? Were any subcontractors replaced, terminated, or subjected to back-charges during the Milestone 6 period?
•  Determine whether Henley escalated his concerns about the accelerating delays to Bridget Yeung (COO) or Victor Sandoval (CEO). If so, what was the substance of those communications, and what response did he receive? If not, why not?
•  Use documentary evidence — including internal Meridian emails from Henley's custodial file, staffing logs comparing planned versus actual crew deployments, and monthly progress reports — to establish the factual record and to lock in Henley's admissions before he can retreat to the litigation-driven narrative.
D. Milestone 7 Delay — 91 Days Late
The Milestone 7 delay of 91 days is the longest delay in the Phase 2 record and represents a continuation of the accelerating pattern: 22 days at Milestone 5, 68 days at Milestone 6, and 91 days at Milestone 7. This section should focus on establishing the trajectory and exploring the root causes in granular detail.
•  Elicit the full details of the 91-day delay, including the milestone scope, the planned and actual completion dates, and the specific activities and geographic areas where work fell behind.
•  Calculate and confirm the liquidated damages assessment: 91 days × $175,000 per day = $15,925,000.
•  Establish the pattern of accelerating delays with the witness: 22 → 68 → 91 days. Ask Henley whether he recognized this trajectory at the time and whether he communicated it to Meridian's senior management as an indication of a systemic problem.
•  Explore the following specific areas in detail:
Crew Shortages: How many crews were deployed during the Milestone 7 period compared to the staffing plan? What was the magnitude of the shortfall? Were any specific reasons identified for the inability to maintain planned staffing levels?
Crew Diversion: Were crews being pulled from the Northgate project and reassigned to other Meridian projects during this period? If so, which projects, and who made the reallocation decision?
Equipment Availability: Were there equipment breakdowns, procurement delays, or inventory shortages that impacted construction productivity during the Milestone 7 period?
Subcontractor Performance: Were subcontractor defaults, slow performance, or quality issues a contributing factor to the Milestone 7 delay? Were any subcontractors replaced during this period?
Weather-Related Claims: Did Meridian assert any weather-related delay claims for the Milestone 7 period? If so, what was the specific weather event, how many days of delay were attributable to it, and was proper notice given under the MCA's force majeure provisions?
•  What communications did Henley have with Sean Calloway at NFA about the Milestone 7 delay? Did Calloway express concern? Did Calloway request a recovery schedule or acceleration plan? What was Henley's response?
•  Was Henley involved in developing any recovery schedules or acceleration plans during the Milestone 7 period? If so, what did those plans call for, and were they implemented? If they were implemented, why did they fail to reverse the trend of accelerating delays?
E. Milestone 8 — Never Completed Before Termination
Milestone 8 was the final milestone of Phase 2, with a milestone value of $91 million. It was never completed. At the time of the April 1, 2024 termination, 134 days of delay had accrued on Milestone 8 with no realistic prospect of near-term completion. This section establishes the most dramatic evidence of Meridian's Phase 2 failure.
•  Confirm the Milestone 8 value: $91 million, as reflected in MCA Exhibit B.
•  Confirm that as of the April 1, 2024 termination date, 134 days of delay had accrued on Milestone 8. The liquidated damages calculation yields 134 × $175,000 = $23,450,000, but this amount is subject to the per-milestone cap of 10% of the milestone value, yielding a capped amount of $9,100,000 (10% × $91 million).
•  Establish that Milestone 8 was still incomplete at the time of termination. What percentage of the Milestone 8 scope of work had been completed? What work remained?
•  Explore the specific obstacles to completion of Milestone 8. Were they the same factors — crew shortages, equipment problems, subcontractor performance — that had driven delays on earlier milestones? Or had new problems emerged?
•  Was there a realistic path to completion of Milestone 8 absent the termination? If Northgate had not terminated the MCA on April 1, 2024, how much additional time would Meridian have needed to complete Milestone 8? Was Henley asked to provide an estimate, and if so, what was it?
•  Explore whether Henley communicated to anyone at Meridian — whether to Yeung, Sandoval, or others — that the project was unrecoverable from a schedule standpoint. Were there emails, text messages, or other communications in which Henley expressed the view that the project could not be completed on schedule? If such communications exist in the custodial file, they should be marked and used as exhibits.
F. Aggregate Phase 2 Liquidated Damages
This subsection walks Henley through the aggregate Phase 2 liquidated damages calculation to ensure the financial consequences of Meridian's performance failures are on the record.
•  Walk Henley through the total Phase 2 liquidated damages:
Milestone 5: 22 days × $175,000/day = $3,850,000
Milestone 6: 68 days × $175,000/day = $11,900,000
Milestone 7: 91 days × $175,000/day = $15,925,000
Milestone 8: 134 days × $175,000/day = $23,450,000, capped at 10% of $91M milestone value = $9,100,000
Total Phase 2 LDs: $40,775,000
•  Calculate the combined Phase 1 and Phase 2 liquidated damages:
Phase 1 (Milestone 3): $8,225,000
Phase 2 (Milestones 5–8): $40,775,000
Combined Total: $49,000,000
•  Confirm that the aggregate cap on liquidated damages under the MCA was $60 million (5% × $1.2 billion). The $49 million in assessed liquidated damages is within the aggregate cap, and therefore the full $49 million is recoverable.
•  Establish Henley's awareness of these financial consequences during the project. Did Henley understand that the accumulating liquidated damages were creating a growing financial liability for Meridian? Did he communicate the magnitude of the LD exposure to Meridian management? Was the LD exposure a topic of discussion in internal meetings or communications?
VI. TOPIC AREA 4: PHASE 3 PERFORMANCE — FAILURE TO MOBILIZE
A. Phase 3 Scope and Status
Phase 3 was the largest and most complex phase of the Northgate fiber build-out, encompassing 9,700 route miles across Maryland, Virginia, and Eastern Pennsylvania. With an aggregate milestone value of $629 million — more than half of the total Contract Price — Phase 3 represented the heart of the remaining work under the MCA.
•  Confirm the Phase 3 scope: Milestones 9 through 14, planned for July 2023 through March 2025, covering 9,700 route miles in Maryland, Virginia, and Eastern Pennsylvania.
•  Confirm the Phase 3 aggregate milestone value: $629 million, making it the largest phase by far.
•  Confirm that Meridian began mobilizing crews in the Phase 3 geography — specifically in Maryland — in July 2023.
B. Minimal Progress
Despite mobilizing in July 2023, Meridian made virtually no meaningful progress on Phase 3 work before the April 1, 2024 termination. This section establishes the extent of the failure and its causes.
•  Establish that only approximately 340 of the planned 9,700 route miles were constructed in Phase 3 before termination. This represents approximately 3.5% of the Phase 3 scope — a staggeringly low completion rate given that mobilization began nine months before termination.
•  Explore the reasons for this near-complete lack of progress. Was the Phase 3 failure attributable to the same operational deficiencies that plagued Phase 2, or were there additional factors?
•  How many crews were deployed in the Phase 3 geography at any given time during the July 2023 to April 2024 period? How did actual deployment compare to the crew plan?
•  Were resources being diverted from Phase 3 to try to finish incomplete Phase 2 work, particularly the unfinished Milestone 8? If so, who made the decision to prioritize Phase 2 over Phase 3, and was Northgate consulted about this reallocation?
•  Was Henley aware that Phase 3 mobilization was severely behind plan? If so, what did he communicate to Meridian management about the Phase 3 shortfall, and what response did he receive?
C. Phase 3 Payment Disputes
The Phase 3 payment dispute is the basis for Count II of Meridian's Verified Complaint, in which Meridian seeks $16.5 million in disputed payment applications. This section establishes the factual record regarding those disputed invoices.
•  Confirm that Meridian submitted payment applications totaling $48.2 million for Phase 3 work performed (or claimed to have been performed) prior to the termination.
•  Confirm that Northgate reviewed those applications, approved and paid $31.7 million, and disputed $16.5 million.
•  Establish the basis for Northgate's dispute of the $16.5 million: the payment applications contained claims for work that was defective and required remediation, and the unit counts submitted by Meridian were inflated beyond the quantity of work actually installed in the field.
•  Explore Henley's involvement in the preparation and certification of the disputed payment applications. Did Henley approve the field-level certifications of work completed that supported those applications? Was he involved in verifying the unit counts before the applications were submitted to Northgate?
•  Were the unit counts that Meridian submitted in its Phase 3 payment applications accurate and supportable? What was the basis for the quantities claimed? Were they derived from field measurements, GPS surveys, crew reports, or some other methodology? Were they independently verified?
•  If Henley signed off on certifications that supported inflated unit counts or claims for defective work, explore whether he was aware of the discrepancies at the time or whether the inflated counts were the result of systemic failures in Meridian's field reporting processes.
VII. TOPIC AREA 5: QUALITY DEFECTS AND NON-CONFORMANCE REPORTS
A. NCR Overview
The volume and severity of non-conformance reports issued during the Northgate project is a central element of Northgate's defense and counterclaims. The 287 NCRs — including 43 classified as critical — document a pervasive pattern of quality failures that Northgate contends was attributable to Meridian's workforce, methods, and inadequate supervisory oversight.
•  Establish the total number of NCRs issued during the project: 287, of which 43 were classified as "critical" and 244 were classified as "non-critical."
•  Confirm that Northgate's quality assurance team documented defects in monthly reports that were provided to Meridian and that formed the basis for the NCRs.
•  Confirm that Henley received NCRs and was required to respond to them in his capacity as Vice President of Field Operations. Establish the process by which NCRs were communicated to Henley, the timeframe in which he was expected to respond, and the nature of the responses he provided.
B. Critical NCRs — 43 Total
The 43 critical NCRs document serious construction defects that affect the integrity, safety, and performance of the fiber network. This section should walk through representative examples in detail while establishing the systemic nature of the critical defect problem.
•  Identify the types of critical defects documented in the 43 critical NCRs:
Splice Loss Exceeding Specification: Fiber splices that exceeded the maximum allowable splice loss per Northgate Technical Specification NS-FIBER-2020 and the applicable ANSI/TIA-568 industry standards. Excess splice loss degrades signal quality and network performance, and affected splices must be re-done at significant cost.
Improper Conduit Depth: Conduit installed below the required burial depth as specified in NS-FIBER-2020 and applicable local code requirements. Insufficient burial depth exposes the fiber infrastructure to damage from surface activities, utility conflicts, and environmental erosion, creating long-term reliability risks.
Unauthorized Route Deviations: Instances where Meridian deviated from the approved design and route plan without obtaining a Change Order or prior engineering approval from Northgate. Unauthorized route deviations can result in encroachment on private property, interference with existing utilities, and non-compliance with easement and right-of-way agreements.
•  Walk through 5 to 8 representative critical NCRs using Bates-stamped documents that have been pre-marked as exhibits. For each exemplar NCR, establish the following:
•  The date the NCR was issued.
•  A detailed description of the defect, including the specific specification or standard that was violated.
•  The geographic location and the milestone to which the defective work was allocated.
•  Whether the defect was cured by Meridian. If so, when was it cured, and what was the cost of remediation?
•  If the defect was not cured, why not? Was a cure attempt made and found inadequate, or was no cure attempted at all?
•  Elicit admissions from Henley regarding the root causes of the critical defects:
•  Were insufficiently trained crews responsible for splice loss failures and conduit depth violations?
•  Did Meridian's field crews fail to follow the requirements of Northgate Technical Specification NS-FIBER-2020? If so, was that a training issue, a supervision issue, or both?
•  Was there adequate field-level quality control by Meridian's supervisory personnel? Were inspections conducted before work was submitted for Northgate's review? If inspections were conducted, how did the defects escape detection?
•  Did Meridian use unqualified or inexperienced subcontractors on portions of the work? Were subcontractors vetted for their ability to perform fiber construction work at the quality level required by the MCA and NS-FIBER-2020?
C. Non-Critical NCRs — 244 Total
While individually less severe than critical NCRs, the sheer volume of non-critical NCRs — 244 over the life of the project — demonstrates a systemic quality management failure rather than a collection of isolated incidents.
•  Confirm the volume: 244 non-critical NCRs. During Phase 2, this volume equated to nearly one non-critical NCR per business day, an extraordinary rate of defect identification that points to deep-seated quality control problems.
•  Elicit testimony establishing that the pattern of non-critical NCRs reflects a systemic quality management failure across Meridian's field operations, not merely random or isolated construction errors. Were the same types of defects recurring across different crews, different geographic areas, and different time periods?
•  Were non-critical NCRs addressed in a timely manner? What was Meridian's average response time to non-critical NCRs? Were there instances where non-critical NCRs remained open for extended periods without corrective action?
D. February 2024 NCRs — 12 Additional Critical NCRs
The 12 additional critical NCRs issued in February 2024 are particularly significant because they were issued during the cure period following Cure Notice No. 2 (February 19, 2024). They demonstrate that Meridian's quality was continuing to deteriorate even as it claimed to be implementing corrective measures.
•  Confirm that 12 additional critical NCRs were issued in February 2024, bringing the total number of critical NCRs from 43 to 55 (or, if the 12 are included within the 43 total, confirm that they represent a significant late-project spike in critical defects).
•  Establish that these NCRs were cited by Northgate in its March 12, 2024 letter rejecting Meridian's Corrective Action Plan as inadequate. The issuance of 12 critical NCRs during the very period when Meridian was supposed to be demonstrating improvement was powerful evidence that the cure was failing.
•  Establish that quality was continuing to deteriorate — not merely failing to improve — even as Meridian claimed to be implementing corrective measures. This undermines Meridian's argument that the termination was premature or pretextual.
•  What was Henley doing in February 2024 to address quality concerns? Did he deploy additional supervisory personnel? Did he implement new QC procedures? Did he replace underperforming crews or subcontractors? If he took these steps, why did they fail to prevent the issuance of 12 additional critical NCRs?
E. Quality Standards Under the MCA
•  Direct Henley's attention to MCA § 12.4 (Quality Standards), which required all work to conform to Northgate Technical Specification NS-FIBER-2020 and applicable industry standards, including ANSI/TIA-568 (telecommunications infrastructure standards) and BICSI guidelines (Building Industry Consulting Service International design and installation standards).
•  Confirm Henley's understanding of these requirements. Were the quality standards clearly communicated to Meridian's field crews and subcontractors? Did Meridian provide training on NS-FIBER-2020 to its workforce?
•  Did Meridian have its own internal QC/QA procedures apart from Northgate's quality assurance program? If so, what did they consist of? Were they followed consistently throughout the project? If Meridian had internal QC procedures and they were followed, why did 287 NCRs — including 43 critical — result?
•  Did Henley ever communicate to Meridian management — Yeung, Sandoval, or others — that the quality problems were systemic rather than isolated? If so, what was the substance of those communications, and what response did he receive?
F. Remediation Costs — Counterclaim III Foundation
This subsection establishes the factual basis for Northgate's Counterclaim III, which seeks $18.3 million in remediation costs to correct the defective work documented in the NCR record.
•  Establish that the defects documented in the critical NCRs require remediation — specifically, re-splicing of fiber connections, re-trenching and re-installation of conduit at the proper burial depth, and route correction for unauthorized deviations. These remediation activities are necessary to bring the installed fiber network into conformance with NS-FIBER-2020 and to ensure the long-term performance and reliability of the network.
•  Explore Henley's knowledge of the estimated costs of remediation. Has Henley or anyone at Meridian estimated the cost to correct the critical defects? Is he aware of industry-standard costs for the types of remediation work required?
•  For purposes of Northgate's Counterclaim III, the remediation costs are estimated as follows:
43 critical NCRs × $275,000 average remediation cost per critical defect = $11,825,000
244 non-critical NCRs × $26,500 average remediation cost per non-critical defect = $6,466,000
Total estimated remediation costs: approximately $18,300,000
•  Does Henley agree or disagree with the characterization that the defective work documented in the NCRs will need to be remediated? If he disagrees, on what basis? Does he contend that any of the documented defects do not require correction?
VIII. TOPIC AREA 6: CREW SHORTAGES AND RESOURCE MANAGEMENT
A. Planned vs. Actual Crew Deployment
Crew shortages are a central element of Northgate's theory of the case. Northgate contends that Meridian's persistent failure to deploy adequate field crews was the single most significant cause of milestone delays across all three Phases. This section explores the gap between Meridian's staffing plan and its actual deployment.
•  What was Meridian's crew deployment plan for the Northgate project at each Phase? How many crews were planned for deployment during Phase 1, Phase 2, and Phase 3, and how were they distributed geographically?
•  How many crews were actually deployed at peak during each Phase? What was the maximum concurrent deployment on the Northgate project?
•  Meridian had approximately 2,400 employees at peak — how many of those were assigned to the Northgate program at any given time? What percentage of Meridian's total workforce was dedicated to the Northgate project versus other Meridian contracts?
•  Use Meridian's crew deployment logs and labor tracking spreadsheets — produced from Henley's custodial file and from Meridian's project management records — as exhibits. Walk Henley through these documents to identify specific shortfalls between planned and actual crew levels, organized by Phase and by milestone period.
•  Identify the periods of greatest shortfall. Were crew shortages most severe during Phase 2, when delays were accelerating? Were shortages even more pronounced during Phase 3, when only 3.5% of the work was completed?
B. Causes of Crew Shortages
Understanding the causes of crew shortages is essential to establishing that the shortages were within Meridian's control and were not attributable to external forces.
•  Were Meridian crews assigned to other Meridian projects simultaneously with the Northgate program? If so, which projects? Who made the allocation decisions? Was Henley consulted, or were allocation decisions made above his level by Yeung, Sandoval, or Ridgepoint Capital?
•  Did Ridgepoint Capital Group's investment thesis or directives affect resource allocation for the Northgate project? Ridgepoint acquired 55% of Meridian in 2018 for approximately $285 million. Was Ridgepoint exerting pressure on Meridian to pursue additional contracts, spread resources across multiple projects, or prioritize profitability metrics over project-specific performance? If Ridgepoint was involved in resource allocation decisions, the examining attorney should explore this topic carefully, as it directly undermines Meridian's claims that crew shortages were caused by market conditions rather than management decisions.
•  Were subcontractors failing to provide their committed labor? If so, was this because Meridian's subcontracts were insufficiently favorable to attract reliable performers, or because the available labor pool in the region was genuinely constrained?
•  Were recruitment and retention challenges a contributing factor? If so, were those challenges within Meridian's control — for example, were Meridian's wage rates and benefits competitive in the market, or was Meridian losing skilled workers to competitors offering better compensation?
C. Impact of Crew Shortages on Schedule
•  Establish the causal link between under-staffing and milestone delays. For each of the delayed milestones (MS3, MS5, MS6, MS7, MS8), can Henley identify the specific impact of crew shortages on the construction schedule? Can he quantify, even approximately, how many days of delay were attributable to insufficient crew levels?
•  Were there specific periods during the project where Henley reported to management that crew levels were insufficient to meet the milestone schedule? If so, when did he make those reports, in what form, and what was the response?
•  Did Henley request additional resources — more crews, more equipment, more subcontractor support — from Meridian management during the project? What was the response from Yeung and Sandoval? Were his requests fulfilled, partially fulfilled, or denied? If denied, what reason was given?
D. Impact of Crew Shortages on Quality
The connection between crew shortages and quality defects is an important element of Northgate's case, because it demonstrates that the same operational failures driving schedule delays were also driving the quality problems documented in the NCRs.
•  Were inadequately trained or inexperienced crews responsible for any of the quality defects documented in the NCRs? Did Meridian's inability to recruit and retain experienced fiber construction workers result in the deployment of less skilled personnel who were more likely to produce defective work?
•  Was Meridian using less experienced or less qualified subcontractors because of its inability to attract the more qualified firms? Did the quality of Meridian's subcontractor pool deteriorate over the course of the project?
•  Is there a connection between rushed work performed by insufficient crews — attempting to maintain schedule with inadequate labor — and the volume of NCRs? In other words, were crews cutting corners or working without adequate supervision because they were spread too thin?
IX. TOPIC AREA 7: MERIDIAN'S PERMITTING DEFENSE (MCA § 5.3)
A. MCA § 5.3 — Permitting Responsibilities
Meridian's principal contractual defense is that NFA's failure to timely obtain municipal permits caused significant delays to the project. This section examines the permitting defense in detail to demonstrate that it is inconsistent with the MCA's allocation of permitting responsibilities, the actual permitting record, and Henley's contemporaneous assessments of delay causation.
•  Walk through MCA § 5.3 with the witness and confirm Henley's understanding of the allocation of permitting responsibilities between Northgate (as Owner) and Meridian (as Contractor). Establish specifically which categories of permits were Owner responsibility and which were Contractor responsibility. The MCA likely distinguishes between high-level franchise or operating permits (Owner responsibility) and local construction permits, road-opening permits, and encroachment permits (Contractor responsibility, or shared responsibility with specific procedural requirements).
•  Meridian's position, as stated in Victor Sandoval's February 2, 2024 response to Cure Notice No. 1, is that NFA's failure to timely obtain municipal permits caused delay. Challenge this assertion by establishing through Henley's testimony precisely which permits Meridian claims were delayed, which entity was responsible for obtaining those permits under § 5.3, and whether Meridian's own permit applications were timely and complete.
•  Were there specific municipal permits that Meridian itself was responsible for obtaining and failed to obtain on a timely basis? If so, those delays are attributable to Meridian, not Northgate.
B. Subpoenas to Municipal Permitting Authorities
Third-party subpoenas were issued to three municipal permitting authorities to obtain records bearing on the permitting timeline. These records may shed light on whether the permitting delays Meridian alleges were caused by Northgate's failure to apply for permits on time or by the permitting authorities' processing timelines, which are outside any party's control but which the MCA's risk allocation framework addressed.
•  Explore Henley's personal knowledge of the permitting timelines. Did Henley have visibility into the status of permit applications during the project? Did he track permitting as part of his schedule management responsibilities?
•  Were there instances during the project where Meridian's field crews arrived at construction locations before the necessary permits had been secured? If so, was that because Northgate had failed to obtain the required permits, or because Meridian's own permitting submissions were late or incomplete?
•  If Meridian's crews were standing down at specific locations waiting for permits, what steps did Henley take to mitigate the delay — for example, did he redeploy those crews to other locations where permits were in hand?
C. Henley's Contemporaneous Communications
This is the most critical subsection of the permitting defense examination. The objective is to demonstrate that Henley's own contemporaneous emails and internal reports attributed project delays to Meridian-caused issues — primarily crew shortages and equipment problems — rather than to permitting delays.
•  Use specific emails and internal reports from Henley's custodial file that discuss the causes of schedule slippage during Phase 2 and Phase 3. If these documents identify crew shortages, equipment failures, and subcontractor problems as the primary causes of delay — without mentioning permitting as a significant factor — they will be powerful impeachment evidence against the permitting defense.
•  Contrast Henley's contemporaneous explanations of delay causation with the litigation-driven permitting defense now asserted in Meridian's pleadings and discovery responses. If the permitting defense did not appear in Henley's real-time assessments, when did it first emerge? Was it developed after the fact, during the litigation, rather than based on Henley's contemporaneous field experience?
•  Ask Henley directly: during the project, did he consider NFA permitting delays to be a significant cause of milestone slippage? If he answers yes, present his contemporaneous communications that tell a different story. If he answers no, his testimony directly undermines one of Meridian's principal defenses.
X. TOPIC AREA 8: MERIDIAN'S SCOPE CHANGE DEFENSE (MCA § 16.1)
A. MCA § 16.1 — Change Order Requirements
Meridian's second principal defense is that Northgate directed 14 scope changes during the project that were never formalized as Change Orders, resulting in additional work and schedule impact for which Meridian was not compensated. This section examines the scope change defense by establishing that Meridian failed to follow the contractual Change Order procedure and that many of the alleged "changes" were not scope changes at all.
•  Confirm Henley's understanding of MCA § 16.1, which prov