Solar CAD Design Services: 10 Procurement Gates

Solar CAD design services produce controlled technical drawings from an EPC’s site data, equipment selection, calculations, and design basis. They can remove a drafting bottleneck, but they can also create repeated redraws when inputs, file standards, review authority, and ownership are vague.

Quick answer: Solar CAD design services should turn an approved design basis into controlled, reproducible drawings. Define each sheet, issue status, input owner, CAD standard, native-file package, technical reviewer, revision class, and acceptance test before award. Accept delivery only after cross-sheet reconciliation, clean-environment opening and plotting, comment closure, and editable archive handover.

Ten Procurement Gates

This guide covers the CAD service transaction. For the wider outsourcing decision, use our in-house vs outsourced solar design comparison. For broad provider selection, see the solar design services buyer’s guide.

What Solar CAD Design Services Should Deliver

The deliverable depends on the design stage and project type. “Solar drawings” is not an adequate scope because a sales layout, permit package, and construction set serve different decisions.

Each sheet should have a drawing number, title, project identifier, scale, status, issue date, revision, author, checker, and approver where required. The document register should state which revision is current.

Classify Stage, Discipline, and Status

Do not request a drawing before naming the decision it supports. A feasibility layout tests usable area and an early capacity case. A sales drawing communicates a qualified concept. Neither should release procurement or construction.

A permit or approval set answers a named authority’s submission route. An issued-for-construction set communicates reviewed work to procurement and the field. Fabrication or shop drawings can add manufacturer and installer detail. Redlines record proposed or observed changes. As-built or record drawings describe accepted installed conditions under the contracted definition.

Create a status code and permitted-use table. Identify who may change a status and who can authorise construction release. Watermarks, title-block fields, filenames, registers, and transmittals should agree. Superseded files must move out of active folders.

Separate disciplines in the responsibility matrix:

• Solar layout, equipment identities, module groups, strings, and production basis
• Electrical architecture, conductor and protection basis, grounding, controls, and connection
• Structural loads, members, attachments, foundations, and connection details
• Civil survey, grading, roads, drainage, trenches, and equipment pads
• Roof covering, penetrations, waterproofing, drainage, access, and warranty interfaces
• Fire access, shutdown, signage, emergency response, and equipment separation
• Authority, utility, client, insurer, manufacturer, and lender document requirements

The drafter can coordinate approved information without owning every technical conclusion. Record the named designer, checker, approver, and professional reviewer for each output. The rooftop solar design-services guide covers the wider engineering chain. The PE-stamped plans guide covers responsible charge and seal boundaries.

The United States National CAD Standard page is one published standard route. Its existence does not make that edition or convention mandatory for every buyer. State the exact owner, authority, or contract standard that controls the project.

CAD Drafting Is Not Engineering

CAD drafting communicates decisions. Engineering establishes and verifies the technical basis behind those decisions. Mixing the roles is a common source of hidden risk.

A drafting provider may place modules, route lines, prepare schedules, and update details from approved markups. It should not silently choose structural loads, conductor sizes, protection settings, or code interpretations unless that engineering scope and competence are explicit.

Before award, classify each output as:

• Drafted from an approved sketch or calculation
• Designed and checked within the provider’s contracted engineering scope
• Supplied by an equipment vendor and incorporated without alteration
• Requiring approval or a seal from a qualified professional
• For coordination only and not suitable for construction

Use clear drawing statuses. A preliminary or approval drawing should never reach the field as an issued-for-construction document.

The Input Pack That Prevents Redraws

Most avoidable CAD revisions begin before drafting. The provider receives incomplete, conflicting, or uncontrolled information and fills the gaps with assumptions.

Your input register should include, as applicable:

1. Survey files, coordinate system, units, datums, roof or terrain geometry, and accuracy statement
2. Approved equipment schedule with exact manufacturer and model identifiers
3. Current design basis, calculations, standards, authority requirements, and client specifications
4. Architectural, structural, electrical, civil, and vendor reference drawings
5. Array capacity, module count, string schedule, and equipment locations
6. Layer, lineweight, text, dimension, block, title-block, sheet, and plotting standards
7. Required DWG or DXF release, PDF standard, naming, folder, and transmittal structure
8. Drawing list, stage, milestone dates, checker, approver, and acceptance criteria
9. Open-item and assumption registers

Do not start detailed drafting until the provider accepts the inputs or records each unresolved item. A deadline should run from complete-input acceptance, not the first email.

The solar scope of work template can be adapted into the brief. If the project begins in solar design software, export and freeze the approved layout and equipment basis before CAD detailing.

