CEO Executive AssistantMajor pipeline and infrastructure projects are among the most capital-intensive, regulatory-heavy, and publicly scrutinized activities an energy company undertakes. A single interstate natural gas pipeline can take five to seven years from initial planning through FERC certificate issuance to in-service date, involve hundreds of landowners, require simultaneous state and federal approvals, and represent billions of dollars in committed capital. The CEO’s role spans all of it: strategic oversight, investor assurance, regulatory credibility, and community accountability.
That breadth of responsibility requires equally broad administrative support. An executive assistant who understands energy CEO pipeline project coordination does not simply schedule meetings. They maintain the operational infrastructure that keeps the CEO informed, prepared, and well-positioned across every major workstream of a long-duration capital project. This article covers the five core areas where skilled admin support makes the most difference.
Managing the Project Steering Committee Meeting Schedule
Large pipeline projects are governed through a steering committee structure that typically includes the CEO, CFO, general counsel, vice president of engineering, vice president of regulatory affairs, and the project executive. These committees meet regularly throughout the project lifecycle to review progress, make resource decisions, address risk items, and align on communications strategy. For a CEO managing multiple projects in parallel, the steering committee calendar is one of the densest and most consequential parts of their schedule.
The EA’s job in managing this structure begins with establishing a standing cadence. Monthly steering committee meetings are standard on active projects, with weekly or biweekly project leadership briefings feeding into those monthly reviews. The EA sets and maintains these recurring series, coordinates attendance across a large and frequently traveling executive group, and ensures that meeting preparation materials arrive at the right time.
Preparation materials for a steering committee meeting are not light reading. A well-run project will produce a standardized project dashboard covering schedule performance, cost performance against budget, open risk items, upcoming regulatory milestones, and any landowner or community escalations. The EA coordinates the assembly of this package from the project management office, ensures it reaches steering committee members at least 48 hours before the meeting, and confirms the CEO has time to review it before the meeting begins.
Agenda Management and Action Item Tracking
Steering committees surface decisions and action items that must be tracked between meetings. The EA maintains the action item log from each session, distributes it within 24 hours of the meeting, and tracks completion status in advance of the next meeting. Items that are overdue or at risk of slipping before the next session require a proactive follow-up from the EA to the responsible party.
Agenda discipline matters at this level. Steering committee time is expensive, and the CEO’s time is the most constrained resource in the room. The EA works with the project executive and the CEO’s chief of staff (where one exists) to ensure agenda items are decision-ready before they reach the committee. Informational briefings that do not require CEO input should be handled at lower levels and summarized in the pre-read materials rather than consuming committee meeting time.
For large projects with multiple work packages or geographic segments, the EA may also coordinate subcommittee structures: separate reviews for environmental compliance, right-of-way acquisition, or construction readiness that report up to the main steering committee. Keeping these nested meeting structures synchronized, and ensuring the CEO receives the right level of detail from each layer, is an ongoing coordination task that requires both organizational discipline and subject matter familiarity.
Tracking FERC and State Regulatory Approval Milestone Calendars
Federal Energy Regulatory Commission approval is required for interstate natural gas pipelines under Section 7 of the Natural Gas Act, and the FERC review process is among the most complex regulatory sequences in the US energy sector. State-level approvals add additional layers: environmental permits, utility commission approvals in states where the pipeline will operate, and in some cases, state-level review under the National Environmental Policy Act or its state equivalents.
The EA supporting a CEO on a pipeline project must maintain a comprehensive regulatory milestone calendar that covers every approval required for the project to proceed. This is not a simple list. A major pipeline project may have 20 or more discrete approval milestones across federal and state agencies, each with its own procedural requirements, comment periods, and decision timelines.
Building and Maintaining the Milestone Tracker
The regulatory milestone tracker should include: the name of the approval, the responsible agency, the current procedural stage, the next key date (comment deadline, agency decision, or procedural milestone), the company lead responsible for each workstream, and a status indicator. The EA builds this tracker in coordination with the regulatory affairs team and updates it on a cadence tied to the steering committee meeting cycle.
The tracker serves two purposes for the CEO. First, it provides a project-wide view of regulatory progress that the CEO needs to speak credibly to investors, board members, and major stakeholders. Second, it flags upcoming deadlines that require CEO-level attention, whether that means signing a formal comment, approving a regulatory strategy decision, or scheduling a meeting with an agency official before a key decision window closes.
See regulatory compliance support for related milestone monitoring disciplines. The same frameworks that govern ongoing compliance apply equally to major project approval processes.
FERC dockets are publicly available, and project opponents use the same public record to monitor progress and identify intervention opportunities. The EA should ensure the CEO is briefed on any significant third-party filings in active FERC dockets before those filings reach the media or are raised in investor conversations.
Coordinating Responses to Regulatory Deadlines
When a FERC information request arrives, or when a state agency sets a public comment deadline, the response process is coordinated by the regulatory affairs and legal teams. The CEO’s role is typically to approve the strategic position and in some cases sign the formal response. The EA’s job is to protect time in the CEO’s calendar for that review and approval, ensure the review materials are clear and decision-ready, and confirm that submissions are made on schedule.
Missed regulatory deadlines carry real consequences on a FERC-jurisdictional project. The EA does not need to be a regulatory expert, but does need to treat regulatory submission deadlines with the same urgency as a board meeting or an earnings call.
Coordinating with Landowner Relations Teams on CEO Communications
Right-of-way acquisition is one of the most complex and publicly visible components of any pipeline project. On a large project, hundreds or thousands of landowners must be contacted, negotiated with, and in some cases taken through eminent domain proceedings. The landowner relations team manages this workstream day to day, but the CEO periodically becomes directly involved, either proactively in high-profile cases or reactively when landowner disputes escalate into media or political attention.
The EA’s role in landowner-related CEO communications is primarily one of coordination and preparation. When the landowner relations team identifies an escalation that requires CEO involvement, the EA schedules the relevant briefing, ensures the CEO receives background materials on the specific landowner situation and any political or media dimensions, and coordinates any follow-up actions the CEO commits to.
Managing CEO-Level Landowner Correspondence
Some landowners request direct communication with the CEO. These requests arrive through the general counsel’s office, the landowner relations team, or directly to the CEO’s office through public channels. The EA screens these requests, routes them to the appropriate team for a recommended response, and ensures the CEO is briefed before any personal response is drafted or sent.
In some cases, the CEO may choose to meet directly with a landowner or landowner group, particularly in communities where the project has significant local impact. These meetings require coordination between the EA, the landowner relations team, the communications team, and in some cases local government affairs contacts. The EA manages the logistics, prepares a briefing document covering the key landowner concerns and the company’s current negotiating position, and ensures the CEO’s commitments from the meeting are documented and tracked.
The same documentation discipline that governs government affairs contacts applies here. Landowner conversations that involve commitments about project design, compensation terms, or mitigation measures can have legal and regulatory implications. Every CEO-level landowner interaction should be documented and reviewed by legal counsel.
Preparing the CEO for Investor Updates on Capital Project Progress
Capital project progress is a consistent theme on energy company earnings calls, analyst days, and investor presentations. Investors want to know whether projects are on schedule and on budget, what regulatory milestones remain, and when the project will begin generating returns. The CEO is the primary voice on these questions, and the quality of that communication depends heavily on the quality of the preparation.
The EA supports investor-facing capital project communications at several levels. The first is ensuring the CEO has accurate, current project data before any investor interaction. This means coordinating a pre-call or pre-meeting briefing with the investor relations team and the project executive, and ensuring the CEO’s briefing materials include the latest project status, any recent milestone updates, and anticipated questions from the investor community.
Supporting Earnings Call and Investor Day Preparation
For quarterly earnings calls, the EA works with the investor relations team to schedule rehearsal sessions and ensure the CEO’s calendar is protected for Q and A preparation on capital projects. Analysts covering the energy sector track pipeline project milestones closely, and CEOs who are caught without current data on a live call create negative impressions that can take time to repair.
For investor days and analyst conferences, preparation is more intensive. The project section of an investor presentation typically requires input from engineering, regulatory affairs, finance, and the communications team. The EA coordinates the review schedule, tracks the assembly of presentation materials, and manages the internal approval process so the CEO receives a finalized presentation with sufficient time for personal preparation.
McKinsey analysis on capital project performance consistently finds that CEO-level visibility into project status, combined with disciplined executive reporting, is a key differentiator between projects that stay on track and those that drift into overruns. The administrative infrastructure that supports CEO engagement with capital project data is not a peripheral concern. It is directly connected to project outcomes.
Managing the Capital Project Communications Calendar
The EA maintains a capital project communications calendar that maps all investor-facing events, board reporting deadlines, and major project milestones onto a single timeline. This calendar helps the CEO and the investor relations team anticipate when key project updates will coincide with investor touchpoints, and prepare accordingly.
When a significant milestone is reached, whether it is FERC certificate issuance, the start of construction, or commercial in-service, the EA coordinates the logistics of any associated communications: press releases, investor calls, employee announcements, and community notifications. These events are often coordinated with tight timelines, and the EA’s role in synchronizing the parallel workstreams is significant.
Supporting Pipeline Safety Management Review Meetings
Pipeline safety is not only a regulatory requirement. It is a reputational and operational priority that reaches the CEO level through formal management review processes. The Pipeline and Hazardous Materials Safety Administration (PHMSA) mandates written integrity management programs for regulated pipelines, and those programs require documented management review and executive accountability.
The CEO’s involvement in pipeline safety management typically occurs through two channels: formal quarterly or annual management reviews of the integrity management program, and incident response when a safety event triggers executive notification requirements. The EA supports both.
Scheduling Safety Management Reviews
Annual management reviews of the pipeline integrity management program are a compliance requirement under 49 CFR Part 192 and Part 195, depending on whether the pipeline carries natural gas or hazardous liquids. These reviews must be documented, and the CEO or a designated executive must be on record as having participated. The EA schedules these reviews on the annual calendar, coordinates attendance with the pipeline operations and safety teams, and ensures the documentation package is prepared and retained in compliance with PHMSA requirements.
Quarterly safety performance reviews, while not always mandated by regulation, are standard practice at well-run pipeline operators. The EA builds these reviews into the standing meeting structure and coordinates the preparation of the safety performance dashboard: incident rates, near-miss reports, integrity assessment status, and any pending PHMSA correspondence.
The connection to the broader safety reporting function is direct. See safety and environmental reporting for a full treatment of this function.
Supporting Incident Response at the Executive Level
When a pipeline incident occurs, the CEO is typically notified within hours. PHMSA has specific reporting timelines for significant incidents, and state agencies may have parallel notification requirements. The EA’s role in incident response is not operational. It is logistical: ensuring the CEO can reach the right internal contacts immediately, that travel and logistics are arranged if the CEO needs to go to the site, that communications and legal counsel are on standby, and that the CEO’s schedule is cleared to focus on the incident.
In the hours and days following a significant incident, the CEO’s schedule is disrupted by the response. The EA manages that disruption, communicates with external parties whose scheduled meetings must be deferred, and maintains a running log of commitments and communications during the response period.
The Operational Role Behind Every Major Project
Energy CEOs leading large pipeline programs need administrative support that matches the scale and complexity of those projects. The EA who supports this function brings more than scheduling ability. They bring a working knowledge of FERC proceedings and regulatory timelines, the organizational discipline to maintain project tracking systems that span years and dozens of milestones, and the judgment to know when a landowner escalation or a safety review gap needs to be escalated to the CEO rather than handled at a lower level.
The projects that define an energy company’s capital program for a decade deserve the same standard of operational excellence in the executive office as they receive in the field. Skilled admin support is how that standard is met.