Solar EPC SOP Templates: 7 Core Procedures and a 7-Part Template

A solar EPC needs 7 core SOPs: sales-to-design handoff, site survey, design review, permitting, installation quality check, commissioning, and handover. An SOP (standard operating procedure) is a 1 to 2 page document that says who does a job, in what steps, and how to know it is done. Write design review and commissioning first.

EPC means engineering, procurement and construction. It is the company that designs, buys for and builds the solar system. When two crews do the same job in two different ways, results vary. One job passes permit review fast, and a similar job is sent back because someone skipped a check. SOPs make the right way the usual way.

This guide gives you the 7 SOPs, a 7-part template to write each one, and a 90-day plan to roll them out. The step lists below are starting points. Change them to fit your market, your codes and your crews.

If you are building an EPC from scratch, read our solar EPC guide first.

In this guide:

• What an SOP is, and what it is not
• The 7 SOPs in one table
• The 7-part template
• The 7 SOPs, one by one
• Why short SOPs work better
• A 90-day rollout plan

What Is a Solar EPC SOP?

An SOP is a short document that makes one repeatable job come out the same way, no matter who does it. A new hire should be able to follow it and deliver the same result as your best lead.

Three things get mixed up with SOPs:

• A policy manual. A policy states a rule, such as “we follow the local electrical code.” An SOP states an action, such as “photograph the panel label and record the main breaker rating.”
• Tribal knowledge copied word for word. If you write down how your best installer works, you get a story, not a procedure. An SOP describes the minimum method everyone must follow.
• A training course. Training explains why. The SOP says what to check. The crew opens it on the roof.

The 7 SOPs in One Table

You do not need 50 procedures. Start with these 7. Each one has a trigger (what starts it), an owner (one role), and an output (the record it leaves).

Add more only when your volume needs them. Common extras are procurement and receiving, subcontractor onboarding (see our guide to solar subcontractor management), and warranty service.

Our solar business operations playbook covers KPIs and meeting rhythm. This guide covers the documents.

The 7-Part SOP Template

Give every SOP the same 7 parts. Then a new hire can pick up any SOP and know where to look.

1. Purpose. One sentence on why the SOP exists.
2. Scope. What it covers, and what it does not. For example, “residential rooftop only.”
3. Owner. One named role, never a department. The owner keeps the document up to date.
4. Inputs required. What must exist before the job starts, such as a signed contract, a utility bill and roof photos.
5. Step checklist. Numbered actions in order. Start each step with a verb and name the record it produces.
6. Acceptance criteria. A clear definition of done that someone else can check.
7. Escalation and revision. Who to call when reality does not match the SOP. Add a version number and a review date.

Two rules help in the field. Keep each SOP to 2 printed pages. And make every step leave evidence, such as a photo, a filled field or a signature. A step with no evidence is only a suggestion.

SOP-01 and SOP-02: Sales Handoff and Site Survey

Most design rework starts with a poor handoff or a thin survey. These two SOPs fix the inputs.

SOP-01: Sales-to-design handoff

Purpose. Pass every important fact about the sold job from sales to design, in one fixed format, soon after the contract is signed.

Steps:

1. Confirm the signed contract and the first payment. Attach both to the job file.
2. Record the sold scope: system size in kW, module and inverter models quoted, battery if any, and price.
3. Attach the customer’s utility bills or meter data.
4. Write down customer limits: roof replacement plans, housing society or HOA rules, an electric vehicle purchase, and look-and-feel wishes.
5. Note any promised dates, such as “customer wants the install done before the rains.”
6. Attach the photos taken at the sales visit: roof sections, main panel, meter.
7. Note how the customer pays (cash, loan, lease or power purchase agreement), because it changes the paperwork later.
8. Assign a designer and a due date. Keep the sales rep reachable for questions.

Done when. The designer can start with no calls to the sales rep. If an input is missing, the job goes back to sales and the bounce is logged.

