White-Label Solar Design for EPC and Engineering Firms

How an EPC or engineering firm should structure subcontracted PV design: where liability sits, who seals, deliverable standards, and scope control.

Picture of Douglas Avila
Douglas Avila

Owner & Editor

Rooftop solar panels and engineering plans labeled “ROOFTOP SOLAR ARRAY SYSTEM”
IN THIS ARTICLE

Key takeaways

  • White-label PV design is a contracting problem before a drafting problem. Settle liability, sealing, and file format in the scope of work, or you bought hours instead of capacity.
  • Professional liability and the PE seal are different questions. E&O exposure follows the firm of record; the seal is a licensure act by a named individual.
  • A PE must be licensed in the state where the project is built. Sealing access, not drafting throughput, gates multi-state work.
  • Specify native CAD, not only PDF. A DWG in your title block and layer standard is an asset your team can revise.
  • Avila Solar Drafting delivers standard solar plan sets in 2–3 business days and Fast Roof plan sets in 1–2 business days, with six months of free revisions.

White-label solar design works for an EPC or engineering firm only when three things are settled in writing before the first project: who carries professional liability, which licensed engineer seals in which state, and what file format the deliverable arrives in. Turnaround, revision windows, and QA get negotiated around those three. Get them wrong and you bought drafting hours, not design capacity.

What is a white-label PV design arrangement?

A white-label PV design arrangement is a subcontract in which an outside firm produces drawings, calculations, and permit packages that your firm issues under its own title block, to your own client, with no visible third party. You keep the client relationship and the professional responsibility. The subcontractor supplies production capacity, jurisdictional familiarity, and — where it is contracted for — a licensed engineer’s seal.

This is a different transaction from an installer buying a plan set. An installer buying outsourced solar drafting services buys a finished product for a job it will build itself. A firm subcontracting design buys an input to a deliverable it issues under its own name, to a client that has never heard of the subcontractor and should not have to.

So the paperwork differs. An installer’s purchase order can be short. A firm’s subcontract has to survive an owner’s counsel, an insurance broker, and a plan checker, years after closeout.

If the open question is whether to hire a drafter at all, see outsourced PV design versus in-house instead. This piece assumes you already have engineering staff.

Where does professional liability sit when you subcontract design?

Professional liability follows the firm of record — the entity that contracted with the owner and issued the drawings. Subcontracting design does not move errors-and-omissions exposure off your policy. A subcontract allocates responsibility between the two firms through indemnity and insurance requirements, but the owner’s claim still lands on the design professional named in the prime agreement.

That is why liability and sealing are separate questions. The seal is a licensure act performed by a named individual in responsible charge. Errors-and-omissions coverage is an allocation between businesses. A subcontractor can carry coverage and still not be the party your owner sues.

Four things belong in the subcontract, and they are the ones firms most often leave out:

  • A professional liability requirement with a stated limit, plus a certificate of insurance naming your firm. Confirm the limit with your own broker.
  • An indemnity scoped to the subcontractor’s own negligent acts, errors, and omissions — not a broad-form indemnity its carrier will not cover.
  • A stated standard of care, so “defective” has a definition when you need one.
  • Ownership of the work product, including native files, with an express license to modify them. Owner-architect instruments-of-service language does not translate here.

The cost-structure side of this decision is worked through in the in-house versus outsourced comparison.

Who has to seal the drawings, and why does that gate multi-state work?

A professional engineer licensed in the state where the project is built must seal the drawings wherever that state requires a seal. Licensure is granted state by state, so a PE licensed in one state cannot seal in another until that board issues a license. For a firm selling into multiple states, sealing access — not drafting throughput — decides where you can take work.

NCEES, whose members are the state and territorial licensing boards, runs a Records program because this is the friction point: an NCEES Record holds what a licensed engineer needs “to apply for comity licensure in additional states,” and NCEES is explicit that a Record “does not guarantee licensure in any jurisdiction.” Comity shortens the application; it does not make one license work in fifty places.

Firms solve this three ways: retain a PE licensed in each target state, buy sealing per project from a firm that holds the licenses, or decline the work. The second is what most firms mean by white-label, which is why you ask which states a partner can seal in today, not which states it works in.

Avila Solar Drafting provides engineering stamps as a scoped add-on or a standalone review, and does not accept projects in APS and SRP territory in Arizona, the City of Peoria, AZ, the City of Phoenix, AZ, Los Angeles County (LABD), CA, or the City of Rochelle, NY.

What deliverable and file-format standards belong in the scope?

Specify native CAD, not only PDF. A PDF is a submittal; a DWG is an asset your team can revise, renumber, and absorb into the project document set. Name the release, title block, layer convention, sheet numbering, external-reference policy, and revision-delta practice in the scope of work, before the first sheet is drawn.