Define the CAD Standard Before the First Sheet

CAD quality is not visual neatness alone. A usable file follows standards that let another person open, understand, print, reference, and revise it.

Define:

• Drawing units, origin, coordinates, scale, and rotation
• Layer names, colors, linetypes, lineweights, and plot rules
• Text, dimension, leader, table, and block styles
• Title block, sheet numbering, revision format, and approval fields
• Xref strategy, relative paths, overlay versus attachment rules, and clipping
• Model-space and paper-space use
• Required layouts, page sizes, viewports, and PDF bookmarks
• File naming, folder structure, document status, and revision sequence
• Purge, audit, proxy-object, and unresolved-reference checks

Ask for a seed drawing or approved sample before production. If the provider has its own standard, compare it line by line with the client’s requirements.

Specify the Complete Native-File Handover

A DWG can appear correct on the provider’s machine and open with missing references, fonts, images, or plot styles on yours. Native-file delivery must be treated as a package.

Autodesk’s current guidance says its eTransmit workflow packages drawings with supporting files such as external references and plot configuration files. It can also save drawings to a specified DWG version. See Autodesk’s drawing transmittal documentation.

Require, where used:

• DWG or agreed editable source files
• Issued PDF set
• Referenced DWG, DGN, PDF, image, or point-cloud files
• CTB or STB plot styles and permitted fonts
• Sheet-set, data-link, block-library, and template files
• Calculation, schedule, or model files required to reproduce the drawing
• Transmittal report listing file names, versions, references, and exclusions
• Readme with units, coordinate system, software release, and known limitations

Open the handover in a clean test folder with no access to the provider’s network paths. Plot every sheet and check for missing references or substitutions.

Agree the DWG version

Autodesk states that newer releases can generally open older DWG files, while drawings created in the latest format may not be backward compatible. Record the receiving team’s required version and test it. See Autodesk’s DWG compatibility guidance.

Conversion to an older format can affect unsupported objects or formatting. The provider should disclose conversion warnings and confirm the plotted output after conversion.

Write Revision Rules That Prevent Disputes

The contract should separate correction from change. Otherwise, every comment becomes a negotiation.

Every comment needs an identifier, originator, date, owner, response, affected drawings, and status. The provider should return a response matrix with the revised files.

Set a design freeze for equipment, geometry, and design basis. Changes after that milestone should identify cost and schedule impact before drafting resumes.

Use a CAD QA Checklist Before Release

Quality control should check technical coordination and file health, not only spelling and linework.

Document-control checks

• Correct project, drawing number, title, status, issue date, and revision
• Sheet index agrees with delivered files
• Current revision is unambiguous
• Required signatures and approvals are present

CAD-file checks

• Units, coordinates, scale, layers, and plot settings follow the standard
• No unexplained missing or circular references
• Fonts, images, and other dependencies are packaged legally and completely
• Model and layouts open, regenerate, and plot without unresolved errors
• No unintended objects, off-sheet content, or stale revision clouds remain

Technical coordination checks

• Equipment identifiers and quantities agree across drawings and schedules
• Array, strings, cables, structures, and civil interfaces align
• Details and callouts point to the correct sheets
• Dimensions can be traced to approved inputs
• Calculations and vendor information match the issued revision

The EPC’s qualified technical reviewers must approve engineering content. Use the solar design QA checklist as a workflow starting point.

Reconcile Every Drawing and Dependency

Independent checking must trace information across the complete package. Matching linework is insufficient when identifiers, ratings, counts, details, or schedules conflict.

Run an identity check for project name, address, parcel, owner, authority, utility, equipment manufacturer, exact model, revision, and document status. Run a quantity check for modules, strings, inverters, batteries, structures, foundations, cables, breakers, and equipment schedules.

Reconcile geometry from the controlled survey or roof source. Confirm coordinates, datums, units, slopes, dimensions, setbacks, obstructions, access, drainage, equipment clearances, and routes. Separate measured, surveyed, calculated, vendor-provided, and assumed values.

Reconcile electrical architecture from layout through diagrams, schedules, calculations, labels, and details. Reconcile structural or civil outputs with the calculation revision, material grades, member identities, attachment pattern, foundation schedule, and issued vendor information.

Check every detail and callout in both directions. A sheet reference must resolve to the intended detail. A detail must identify its scope, material, interface, and governing input. Remove stale notes, hidden objects, duplicate blocks, and superseded clouds.