A good handoff also protects the proposal numbers. If the sold design came from PV proposal software, the layout and numbers move as data, not as a screenshot.

SOP-02: Site survey

Purpose. Capture every physical fact that design and install will need in one visit. A second visit costs time and money.

Steps:

1. Photograph all roof sections. Note vents, chimneys, skylights and other obstructions, with measurements.
2. Record the roof material, its age and its condition. Flag a needed re-roof before install.
3. Measure the rafter or truss spacing and note attic access.
4. Photograph the main service panel with the door open. Record the busbar rating, the main breaker rating and the free breaker spaces.
5. Locate the meter and photograph it. Note the utility and the service size.
6. Record shading: trees, nearby buildings and poles. Use a shade tool, or measure obstruction heights and distances.
7. Plan the cable route from the roof to the inverter and the panel. Measure the distances.
8. Check the mobile signal if the inverter has online monitoring.
9. Show the customer where the equipment will go and get their agreement.
10. Finish the survey form before you leave the site.

Done when. The form is complete, the panel label can be read in the photo, shade data is captured, and no return trip is needed.

Shading is the step most often skipped. When survey photos and obstruction measurements go into solar shadow analysis software, the energy estimate reflects the real roof. After the survey, the survey to proposal workflow shows how that data moves into the quote.

SOP-03 and SOP-04: Design Review and Permitting

Design review is the quality gate. Permitting is the schedule gate. Errors caught here cost minutes. Errors that pass through cost a return visit.

SOP-03: Design review

Purpose. A second qualified person checks every design against the survey and the code before it goes to permit or to the customer. One designer working alone will repeat their own mistakes.

Steps:

1. Check that the module layout matches the surveyed roof, the setbacks and the fire access paths.
2. Check string sizing against the inverter datasheet. A string is a row of modules wired in series. Check the voltage range at the coldest and hottest expected temperature, the current limits, and the MPPT assignments. MPPT is the inverter function that finds the best operating point of the array.
3. Confirm the rapid shutdown set-up and the equipment listings your area requires. Rapid shutdown is a safety feature that quickly lowers the voltage on roof wiring when you switch power off.
4. Check how the system connects to the building’s main panel. Use the sizing rule your electrical code sets for this connection.
5. Check the energy estimate. Compare the yield per kW with similar local systems. If it is far higher, find out why.
6. Check the structure: attachment spacing, wind and snow loads for the site, and whether a structural letter is needed.
7. Check the bill of materials (BOM, the parts list) against the layout: rails, clamps, attachments, wire and disconnect switches.
8. Confirm the design matches the sold scope from SOP-01. If it does not, write a change order before work continues.
9. Check the single line diagram (SLD, a simple drawing of how the system is wired). Make sure it is complete enough for the permit.
10. Sign and date the review. File it with the job.

Done when. Someone other than the designer has signed every check. Track your first-pass permit approval rate. It tells you whether this SOP works.

When layout, string sizing and BOM come from one solar design software project, the reviewer checks one model. The reviewer does not have to rebuild a CAD drawing.

SOP-04: Permitting and interconnection

Purpose. Send a complete, correct permit package the first time, and track it until it is approved. Interconnection means the utility’s approval to connect your system to the grid.

Steps:

1. Get the current requirements from the authority having jurisdiction (AHJ, the office that issues permits where the site is). Do not reuse last quarter’s package without checking.
2. Check the utility’s connection rules. Send the utility application at the same time as the building permit, not after.
3. Build the package: single line diagram, site plan, spec sheets, structural letter if needed, labels and contractor license papers.
4. Review the package against the AHJ checklist before you send it. Log who reviewed it.
5. Record the application number, the date sent and your contact at the AHJ.
6. Set follow-up dates. If nothing changes for a set number of days, call. Log every contact.
7. If the AHJ asks for corrections, answer quickly and log the reason. Repeat corrections mean SOP-03 has a gap.
8. When approved, file the permit, tell scheduling the same day, and book the inspection.