Autodesk describes DWG as “the native file format for Autodesk’s AutoCAD software”, holding “all the information that a user enters in a CAD drawing.” A flattened PDF ends the relationship at delivery; a native file lets your engineer of record revise the drawing three years later when the owner adds a second phase.

ItemWhat to specify
File formatNative DWG at a named release, plus a flattened PDF submittal set
Title blockYour block, your project numbering, your revision table
LayersYour office standard, or a named published standard
Sheet numberingYour discipline prefixes and sheet order
External referencesBound or attached, stated explicitly
Revision controlDelta numbers, clouded changes, revision history on the sheet
Model filesNative Aurora, Helioscope, or PVsyst files

The last row matters more than it looks. If your roof plan traces back to a shade model you cannot open, you cannot defend the yield number. Ask for the native model alongside the production modeling reports.

How do you bound revision cycles and change orders?

Separate three categories in the scope: corrections to the subcontractor’s own errors, revisions driven by AHJ comments, and changes driven by you or the owner. Only the third is a change order. Write the distinction down, attach a revision window with a stated duration, and require every revision to carry a delta number so the document history stays auditable.

Most disputes over subcontracted design are disputes about which bucket a revision belongs in. A plan checker asking for a dimension that was never shown is a correction. The owner moving the interconnection point is a change order. Unnamed categories turn every revision into a negotiation.

A revision window is the benchmark to compare partners against. Avila Solar Drafting includes free revisions for six months from the order date, which covers a permit cycle, an AHJ correction round, and a late equipment substitution. Ask a partner what starts the clock — order date, delivery date, or first submittal produce very different coverage.

Bound turnaround the same way. Avila delivers standard solar plan sets in 2–3 business days and Fast Roof plan sets in 1–2 business days, with the clock starting when complete site data is received. That clause is the one to negotiate, because “complete site data” is where schedule disputes live.

How do you plan design capacity against a lumpy pipeline?

Size internal design capacity to the trough and contract the difference. An EPC pipeline moves in steps — an award, a notice to proceed, a financing close — so design demand arrives in blocks, not a steady stream. Capacity sized to the peak sits idle between blocks; capacity sized to the trough fails at every award. The subcontract covers the gap.

Structure it as a master services agreement with a standing rate schedule and a committed response window, not one-off purchase orders. The legal work happens once, when nobody is under schedule pressure, and each project becomes a task order against accepted terms. Firms that negotiate the subcontract during the first award negotiate it badly.

Two habits make it work:

  1. Forecast, do not surprise. Send the partner your award pipeline monthly, including projects you expect to lose. A partner that knows a 12-site batch is 60 days out will hold room for it.
  2. Batch intake, not batch delivery. Send site data as it is confirmed. Sequential delivery surfaces a systemic drawing problem on site one instead of site twelve.

The same logic applies with longer lead times on utility-scale PV system design, where the notice-to-proceed date sets the schedule. Most design decisions that drive project success are made before anyone opens AutoCAD.

Who performs independent QA review on subcontracted design?

Both firms, at different points, and the scope should say so. The subcontractor checks internally before delivery. Your firm reviews independently before the drawings are issued under your title block or your engineer’s seal. Reviewing your subcontractor’s work is the act that makes the drawings yours.

Your review does not redraw the package. It catches four things:

  • Adopted code cycle. Confirm which edition of NFPA 70, the National Electrical Code, the jurisdiction adopted, and confirm the sheet cites it. NEC 2023 690.12(B)(1) requires controlled conductors outside the array boundary to drop to 30 volts or less within 30 seconds of rapid shutdown initiation; earlier cycles differ. A sheet citing the wrong edition reads as a correction to a plan checker and a defect to a claims adjuster. Our NEC solar and storage rules breakdown treats the adopted cycle as the first thing to establish.
  • Internal consistency. Conductor ampacity, overcurrent protection, and the interconnection method have to agree with each other and with the equipment schedule.
  • Structural basis. The referenced ASCE 7 edition, the wind and snow figures, and the attachment detail have to describe the same building.
  • Field reality. Equipment locations on the site plan have to match what gets installed.

Ask whether a partner’s internal check is done by someone other than the drafter, then run your own checklist on the first three packages — the discipline that decides whether a package is ready to submit in house.

How is client-facing anonymity handled in a white-label arrangement?

By contract, not by convention. A white-label agreement should state that the subcontractor does not contact your client, does not appear in the title block or file metadata, does not name the project in its own marketing, and returns or destroys project data on request. Put it in a mutual NDA and repeat it in the scope of work — the NDA governs information, the scope governs conduct.

The practical items are easy to miss:

  • File metadata. CAD author fields, PDF producer strings, and model file properties all carry a name. Ask for them scrubbed or set to your firm.
  • Correspondence. Decide whether the partner may appear on an email with your client, and under what address. The default is no.
  • Portal access. If your client can see a shared project folder, the partner’s presence in the access list is a disclosure.
  • Portfolio use. Silence is the default unless you say otherwise in writing.