The rooftop structural assessment guide explains evidence boundaries for an existing roof. The PVsyst simulation-services guide explains reproducible energy-model handover. A CAD file should reference these approved outputs where relevant, not recreate their conclusions silently.

Control Comments, Field Changes, and Records

A comment log should identify the originator, date, issue, affected document, responsible party, response, revision, checker, approver, and closure evidence. Closing a comment in a spreadsheet is not enough. Confirm the change appears everywhere it affects.

Classify each change before drafting:

1. Provider correction against complete and correct approved input.
2. Resolution of a disclosed assumption or missing input.
3. Buyer, owner, installer, or equipment change after freeze.
4. Authority, utility, insurer, lender, or reviewer comment.
5. Cross-discipline coordination change.
6. Field deviation, unforeseen condition, or inspection correction.
7. New project stage, deliverable, discipline, or jurisdiction scope.

For field changes, record the issued reference, observed condition, photograph or measurement, proposer, technical assessment, safety impact, authority impact, approval, installer instruction, and final status. Do not let an informal markup overwrite an approved set.

The final record package should preserve issued files, approved changes, inspection corrections, equipment substitutions, calculation revisions, and the accepted installed condition. Define whether the contract requires redlines, as-builts, record drawings, or another closeout form. Those terms can carry different duties.

The US Department of Energy permitting overview separates local permitting, inspection, and utility connection. Use it as process context only. The current authority and utility control the actual drawing and closeout requirements. The solar permit drawings guide covers that authority-facing package.

Control File Ownership and Reuse Rights

Paying for a PDF does not automatically establish ownership of editable files, reusable blocks, provider templates, or third-party content. Put the rights in writing.

The agreement should address:

• Ownership of project-specific DWG, DXF, PDF, schedules, and calculations
• Delivery timing for editable files
• EPC rights to revise, reuse, archive, and share files with clients or contractors
• Provider rights to retain templates, libraries, or anonymized know-how
• Third-party blocks, fonts, imagery, surveys, and vendor files
• Confidentiality, access, storage location, retention, deletion, and subcontractors
• Responsibility when another party alters an issued file
• Exit handover for open projects

Have counsel review ownership and license language for high-value or repeat programs. Do not rely on a file extension as proof of rights.

Evaluate a Solar CAD Provider With a Paid Pilot

Use a real project representative of production work. A polished portfolio sample does not test your inputs, standards, or handover.

Score the pilot on:

Pilot at least one normal project and one realistic exception before committing volume. Keep the acceptance checklist unchanged when comparing providers.

Normalise Price and Schedule

Compare bids against the same project profile, drawing register, input condition, CAD standard, review path, and handover. A price per sheet is meaningless when one bidder includes checking and native dependencies while another supplies PDFs only.

Separate these commercial fields:

• Account setup, templates, libraries, title blocks, and standard onboarding
• Drafting by drawing, project, capacity band, discipline, or labour unit
• Design, calculations, checking, professional review, and sealing when contracted
• Reference cleanup, survey conversion, point-cloud work, model conversion, and data entry
• Included comments, correction rounds, authority responses, and coordination meetings
• Buyer changes, equipment substitutions, missing inputs, and new scope after freeze
• Expedited work, overtime, travel, site support, filing, printing, tax, and transfer fees
• Native files, dependencies, final archive, data export, and exit assistance

Build a representative portfolio model. Include normal projects, complex roofs, storage, ground work, service changes, incomplete surveys, comments, substitutions, cancellations, and field changes. Add buyer review time and downstream rework.

Start the delivery clock from a defined event. It may require complete inputs, accepted assumptions, a purchase order, assigned reviewers, and cleared payment. Split drafting, independent checking, buyer review, engineering review, authority review, correction, and final handover.

Use acceptance milestones instead of file-send dates. A milestone closes when the agreed package passes its checks, not when an email contains attachments. State escalation, recovery, credit, termination, and work-file handover terms for provider-controlled failure.

The solar scope-of-work template can structure the deliverable and responsibility schedule. The commercial solar design-services guide adds C&I discipline and project-stage controls.

Secure the Working Files and Exit

Solar CAD packages can contain site coordinates, building plans, electrical details, owner information, signatures, professional credentials, and confidential equipment layouts. Treat their transfer and storage as project data processing.

Define authorised users, least-privilege access, authentication, approved devices, storage locations, subcontractors, sharing, backups, retention, deletion, incident notice, and account closure. Separate provider libraries from buyer data. Prohibit unrelated client content in blocks, xrefs, templates, and transmitted folders.