Done when. The package is accepted with no rejection for missing documents. Track the days to permit for each AHJ and review them every month.

In the United States, some places use SolarAPP+. On its own site, SolarAPP+ says that installers enter the system design, the platform checks it against code, and a code-compliant application receives a permit instantly. It covers residential solar and energy storage in the places where it is available. If your area uses it, route eligible jobs through it.

SOP-05 to SOP-07: Installation Quality Check, Commissioning and Handover

The last three SOPs protect your reputation and your crew.

SOP-05: Installation quality check

Purpose. Find defects on the day they happen, while the crew and the ladder are still on site.

Steps:

1. Hold a briefing. The crew lead goes over the plan set, change orders and site hazards. Everyone signs in.
2. Check delivered materials against the BOM before anything goes on the roof.
3. Confirm fall protection, ladder tie-offs and electrical lockout before roof work. Photograph the set-up.
4. Check attachment layout against the structural plan: spacing, rafter hits, flashing and sealant as the maker specifies.
5. Tighten every specified fastener to the maker’s torque value with a calibrated tool. Mark each one after checking.
6. Check wire management: no sharp edges, UV-rated ties, and conduit that is properly supported.
7. Photograph every attachment row, wire run and roof penetration before the modules cover them. This is your proof if a warranty claim comes.
8. At the end of the day, the crew lead walks the job against the checklist. Fix defects before leaving.
9. File the signed checklist and photos the same day.

Done when. No defects are carried to a punch list. Track your callback rate. For more detail, pair this SOP with our solar installation quality inspection guide. Our guide on how to organize a solar panel installation covers crew planning.

On fall protection, OSHA (the US Occupational Safety and Health Administration) says that falls are among the most common causes of serious work-related injuries and deaths. It requires fall protection at six feet in the construction industry. Check the rule that applies where you work, and write it into this SOP.

SOP-06: Commissioning

Purpose. Prove the system is safe, complete and working as modeled before anyone calls it done. Commissioning is a test, not a walk-through.

Steps:

1. Confirm all quality-check items are closed and the inspection is approved or booked.
2. Test continuity and polarity on all strings before you switch on. Record the values.
3. Test insulation resistance on the DC circuits. Record the values against the minimum in your standard.
4. Check earthing (grounding) continuity and the torque marks on all terminations.
5. Test rapid shutdown with a witnessed activation.
6. Switch on in the order the maker gives. Record the inverter firmware version and set up monitoring.
7. Compare first-day output with the model for that weather and time of day. Look into any large gap.
8. Complete the commissioning report and file the test values. Our solar commissioning checklist gives you a starting point.

Done when. All test values are recorded and in range, monitoring is live, and the inspection has passed.

IEC 62446-1 is the international standard for this job. The IEC webstore says it defines the documents to hand to the customer after installing a grid-connected PV system. It also describes the commissioning tests and inspection criteria that check safe installation and correct operation. The full text is sold by IEC, so build your form from the standard itself.

SOP-07: Customer handover

Purpose. Give the customer what they need to run the system, and close the job cleanly.

Steps:

1. Prepare the handover pack before the visit: warranties, as-built drawings, monitoring login, maintenance schedule and emergency contacts. Our solar handover pack guide lists what belongs in it.
2. Walk the customer through the equipment: inverter, disconnect switch, rapid shutdown device and meter.
3. Set up the monitoring app on the customer’s phone. Check that they can read their output.
4. Explain what normal output looks like through the year, and when to call for service.
5. Explain the warranty periods for modules, inverter and workmanship, and how to make a claim.
6. Collect final payment and signatures. Confirm the utility’s permission to operate.
7. Ask for a review, and schedule a follow-up call.

Done when. The handover document is signed, monitoring works on the customer’s phone, and the follow-up is booked.

Why Short SOPs Work Better

A 60-page manual looks serious in the office. Crews rarely open it. Over time it describes a process nobody follows.

