Solar EPC standard operating procedures (SOP guide)

A solar EPC standard operating procedure is a short, written, step-by-step document that says exactly how one task in your solar business is done, every time, by anyone. A survey SOP, a quotation SOP, a net-metering SOP — each one takes a job that used to live in the owner’s head and turns it into a checklist the whole team can follow. That single shift is what lets a solar company grow without quality falling apart.

This guide is for the founder-operator whose business only runs well when they are personally in the room. You are the best surveyor, the best quoter, the one who catches the ALMM mistake before it costs you a subsidy. That is exactly the problem. This guide gives you the full SOP library a rooftop EPC needs, one fully worked example you can copy, and an honest path to making SOPs stick — on paper first, then as enforced workflow. If it lives with SuryaHub’s complete guide to solar EPC operations, this is the how-to that makes those operations repeatable.

What is a solar EPC SOP?

An SOP — standard operating procedure — is a short written document that describes exactly how one task is done, in order, by anyone on the team. It is not a training manual or a policy binder. It is a checklist for a single job: how to run a site survey, how to raise a quote, how to file a net-metering application. One task, one page, one right way.

Think of it as writing down what your best person already does. When your top surveyor visits a roof, they check the same things in the same order without thinking about it. An SOP captures that invisible routine and hands it to everyone else. New hires reach a good standard in weeks, not months, because they are following a proven path instead of guessing.

The words every time and anyone are the whole point. A great installer who never writes anything down is a single point of failure. The day they are on leave, sick, or poached by a rival, their standard walks out with them. An SOP is how you keep the standard even when the person is gone. It is the difference between a business and a very busy job.

Why do SOPs matter for a scaling solar company?

SOPs matter because at scale you can no longer inspect every job yourself — so the SOP has to inspect it for you. When you run five projects a month, you are on every roof. At fifty, you are on none. The only thing standing between your reputation and a bad install is whether the crew followed a known-good procedure. Four concrete things break without SOPs.

Here is the honest trade. Writing SOPs is boring, up-front work with no reward on day one. But it is the single highest-leverage thing an owner can do to stop firefighting. Every hour spent writing a good SOP saves ten hours of re-explaining, re-checking and re-doing later. It is the operations equivalent of paying down debt.

The complete SOP library for a solar EPC

A rooftop EPC needs about thirteen core SOPs — one for each stage of the project lifecycle, from lead handling to AMC. The table below is a full SOP library mapped to SuryaHub’s 12-stage lifecycle, plus AMC. For each one it names what the SOP standardises and the key points the checklist must cover. This is your master list; you do not need to write them all at once.

Do not try to write thirteen SOPs this month. Print this table, then honestly mark which three stages cause you the most rework, arguments or lost money right now. Write those three first. For most rooftop EPCs the worst offenders are the technical survey, procurement and ALMM, and metering and DISCOM stages — the ones where a single missed step costs a re-visit or a rejected subsidy claim. If delays are your pain, our breakdown of the most common causes of solar project delays points you straight at the stages to standardise first.

A worked example: the Technical Survey SOP

Here is one SOP written out in full, so you can see exactly what “good” looks like. The technical survey is a smart place to start, because a sloppy survey poisons every stage after it — a wrong measurement means a wrong quote, a wrong BOM and a wrong order. Copy this shape for your own SOPs.

Read the shape, not just the steps. It has a named owner, a clear trigger, numbered steps in order, a proof at each step (usually a photo), and a sign-off that ends it. Every SOP you write should have those five parts. If a step can’t be ticked with a clean yes or no, rewrite it until it can.

How do you write an SOP people actually follow?

The best SOP is the one people actually use, and that means short, checklist-style, owned and living — not a polished document nobody opens. Most SOPs fail not because they are wrong but because they are unusable. Four rules keep them usable.

• Keep it short. One page a person can follow on a phone at the site. If it runs to five pages, it is a manual, and manuals get ignored. Cut every word that is not a step.
• Make it a checklist. Numbered actions with tick-boxes, not paragraphs of prose. People follow lists; they skim essays. Each line should be one clear thing to do.
• Give it an owner. One named person is responsible for keeping each SOP correct. An SOP that belongs to everyone belongs to no one and quietly rots.
• Keep it living. An SOP is never finished. When a rule, rate or price changes, the SOP changes the same day. Put a review date on every one.

The best way to write the first draft is to watch your best person do the job and write down what they do. Do not invent an ideal process from a chair. Capture the real, proven one, then tidy it. Write in the plain, ESL-friendly words your team already uses on site — Hindi terms included where that is how the crew actually talks. An SOP in language nobody uses is an SOP nobody follows.

How do you roll SOPs out and keep them updated?

Roll out one SOP at a time, train the team on it, and make it the only accepted way to do the task — then review every SOP at least once a quarter. A folder full of perfect SOPs that nobody was trained on changes nothing. Adoption is the hard part, not writing.

Three moves make a rollout stick:

• Introduce them one by one. Drop thirteen new procedures on a team at once and they will follow none. Roll out the survey SOP this month, procurement next month. Let each become a habit before adding the next.
• Train, don’t email. Walk the team through the SOP on a real job, answer questions, and agree that from today this is how the task is done. A shared understanding beats an attachment nobody opened.
• Make the SOP the only way. If people can still do the job the old way, they will. The SOP has to become the path, not a suggestion — which is exactly where software comes in.

