When to Fire Your Compliance Consultant

Foreword

Foreword

This professional reference is one of a series Energy Compliance, Inc. publishes for registered entities and the people who run their compliance programs. I have spent more than thirty years on every side of the bulk electric system. I have operated control centers as a Reliability Coordinator, Transmission Operator, and Power System Operator. I have audited grid facilities and signed off on findings as a senior compliance auditor. I have worked enforcement matters from inside the regulator's process. For the last several years I have advised registered entities directly through the firm I founded. The entities that do reliability well share a common habit. They take the standards seriously without confusing them with reliability itself. They know that a NERC Reliability Standard is a floor, not a ceiling. They know that compliance is something an auditor evaluates, but reliability is something a system either delivers or does not. They prepare for audits by building programs that survive real questions, not binders that look thick. That is the perspective these references try to share. Each one focuses on a single topic. A standard family, an operational function, a regulatory framework, or an emerging industry challenge. Each one walks through how the topic actually works. These references are written for the compliance manager who wants to understand the system, not just memorize requirements. For the legal counsel who has to brief a board honestly. For the senior operator who has been told that compliance and reliability are the same thing and suspects they are not. For the new compliance hire who was handed a binder and told good luck. Energy Compliance exists because much of the consulting offered to registered entities today is structured for billable hours rather than for outcomes. We staff every engagement with one senior practitioner. We do not bring five people to a meeting that needs one. We automate the work that should be automated, and we apply senior judgment to the work that requires it. If that approach is what you are looking for in a compliance partner, the back of this reference has our contact information. If not, the reference still belongs to you. Take what is useful. Apply it well. And remember the only test that ultimately matters: when the system needs to perform, does it?

— Rob Smith Founder, Energy Compliance, Inc.

EC-WP-705 When to Fire Your Compliance Consultant

The Sunk-Cost Trap in Compliance Engagements

The Sunk-Cost Trap in Compliance Engagements

Most entities know the engagement has gone wrong. They stay anyway because the math of leaving feels worse than the math of staying. It almost never is.

Compliance engagements are uniquely vulnerable to the sunk-cost trap. The fee has been paid. The deliverables have been received. The team has invested time learning the consultant's framework. Switching means giving up the perceived value of all of that, and the perceived value usually overstates the actual value by a significant margin. The math also gets distorted by uncertainty. Staying with the current consultant is a known quantity, even if the quantity is mediocre. Switching introduces unknowns. New onboarding. New context-building. Possible disruption to the audit calendar. Faced with that contrast, leadership often defaults to staying, on the theory that mediocre and known is safer than potentially-better and unknown. The theory is wrong more often than the entity recognizes. The actual math runs the other way. Staying with a failing engagement compounds cost month over month. Each additional engagement cycle adds documentation the entity will eventually have to maintain, complexity the entity will eventually have to explain, and dependency the entity will eventually have to unwind. The cost of switching is paid once. The cost of staying is paid forever, or until the audit forces the issue, at which point the entity is paying both. Recognizing the trap is the first move. The question is not whether the engagement was worth what was paid. That money is gone. The question is whether the next dollar of engagement spending produces more value than the next dollar of replacement or termination spending. Asked that way, the answer is usually obvious, and usually different from the answer the sunk-cost frame would have produced.

FROM THE FIELD Sunk-cost reasoning is the single most common reason entities stay in failing compliance engagements past the point of value. The right question is not whether the engagement was worth what was paid. The right question is whether the next dollar produces more value here or somewhere else. Staying with a failing engagement compounds cost. Switching pays the cost once. The math almost always favors switching earlier than entities choose to.

The Leading Indicators of a Failing Engagement

The Leading Indicators of a Failing Engagement

Failing engagements telegraph the failure for months before the entity acts. The signals are recognizable. Listening for them earlier saves significant cost.

