FTC R-value receipts and savings claims: a pre-invoice checklist.

In the United States, part of an insulation installer's paperwork is written by the Federal Trade Commission. Part 460 of Title 16 of the Code of Federal Regulations, on the labeling and advertising of home insulation, contains three sections that reach an installer's paperwork: 460.15 on showing fact sheets before the sale and 460.17 on what the receipt must say, on every job, and 460.19 on savings claims, whenever something the customer sees says or implies savings (as checked on 15 October 2026 against the eCFR and Cornell's Legal Information Institute).

Each can be checked line by line before the invoice goes out, a good job for a supervised AI assistant running a nightly routine that compares the job file with the rule and lists every gap. It never fills a gap with its own number, never decides an R-value and never signs the receipt. This article describes the rule's text; it is not legal advice, and the installer confirms their obligations with their own adviser.

Section 460.3 lists who is covered by the part, and installers are named alongside manufacturers, distributors, retailers, utility companies and advertisers. Section 460.1 says that breaking any of the part's rules is an unfair or deceptive act or practice under Section 5 of the FTC Act, and that a civil penalty can apply each time a rule is broken (as checked on 15 October 2026). A missing bag count is a gap in a document a federal rule prescribes, not a formatting slip.

Section 460.15 requires an installer to have fact sheets for the insulation products it sells, and to show customers the fact sheet for each type of insulation they want before they agree to buy. The method is the installer's choice; the rule offers a copy for each customer, or a binder shown before the sale, as examples.

The pre-invoice check is therefore about order and coverage. For each insulation type on the receipt, the checklist looks for a record that its fact sheet was shown, and compares that record's date with the date the contract was signed. A type that was installed but never quoted, such as batts added over a garage ceiling on the day, appears as a type with no fact-sheet record. The assistant lists it, and the installer explains it.

Section 460.17 requires the installer to give the customer a contract or receipt for the insulation installed. The receipt is dated and signed by the installer, the R-value is worked out from the data the manufacturer provides, and the fields depend on the type of insulation.

Two instructions in the section are easy to break when a receipt is typed in a hurry. Where insulation goes into more than one part of the house, the receipt gives the data for each part, and one receipt may cover them all only if the coverage areas and R-values of different parts are not added together. And the R-value for one inch is never multiplied by the number of inches installed. The checklist flags any combined total on a multi-area receipt, and any R-value it cannot find in the manufacturer's data.

The check on the bag count rests on a neighboring section. Section 460.12 requires the label on loose-fill insulation to give, for a set of R-values, the minimum settled thickness, the initial installed thickness, the maximum net coverage area, the number of bags per 1,000 square feet and the minimum weight per square foot (as checked on 15 October 2026).

Comparing the receipt with that chart is Aevrion's pattern, not a step the rule itself requires. The assistant reads the chart for the product and bag size the crew used, works out what it implies for the recorded area and R-value, and sets that beside the count on the receipt. A count that does not fit is a question for the installer: a typing error, a second area left off, or a real shortfall in the attic. The assistant asks; it never corrects the count, the thickness or the R-value.

Section 460.19 applies when ads, labels or other promotional materials say or imply that insulation can cut fuel bills or fuel use. The seller then needs a reasonable basis for the claim, and must include this statement: "Savings vary. Find out why in the seller's fact sheet on R-values. Higher R-values mean greater insulating power."

• REASONABLE BASIS

  Needed for any claim that insulation can slash or lower fuel bills, save money or cut fuel use; those are the section's own examples.

• THE STATEMENT

  The three sentences above, word for word, wherever such a claim is made.

• COMBINATIONS

  A claim about several products, or several parts of the house, must list them and say how much of the savings came from each, or rank them where figures cannot be given.

• WHERE IT IS NOT REQUIRED

  The disclosure requirements do not apply to television or radio ads, or to space-constrained ads. Section 460.18(e) defines those as interactive media whose limits prevent a clear and conspicuous disclosure, and the seller carries the burden of showing the space was insufficient.

• WHO IS LIABLE

  Manufacturers need a basis before making a claim. A seller that is not the manufacturer is liable only if it knows, or should know, that the manufacturer lacks one.

• RECORDS

  The data behind savings claims is kept for at least three years, and the three years start again each time the claim is made. FTC staff may inspect the records after giving reasonable notice.

Paragraph (g) lifts the disclosure requirements only; nothing in it removes the need for a reasonable basis. Step six of the nightly check below looks for the statement wherever savings language appears. It never drafts a savings figure; whether a basis is reasonable is the owner's call.

In Grok Bot, a routine tells one Bot to run a workflow on a schedule, at least five minutes apart; a Bot can own up to 50 routines, and the app keeps the 20 most recent run records for each. A nightly pre-invoice check fits that shape, and its output is one the documentation suggests asking for: a spreadsheet with defined columns, one row per check per job. Reading install sheets and receipts from the contractor's job software is a custom integration, or supervised browser use where the vendor permits it, subject to testing. The checklist itself is an Aevrion pattern.

When setting up a routine, the documentation says to confirm what happens when a source is missing. Here the answer is to report the job as unchecked, never to check it against last week's copy. If the morning sheet does not arrive, that absence is the signal for someone to look.

1. 01

   Collect

   Decides

   Which jobs are installed but not yet invoiced?

   Output

   A list of jobs with their install sheets, receipts and proposals

2. 02

   Fact sheets

   Decides

   Was a sheet shown for every type installed, before the contract date?

   Output

   A row per insulation type with the showing record and both dates

3. 03

   Receipt fields

   Decides

   Does each area carry every field its type requires?

   Output

   A row per area with each 460.17 field marked present or missing

4. 04

   Arithmetic

   Decides

   Are areas or R-values added across parts of the house, or is an R-value missing from the manufacturer's data?

   Output

   Flags, each with the receipt line it came from

5. 05

   Bag count

   Decides

   Does the loose-fill count fit the label's coverage chart?

   Output

   A question for the installer wherever it does not

6. 06

   Savings language

   Decides

   Did anything the customer saw make a savings claim without the statement or a basis on file?

   Output

   A list of documents and the sentence that raised each flag

7. 07

   Hand over

   Decides

   What must a person decide?

   Output

   The sheet, with every question and the signature line left for the installer

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

Everything the routine produces is preparation. The R-value on the receipt comes from the manufacturer's data and the installer's own measurement; the assistant can check that the two agree, but cannot decide which is right. The signature is the installer's statement about work they did, and a Bot has no standing to give it.

The nightly run reads the job software through a login saved on the one cloud computer every Bot on the account shares, so that login is open to all of them; the documentation says separate Bots are not a security boundary. And any approval a nightly run asks for lapses unanswered after roughly ten minutes (Cursor's help pages say thirty), with nothing executed, so the check is designed never to ask: it reads and reports.

Turning sections 460.15, 460.17 and 460.19 into checklist columns, building the nightly run and linking it to your job software, if that vendor's API or terms permit and once tested, is work Aevrion Ops can scope with you. For routine design in general, see the reliable workflows article; for your own business, the workflow automation readiness assessment comes first.

1. 460.15: the fact sheet for each type is shown before the customer agrees to buy.
2. 460.17: coverage area, thickness and R-value, plus both thicknesses and the bag count for loose-fill, on a receipt the installer dates and signs; parts of the house are never added together.
3. 460.19: a savings claim needs a reasonable basis and the 'Savings vary' statement; the supporting data is kept for at least three years from each time the claim is made.
4. A nightly routine can produce the checklist as a spreadsheet; it asks questions and never corrects a number.
5. Only the installer signs the receipt or decides an R-value.