Okay, let's break this down. It sounds like you're in a tough spot, and it's understandable why you're frustrated. Here's a clear look at the situation and what might be going on, along with suggestions for moving forward

Analysis of the Situation:
Clear Role Definition is Key

Your description outlines a clear separation of responsibilities:

Planning/Permitting Department

Responsible for assessing project needs, obtaining permits, understanding code requirements, and preparing the project for execution. They own the feasibility stage.

Project Manager (You)

Responsible for executing the project according to the plan, once it's deemed ready.

The Breakdown

The problem lies in the breakdown of communication and process before the project was handed to you. Here's where the failures seem to have occurred:

Inaccurate Initial Assessment

The initial determination that no permits were needed was wrong. This set the entire project on the wrong foot.

Incomplete Due Diligence by POCO Consultant

The POCO consultant (hired by your company's planning/permitting department) should have identified the need to bring the service up to current standards during the permitting process. That's their job. They failed to do a thorough assessment.

Lack of Communication

Even if the consultant missed it, the planning department should have anticipated this as a potential issue (especially if it's a common requirement in your area). There seems to be a lack of institutional knowledge or a gap in their checklist.

Why It's NOT Primarily Your Fault



Scope of Your Role

Your role is execution. You're not responsible for the upfront planning, permitting, and code compliance research.

"Ready to Schedule" Implies Completeness

The fact that the project was presented to you as "Ready to Schedule" means that, in your company's process, all the necessary approvals, permits, and pre-work should have been completed.

Specialized Knowledge

You're not expected to be an expert in all local POCO (Power Company) standards, especially since that's the responsibility of a specialized consultant hired by your company.

Why Your Boss Might Be Frustrated (Even if He's Wrongly Placing Blame)



Project Delay

The project is delayed, which reflects poorly on the company. Someone needs to be held accountable, and in the heat of the moment, it's easy to point fingers.

Cost Overrun

Unexpected requirements often lead to increased costs, which affects profitability.

Client Dissatisfaction

The client is understandably unhappy with the delay and the unexpected changes.

Lack of Understanding of Your Role He may not fully understand the constraints of your role.

What You Should Do Now


Document Everything (Objectively)



Your Role

Document your role as project manager, emphasizing the responsibilities and handoff points as defined by company processes.

Project Timeline

Create a timeline of the project, highlighting key dates: Date the project was assigned to you as "Ready to Schedule." Date the permitting issue was discovered. Date the POCO standards issue was identified. Who was informed and when.

Communication

Keep a record of all communications (emails, meeting notes) related to the project.2.

Calmly and Professionally Discuss with Your Boss (Again)



Start with Empathy

Acknowledge the project's delay and the frustration. Something like: "I understand the frustration with the project delay, and I want to find a way to prevent this in the future."

Reiterate Your Role

Explain your role and responsibilities within the company's established processes. Emphasize that you rely on the information and approvals provided before the project reaches you.

Focus on Process Improvement

Shift the conversation away from blame and towards preventing future issues. Ask questions like: "What changes can we make to the pre-planning process to ensure all POCO requirements are identified before scheduling?" "How can we improve communication between the planning/permitting department and the project management team?" "Should we create a checklist specifically for POCO requirements in this county?"

Offer Solutions

Suggest specific steps to improve the process. For example: "Perhaps we should require a second review of all permits by a senior member of the planning department." "Maybe we need a mandatory meeting between the POCO consultant and the project manager before scheduling." "We could create a standardized checklist for all projects that includes POCO requirements, based on location."3.

Escalate (If Necessary)

If your boss continues to unfairly blame you, you might need to escalate the issue to their boss (your manager's manager) or HR. However, try to avoid this unless it's absolutely necessary. Always frame it as a "process improvement" issue, not a personal complaint.4.

Learn from the Experience (Even if It's Not Your Fault)

While it's not your primary responsibility, use this experience to learn about potential POCO requirements in your area. This will make you a more informed PM and allow you to flag potential issues in the future, even if it's outside your official role.

Key Takeaways



Clear Role Definitions are Crucial

Ensure everyone understands their responsibilities.

Robust Processes are Essential

Implement checklists, reviews, and communication protocols to prevent errors.

Focus on Solutions, Not Blame

When problems arise, focus on improving processes to avoid future issues.

Documentation is Your Friend: Keep a record of everything.By taking these steps, you can protect yourself, improve the company's processes, and hopefully avoid similar situations in the future. Good luck! Flag for review