Solar Cost Atlas

Richmond Solar Guide: Historic Resources, iMS and Exact Approval Documents

Check Richmond's historic-resource prerequisite, current contractor and business-license conditions, exact attachment names and the separate iMS city application.

Sources reviewed: 2026-10-24

Key takeaways

  • Richmond requires the stated certificate of appropriateness before SolarAPP+ submission for solar installations on resources listed on its Historic Register.
  • The instant-permit conditions include current contractor and city business records plus exact named approval and signed-application attachments.
  • The city's iMS Help page says all new permit applications use iMS, separate from the SolarAPP+ design-review platform.
  • The general residential solar resource page is not evidence that its older documents or process apply unchanged to commercial or industrial installations.

This Richmond solar guide combines local official application evidence with saved production and housing datasets. Use it to ask better questions about the complete proposed installation, not as a permit, roof assessment, local price survey or personalized financial recommendation. The local review route and electricity account matter independently of the energy model.

Check historic-resource status before platform submission

Richmond's SolarAPP+ page adds a specific local prerequisite for solar installations on historic resources. It says projects on sites listed on the Richmond Historic Register need a certificate of appropriateness from the Planning Division before submitting through SolarAPP+. The page connects that decision with consistency with the Secretary of the Interior's rehabilitation standards. Confirm the actual property's register status and the required planning determination before treating automated review as the first step. A familiar residential roof or an installer account does not establish that the historic-resource condition is irrelevant. Richmond SolarAPP+, historic-resource certificate, license conditions and exact attachment names

This is a specific stated trigger, not a claim that every Richmond rooftop installation needs that certificate or that the city will issue one automatically. Nor does an energy model assess historic compatibility or authorize a mounting location. Keep the actual planning record for the proposed layout where applicable and align it with the platform and city application. If the array location or other relevant details change, ask the responsible reviewer what must be updated instead of assuming the first certificate covers any later arrangement with the same nominal module capacity. Richmond SolarAPP+, historic-resource certificate, license conditions and exact attachment names PVWatts V8 model documentation

Richmond: project and approval records

  1. Check property and scope: Confirm residential eligibility and whether the project site is on Richmond's Historic Register.
  2. Resolve prerequisites: For applicable historic resources, obtain the certificate before SolarAPP+; confirm current contractor and business records.
  3. Complete platform and city records: Retain the approval ID and submit the actual iMS application with correctly named required attachments.
  4. Retain final permissions: Keep issued local records and inspection results separate from serving-provider operating permission.
A conceptual document checklist, not a promised schedule or technical eligibility decision. Follow the current local route and serving utility; some steps can overlap.

Diagram sources: www.ci.richmond.ca.us, www.ci.richmond.ca.us, www.ci.richmond.ca.us, www.pge.com, www.pge.com

Verify the current contractor and city business records

Richmond's instant-permit conditions include a current, valid contractor CSLB license and a current, valid City of Richmond Business Tax Certificate, described as the business license. These are independent checks, not interchangeable signs of platform membership. Ask the installer to identify the responsible contractor and applicable city records for the actual application. A SolarAPP+ login, a marketing badge or experience in a nearby city does not prove that the stated Richmond conditions are satisfied today. Keep the licensed entity consistent with the accepted project documents and written installation agreement. Richmond SolarAPP+, historic-resource certificate, license conditions and exact attachment names

The page describes automation for qualifying residential, roof-mounted retrofit photovoltaic systems and points to an eligibility checklist. This article does not turn that general description into approval of every battery arrangement, existing-system change or building type. Have the responsible contractor check the complete current scope and ask Building Division about work outside the described route. The city's list says an instant permit follows when all stated conditions are satisfied; satisfying one or two conditions does not establish that the complete record is accepted, technically eligible or ready for installation. Richmond SolarAPP+, historic-resource certificate, license conditions and exact attachment names

Use Richmond's exact attachment names and actual approval ID