Failing engagements produce recognizable leading indicators long before the entity decides to act. The senior named on the contract starts attending fewer meetings. The decisions that used to come back inside a day now come back inside a week. Status reports get longer and contain less substance. Requests for clarification on the consultant's deliverables go to a different person each time. None of these signals are dramatic. All of them are diagnostic. A second category of signal involves the deliverables themselves. The deliverable arrives later than promised. When it arrives, it is closer to a draft than to a finished product. The framework it describes has expanded since the kickoff without anyone explaining why. The recommendations come with extensive qualification language that preserves optionality for the consultant rather than committing to a position. Each individual deliverable is reasonable enough. The trajectory is not. The third category involves the entity's experience of the engagement. Internal staff begin to dread the consulting meetings. They feel the meetings are taking time without producing forward motion. They start working around the consultant rather than through them. They handle compliance questions internally that they would previously have routed to the engagement. This is the program quietly reclaiming ownership because the engagement is no longer providing it. Programs that surface these signals early run a deliberate quarterly review of the engagement, separate from the engagement itself. The reviewer is a senior leader inside the entity who has not been the day-to-day point of contact and who is empowered to call the question honestly. The review takes an hour. The investment pays for itself many times over by surfacing failing engagements before they have caused months of additional damage.

FROM THE FIELD Failing engagements telegraph the failure for months before the entity acts. The senior absences, the slipping deliverables, the qualification language. All of them are diagnostic. When internal staff start working around the consultant rather than through them, the program is telling you the engagement has stopped producing value. A quarterly engagement review by someone who is not the day-to-day point of contact is the cheapest insurance available against extended bad engagements.

The Lagging Indicators You Should Have Caught Earlier

The Lagging Indicators You Should Have Caught Earlier

Some signals only appear once the damage is done. Recognizing them at all costs less than failing to recognize them, but earlier signals existed and were missed.

Some indicators of engagement failure are lagging by definition. The audit lands. The findings include issues the consultant was specifically retained to address. The mitigation timeline runs longer than expected because the program is harder to defend than the consultant claimed. The leadership conversation that follows is uncomfortable, and the conversation usually ends with a question the entity should have been asking eighteen months earlier. Other lagging indicators surface during personnel transitions. A compliance manager rotates and the new manager cannot reconstruct the reasoning behind a structure the engagement introduced. The consultant is asked to explain and provides a memorandum that does not actually answer the question. The new manager is left to inherit a program they cannot fully defend, and the engagement is exposed as having operated on context that lived only in the consultant's head. A third lagging indicator involves cost trajectory. The engagement's annualized fee has grown each cycle without the underlying work expanding. The growth was justified at each renewal on the basis of expanded scope, additional support, or new methodology, but no individual increase was large enough to trigger a real review. By the time the entity adds up the cumulative growth, the engagement costs significantly more than its original framing and produces no commensurate increase in program quality. These signals are painful because they prove the leading indicators existed and were missed. The mature posture is to treat each lagging signal as a reason to revisit the entity's engagement-review discipline, not as a reason to feel inadequate. Programs that learn from these moments build the muscle to catch the next failing engagement earlier. Programs that do not run the same arc again with the next consultant.

FROM THE FIELD Lagging indicators are diagnostic too, but at much higher cost. The leading indicators existed eighteen months earlier. Listen better next time. Cost trajectory is the indicator entities miss most often. Cumulative fee growth across cycles is rarely justified by cumulative value growth. Treat every lagging signal as a reason to strengthen the engagement-review discipline, not as a reason to feel inadequate. The discipline is what catches the next one early.

The Difference Between Friction and Failure

The Difference Between Friction and Failure

Not every uncomfortable engagement is failing. Some good engagements feel uncomfortable because they push back honestly. Telling the difference matters.