Then keep them alive. Indian solar rules move constantly: GST rates changed in September 2025, ALMM List-II obligations shift in 2026, subsidy slabs and DISCOM processes vary by state. An SOP written last year can quietly start telling people the wrong thing. Put a review date and an owner on every SOP, and update it the day a rule changes. For the compliance-heavy stages, our solar EPC operations guide and the resource hub below are where we track what changed.

Why software beats a PDF nobody reads

A PDF can describe the right steps, but it cannot make anyone follow them — and under deadline pressure, a document in a folder is the first thing skipped. This is the ceiling every SOP hits. You write it, you train on it, and three busy weeks later the crew is back to doing it their own way, because nothing stops them.

Software closes that gap by turning the SOP into an enforced workflow. The difference is simple but total:

This is why SOPs and software belong together. Write the procedure on paper first — you must know the right steps before you can automate them. But the moment a procedure matters, move it into a system that enforces it. A solar project management platform that will not advance a job until the current stage’s proof is in is an SOP that enforces itself, on every job, without you standing over anyone.

Running SOPs as enforced workflow with SuryaHub

SuryaHub is built so your SOPs are the workflow — each of the 13 lifecycle stages is a step the system will not let you skip, with photo proof and sign-off baked in. Everything in this guide describes a connected operating system where the right procedure is the only path through a job. That is exactly what we are building for Indian solar EPCs.

On a live project, the SOPs stop being documents and become the software:

• Lead & qualification — capture and qualify every enquiry to a set standard, then auto-open a job file so the survey SOP can begin.
• Technical survey — the structured form and photo uploads run the survey SOP for you, with the 3-level approval built in as the sign-off.
• Procurement & dispatch — material request to delivery note, with ALMM and DCR records kept per job, so the procurement SOP can’t be short-cut.
• Installation & commissioning — the five site stages each require photo and GPS proof on a phone before the next opens, offline-capable at the roof.
• Payment, handover & AMC — milestone-linked invoicing and auto-scheduled AMC visits with 90/60/30-day renewal reminders, so the service SOP never lapses.

Now the honest part. SuryaHub is pre-revenue and building alongside two pilot EPCs, Suryantra Energy and RGESPL. We are not going to show you invented install counts, fake testimonials, or a logo wall of customers who don’t exist. There is no native array-design or shading engine here — SuryaHub captures a technical survey and quotes from rate cards, so bring your own design tool. And any AI features you may have seen are on our roadmap, not shipped. What we can show is how your own SOPs run as enforced workflow on your real projects, with the mobile field app keeping the roof and the record in sync.

Frequently asked questions

What is a solar EPC standard operating procedure?

A solar EPC standard operating procedure (SOP) is a written, step-by-step document that describes exactly how one task in your solar business is done, every time, by anyone on the team. Examples include a site survey SOP, a quotation SOP or a net-metering SOP. A good SOP is short and checklist-style, not an essay. It turns the owner head-knowledge into a repeatable system, so quality does not drop when a new person does the job.

How many SOPs does a solar EPC company need?

Most rooftop EPCs need around a dozen core SOPs, one for each major stage of the project lifecycle: lead handling, qualification, quotation, technical survey, order confirmation, procurement and ALMM, dispatch, installation, metering, commissioning, payment and GST, handover, and AMC. Start with the three stages that hurt most today, not all twelve at once. You can always add more as the business grows.

What should a solar installation SOP include?

A solar installation SOP should include the trigger that starts it, the owner responsible, a numbered list of steps in order, the photo or document proof required at each step, the safety checks, and the sign-off that ends it. Keep it to one page a person can follow on a phone at the roof. If a step cannot be ticked off with a clear yes or no, rewrite it until it can.

How do you write an SOP that people actually follow?

Write it short, as a checklist, in the plain words your team already uses. Give every SOP a single owner, base it on how your best person really does the job, and keep it to one page where possible. SOPs that read like a policy manual get ignored. SOPs that read like a checklist get used. Then make it a living document you update whenever a rule or price changes.

Where can I get a solar SOP template?

You can start from the SOP library in this guide, which lists the dozen core SOPs a solar EPC needs and shows one fully worked example, the technical survey SOP. SuryaHub also offers a free solar EPC SOP starter pack you can adapt to your own business. It is a set of editable checklists mapped to the 12-stage lifecycle. Grab it with a quick demo and change the steps to match how you work.

Do solar SOPs need software, or is a PDF enough?

A PDF is a fine place to start, but a PDF cannot force anyone to follow it. A document sits in a folder and gets skipped under pressure. Software turns the same SOP into an enforced workflow: the next step will not open until the current one is done, and the photo proof is required, not optional. A system that will not let you skip a step beats a PDF that nobody reads.

How often should you update your solar SOPs?

Review your solar SOPs at least once a quarter, and immediately whenever a rule, rate or price changes. In Indian solar, GST rates, ALMM and DCR requirements, subsidy slabs and DISCOM processes all shift, so an SOP written last year can quietly go out of date. Put a review date and an owner on every SOP. A stale SOP that tells people the wrong thing is worse than no SOP at all.

Keep reading

More playbooks and checklists live in the SuryaHub resources library.

Want your SOPs to run as workflow the team can’t skip — not a PDF nobody reads?

Book a demo →