The city specifies an uploaded SolarAPP+ approval attachment named SolarAPP+ Approval Documents and a signed application attachment named PAF Permit Application. It expressly says the attachment naming convention must match. Preserve those labels in the actual city record rather than assuming an informally named file or a link to a contractor's drive meets the instruction. The required approval and signed application are different documents. Confirm the final accepted versions describe the real property, responsible applicant, selected equipment and complete installation, not an earlier proposal with superficially similar capacity. Richmond SolarAPP+, historic-resource certificate, license conditions and exact attachment names

Richmond also tells applicants to reference the SolarAPP+ APPROVAL ID on the building-permit application and upload the documents generated by the platform. The platform processing charge is not presented here as the complete city permit cost. Obtain the actual city assessment and accepted record. If the system reports a missing or rejected attachment, resolve the specific document or account issue instead of treating the existence of the approval ID as proof of issuance. The city-facing application, its attachments and the design-review outcome need to agree, but each serves a distinct administrative purpose. Richmond SolarAPP+, historic-resource certificate, license conditions and exact attachment names

Complete the separate iMS city application

Richmond's current iMS Help page says the city only accepts applications through its online Intuitive Municipal Solutions system and that all new permit applications must use that portal. It describes creating an account, submitting applications, uploading documents, checking review status and communicating with staff. The solar page separately directs applicants to iMS after platform review. Do not confuse a SolarAPP+ account with the city's portal account, or assume design approval creates every required city record without the stated application and document steps. Use the real project identifiers when asking staff about status. Richmond SolarAPP+, historic-resource certificate, license conditions and exact attachment names Richmond iMS Help, exclusive online application channel, accounts, documents and status tracking

The iMS help page links account, contractor/business registration, inspection and digital-plan-room resources. Their presence identifies support routes; it does not establish that every project uses an identical account category, document format or inspection sequence. Ask the city about a missing application option or unclear project type rather than choosing an unrelated category merely to submit something. Keep an actual acceptance or issuance record, not only an upload screenshot. A later revision may require further review, so align final approved documents with the installed equipment and confirm how the city wants any change recorded. Richmond iMS Help, exclusive online application channel, accounts, documents and status tracking

Keep residential resource limits and operating permission intact

Richmond's separate Residential Solar Systems page links a guidebook, checklists and standard-plan resources, while explicitly limiting that information to residential systems and directing commercial and industrial questions to Building Division. It includes a 2019 guidebook reference. The page is useful for locating resources, but its existence does not prove that all older technical documents are the current requirements for every project. This guide does not copy numerical engineering rules from document titles, apply residential attachments universally to commercial work or infer a guaranteed review or inspection schedule from the city's solar policy goals. Richmond Residential Solar Systems, residential-only resources and separate commercial/industrial contact

For an actual PG&E account, provider interconnection review and official written permission to operate remain separate from Richmond planning, platform approval, city issuance and inspection. Do not operate before that permission. Keep the real local inspection result and final accepted equipment aligned with the provider application. Verify current account terms and any separate generation arrangement before analyzing the bill. The residential Solar Billing Plan distinguishes monthly statements from annual True-Up, but no marketing savings percentage is adopted here. The representative-point model does not decide historic compatibility, electrical suitability, permit completion or household savings. PG&E Getting Started with Solar, separate interconnection and official written permission to operate PG&E Solar Billing Plan, residential monthly statements and annual True-Up; marketing savings not adopted PVWatts V8 model documentation

Compare the complete Richmond offer with clearly labeled arithmetic

For arithmetic only, suppose a hypothetical cash offer prices 6 kW DC at $2.75 per watt: 6,000 watts times $2.75 equals $16,500. This is invented arithmetic, not an observed Richmond installation price, contractor quotation or assessment of a fair local budget. No former residential federal credit is deducted for property placed in service after the IRS cutoff. Request an itemized written offer for the actual equipment and complete construction, with assessed charges identified separately. Comparing identical panel capacities without checking the remaining scope can conceal substantial differences between proposals. IRS Residential Clean Energy Credit, placed-in-service cutoff