Not every difficult engagement is a failing engagement. Some of the strongest compliance engagements feel uncomfortable from the inside because the consultant pushes back on internal practices, declines to bill hours the engagement does not require, and refuses to ratify documentation the entity wanted ratified. That discomfort is usually a sign of a working engagement, not a failing one. Confusing it with failure costs the entity a strong consultant and replaces them with a weaker one who will be more agreeable and produce worse outcomes. The signal that distinguishes friction from failure is the trajectory of the program. Friction with a strong consultant produces a program that gets simpler, more defensible, and easier for operators to explain. Failure with a weak consultant produces a program that gets larger, more complex, and more dependent on the consultant. The two trajectories are visible inside six months. The friction may persist. The trajectory tells the entity which kind of engagement they actually have. Another differentiator is who initiates the friction. A strong consultant pushes back on the entity when the entity is wrong, and the entity may experience the pushback as obstruction. A weak consultant pushes back on the entity when the consultant is protecting their billable hours, and the entity may experience the pushback as concern for the program. Distinguishing the two requires honest internal review of the substance of the disagreement, not just the experience of it. The simplest test is to ask whether the consultant is willing to lose the engagement to deliver an honest answer. Strong consultants are. Weak consultants are not. If the engagement has produced multiple instances of the consultant declining to bill work that did not need to be done, declining to expand scope that did not need to expand, or refusing to ratify a position the entity wanted ratified, the friction is almost certainly the friction of a working engagement. Reframe accordingly.

FROM THE FIELD Friction is normal in strong engagements. The strongest consultants are uncomfortable to work with because they push back honestly. The trajectory of the program tells the entity which kind of engagement they have. Simpler and more defensible means working. Larger and more dependent means failing. Strong consultants are willing to lose the engagement to deliver an honest answer. If yours has demonstrated that posture, do not confuse the discomfort with failure.

Building the Exit Case Internally

Building the Exit Case Internally

The exit case is built internally before it is delivered externally. Skipping the internal alignment step makes the external conversation significantly harder.

Exiting a compliance engagement requires internal alignment that takes longer to build than most entities anticipate. The compliance manager may be ready to end the engagement. The senior leader who approved the engagement originally may not be. Legal may have concerns about the contract. Procurement may have process requirements. Until those internal conversations have converged, the external exit conversation will not land cleanly. The case for exit is built on three pillars. First, the documented gap between what the engagement promised and what it delivered, with specific examples. Second, the cost of continuing, including the projected forward-cost trajectory and the ongoing complexity the engagement is adding to the program. Third, the realistic alternative, which may be a different consultant, a different engagement model, or no consultant at all. Without all three pillars, the internal conversation tends to stall on the first concern that arises. Internal alignment also requires honest acknowledgment of what the entity got right and got wrong in the original selection. The selection process may have weighted the wrong criteria. The contract may have lacked accountability provisions that would have made the current situation easier to manage. The engagement-review cadence may not have caught the failure earlier. Naming these honestly inside the entity is uncomfortable and necessary, because it informs the next selection cycle and prevents the same pattern from repeating. Once the internal alignment is in place, the external conversation becomes considerably easier. The case is documented. The decision-makers are aligned. The replacement plan is ready. The exit conversation then becomes a delivery, not a negotiation, and the consultant has limited room to argue the case backward. Entities that try to skip this step and conduct the exit conversation without internal alignment usually end up renewing the engagement they intended to end, which makes the next exit attempt harder still.

FROM THE FIELD The exit case is built internally before it is delivered externally. Skipping that step usually means the consultant talks the entity into renewing. Three pillars: the documented gap, the cost of continuing, the realistic alternative. Without all three, the internal conversation stalls on the first concern. Acknowledge what the entity got wrong in the original selection. That honesty informs the next cycle and prevents the pattern from repeating.

Conducting the Exit Conversation

Conducting the Exit Conversation

The exit conversation is a delivery, not a negotiation. The structure protects the entity, the program, and the relationship.

