--- title: "Collision shop AI rules: data, approvals, and spend" description: "Set collision shop AI rules for repair records, insurer files, customer approvals, payment data, and budget stops before connecting office functions" canonical: "https://scalewithsearch.com/articles/collision-shop-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) # Collision shop AI rules: data, approvals, and spend A collision shop's AI rules should identify which repair record controls the work and which person can authorize the next action. Write those rules before connecting customer inquiries, estimate files, or insurer correspondence to a function. Use this as a proposed administrative policy. Check your state's repair requirements and your shop's actual agreements before implementation. Keep the rule for drafting an update distinct from the rule for authorizing repair work or taking payment. The [collision shop hub](/for/auto-body-and-collision-shops) introduces the office workflow. This guide defines the data, approval, and spend limits around that workflow. ## Start with state repair rules and actual agreements Build a source sheet listing the state, shop location, applicable repair rules, insurer arrangements, and records owner. Have the shop's responsible reviewer approve that sheet. Do not copy an authorization workflow from another state's shop. North Carolina's Motor Vehicle Repair Act addresses written estimates and disclosures, additional-work notification and authorization, and invoices. Its scope contains exceptions. Use it as a state-specific example, rather than a national authorization template. [North Carolina Motor Vehicle Repair Act](https://ncleg.gov/EnactedLegislation/Statutes/HTML/ByArticle/Chapter_20/Article_15B.html), checked 2026.10.26. Keep legal requirements separate from the shop's stricter internal rules. You can require a manager's review of every proposed supplement even when that review is an operational choice. Label the policy accurately so staff know which changes require professional review. Do not let the function determine that a legal exception applies. Route the question to the person responsible for the shop's compliance process. Keep the current approved instruction in a readable record. ## Classify data by the function that needs it Give each function an allowlist. An inquiry summary should not receive the full repair database. A customer-update draft should not receive payment-card data. A supplement comparison should read only the baseline and proposed changes for that repair. | Record | Proposed treatment | Review owner | | --- | --- | --- | | Approved public services and hours | Read for office replies | Front-desk lead | | Customer inquiry and approved photos | Limit to the intake function | Estimator | | Current estimate and supplement | Restrict to the named repair | Estimator | | Claim and insurer correspondence | Limit to approved purpose and recipients | Office manager | | Card verification codes and PIN data | Exclude from AI inputs and logs | Payment owner | | Vehicle access instructions and keys information | Exclude from general drafting | Shop manager | | Unrelated repair files | Exclude | Records owner | These are proposed defaults for a first function. Confirm contractual limits and the tool's data handling before granting an exception. Record who approved the exception, its purpose, and when staff must review it again. The FTC recommends knowing where personal information flows and keeping only what the business needs. Apply that guidance to addresses, identifiers, and uploaded attachments. [FTC data-security guidance](https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business), checked 2026.10.26. ## Keep card collection in the payment system Do not collect a payment-card number or verification code in a general AI intake conversation. Route payment questions to the shop's approved payment process. Keep the function limited to a payment status reference where that is sufficient. PCI SSC states that sensitive authentication data must not be stored after authorization, even if encrypted. Its examples include card verification codes and PIN information. [PCI SSC FAQ 1533](https://www.pcisecuritystandards.org/faqs/1533/), checked 2026.10.26. Make the exclusion cover prompts, attachments, tool output, debugging files, and run receipts. Ask the builder to show what happens if a synthetic card-code field appears in an incoming test record. The function should block or route the record without copying that field into its report. Keep card refunds, charges, and changes to payment instructions outside the first function. A customer message about a balance is a request for staff review. It is not authority for a model to alter money records. ## Define the meaning of approved Use separate fields for estimator review, insurer response, customer authorization, and scheduling confirmation. Require the authoritative record and date for each. A single “approved” flag should not stand in for all four. For a proposed supplement, have the estimator check the changed scope and amounts. Have the office reviewer check the recipient and explanation. Obtain any required customer authorization through the established process before work proceeds. Do not treat an insurer's correspondence as a universal substitute for the customer's instruction. Ask the responsible reviewer to define the relationship for the specific agreement and state. Preserve uncertainty instead of having the model resolve it. Approval should cover one version, one repair reference, one recipient, and one action. If the amount or scope changes, send the item back for review. Keep the approved text and supporting record together. ## Prevent unsupported status and safety messages Require customer-update drafts to read the current repair status at preparation time. Define how long each source may remain current. If a dependency is stale or contradictory, return a question for the repair planner. Keep ordered, received, installed, checked, and ready for collection distinct. Have the shop define the source required for each label. Do not allow a draft to advance the status because the next step sounds likely. Have the repair planner approve status facts and the service lead approve the final send. Keep roadworthiness, repair suitability, and technical conclusions outside the administrative draft. Require the shop's designated professional process for those judgments. Use the [repair-time FAQ guide](/articles/collision-shop-repair-time-website-faq) for public timing language. Keep customer-specific progress messages tied to the individual repair record. ## Limit access in the connected software Make the source restriction part of the executor's configuration. A written instruction to avoid other repairs is insufficient if the connector can read every record without checks. Ask for a demonstration using two synthetic customers. Give incoming attachments no power to change permissions. A note inside a claim PDF must not authorize sending the repair file to a new address. Treat that note as content for review. Require draft-only output for the first function. Keep sending, booking, repair-order changes, and payments behind their own permissions. Inspect the effective account access during acceptance rather than relying on the proposed design. ## Assign cover for an unresolved repair packet Name the staff role that handles a packet when the original estimator is unavailable. Require the shop manager to approve any substitute reviewer. The function should preserve the unresolved questions and wait when no authorized checker is assigned. Test this case with a synthetic repair. Remove the review assignment and require a hold. Keep the draft visible in the office queue without issuing a customer message or changing the repair order. ## Put spend controls beside each function Set a separate monthly allowance for intake packets, update drafts, and supplement comparisons. Give each a per-run limit and a named alert recipient. Name the person who may approve extra spend. Limit pages per packet, model calls per job, and retry attempts. Check remaining allowance before another paid call. If the service cannot provide a dependable cost basis, hold that paid step for the budget owner instead of assuming a zero cost. Every run should leave a receipt with the job reference, source versions, model used, result, and cost. Exclude customer-identifying detail that the receipt does not need. Keep approved models named in internal settings and test replacements before use. ## Accept failure behavior as part of the job Test an unauthorized supplement, stale status, another customer's attachment, a changed recipient, forbidden payment fields, and exhausted budget. Repeat a completed job reference. Require no duplicate send or repair-order change. Keep the expected result beside each fixture. Have the shop owner inspect the generated packet and effective permissions. A readable draft does not establish that the boundary worked; test the prohibited action itself in a controlled environment. Bring the policy and failed cases to Scale With Search. Read [AI systems](/ai-systems), then request a bounded function with these acceptance checks through the [written scope form](/work). Continue the website review: [AI-native auto body and collision shops: first functions to build](/articles/ai-native-collision-shop-first-functions); [Auto marketing: a website plan for body shops](/articles/auto-body-marketing-website-local-search); [Auto Body Estimate Emails Missing: Trace the Request](/articles/auto-body-shop-estimate-email-delivery-check); [Auto Body Shop FAQ Schema: Check the Current Rules](/articles/auto-body-shop-faq-schema-current-rules); [How Auto Body Shops Can Ask for Google Reviews](/articles/auto-body-shop-google-review-requests); [Hail Damage Pages for Auto Body Shops: Define the Work](/articles/auto-body-shop-hail-damage-service-page); [Auto Body Shop Photo Estimate Form: What to Ask](/articles/auto-body-shop-photo-estimate-form); [Auto Body Shop Tow-In Pages: Explain the Arrival](/articles/auto-body-shop-tow-in-directions-page); [Collision Shop Certifications: What Your Site Can Say](/articles/collision-shop-certifications-website); [Collision Shop Google Appointment Links: Check the Path](/articles/collision-shop-google-appointment-link); [Collision Shop Insurance FAQs: Separate Each Promise](/articles/collision-shop-insurance-website-faq); [Collision Shop Location Pages: Route Each Inquiry](/articles/collision-shop-multiple-location-website-inquiries); [Collision Shop Repair-Time FAQs: Explain the Stages](/articles/collision-shop-repair-time-website-faq). [auto body and collision shops](/for/auto-body-and-collision-shops): website and search resources. ## Related: auto body and collision shops - [Collision Shop Certifications: What Your Site Can Say](/articles/collision-shop-certifications-website) - [Collision Shop Google Appointment Links: Check the Path](/articles/collision-shop-google-appointment-link) - [Collision Shop Insurance FAQs: Separate Each Promise](/articles/collision-shop-insurance-website-faq) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```