Scope and caveat. This guide covers process and communication only. It gives no pricing advice. Notice periods and delivery rules depend on your lease and state law, so check both. This is not legal advice.
What the notice has to do
A rent change notice has three jobs. It must reach the tenant. It must be clear. And you must be able to prove later that it was sent.
Automation helps with all three. It applies the same timing to every tenant, fills the right details from the account, and keeps a record. It also removes the risk of someone forgetting a batch.
What sets the rules
Several things decide how and when you notify tenants. Check each before you build the workflow.
- Your lease. Most self storage leases state how rent changes are communicated and how much notice is given.
- State law. Some states set rules for notice or delivery. Check your lease and state law, ideally with a lawyer.
- Consent to electronic notices. If a law requires written notice, federal ESIGN rules set consent steps before email can satisfy it.[1]
- Autopay rules. For bank debits that change in amount, Regulation E requires written notice of the amount and date at least 10 days before the transfer.[2] Regulation E lets the consumer elect notice only when the amount falls outside a specified range.[2]
We make no claim about any specific state's notice period. Write your own required lead time into the workflow once it is confirmed.
Step-by-step notice workflow
This workflow assumes the pricing decision has already been made. It starts when you have a list of tenants and new rates.
- Confirm the lead time. Record the notice period your lease and state law require. Add a buffer for mail delivery if you send paper.
- Set the effective date. Pick a date that leaves at least the required notice period from the send date. Many operators align it with a billing date.
- Build the tenant list. Export from your management software. Include unit, current rent, new rent, effective date and contact details.
- Apply exclusions. Remove tenants already in lien or move-out, and any you have decided to exclude. Record why each was excluded.
- Check delivery method per tenant. Use email or text only where the tenant consented to electronic notices. Use mail where required or where consent is missing.
- Merge the template. Fill each notice from the account data. Do not type figures by hand.
- Review a sample. A person checks a sample of merged notices against the source list. Check names, units, amounts and dates.
- Schedule the rate change in the software. Set the new rent to start on the effective date, so billing matches the notice.
- Send. Send in one batch, or in batches by facility if your support capacity is limited.
- Log delivery. Store a copy of each notice, the send time and delivery status in the tenant record.
- Handle bounces and returns. Resend by another permitted method. Note it in the record.
- Send autopay notices if required. Make sure any varying-amount notice meets its own timing rule.
- Prepare for replies. Brief whoever answers calls and messages. Give them the effective date and the tenant's options.
- Confirm the first bill. After the effective date, check a sample of invoices show the new rent correctly.
What to put in the notice
Keep the notice short and factual. Tenants should understand it in one read.
| Element | Why it matters |
|---|---|
| Tenant name and unit | Shows the notice applies to this account |
| Current monthly rent | Gives the starting point |
| New monthly rent | States the change exactly |
| Effective date | Says when the new rent first applies |
| Autopay effect | Tells autopay tenants their charge will change |
| Tenant options | States how to ask questions or give notice to vacate, per the lease |
| Contact details | Gives a phone, email or portal link for questions |
| Date of notice | Supports your record of timing |
Avoid marketing language in a rent notice. Have your lawyer review the template once, then reuse it.
Choosing delivery channels
Each channel has trade-offs. Many operators use more than one for the same notice.
- Email: fast and cheap, with delivery tracking. Needs valid consent where written notice is required.
- Text message: high visibility, but short. Best as a pointer to the full notice. Needs consent for texts.
- Tenant portal: a reliable place to store the notice. Tenants may not check it unprompted.
- Mail: slower and costlier. May be required by your lease or state law. Certificates of mailing help with proof.
Our guide to tenant text and email reminders covers consent and message design. The online lease e-signature guide explains ESIGN consent for electronic records.
Handling replies
Rent notices produce calls and messages. Plan for them, especially at a facility with no on-site staff.
- Send notices at a time when someone can answer replies.
- Give the answering team a short script with the facts and the tenant's options.
- Log every reply against the tenant record.
- Track move-out notices that follow, so you can see the operational effect.
If calls go to a remote team or service, see call handling options.
Records to keep
If a tenant disputes a rent change, records are your answer. Keep these in the tenant file:
- The notice as sent, with merged figures.
- Send date, channel and delivery status.
- Any resend, with reason and method.
- The tenant's electronic consent record, if notice was electronic.
- Any autopay varying-amount notice.
- Replies and how they were resolved.
Testing the workflow before a real batch
Run the workflow once on test accounts before sending real notices. It catches problems while they are cheap to fix.
- Create two or three test tenants with email, text and mail delivery preferences.
- Give one test tenant autopay by bank debit.
- Run the merge and compare every field with the source data.
- Send the test notices and confirm each arrives in the expected channel.
- Check the tenant record shows the notice copy and delivery status.
- Confirm the scheduled rent change appears on the next invoice preview.
- Delete or close the test accounts afterwards.
Repeat the test after any template, software or channel change. Keep a short note of each test run with the date.
Multi-site portfolios
Operators with several facilities face extra coordination. Leases and state law may differ between sites.
- Keep a separate lead time and template per state, and per lease version if they differ.
- Run the merge per facility, so a mistake affects one site, not all of them.
- Stagger send dates if one team answers replies for every facility.
- Use one shared log format, so records look the same everywhere.
A shared calendar of notice batches helps the whole team see what is coming.
Frequently asked questions
How much notice do I have to give?
That depends on your lease and state law. Check both, ideally with a lawyer.
Can I send rent change notices by email only?
Possibly, if the tenant validly consented to electronic notices and your lease and state law allow it. Otherwise use mail.
Do autopay tenants need a separate notice?
For bank debits that change in amount, Regulation E sets its own advance notice rule. One notice can often cover both if it meets every requirement.
Should a person review automated notices?
Yes. Review a sample each batch to catch template or data errors before they reach every tenant.
Does this guide tell me how much to raise rent?
No. It covers process and communication only.
Sources
- 15 U.S. Code § 7001, General rule of validity (ESIGN Act), Legal Information Institute, Cornell Law School (accessed October 24, 2026)
- 12 CFR 1005.10, Preauthorized transfers (Regulation E), Consumer Financial Protection Bureau (accessed October 24, 2026)