--- title: "Solar installation AI rules: data, approvals, and spend" description: "Set solar AI rules for utility bills, project records, proposal claims, approval gates, and per-function costs before connecting files and private data" canonical: "https://scalewithsearch.com/articles/solar-installation-ai-data-approval-spend-rules" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Solar installation AI rules: data, approvals, and spend Write solar AI rules before a function reads utility bills, proposals, project notes, or service records. Specify which records it may process, which decisions belong to people, and how the job stops when its budget runs out. A useful policy follows one project through preparation, review, and the next action. It names the source and approver for every customer-facing commitment. Use this worksheet with the [solar installation overview](/for/solar-installation) to define that boundary for your operation. The controls below are recommendations. They do not determine local installation requirements, tax eligibility, financing suitability, or whether a particular service may receive a customer's documents. Resolve those questions from the actual project and approved professional review. ## Separate project facts from access secrets Create a data map before granting a function access. List the record, purpose, approved reader, processing destination, retention rule, and person who can change the permission. Include temporary exports and generated drafts in the map. Use a narrow export for each task. A permit-packet gap check may need document status and approved references. It should not automatically receive household financial information or credentials for a utility account. | Data category | Proposed handling rule | | --- | --- | | Public service descriptions | Read only current approved copy | | Customer utility bill | Process only approved fields through an approved path | | Account passwords and access codes | Keep outside prompts and logs | | Signed proposal and change orders | Restrict to the named project and version | | Financing application or identity document | Exclude from the first office function | | Site photographs and roof documents | Check rights, project identity, and intended use | The FTC recommends avoiding unnecessary personal data collection and controlling access to sensitive information. [FTC security guidance, checked 2026.10.26](https://www.ftc.gov/business-guidance/resources/start-security-guide-business). Translate that principle into a field list. If the job only needs a usage figure, ask whether an approved extract can serve the task. Do not copy the whole household record merely because it is attached to an email. ## Give every claim a controlling source Require proposal drafts to distinguish measured inputs, estimates, assumptions, accepted terms, and unresolved questions. Label the source date. Do not let polished language erase uncertainty. The FTC recommends written solar bids that distinguish expected production, installation costs and permit fees, guarantees, and warranties. [FTC solar guide, checked 2026.10.26](https://consumer.ftc.gov/articles/solar-power-your-home). Use that distinction to set your review fields. A prepared summary should not convert an estimated output into a guarantee. A warranty reference should identify the applicable terms instead of asserting that every repair is covered. Keep tax, utility-credit, and financing statements out of a first general drafting function unless the responsible reviewer supplies current authoritative support. An older proposal is not current authority for a new customer's eligibility. The [solar website savings-claim review](/articles/solar-installer-website-savings-claims) covers publication evidence. Internal drafts need the same discipline before a salesperson repeats a statement to a customer. ## Define the approval map by action Choose the approver for each kind of output. A project coordinator may check whether a file appears in a register. A responsible technical reviewer checks design statements. The commercial owner approves price and accepted scope. The scheduler approves a commitment to attend. Require a person to approve the exact proposal, change order, customer update, application submission, or service message before it leaves the business. Include the recipient, destination account, attachments, record versions, and final text in the preview. Do not treat approval of the writing style as approval of technical content. Show unresolved technical questions separately. Keep the message waiting until the authorized role resolves them. If the scope, equipment reference, proposed date, customer, or recipient changes, invalidate the previous approval. The sending process should check the current version immediately before transmission. Preserve a failed or stale approval as a record rather than silently resending. ## Keep project status precise Use distinct states for requested, prepared, submitted, reviewed, approved, and scheduled. Give each state an owner and the evidence needed to enter it. Do not infer approval from a filename containing final. For a permit-packet function, require the actual recorded authority response before it can report approved status. For installation readiness, preserve unresolved conditions until the authorized owner closes them. For service, distinguish a received request from accepted work. Keep the model from editing the authoritative project register during the pilot. Let it write a proposed update with sources. Staff can accept that update through the existing controlled process. A source conflict should produce a visible exception. If a customer message asks for a date that differs from the office schedule, preserve both facts. Do not let the function choose whichever makes the reply sound more helpful. ## Protect payment information and financial decisions Exclude card numbers, verification codes, banking credentials, and financing login details from general AI inputs. Use the payment provider's approved workflow. Give administrative functions only the payment status they are authorized to read. PCI DSS prohibits keeping card verification codes after authorization, including in encrypted storage. [PCI Security Standards Council FAQ 1280, checked 2026.10.26](https://www.pcisecuritystandards.org/faqs/1280/). Check notification messages, attachments, and error logs for copied payment data. Removing a field from the visible draft does not establish that it never entered another record. Have the responsible reviewer inspect the actual processing path. Keep refunds, charges, finance applications, and bank-detail changes outside the preparation function's capabilities. A model-generated suggestion must not become authority to move money or alter the customer's agreement. ## Make spend control enforceable per function Budget permit-packet preparation, readiness briefs, and service handoffs separately. Give each a monthly allowance, maximum request size, per-run ceiling, retry limit, and alert owner. Record who may approve an increase. Before processing, reserve an amount sufficient for the bounded request. Include document processing and allowed retries. When remaining allowance is insufficient, leave a blocked receipt and route the job for manual handling. Do not automatically switch to a more expensive process. After each attempt, reconcile actual cost against the reservation. Include failed requests in the total. Stop retry loops after the configured limit. If the cost record cannot be written, stop new processing until the record is restored. Keep price assumptions and model identifiers in dated configuration. Require a review when a processor, model, or data location changes. Test a replacement against the same approved inputs before it handles real project work. ## Test what the policy forbids Build a synthetic project with a mismatched customer reference, an old proposal, a missing approval, and an expired message preview. Write the expected behavior first. Require a separate exception for each problem. Add a file containing a fake password and a payment-code marker. Verify that the intake filter blocks prohibited material and that error receipts do not repeat it. Check access as an unauthorized user through the same function. Run the budget-exhausted case. Confirm that processing stops before a new paid request. Test the alert route using internal recipients approved for the exercise. Record the outcomes and any corrections in the operating record. ## Put ownership into the handoff Keep the data map, approval rules, source versions, configuration, tests, and runbook in business-controlled records. Give the office a stop control and a documented manual path. Train a backup to use both. Review the policy when accepted work, data categories, processors, or sending permissions change. Preserve the distinction between a working preparation function and the people who make technical and commercial decisions. Use the [approval matrix guide](/articles/ai-agent-approval-matrix) to record who may approve each action in this operating policy. Bring Scale With Search the permitted sources, approval owners, and sample project. Read the [AI systems scope](/ai-systems), then [send your requirements](/work#send-your-brief) for a written function definition. Continue the website review: [AI-native solar installation: the first functions to build](/articles/ai-native-solar-installation-first-functions); [Solar brochure PDFs: decide what search should find](/articles/solar-brochure-pdf-search-indexing); [Solar project pages: separate installed work from estimates](/articles/solar-installation-project-case-study-page); [Solar installer review requests: keep the wording neutral](/articles/solar-installer-google-review-request-process); [Solar installer local SEO: connect coverage to real proof](/articles/solar-installer-local-seo); [Solar installer videos: give each useful clip a page](/articles/solar-installer-video-website-search); [Solar installer credentials: make website claims precise](/articles/solar-installer-website-certification-claims); [Solar website FAQs: publish answers you can maintain](/articles/solar-installer-website-faq-content); [Solar installer quote form: ask for the first useful facts](/articles/solar-installer-website-quote-form); [Solar website savings claims: show the assumptions](/articles/solar-installer-website-savings-claims); [Solar website warranty page: name the actual coverage](/articles/solar-installer-website-warranty-page); [Solar repair page: separate service from installation](/articles/solar-maintenance-repair-website-page). [solar installers](/for/solar-installation): website and search resources. ## Related: solar installers - [Solar project pages: separate installed work from estimates](/articles/solar-installation-project-case-study-page) - [Solar installer review requests: keep the wording neutral](/articles/solar-installer-google-review-request-process) - [Solar installer local SEO: connect coverage to real proof](/articles/solar-installer-local-seo) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```