The exit conversation is a single meeting, conducted in person where possible, by the senior leader inside the entity who owns the engagement decision. The conversation is short. The framing is direct. The engagement is ending. The reasons are summarized briefly. The transition timeline is stated. The expectations for transition deliverables are stated. The conversation is not an invitation to debate the decision. The tone matters. A professional, measured exit conversation preserves the option of working with the firm again on different terms in the future. A combative or accusatory exit conversation closes that option and also tends to produce a less cooperative transition. The entity has nothing to gain from making the conversation harder than it has to be. The consultant will hear the message either way. Choosing the professional version protects the entity's reputation in a small industry. The conversation should also include the specific transition deliverables the entity expects. A complete file inventory. Documentation of any frameworks or methodologies the engagement introduced, in language the entity can maintain. A walk-through with the entity's internal team for any institutional knowledge the engagement holds. A timeline for handoff. These expectations should be stated in the meeting, then confirmed in writing within twenty-four hours so that the consultant cannot later claim the requests were not made. Most exit conversations land cleanly when conducted this way. The consultant may push back briefly on the decision. The push-back almost never changes the outcome if the internal alignment was built first. The conversation closes, the transition begins, and the entity has executed the hardest part of the exit. The remaining work is logistical, and logistical work is more tractable than political work.

FROM THE FIELD The exit conversation is a delivery, not a negotiation. Frame it that way and conduct it as a single meeting. Choose the professional version of the conversation. The industry is small and the relationship may matter again later. State the transition deliverables in the meeting. Confirm them in writing within twenty-four hours. Do not leave room for them to be later disputed.

Protecting the Program on the Way Out

Protecting the Program on the Way Out

Programs leak knowledge during transitions. Plan the leak. Don't discover it.

Compliance programs are vulnerable during consultant transitions. Institutional knowledge that lived inside the consultant is at risk of walking out the door with them. Frameworks and methodologies the consultant introduced may not be fully understood internally. Documentation may reference decisions whose reasoning is not captured in the documentation itself. Without deliberate planning, the entity ends up with a program it cannot fully defend and no path to the explanations it needs. The transition plan starts with a knowledge inventory. What does the consultant know that the entity does not. What decisions has the consultant made on the entity's behalf that the entity has not internalized. What documentation exists that requires the consultant's context to interpret correctly. The inventory is built jointly with the consultant where possible, and built unilaterally if the consultant is uncooperative. Either way, the inventory is the basis for the transition deliverables. Once the inventory exists, the transition deliverables become specific. Walk-throughs of each major framework with internal staff present and recording where appropriate. Written documentation of any decisions whose reasoning is not already captured. Handoff of any tools, templates, or working files the consultant has been maintaining. A list of any external contacts (regulators, regional entity staff, other consultants) the engagement has been managing on the entity's behalf. The list should be exhaustive. Anything missed becomes a gap the next audit may surface. Programs that survive transitions cleanly treat the transition as a project with its own owner, its own timeline, and its own quality bar. The work is finite, intensive, and uncomfortable. It produces a program the entity owns end to end. Programs that treat the transition as cleanup or housekeeping discover months later that they have lost something important and have no way to recover it. The cost of that recovery, when it is recoverable at all, far exceeds the cost of conducting the transition properly the first time.

FROM THE FIELD Programs leak knowledge during transitions. Plan the leak. Don't discover it. Build a knowledge inventory before the transition starts. What does the consultant know that you do not? What decisions have they made on your behalf? The transition is its own project, with its own owner and its own quality bar. Treating it as cleanup guarantees you lose something you needed.

Selecting the Replacement (or Choosing Not To)

Selecting the Replacement (or Choosing Not To)

) The replacement decision is the harder decision. Sometimes the replacement is no consultant at all.

After the exit, the entity faces a second decision that is often harder than the first. Who replaces the consultant. The default assumption is that another consultant fills the gap. That assumption deserves scrutiny. The original engagement may have failed because the entity did not need that engagement in the first place. Replacing it with a similar engagement may simply repeat the cycle. The honest replacement question is what the entity actually needs from external compliance support. Strategic advice on a defined scope, episodically, from a senior practitioner. Subject-matter expertise on a particular standard family for a defined deliverable. Audit-defense support during a specific audit cycle. Each of these is a narrow scope that can be addressed by a specific engagement, and none of them implies the long-running, multi-person, framework-heavy engagement that often gets sold as the default model. The replacement may also be no consultant at all. Many entities discover, after exiting a heavy consulting engagement, that the program runs better without the consultant than it ran with them. The engagement was producing complexity faster than the entity could absorb it. The exit removes the complexity faucet, the program shrinks to a size the entity can actually defend, and the next audit lands more cleanly than the previous one. That outcome is uncomfortable to predict and common when it happens. If the entity does select a replacement, the selection should be informed by what the previous engagement taught. The criteria that matter are the ones described in EC-WP-700: senior accountability, single named owner, willingness to push back, alignment of fee structure with outcomes rather than hours. The procurement-style selection that produced the previous engagement is likely to produce another one of the same kind. The risk-management-style selection produces a different result. Choose deliberately. The replacement decision is the hinge on which the program's next two years turn.