Identify applicable historic-resource review, current contractor/business records, actual city charges, related construction and responsibility for correctly accepted revised documents. Separate roof work, modules, inverter, storage, service changes, professional records, finance charges and actual city or provider obligations. Identify responsibility for revisions, corrections and further inspections. No incentive award, export revenue, savings or payback is calculated here. For a verified PG&E account, its residential Solar Billing Plan resource distinguishes monthly statements from annual True-Up. Actual consumption, import and export timing, account terms and any battery dispatch are required to value those exchanges. Annual reference production cannot replace those inputs or establish whether a financed offer is suitable for the household. PG&E Getting Started with Solar, separate interconnection and official written permission to operate PG&E Solar Billing Plan, residential monthly statements and annual True-Up; marketing savings not adopted PVWatts V8 model documentation

A documented 6 kW reference scenario for Richmond

The saved Richmond scenario estimates approximately 9,670 kWh AC annually at the Census representative point, not at a surveyed household roof. Its fixed inputs are 6 kW DC of modules, a roof-mounted south-facing array, 20-degree tilt, 14% aggregate system losses, a 1.2 DC/AC ratio and 96% inverter efficiency. The implied nominal inverter capacity is 5 kW AC. Module capacity, inverter capacity and annual energy are different quantities; none alone establishes permit eligibility. PVWatts V8 model documentation

PVWatts uses typical-year weather, not measured 2026 electricity production. The Richmond table retains all twelve modeled months and the annual total, with no extra 0.80 multiplier applied to its already modeled AC output. Model 0660620-roof-6kw-south-20deg-v1, provider version 8.5.0, identifies the saved scenario. It does not inspect shade, usable roof area, framing or electrical equipment, simulate storage dispatch, or calculate bills. Obtain a new estimate for the actual layout if module count, orientation or other inputs change. PVWatts V8 model documentation

Richmond: solar energy is not design approval or savings

  1. Survey the property: Describe the real roof, shading, structure and complete electrical scope.
  2. Model solar energy: Use the actual layout and identify DC module kW, AC inverter kW and annual AC kWh separately.
  3. Confirm approvals: Obtain the appropriate local review and serving provider's authorization for the final equipment.
  4. Analyze the bill: Use consumption, imports, exports, tariff and any battery operating assumptions; energy alone is not savings.
The fixed 6 kW DC scenario implies 5 kW nominal AC inverter capacity. Annual AC kWh does not establish structural suitability, permit eligibility, battery runtime or bill savings.

Diagram sources: developer.nlr.gov, www.ci.richmond.ca.us, www.pge.com, www.pge.com

Read the Richmond housing estimates with their uncertainty

The housing table joins Richmond to its exact Census place GEOID 0660620, using the 2020-2024 ACS five-year survey and 2024 geographic vintage. It reports occupied and owner-occupied housing units with their separate published 90% margins of error. These are multi-year estimates, not current 2026 household counts or counts of roofs eligible for solar. Keep the estimate and margin together when citing the data, and do not interpret ownership alone as installation permission or structural suitability. Census 2020-2024 ACS five-year dataset documentation

Survey acs-2020-2024-0660620 supplies the saved Richmond figures. Local ownership and occupancy context can help explain whom a guide may serve, but cannot establish roof condition, financial suitability or the number of installations. Small differences in modeled production or survey counts between neighboring places are not evidence that one community has better solar economics. The property assessment, verified account and local project records are the decision inputs. Displayed monthly and annual energy values are rounded independently, so their displayed totals can differ slightly. PVWatts V8 model documentation Census 2020-2024 ACS five-year dataset documentation

Check the installation date rather than assuming a federal credit

For new-installation planning, the IRS says property placed in service after December 31, 2025 is not eligible for the former residential clean energy credit. No such credit is deducted from the hypothetical cash example here. Older eligible expenses and unused-credit carryforwards are separate tax-return matters. Do not use a legacy incentive link on an otherwise useful municipal or utility page as proof of a current benefit, or replace an expired credit with an unverified local rebate. Confirm any other claimed benefit for the actual applicant, equipment and timing. IRS Residential Clean Energy Credit, placed-in-service cutoff