Agree ownership, licences, and permitted reuse for project drawings, templates, fonts, blocks, surveys, images, vendor files, calculations, and third-party references. A buyer may need editable project files without receiving ownership of every provider library. The contract should make that boundary usable.

Test exit during the pilot. Export the current PDF and native package into a clean environment. Resolve references, plot every sheet, inspect metadata, and confirm another authorised drafter can continue. Record conversion warnings and missing proprietary objects.

Keep an indexed archive with checksums or another integrity method. Retain transmittals, issue history, comments, approvals, source revisions, and rights evidence. Test restore and deletion procedures before the provider account closes.

When Heaven Designs May Fit

Heaven Designs may fit EPCs seeking CAD-based layouts and coordinated engineering drawings for rooftop or ground-mounted projects. Its current detailed-engineering page lists layouts, electrical drawings, structural reports, and permit documentation. These are related-party, provider-published scope statements.

Confirm the project stage, exact drawing list, CAD standard, editable-file package, engineering responsibility, revision terms, schedule, and current capacity in the quote. Do not infer the assigned team, professional scope, software version, turnaround, price, or outcome from the page.

Limitation: the public page does not establish that every project includes native DWG ownership, every discipline, professional seals, application filing, or construction support. Treat each as unknown until the signed scope resolves it.

Disclosure: SurgePV is promoting Heaven Designs through a commercial relationship. Apply the same sample review, paid pilot, file-handover test, and qualified engineering review described in this guide.

Review the Heaven Designs detailed engineering service, then request CAD and engineering samples matched to your project type.

SurgePV can supply an approved layout and equipment basis to the drafting workflow. It does not replace CAD production, engineering judgement, authority approval, professional responsibility, construction release, or field verification.

Solar CAD Services Buying Checklist

Complete these checks before award.

• Every drawing has a purpose, stage, status, and acceptance criterion.
• Inputs, assumptions, responsibilities, and design-freeze rules are written.
• CAD and plotting standards are attached to the contract.
• Engineering decisions and professional review are assigned to qualified people.
• DWG version, editable files, references, fonts, plot styles, and report are included.
• Ownership, reuse, alteration, confidentiality, retention, and exit rights are agreed.
• Revision classes and included correction rounds are defined.
• CAD and technical QA evidence is required before release.
• The complete handover passes a clean-folder open-and-plot test.
• A paid representative pilot passes before recurring volume begins.

Frequently Asked Questions

What do solar CAD design services deliver?

Deliverables may include array layouts, site plans, electrical diagrams, cable layouts, mounting details, equipment schedules, discipline sheets, and as-built drawings. The contract should list each sheet, file format, scale, status, calculation, and professional-review requirement.

Should a solar CAD provider give me the DWG files?

Require native DWG or agreed editable files when your team must revise, reuse, or archive the design. The handover should also include PDFs, linked references, fonts or permitted substitutes, plot styles, images, sheet-set files, and a transmittal report. State ownership, reuse rights, and third-party license limits in the contract.

How can an EPC reduce revisions in outsourced CAD work?

Use a controlled input checklist, approved equipment schedule, drawing standard, responsibility matrix, and staged reviews. Freeze the design basis before detailed drafting, record every assumption, and classify comments as provider error, missing input, client change, or authority change. This separates included corrections from chargeable scope changes.

What CAD file version should I request?

Request the DWG version your team and downstream partners can open without conversion. Autodesk states that older AutoCAD versions cannot open newer DWG formats. Record the required release format in the scope, then test one complete transmittal before production work begins.

Is CAD drafting the same as solar engineering?

No. CAD drafting records and communicates a design; engineering establishes and verifies the technical basis. A drafter should not make structural, electrical, safety, or code decisions outside the agreed competence and review process. Identify which outputs require calculations or approval by a qualified professional.

How should I evaluate a solar CAD design company?

Review project-matched samples, the proposed drafter and checker, layer and title-block standards, cross-reference handling, QA records, revision policy, data security, native-file handover, and recent client references. Run a paid pilot and score completeness, accuracy, coordination, accepted turnaround, and revision quality.

What is the difference between permit and IFC drawings?

Permit drawings support authority review within the named route. Issued-for-construction drawings direct authorised field work and need resolved calculations, interfaces, details, quantities, approvals, and change control.

How should field changes enter the CAD record?

Log the approved-plan reference, field condition, proposer, technical review, authority impact, approval, affected sheets, installation status, inspection result, and required as-built or record revision.

How should solar CAD services be priced?

Compare a normalised sheet and service scope. Separate setup, drafting, engineering, checking, conversions, revisions, field changes, travel, authority work, taxes, and final editable-file handover.