FROM THE FIELD The replacement decision is the harder decision. Sometimes the right replacement is no consultant at all. Honest replacement question: what does the entity actually need from external support? The answer is usually narrower than the previous engagement assumed. If you select a replacement, select against the criteria that mattered, not the criteria that produced the engagement you just exited.

About the Author

About the Author

Rob Smith is a senior electric industry professional with over thirty years of experience across every major function of the North American Bulk Electric System. His work spans reliability coordination, transmission operations, regulatory compliance, and cybersecurity reliability. Rob has worked directly in real-time grid operations as a Reliability Coordinator, Transmission Operator, and Power System Operator within RTO/ISO and utility control center environments. He has also held senior regulatory and oversight roles, including senior compliance auditor and subject matter expert for NERC Reliability Standards. In those roles he audited grid facilities for compliance with applicable standards, evaluated the adequacy of mitigation actions, supported the development of violation notifications and settlements as part of FERC-directed enforcement actions, and participated in risk-based oversight of utility mitigation activities. Rob founded Energy Compliance, Inc. to bring senior, regulator-side compliance authority to registered entities directly, without the layered staffing, billable-hour overhead, and generalist advice typical of larger consulting firms. Every Energy Compliance engagement is led by Rob personally.

About Energy Compliance, Inc.

About Energy Compliance, Inc.

Energy Compliance, Inc. is an independent consulting and advisory firm focused exclusively on electric reliability, cybersecurity reliability, and regulatory compliance for organizations connected to the North American Bulk Electric System. Our work supports registered entities, including Generator Owners and Operators, Transmission Owners and Operators, Reliability Coordinators, Balancing Authorities, and Distribution Providers. We work across NERC Reliability Standards, FERC orders, RTO/ISO market participation rules, Regional Entity oversight, and state regulatory frameworks. We do this work differently than larger consulting firms. Engagements are led by a single senior practitioner with regulator-side experience. We do not staff for billable hours. We staff for outcomes. Our deliverables are written to be operationally executable and audit-defensible, not to manufacture activity. Where automation can replace manual work, we build the automation. Where senior judgment is required, the senior is in the room. Energy Compliance is not affiliated with, sponsored by, or endorsed by the North American Electric Reliability Corporation, the Federal Energy Regulatory Commission, or any Regional Entity.

Services Provided Our services are written to be clearly defensible. Operationally executable in real time. Audit-defensible at compliance review. Every deliverable is structured for the auditor's question, not the consultant's binder.

Energy Compliance services include, but are not limited to:

• NERC reliability and compliance advisory support
• Reliability governance and program assessments
• Registration and applicability analysis
• Operational and engineering reliability alignment
• Compliance program design and improvement
• Audit and enforcement support (non-advocacy)
• Mitigation planning and Self-Report development
• Training and executive briefings on reliability frameworks
• Regulator-perspective program reviews

Each engagement is scoped to the entity's role, function, and bulk system impact.

ENERGY COMPLIANCE PROFESSIONAL REFERENCE

Rigorous Compliance. Defensible Programs. Energy Compliance, Inc. partners with registered entities on the institutional and technical questions that define strong reliability and cybersecurity programs, from classification through audit through enforcement response.

NERC COMPLIANCE SENIOR ADVISORY Program support, interpretation, and audit Direct engagement on complex reliability preparation. questions.

INDUSTRY ENGAGEMENT AUDIT DEFENSE Standards development and working-group Notice of Penalty response and settlement participation. posture.

CONNECT WITH US