Keep the Richmond sources and account references together

The municipal, utility and IRS source text used for this Richmond article was reviewed October 23, 2026. Review means checking the public documents and their stated limits, not obtaining municipal staff approval or confirming every dated fee or code reference as newly effective. The production and housing data are saved research snapshots. Retain project-specific written requirements, final equipment and assessed charges as the project develops.

Read the California state guide for broader context. Only if the actual electricity account identifies PG&E, consult the PG&E utility guide. This is not a parcel-level territory assignment or confirmation of the generation supplier. Verify the serving provider, applicable account terms, interconnection status and any separate generation arrangement before analyzing imports, exports or savings. SMUD and neighboring-city rules are not substitutes for the actual account's requirements.

Richmond: reference production, 6 kW DC

Richmond: reference production, 6 kW DC
MonthModeled AC production (kWh)
January489
February491
March809
April947
May1,042
June1,094
July1,097
August1,008
September906
October763
November574
December449
Annual total9,670

Richmond: 2020-2024 ACS housing estimates

Richmond: 2020-2024 ACS housing estimates
MeasureFive-year estimate90% margin of error
Occupied housing units40,806±1,120
Owner-occupied housing units22,321±953

Richmond: scope and verification decisions

Richmond: scope and verification decisions
Project questionDocumented fact or boundaryWhat to verify
Historic-register propertyThe city requires a certificate of appropriateness before SolarAPP+ application in the stated case.Confirm register status and the actual Planning Division decision.
Instant permit conditionsCurrent CSLB license, city Business Tax Certificate and named attachments are required.Do not equate platform registration with valid city records or accepted uploads.
City intakeAll new applications use iMS according to the official help page.Create the correct account/record and track actual review status.
Commercial or industrial scopeThe residential resource page directs those questions to Building Division.Do not apply residential-only resources as universal requirements.

Frequently asked questions

When does the stated historic-resource certificate apply?

The page identifies sites listed on the Richmond Historic Register and requires the certificate before SolarAPP+ submission for the stated solar installation. Confirm the actual property and planning decision. [Richmond SolarAPP+, historic-resource certificate, license conditions and exact attachment names](https://www.ci.richmond.ca.us/4174/SolarAPP-For-Solar-Installers)

Does a SolarAPP+ account prove the contractor's city business record is current?

No. Richmond separately requires a valid CSLB license and current city Business Tax Certificate for the described instant-permit conditions. [Richmond SolarAPP+, historic-resource certificate, license conditions and exact attachment names](https://www.ci.richmond.ca.us/4174/SolarAPP-For-Solar-Installers)

What approval-attachment name does Richmond specify?

The city says SolarAPP+ Approval Documents, with the exact naming convention retained. [Richmond SolarAPP+, historic-resource certificate, license conditions and exact attachment names](https://www.ci.richmond.ca.us/4174/SolarAPP-For-Solar-Installers)

What should the signed application attachment be called?

The specified attachment name is PAF Permit Application. It is separate from the platform approval documents. [Richmond SolarAPP+, historic-resource certificate, license conditions and exact attachment names](https://www.ci.richmond.ca.us/4174/SolarAPP-For-Solar-Installers)

Where do new Richmond permit applications go?

The official iMS Help page says all new permit applications use the city's iMS web portal. [Richmond iMS Help, exclusive online application channel, accounts, documents and status tracking](https://www.ci.richmond.ca.us/4795/iMS-Help)

Can commercial work simply use the residential resource list?

Do not assume so. The residential page limits its information and directs commercial and industrial questions to Building Division. [Richmond Residential Solar Systems, residential-only resources and separate commercial/industrial contact](https://www.ci.richmond.ca.us/2771/Residential-Solar-Systems)

Sources and references