SOP Pitfalls for Commercial Solar and Energy EPC Teams

Permitting timelines vary by jurisdiction, and a project team that does not track submission and follow-up dates finds out about a delay only when the crew is scheduled and the permit still is not in hand.

• Build a Process Street task that fires on submission with a follow-up reminder if the jurisdiction has not responded within its typical review window.
• Document each jurisdiction's typical requirements and review timeline in SweetProcess so a project manager working a new municipality is not starting from zero.
• Flag any jurisdiction-specific quirk, an extra inspection, a specific submittal format, as part of that documented reference.

A permitting delay caught two weeks early is a schedule adjustment; caught the week of installation, it is a crew standing around with nothing to do. Documenting jurisdictions you work repeatedly also means the second and third project in that same municipality get faster, not just the first.

Utility interconnection applications typically get rejected or delayed for missing or inconsistent technical data, not for the underlying project being unusual.

• Document the utility's required data fields and common rejection reasons in SweetProcess, since this standard is stable across projects with the same utility.
• Run the application itself as a Process Street checklist requiring every field to be confirmed complete before submission.
• Track the utility's typical response timeline the same way you track permitting, with a follow-up task if it goes quiet.

A bounced application does not just cost the resubmission time; it usually costs a place in the utility's queue, which can push a project's interconnection date out by months, which is exactly the kind of delay that is invisible until a client asks why their system still is not exporting power.

Safety procedures that live only in a training session from months ago drift the moment a crew is working a rooftop configuration they have not seen before.

• Document fall protection and electrical lockout procedures by installation type in SweetProcess, not as one generic safety talk.
• Require a Process Street checklist confirming the crew lead verified the correct procedure for that day's specific work before installation begins.
• Treat any deviation as an incident worth documenting, not a one-off judgment call that goes unrecorded.

A documented, job-specific standard is what actually holds up when an incident review asks what procedure applied to that exact configuration.

Commissioning is the last checkpoint before a system goes live, and it is also the phase most likely to get compressed when a project is running behind.

• Run commissioning as its own Process Street checklist, separate from installation, with every test step required before sign-off.
• Document what a complete commissioning record needs to include in SweetProcess, so it holds up if a warranty claim later questions whether the system was properly commissioned.
• Require a second person's sign-off on the commissioning checklist, not just the technician who performed the work.

A system that goes live without a complete commissioning record is a liability the moment something underperforms and the warranty conversation starts.

A project can be built and commissioned correctly and still leave the client unable to maintain it, if the operations and maintenance handoff is treated as an afterthought.

• Document what a complete O&M package includes, as-built drawings, warranty terms, maintenance schedule, in SweetProcess as a standard checklist for every project type.
• Run the actual handoff as a Process Street task with a required client sign-off confirming they received it.
• Route ongoing service and maintenance billing through a back-office platform like Every once O&M contract volume grows past what a spreadsheet can track.

A client who cannot find their own warranty documentation two years later is a support call and a reputation cost that a documented handoff standard prevents. Olivia, MeetMyCOO's AI COO, can help a growing EPC team decide which of these five pitfalls is costing the most schedule time right now.