One caveat: many owner and prime agreements require disclosure of subconsultants, and some public-sector contracts require approval of them. White-label is a posture between you and your client, not a way around a disclosure obligation you already signed. Read your prime agreement before promising anonymity you cannot deliver.

Worked example: a three-state commercial rollout

A regional EPC firm wins three C&I rooftops in one quarter: 340 kW in Oregon, a 480 kW carport-and-roof project in Texas, and 610 kW in Washington, DC. The in-house team is two designers and one PE licensed in Oregon only.

Drafting capacity is not the binding constraint. Three packages at roughly 20 sheets each is a few weeks for two designers.

Sealing is the binding constraint. Oregon is covered internally. Texas and DC are not, and both need a structural seal from an engineer licensed there. Hiring is a multi-month path through two state boards; buying sealing access per project is a same-quarter path. That fact, not throughput, decides whether the firm subcontracts.

Code cycles diverge. The three jurisdictions are not on the same NEC edition, so rapid shutdown language and labeling differ across the packages. Each sheet cites its own AHJ’s cycle.

One project sits above the self-serve ceiling. Avila Solar Drafting handles commercial solar PV designs up to 500 kW through the standard order path; the 610 kW package is quoted directly. The Texas project wants a partner already working that state’s AHJs — see Texas solar plan sets.

What the firm contracts for: native DWG in its own title block, PDF submittal sets, structural seals in two states, a defined intake package, and a revision window covering the permit cycle. What it keeps: the client, the judgment, the final review.

What outsourcing PV design does not solve

It does not transfer engineering judgment, and it does not make the AHJ faster. A subcontractor can produce the calculation. Deciding whether the assumption behind it is right for this owner, this site, and this schedule is still your engineer’s call, and it always will be — that is what responsible charge means.

It also does not shorten a plan check. Review queues belong to the jurisdiction. A well-drawn package reduces correction rounds, a real schedule benefit, but no vendor controls the calendar in a building department.

What it does solve is narrower and still worth buying: production capacity that flexes with your award pipeline, sealing access in states where you hold no license, familiarity with jurisdictions you enter once a year, and a drawing standard maintained by people who draw permit sets every day.

That is a real list, and it is the list to write the subcontract against. A firm that scopes the arrangement to those four things gets capacity it can forecast. A firm that scopes it as a way to stop thinking about design gets drawings nobody in the building is prepared to defend.


FAQ

Who is responsible if a subcontracted solar design has an error?

The design professional of record — the firm that contracted with the owner and issued the drawings — carries responsibility to the client. A subcontract allocates risk between the firms through indemnity, insurance requirements, and a stated standard of care, but does not remove the prime firm from the claim.

Does a PE licensed in one state cover projects in another?

No. Engineering licensure is granted state by state, and a seal is valid only in the state that issued the license. NCEES’s Records program streamlines applying for comity licensure elsewhere, but does not guarantee licensure anywhere.

Should a white-label design contract require native CAD files?

Yes. Ask for native DWG at a named release plus a flattened PDF submittal set, and specify your title block, layer convention, and sheet numbering in the scope.

How long should a revision window run on subcontracted PV design?

Long enough to cover a permit cycle plus one correction round. Avila Solar Drafting includes free revisions for six months from the order date. Ask what starts the clock: order date and first submittal produce very different coverage.

Where does Avila Solar Drafting take white-label projects?

Nationwide, with five exclusions: APS and SRP territory in Arizona, the City of Peoria, AZ, the City of Phoenix, AZ, Los Angeles County (LABD), CA, and the City of Rochelle, NY.


Scope a white-label design program

Most firms do not lose projects because nobody could draw them. They lose them because the seal was not available in that state, or the deliverable arrived as a PDF nobody could revise.

Avila Solar Drafting works as a subcontracted design partner under your title block: native CAD deliverables, engineering stamps scoped per project, standard plan sets in 2–3 business days, our guarantee of accurate solar plan sets, and six months of free revisions — designed to pass first-time review.

Call 971-410-0655 to scope a program. Multi-state sealing, portfolio work, and anything above 500 kW is quoted directly, so a conversation gets further than a form.

Prefer one project first? Create a free account and send a single site through the process.

SHARE:
Create A Free Account

Create an account to view all our services and see how your orders will be managed.

IN THIS ARTICLE
Roof geometry, framing allowance, conduit, busbar rating, equipment space: what architects specify at design stage…
September 22, 2026
An ESS permit package is more than a PV plan set: NEC 2023 Article 706,…
September 15, 2026
Ground-mount solar plan sets add foundations, geotech, frost depth, trenching and zoning. Here’s what changes…
September 8, 2026