Short SOPs leave out rare cases. A one-page install SOP cannot cover a clay tile roof on an old building. Put those cases in an appendix that crews open when needed. The SOP stays short, and the detail is still there.

Safety is the exception. Lockout and energized-work procedures can be long, because a skipped step can cost a life. Follow the safety rules of your country and your employer for those.

Here is a simple test. Give the SOP to a new hire in their second week. If they can follow it without asking a question, it is long enough. If they cannot find an answer quickly, it is too long.

A 90-Day Rollout Plan

Do not write all 7 SOPs in one weekend. Start with the ones that catch the costliest errors, and let each one prove itself.

Days 1 to 30: write SOP-03 and SOP-06. Design review and commissioning sit before and after the costly middle. Have the senior designer and the lead commissioning technician write the drafts. Run them for 2 weeks. Then meet for 30 minutes: which step did reality break? Fix it and issue version 1.1.

Days 31 to 60: protect the inputs. Add SOP-01 and SOP-02. Sales teams may see handoff rules as extra paperwork. Show them the reason: a bounced design delays the job. Track survey return trips and design bounces from week 1.

Days 61 to 90: close the loop. Add SOP-04, SOP-05 and SOP-07. By now the crew has seen four SOPs make work easier. End the quarter with a first review of every SOP: new version number, owner check and a short talk to the crew.

Three rules help adoption. Owners write and managers edit. Pick one KPI (a number you track) per SOP from day 1, such as first-pass permit rate, callback rate or survey return trips. And never blame someone for saying an SOP does not fit reality.

Conclusion

SOPs are not red tape. They are how a solar business grows without losing control of quality. The library is small: 7 documents, 2 pages each, one fixed template.

Start this week:

• Draft SOP-03 and SOP-06 first. Ask your senior designer and lead technician to write them with the 7-part template.
• Pick one KPI for every SOP. If you cannot measure it, you will drop the SOP.
• Book the first review now. Put a review date on every SOP, so none of them goes stale.

When your procedures are ready, look at the tools that carry data from survey to proposal. See solar software from SurgePV, then book a free demo.

Frequently Asked Questions

What SOPs does a solar EPC need?

The core library is 7 SOPs: sales-to-design handoff, site survey, design review, permitting and interconnection, installation quality check, commissioning, and customer handover. Larger EPCs add procurement, subcontractor onboarding, and warranty service SOPs. Write design review and commissioning first.

What is a solar installation SOP?

A solar installation SOP is a short written procedure for the install day. It lists the checks before roof work, the steps for mounting and wiring, the photos to take, and the sign-off the crew lead gives at the end of the day. In this guide it is SOP-05, installation quality check.

What is an SOP for solar project management?

It is the set of SOPs that follow a job from sale to handover. Each SOP has a trigger, an owner and an output, so the project manager can see which step a job is in and who is responsible. The 7 SOPs in this guide are that set.

How long should a solar SOP be?

Aim for 1 to 2 pages. A procedure that fits on one printed sheet is easier to use on site than a long manual. If a job needs more detail, keep the SOP short and put the rare cases in a separate appendix.

What is the difference between an SOP and a checklist?

A checklist lists the steps or inspection points. An SOP wraps the checklist with a purpose, a scope, a named owner, the inputs needed, a definition of done, and a date for the next review. Every good SOP contains a checklist, but a bare checklist has no owner.

Who should write solar EPC SOPs?

The person who does the job well writes the first draft. The process owner edits it. For example, a lead installer drafts the install checks and the senior designer drafts design review. Management sets the template, approves the definition of done, and checks the review dates.

How often should solar SOPs be revised?

Set a regular review date on every SOP, for example every 6 months. Also review it after a failed inspection, a callback or warranty claim, or a change in code, equipment or utility rules. Give each revision a new version number and tell the crew.

Do small solar installers need SOPs?

Yes, as soon as more than one person or crew does the same job. Until then the owner can check every job. After that, work that is not written down gets done in different ways, and the fix costs time and money.