PRICE-INCREASE-NOTICE-CHECKLIST-READY. STOP PUBLISHING: do not let AI publish price-increase, rate-change, grandfathering, renewal, discount, cancellation, refund, notice-period, or exception claims until the owner, finance lead, support lead, or policy reviewer verifies the current source and approves exact wording.

1. Price-change source card

Offer/product/service affected: [name]
Current public price/source URL:
New approved price/source URL:
Effective date and timezone:
Who is affected: [new customers / renewals / all customers / segment]
Who is not affected or grandfathered:
Notice sent where: [email / invoice / site banner / account page / support macro]
Approved explanation in one sentence:
Support owner for questions:
Last reviewed by/date:

2. Exception and risk fields

Discount/coupon allowed? [yes/no/source]
Refund/credit/proration rule:
Cancellation or downgrade option:
Existing contract / renewal impact:
Tax/fee/checkout impact:
Sales quote validity impact:
Customer-safe wording limit:
Do-not-promise list: [grandfathering, refunds, discounts, deadlines, legal rights, contract terms, future pricing]

3. Safe customer wording starters

Short notice

We are updating the price for [offer] on [effective date]. Your current record shows [verified impact]. Please use [official page/contact] for the current details; we do not want to guess about discounts, grandfathering, refunds, or renewal terms.

When facts are missing

Thanks for asking. I do not want to give you an unsupported answer about the price change. I am checking the approved policy/source record and will confirm the exact effective date, affected plan, and next step through [official channel].

4. AI audit prompt

You are reviewing a small-business website, support macro, sales page, chatbot answer, or AI-search snippet about a price increase or rate change. Use only the approved source card below. Do not invent prices, effective dates, grandfathering, refunds, credits, cancellations, renewal terms, discount eligibility, legal rights, contract terms, or future pricing. Return: (1) safe public answer, (2) unsupported claims to remove, (3) missing source fields, (4) customer questions needing human review, and (5) STOP PUBLISHING triggers.

Approved source card:
[PASTE VERIFIED SOURCE CARD]

5. Public-page QA before publishing

Does the public wording match the current price source, not a sales rep memory or old PDF?
Are effective dates, timezones, and affected customer segments explicit?
Are grandfathering, coupons, credits, refunds, and cancellation paths either verified or omitted?
Are old FAQ, pricing, checkout, help-center, PDF, and chatbot sources updated or linked to the new source?
Is there an owner-approved rollback note if the change is delayed?

6. Product signal

If this resource earns reuse, replies, or traffic, add a pricing-change/source-control worksheet to SEO After AI: effective-date records, grandfathering proof, support macros, and AI-search audit prompts for price-sensitive pages.