---
name: Resident Communications Expert
description: Resident letter, rent increase notice, newsletter, community notice, resident complaint, maintenance notice, acquisition letter, rule violation, collections notice, resident communication, policy update, welcome letter, emergency notice.
agent: resident-communication-specialist
---

# Resident Communications Expert

Comprehensive reference for drafting, reviewing, and delivering resident-facing communications across Sunrise Communities' 15-state manufactured housing portfolio. Covers rent increase notices, change-of-ownership letters, maintenance/emergency notices, newsletters, collections, rule enforcement, utility rate changes, retention communications, difficult situations, AI-safe patterns, multilingual requirements, delivery methods, and Fair Housing guardrails.

> **Workflow handoffs:** This skill participates in multi-step workflows:
> - **Eviction:** `mhp-regulatory` (notice requirements) → `delinquency-model` (risk scoring, collection escalation) → `resident-communications` (notices/letters) → `fair-housing` (compliance check)
> - **Rent Increase:** `mhp-operations-expert` (market analysis) → `resident-communications` (draft notice) → `fair-housing` (disparate impact check) → `mhp-regulatory` (state notice period/method requirements)

**Scope:** All outbound communications to TOH (Tenant-Owned Home) and POH (Park-Owned Home) residents, including formal legal notices, informal community updates, Sunny AI chatbot interactions, and staff-drafted correspondence.

**Primary Sources:** State landlord-tenant statutes, manufactured home park acts, Fair Housing Act (42 U.S.C. 3601-3619), Fair Debt Collection Practices Act (15 U.S.C. 1692), HUD LEP guidance, state-specific MH park regulations.

**Last verified: March 2026**

> **CRITICAL DISCLAIMER:** This skill provides communication guidance and compliance frameworks but does NOT constitute legal advice. All eviction notices, legal threats, Fair Housing complaints, ADA accommodation responses, and collections referrals to third parties MUST be reviewed by qualified legal counsel before sending.

---

## Table of Contents

1. [Sunrise Communication Standards](#1-sunrise-communication-standards)
2. [Rent Increase Notices — 15-State Matrix](#2-rent-increase-notices--15-state-matrix)
3. [Change-of-Ownership Notifications](#3-change-of-ownership-notifications)
4. [Maintenance and Emergency Notices](#4-maintenance-and-emergency-notices)
5. [Community Newsletter Framework](#5-community-newsletter-framework)
6. [Collections Communication](#6-collections-communication)
7. [Rule Enforcement Notices](#7-rule-enforcement-notices)
8. [Utility Rate Change Notices](#8-utility-rate-change-notices)
9. [Resident Retention Communications](#9-resident-retention-communications)
10. [Difficult Situation Playbook](#10-difficult-situation-playbook)
11. [AI-Safe Communication Patterns](#11-ai-safe-communication-patterns)
12. [Multilingual Requirements](#12-multilingual-requirements)
13. [Digital vs Physical Delivery](#13-digital-vs-physical-delivery)
14. [Fair Housing Guardrails](#14-fair-housing-guardrails)
15. [Template Library](#15-template-library)
16. [Decision Trees](#16-decision-trees)
17. [Common Gotchas](#17-common-gotchas)
18. [Output Formats](#18-output-formats)
19. [References](#19-references)

---

## 1. Sunrise Communication Standards

### 1.1 Brand Voice and Tone

**Core Identity:** Sunrise Communities provides "forever homes" — affordable, well-maintained manufactured housing communities. Communications must reflect the tension between operating a value-add investment and serving residents who depend on stable, affordable housing.

**Voice Principles:**
| Principle | In Practice |
|-----------|------------|
| Professional but Warm | "We're neighbors, not just landlords" — use first-person plural ("we"), address by name |
| Clear and Direct | No legal jargon unless legally required; plain language at 6th-8th grade reading level |
| Empathetic | Acknowledge impact on residents before stating the business reason |
| Action-Oriented | Every notice must answer: "What do I need to do?" with clear next steps |
| Honest | Never obscure a rent increase behind euphemisms; state the change directly |

**Approved Language vs Prohibited Language:**

| Use This (Approved) | Not This (Prohibited) |
|---------------------|----------------------|
| "We're writing to let you know..." | "This letter serves as notice that..." |
| "Please reach out with questions" | "Failure to comply will result in..." |
| "Your lot rent will increase to..." | "An adjustment has been assessed..." |
| "Thank you for being part of our community" | "Your tenancy is contingent upon..." |
| "We understand this impacts your budget" | "This increase is non-negotiable" |
| "Community improvement" | "Capital expenditure recapture" |
| "Your home" / "your community" | "The unit" / "the premises" / "the property" |
| "[Community Name]" | "The park" / "the trailer park" |

**Prohibited terms in ALL resident communications:**
- "Trailer" or "trailer park" (use "manufactured home" and "community")
- "Mobile home" in formal notices (use "manufactured home" unless referencing a state statute that uses "mobile home")
- "Tenant" in resident-facing materials (use "resident" or "homeowner" for TOH)
- Threatening or coercive language outside of legally required notice language
- Internal business terms: "loss-to-lease," "NOI," "cap rate," "value-add," "forced appreciation"
- Any language suggesting increases fund investor returns

### 1.2 TOH vs POH Communication Differences

| Element | TOH (Tenant-Owned Home) | POH (Park-Owned Home) |
|---------|------------------------|----------------------|
| Primary relationship | Lot lease / land lease | Home rental + lot |
| How to address | "Homeowner" or "Resident" | "Resident" |
| Rent increase scope | Lot rent only | Total rent (home + lot) |
| Maintenance responsibility | Resident maintains home; community maintains infrastructure | Community maintains home and infrastructure |
| Home sale rights | Resident can sell home in place (most states) | N/A |
| Move-out complexity | Must relocate home (costly) — extra empathy needed | Standard move-out |
| Utility billing | Often sub-metered or RUBS for lot | May be included in rent |

**Key principle:** TOH residents have significantly more at stake with rent increases because they own a home that is difficult and expensive to move. Communications to TOH residents must acknowledge this reality and provide adequate time and information for them to plan.

### 1.3 Required Elements on All Formal Notices

Every formal notice (rent increase, rule change, policy update, utility change) must include:

1. **Community name** — full legal name, not abbreviation
2. **Date of notice** — date sent/posted
3. **Effective date** — when the change takes effect
4. **What is changing** — specific, quantified where applicable
5. **Resident action required** — what they need to do, if anything
6. **Contact information** — community manager name, phone, email, office hours
7. **Equal Housing Opportunity statement** — on all formal/printed notices
8. **ADA accommodation note** — "If you need this notice in an alternative format, please contact [name]"

### 1.4 Signature Block Standard

```
Sincerely,

[Manager Full Name]
Community Manager
[Community Name]
[Phone Number] | [Email Address]
Office Hours: [Days and Times]

[Equal Housing Opportunity Logo]
```

---

## 2. Rent Increase Notices — 15-State Matrix

### 2.1 Notice Period Requirements by State

This is the most critical compliance table for Sunrise operations. The value-add model relies on recapturing loss-to-lease through lot rent increases, making these notices among the most frequent and legally sensitive communications we send.

| State | MH Park Notice Period | Statute / Authority | Cap / Restriction | Delivery Method | Special Requirements |
|-------|----------------------|--------------------|--------------------|-----------------|---------------------|
| **OH** | 30 days written | ORC 4781.40 | No cap; no increase during lease term | Written notice to all residents | Date of implementation must be specified |
| **IN** | 30 days (general); 60 days (MH-specific best practice) | IC 32-31 (general L-T) | No cap; no rent control | Written notice | No MH-specific statute; follow lease terms |
| **MD** | 60 days (check jurisdiction) | MD Real Prop. Code | **10% cap for 3 years post-acquisition** | Certified or registered mail + posted in community | Purchaser must file affidavit; $10K penalty for violation |
| **MI** | 30 days written | MHCA (Act 96 of 1987) | No cap; increase cannot be "excessive" to force eviction | Written notice specifying new amount + effective date | File complaint with LARA if improper notice |
| **FL** | **90 days written** | Fla. Stat. 723.037 | No cap; 90-day notice is non-waivable | Written notice to each homeowner + HOA board | Triggers right to meet and discuss (within 60 days before effective date); must identify affected homeowners |
| **WV** | 30 days (month-to-month) | WV Code 37-6 | No cap | Written notice | No MH-specific statute; follow general L-T law |
| **PA** | 30 days written | MHCRA (Act 261 of 1976) | No cap; max 1 increase per year; no increase during lease term | Written notice + posted in community + mailed | Cannot be enforced until 30 days after notice posted AND mailed |
| **AL** | 30 days (practice standard) | AL Code 35-9A (Uniform RLTA) | No cap | Written notice | No MH-specific statute; follow lease terms |
| **GA** | **60 days written** | GA Code 44-7 | No cap; cannot increase during lease term | Written notice | Must state precise amount and effective date |
| **AR** | 30 days (month-to-month) | AR Code 18-17 | No cap | Written notice | Minimal MH-specific regulation |
| **MN** | **60 days written** | MN Stat. 327C.06 | No cap; max 2 increases per 12 months; no increase to pay fines | Personal delivery, mail, or delivery to home | Certified mail effective even if refused; **no admin/capital/distribution markup on utility billing (327C.04)** |
| **ND** | 30 days (month-to-month) | ND Century Code 47-16 | No cap | Written notice | Minimal MH-specific regulation |
| **WI** | 28 days (general); **60 days (manufactured home communities)** | WI Stat. 710.15 | No cap | Written notice | MH community lease must outline rent formula |
| **MO** | **60 days (MH land lease communities)** | RSMo 700.600 | No increase during 60 days before or after park closure notice (except property tax pass-through) | Written notice | Specific protections for MH communities |
| **IL** | **90 days written** | 765 ILCS 745 | No cap; resident has 30 days to accept/reject; rent deferral program available | Written notice | Tenant can defer increase for up to 1 year if qualifying hardship |

### 2.2 Quick-Reference: Longest Notice States

**90-day states (HIGHEST RISK):** Florida, Illinois
**60-day states:** Maryland, Georgia, Minnesota, Wisconsin (MH), Missouri (MH)
**30-day states:** Ohio, Indiana, Michigan, West Virginia, Pennsylvania, Alabama, Arkansas, North Dakota

**Sunrise operational rule:** When in doubt, default to 60 days. For any state with an MH-specific statute, follow the MH statute, not the general landlord-tenant law.

### 2.3 Maryland Post-Acquisition Rent Cap (Special Rule)

Maryland imposes the strictest post-acquisition restrictions in the Sunrise portfolio:

- **Cap:** Rent cannot increase more than 10% per year for the first 3 years after acquisition
- **Affidavit required:** Purchaser must file an affidavit in county land records stating: (1) continued use as MHC for 5 years, and (2) the 10% cap commitment
- **Notification:** Each homeowner must receive notice by certified/registered mail; affidavit must be posted in a public area
- **Penalty:** $10,000 to homeowners' organization if affidavit is violated
- **Source:** MD Manufactured Housing Modernization Act (MHMA, 2023); MD Real Prop. Code

**Operational impact for Sunrise:** Underwriting for MD acquisitions must account for the 3-year rent cap. Year 1-3 rent increase notices in MD must reference the affidavit and confirm compliance with the 10% cap.

### 2.4 Rent Increase Notice Template

```
[COMMUNITY LETTERHEAD]

[Date]

[Resident Name]
[Lot/Site Number]
[Community Name]
[City, State ZIP]

RE: Notice of Lot Rent Adjustment — Effective [DATE]

Dear [Resident Name],

We hope this letter finds you well. We are writing to notify you of an
upcoming adjustment to your lot rent at [Community Name], effective
[EFFECTIVE DATE].

    Current Monthly Lot Rent:   $[CURRENT]
    New Monthly Lot Rent:       $[NEW]
    Monthly Increase:           $[DIFFERENCE]
    Effective Date:             [DATE]

This adjustment reflects [SELECT APPROPRIATE REASON(S):
- increased property taxes and insurance costs
- investments in community improvements, including [SPECIFIC IMPROVEMENTS]
- rising costs of water/sewer/waste services
- general increases in operating and maintenance costs].

[FOR MD POST-ACQUISITION (Years 1-3) ADD:]
This increase is within the 10% annual cap as set forth in the affidavit
filed in [County] land records at the time of community purchase.

We understand that any increase impacts your household budget, and we
do not make this decision lightly. We remain committed to maintaining
[Community Name] as a quality, well-maintained community you are proud
to call home.

[FOR FL/IL (90-day states) ADD:]
Under [Florida Statute 723.037 / 765 ILCS 745], you have the right to
[meet and discuss this increase with community management / accept or
reject this increase within 30 days]. Please contact us to schedule a
time to discuss.

If you have any questions or would like to discuss this change, please
contact us at [PHONE] or [EMAIL]. Our office is open [OFFICE HOURS].

Thank you for being part of our community.

[SIGNATURE BLOCK]

[Equal Housing Opportunity Logo]
This notice is provided in compliance with [STATE] law requiring
[X] days' written notice of rent adjustments.

If you need this notice in an alternative format or language,
please contact [Manager Name] at [Phone].
```

### 2.5 Rent Increase Pre-Send Checklist

- [ ] Correct state notice period verified (see matrix above)
- [ ] Effective date is at least [X] days from send date
- [ ] Current and new amounts are accurate (verified against lease/RM records)
- [ ] MD post-acquisition: increase is within 10% annual cap
- [ ] FL: notice includes right to meet and discuss
- [ ] IL: notice includes right to accept/reject within 30 days
- [ ] MN: no more than 2 increases in trailing 12 months
- [ ] PA: no more than 1 increase per year; not during lease term
- [ ] Delivery method matches state requirement (see Section 13)
- [ ] Equal Housing Opportunity statement included
- [ ] Alternative format/language offer included
- [ ] Contact information complete and accurate
- [ ] No prohibited language (see Section 1.1)
- [ ] Copy retained in resident file with proof of delivery

---

## 3. Change-of-Ownership Notifications

### 3.1 When Sunrise Acquires a Community

Sunrise's value-add model means acquisitions are frequent. The first communication residents receive sets the tone for the entire relationship.

**Timing:** Send within 5 business days of closing (earlier if required by state law; MD requires pre-closing notification).

**Key principles:**
- Lead with reassurance, not change
- Introduce Sunrise's philosophy (community, investment, quality)
- Do NOT mention planned rent increases in the acquisition letter
- Provide immediate, accessible contact information
- Acknowledge that change is unsettling

### 3.2 State-Specific Requirements

| State | Requirement | Source |
|-------|------------|--------|
| **MD** | Pre-closing: purchaser files affidavit (5-year continued use, 10% rent cap for 3 years); notice by certified/registered mail to each homeowner + posted in community | MHMA 2023 |
| **OH** | Residents have notification rights if park is sold or closed | ORC 3733 / 4781 |
| **MN** | 180 days' written notice before park closure; residents have right of first refusal to purchase | MN Stat. 327C |
| **MO** | 120 days' notice before requiring vacating due to change in use | RSMo 700.600 |
| **FL** | Park owner must notify residents of lot tenancy terms; new owner bound by existing rental agreements | Fla. Stat. 723.031 |
| **All others** | No MH-specific change-of-ownership notification statute; follow general landlord-tenant law and existing lease terms |

### 3.3 Acquisition Welcome Letter Template

```
[SUNRISE COMMUNITIES LETTERHEAD]

[Date]

Dear [Community Name] Residents,

We are pleased to introduce ourselves as the new owners of [Community
Name], effective [CLOSING DATE]. Our company, Sunrise Communities,
owns and operates manufactured housing communities across [X] states,
and we are committed to making [Community Name] a place you are proud
to call home.

WHAT THIS MEANS FOR YOU:
- Your lease remains in effect under its current terms
- Your current lot rent will not change until [proper notice period]
- Your home is yours — nothing about your homeownership changes
- Community rules remain the same unless you are notified in writing

WHAT YOU CAN EXPECT FROM US:
- A community manager who is responsive and accessible
- Investment in community infrastructure and appearance
- Clear, honest communication about any future changes
- Respect for your home and your rights as a [resident/homeowner]

YOUR NEW CONTACTS:
  Community Manager: [Name]
  Phone: [Number]
  Email: [Email]
  Office Hours: [Hours]
  Emergency After-Hours: [Number]

We will be hosting a Meet and Greet on [DATE] at [LOCATION] from
[TIME] to [TIME]. Please join us — we would love to hear from you
about what you value most in your community.

[FOR MD ADD:]
In accordance with Maryland law, an affidavit has been filed in
[County] land records confirming that [Community Name] will continue
to operate as a manufactured housing community for at least five
years, and that lot rent will not increase by more than 10% per year
for the first three years following this purchase.

We look forward to being part of your community.

Warmly,

[Signature Block]

[Equal Housing Opportunity Logo]
```

---

## 4. Maintenance and Emergency Notices

### 4.1 Urgency Tiers

| Tier | Response Time | Delivery Method | Examples |
|------|--------------|----------------|----------|
| **EMERGENCY** | Immediate (within 1 hour) | Door-to-door + posted at entries + phone/text blast | Water main break, gas leak, severe weather, fire, flood |
| **URGENT** | Same day | Posted at entries + door hangers + email/text | Planned water shutoff (same day), road closure, boil advisory |
| **SCHEDULED** | 48-72 hours advance | Posted at entries + mailed/emailed | Planned infrastructure work, pest treatment, tree trimming |
| **INFORMATIONAL** | 5-7 days advance | Posted at entries + newsletter/email | Seasonal maintenance reminders, landscaping schedules |

### 4.2 Emergency Notice Template

```
*** EMERGENCY NOTICE ***
[COMMUNITY NAME]

Date: [DATE]          Time: [TIME POSTED]
Affected Areas: [SPECIFIC LOTS / SECTIONS / "ENTIRE COMMUNITY"]

WHAT IS HAPPENING:
[Brief, clear description of the emergency]

WHAT YOU NEED TO DO:
  1. [Specific action — e.g., "Do not use tap water until further notice"]
  2. [Specific action — e.g., "Evacuate to [location] immediately"]
  3. [Specific action — e.g., "Move vehicles from [area]"]

ESTIMATED DURATION: [Time estimate or "Until further notice"]

EMERGENCY CONTACT: [Name] at [Phone Number]
If life-threatening: CALL 911

We apologize for the disruption and will provide updates as the
situation develops.

— [Community Name] Management
```

### 4.3 Scheduled Maintenance Notice Template

```
[COMMUNITY LETTERHEAD]

MAINTENANCE NOTICE — [COMMUNITY NAME]

Date Posted: [DATE]

Dear Residents,

We will be performing [TYPE OF WORK — e.g., "water line repairs",
"road resurfacing", "tree trimming"] in the community.

WHEN:       [DATE(S)] from [START TIME] to [END TIME]
WHERE:      [Specific lots/sections affected]
IMPACT:     [What residents will experience — e.g., "Water service
            will be interrupted for approximately 4 hours"]
WHAT TO DO: [Instructions — e.g., "Please store water in advance",
            "Move vehicles from the roadway by 7:00 AM"]

This work is necessary to [REASON — e.g., "improve water pressure
and prevent future leaks"]. We appreciate your patience as we make
these improvements to our community.

Questions? Contact [Name] at [Phone] or [Email].

— [Community Name] Management
```

### 4.4 Maintenance Communication Best Practices

- **Over-communicate, especially on timing.** Residents plan their days around work schedules, childcare, and medical needs. A surprise water shutoff at 8 AM can ruin someone's day.
- **Update when timelines change.** If work runs long, post an update — even a brief "Work is taking longer than expected; estimated completion now [TIME]."
- **Close the loop.** When work is complete, post a brief "ALL CLEAR" notice thanking residents for their patience.
- **Seasonal reminders calendar:**
  - Spring: Skirting inspection, lot cleanup, sewer line reminders
  - Summer: Heat safety, watering restrictions, pest control
  - Fall: Winterization checklist (heat tape, pipe insulation, furnace service)
  - Winter: Snow removal procedures, freeze warnings, space heater safety

---

## 5. Community Newsletter Framework

### 5.1 Recommended Cadence

**Monthly** is the recommended cadence for active Sunrise communities. Monthly provides enough frequency to keep residents informed without creating content fatigue.

- **Monthly:** For communities with 50+ lots, active improvement programs, or new acquisitions (first 12 months)
- **Bi-Monthly:** For stable communities with fewer ongoing changes
- **Quarterly:** Minimum acceptable frequency; suitable only for small, stable communities

### 5.2 Standard Newsletter Sections

| Section | Purpose | Content Source |
|---------|---------|---------------|
| **Community Manager Message** | Personal touch; top of newsletter | Community manager drafts; Aurora can assist |
| **Community Updates** | Construction, improvements, policy changes | Operations team |
| **Upcoming Events** | Community gatherings, local events, office closures | Community manager |
| **Maintenance Reminders** | Seasonal tips, resident responsibilities | Operations; use seasonal calendar (Section 4.4) |
| **Resident Spotlight** (optional) | Profile a long-term or contributing resident | Community manager with resident consent |
| **Important Dates** | Payment due dates, office hours, holidays | Standard |
| **Safety Tips** | Fire safety, weather prep, scam alerts | Standard library |
| **Contact Information** | Manager, emergency, maintenance request process | Standard footer |

### 5.3 Newsletter Content Guidelines

**Do:**
- Keep total length to 1-2 pages (front and back of one sheet for print)
- Use headers, bullets, and white space — no walls of text
- Include at least one positive/community-building item per issue
- Use photos when possible (with resident permission)
- Maintain consistent layout issue-to-issue
- Post the top 2-3 items as a cover section visible at a glance

**Do not:**
- Use the newsletter to announce rent increases (use formal notices)
- Include individual resident names in a negative context
- Reference specific legal disputes or complaints
- Include content that could be construed as favoring any protected class
- Use the newsletter as a threat vector ("Violators will be evicted")

### 5.4 Distribution Methods

- **Print:** Posted at community bulletin board + delivered to each lot (door hanger or mailbox per USPS rules)
- **Email:** To all residents with email on file
- **Text/SMS:** Summary with link to full newsletter (for communities using text platforms)
- **Sunny AI:** Chatbot can reference newsletter content when residents ask about community updates

---

## 6. Collections Communication

### 6.1 FDCPA Compliance Summary

> **Cross-reference:** See `delinquency-model` skill Section 6 "Legal Requirements for Collections" for the full FDCPA/TCPA compliance framework, applicability analysis, Regulation F details, bankruptcy protections, and SCRA rules. This section covers communication-specific guidance only.

**Key rules for collections COMMUNICATIONS:**
- Send validation notice within 5 days of first third-party contact (amount, creditor, dispute rights)
- No contact before 8 AM or after 9 PM local time
- Never discuss debt with anyone other than the resident, their attorney, or a credit bureau
- Include opt-out mechanism in all electronic communications
- Limit: no more than 7 calls per debt per 7-day period (Regulation F)

### 6.2 Internal Collections Escalation Timeline

| Day | Action | Communication Type |
|-----|--------|--------------------|
| Day 1 (due date) | Rent due per lease | No action |
| Day 2-5 | Grace period (if applicable per lease/state) | No action |
| Day 6 | Friendly reminder | Phone call or text: "This is a courtesy reminder that your [month] lot rent of $[amount] has not been received. Please contact us if you have questions." |
| Day 10 | Written late notice | Formal letter: state amount owed + late fee + payment options |
| Day 15 | Follow-up call | Personal call from community manager; document conversation |
| Day 30 | Demand letter | Formal demand with cure-or-quit timeline per state law |
| Day 45+ | Legal referral | Escalate to attorney; FDCPA applies fully from this point |

### 6.3 Collections Language Rules

**Approved internal collections language:**
- "Your account shows a balance of $[X] for [month]. Please contact us to arrange payment."
- "We'd like to work with you to resolve this balance. Payment plans may be available."
- "If you're experiencing financial hardship, please contact us. We may be able to connect you with assistance programs."

**Prohibited language (internal or external):**
- "You will be evicted" (unless legal process has actually begun)
- "We will report this to credit agencies" (unless you actually do and have disclosed this)
- "Everyone in the community knows you haven't paid"
- Any reference to the resident's personal circumstances, family status, or protected characteristics
- "This is your final notice" (unless it actually is the final notice before legal action)

### 6.4 Late Payment Notice Template

```
[COMMUNITY LETTERHEAD]

[Date]

[Resident Name]
[Lot/Site Number]
[Community Name]

RE: Past Due Lot Rent — [MONTH/YEAR]

Dear [Resident Name],

Our records show that your [MONTH] lot rent payment of $[AMOUNT] has
not been received. As of [DATE], your account balance is:

    Lot Rent Due:       $[AMOUNT]
    Late Fee:           $[LATE FEE]
    Total Due:          $[TOTAL]

Please submit payment by [DATE] to avoid further action. Payment
can be made by [ACCEPTED METHODS — e.g., "check, money order, or
online at [URL]"].

If you are experiencing financial difficulty, please contact us at
[PHONE]. We may be able to discuss payment arrangements or connect
you with local assistance resources.

Sincerely,

[SIGNATURE BLOCK]
```

---

## 7. Rule Enforcement Notices

### 7.1 Progressive Enforcement Framework

Consistent, documented, progressive enforcement protects Sunrise from selective enforcement claims (which can become Fair Housing complaints) and gives residents a fair opportunity to correct behavior.

| Stage | Notice Type | Timeline | Consequence |
|-------|------------|----------|-------------|
| **1. Verbal Warning** | Documented phone call or in-person conversation | Immediate | Note date, time, content in resident file |
| **2. First Written Warning** | Courtesy notice (friendly tone) | 7-14 days to cure | No penalty; document delivery |
| **3. Second Written Warning** | Formal notice (firm tone) | 7 days to cure | Reference first warning and date |
| **4. Violation Notice** | Lease violation notice (legal tone) | Per state cure period | Reference prior warnings; state consequences |
| **5. Legal Action** | Attorney referral / cure-or-quit | Per state eviction law | MUST involve legal counsel |

**Critical rule:** Enforcement must be applied uniformly across all residents regardless of protected class status. Document every action. Selective enforcement (enforcing rules against some residents but not others) creates Fair Housing liability.

### 7.2 Common Violation Categories

| Category | Examples | Typical Cure Period |
|----------|---------|-------------------|
| **Lot appearance** | Unmowed grass, debris, unauthorized structures, skirting damage | 14-30 days |
| **Vehicle/parking** | Unregistered vehicles, parking on grass, commercial vehicles | 7-14 days |
| **Noise** | Excessive noise during quiet hours, loud music, barking dogs | Immediate (verbal) → 7 days (written) |
| **Pets** | Unauthorized pets, unleashed animals, pet waste | 7-14 days |
| **Unauthorized occupants** | Undisclosed residents, extended guests beyond lease limit | 14 days |
| **Property damage** | Damage to community property, common areas | 7-14 days + repair cost |
| **Illegal activity** | Drug activity, criminal behavior | Immediate escalation to legal |

### 7.3 First Written Warning Template (Courtesy Notice)

```
[COMMUNITY LETTERHEAD]

[Date]

[Resident Name]
[Lot/Site Number]

RE: Community Standards Reminder — [VIOLATION TYPE]

Dear [Resident Name],

During a recent review of our community, we noticed [SPECIFIC
DESCRIPTION OF ISSUE — e.g., "several items stored outside the
skirting of your home that are not consistent with our community
appearance standards"].

Our community guidelines [reference specific rule section] require
[STATE THE RULE]. We would appreciate your help in addressing this
by [SPECIFIC DATE — typically 14 days].

If you have questions about this notice or need additional time due
to circumstances beyond your control, please contact us at [PHONE].
We are happy to work with you.

Thank you for helping us maintain [Community Name] as a great place
to live.

[SIGNATURE BLOCK]
```

### 7.4 Formal Violation Notice Template

```
[COMMUNITY LETTERHEAD]

[Date]

[Resident Name]
[Lot/Site Number]

RE: Community Rule Violation — Second Notice

Dear [Resident Name],

This letter is a follow-up to our previous notice dated [DATE OF
FIRST WARNING] regarding [VIOLATION TYPE] at your home site.

We have observed that [DESCRIBE CURRENT STATUS — e.g., "the items
referenced in our previous notice remain on your lot"]. As outlined
in your lease agreement, Section [X], and our Community Rules,
Section [Y], [STATE THE RULE].

Please correct this matter by [DATE — typically 7 days from notice].
If this issue is not resolved by that date, further action may be
taken in accordance with your lease agreement, which may include
[SPECIFIC CONSEQUENCE — e.g., "charges for community-performed
cleanup" or "formal lease violation proceedings"].

We prefer to resolve this cooperatively and invite you to contact
us at [PHONE] if you would like to discuss.

[SIGNATURE BLOCK]
```

---

## 8. Utility Rate Change Notices

### 8.1 Sub-Metering vs RUBS

**Sub-Metering:** Individual meters measure each lot's actual usage. Residents pay for what they use. Most transparent and preferred method.

**RUBS (Ratio Utility Billing System):** Total community utility bill is allocated among residents based on a formula (typically occupant count, lot size, or equal share). Less precise but simpler to implement.

### 8.2 State-Specific Utility Billing Restrictions

| State | Key Restriction | Source |
|-------|----------------|--------|
| **MN** | **No admin, capital, or distribution markup** on utility billing. Park owner cannot charge more than the commodity rate they pay. No disconnection, reconnection, or late payment fees on utilities. | MN Stat. 327C.04 |
| **FL** | Utility charges must be disclosed in lot rental agreement; 90-day notice for changes to services or utilities | Fla. Stat. 723.037 |
| **WI** | Lease must outline rent formula including utility calculation method | WI Stat. 710.15 |
| **PA** | Utility billing changes require 30-day notice and posting | Act 261 |

**Sunrise operational rule:** Never mark up utility pass-through costs in ANY state. Even where permitted, markup creates resident resentment and regulatory risk. Bill at cost.

### 8.3 Utility Rate Change Notice Template

```
[COMMUNITY LETTERHEAD]

[Date]

Dear [Community Name] Residents,

NOTICE OF UTILITY RATE CHANGE

Effective [DATE], the [UTILITY TYPE — e.g., "water and sewer"]
rates at [Community Name] will be adjusted as follows:

    Current Rate:    $[CURRENT] per [unit — e.g., "1,000 gallons"]
    New Rate:        $[NEW] per [unit]
    Base Fee:        $[BASE] per month (if applicable)

This change reflects [REASON — e.g., "an increase in the rates
charged to us by [Utility Provider Name]"]. [Community Name] does
not add any markup or administrative fees to utility charges — we
pass through the exact cost we are charged.

[FOR RUBS COMMUNITIES:]
Your individual utility charge is calculated based on [FORMULA —
e.g., "the number of occupants in your home as a proportion of
total community occupants"]. Your specific charge will appear on
your next monthly statement.

If you have questions about this change or would like to see the
utility provider's rate schedule, please contact [Name] at [Phone].

[SIGNATURE BLOCK]
```

---

## 9. Resident Retention Communications

### 9.1 Why Retention Matters for MHP Operations

In manufactured housing, turnover is extraordinarily costly:
- TOH: vacant lots generate zero revenue; filling requires marketing, home sales/placement, utility hookup
- POH: vacancy + turnover costs (cleaning, repairs, marketing, lost rent during vacancy)
- Reputation: high turnover signals community problems to prospective residents

**Retention ROI:** Retaining one TOH resident who might otherwise move their home avoids $5,000-$15,000 in lot preparation and marketing costs. Retaining one POH resident avoids $2,000-$5,000 in turnover costs.

### 9.2 Retention Communication Calendar

| Timing | Communication | Purpose |
|--------|--------------|---------|
| **Move-in + 30 days** | Welcome check-in call/note | "How is everything? Any questions?" |
| **Move-in + 90 days** | Satisfaction survey (brief) | Identify issues before they become move-out reasons |
| **Annually** | Lease renewal letter (60-90 days before expiration) | Early renewal incentive; confirm satisfaction |
| **Resident anniversary** | Thank-you note or small gift | "Thank you for X years at [Community Name]" |
| **After maintenance completion** | Follow-up call/note | "Was the repair completed to your satisfaction?" |
| **After rent increase** | Check-in call (2 weeks post-effective date) | "Do you have any questions about the change?" |
| **Holiday/seasonal** | Community greeting | Holiday card, seasonal newsletter |

### 9.3 Lease Renewal Letter Template

```
[COMMUNITY LETTERHEAD]

[Date]

[Resident Name]
[Lot/Site Number]

RE: Lease Renewal — [Community Name]

Dear [Resident Name],

Your current lease at [Community Name] expires on [DATE]. We value
you as a member of our community and hope you will choose to renew.

Your renewal terms:
    Lease Term:         [12 months / month-to-month]
    Monthly Lot Rent:   $[AMOUNT]
    Effective Date:     [DATE]

[IF RENEWAL INCENTIVE:]
As a thank-you for your continued residency, we are pleased to offer
[INCENTIVE — e.g., "a one-time $50 credit on your next month's rent"
or "a complimentary home exterior power wash"].

Please sign and return the enclosed renewal agreement by [DATE].
If you have any questions or concerns, we would love to hear from
you — please call [PHONE] or stop by the office.

Thank you for making [Community Name] your home.

[SIGNATURE BLOCK]
```

### 9.4 Resident Appreciation Strategies

- **Milestone recognition:** 5-year, 10-year, 15-year certificates or small gifts
- **Community events:** Summer cookout, holiday gathering, back-to-school supply drive
- **Referral bonus:** Offer existing residents $100-$250 for referring new residents who sign a lease
- **Maintenance responsiveness:** The single strongest retention tool is responding to maintenance requests quickly and completely
- **Community improvements:** When you make improvements, communicate what you did and why — residents who see investment stay longer

---

## 10. Difficult Situation Playbook

### 10.1 Noise Complaints

**Response framework:**
1. **Acknowledge:** "Thank you for letting us know. We take quality of life seriously."
2. **Document:** Date, time, nature of noise, complainant (kept confidential)
3. **Investigate:** Do not assume the complaint is accurate; approach the other party neutrally
4. **Address:** "We've received a report of [noise type] from this area of the community. We wanted to check in."
5. **Follow up:** Contact complainant within 48 hours with status

**Do NOT:**
- Reveal the complainant's identity
- Take sides before investigating
- Characterize the noise as "your music" or "your party" (use neutral language)
- Make assumptions based on the resident's background, age, or family composition (Fair Housing)

### 10.2 Unauthorized Occupants

**Response framework:**
1. Send written notice referencing lease occupancy clause
2. State the policy neutrally: "Your lease permits [X] occupants. Our records show [Y] persons."
3. Offer a path to compliance: "If you have additional household members, we'd be happy to process a lease addendum."
4. Do NOT assume family relationships, immigration status, or make judgments about household composition

**Fair Housing alert:** Occupancy standards must be based on objective criteria (square footage, building code, health/safety) — not assumptions about family status. HUD guidance: generally 2 persons per bedroom is reasonable.

### 10.3 Property Damage

**Response framework:**
1. Document with photographs and written description
2. Determine responsibility (resident, community, third party, weather)
3. If resident responsibility: send written notice with specific description, repair timeline, and cost allocation per lease
4. Offer assistance connecting with insurance or repair resources

### 10.4 Non-Payment Conversations

**In-person or phone approach:**
1. "I'm calling about your account. Our records show a balance of $[X]. Can we discuss?"
2. Listen first — there may be circumstances you're unaware of
3. "Would a payment arrangement help? We could consider [options]."
4. Document the conversation and any agreement IN WRITING
5. Follow up with a written confirmation of any payment plan

**Never:**
- Discuss in front of other residents
- Threaten disconnection of essential services (illegal in most states)
- Reference other residents' payment status
- Promise outcomes you cannot guarantee

### 10.5 Resident-to-Resident Disputes

**Role:** Facilitator, not adjudicator. Sunrise manages the community, not personal relationships.

1. Listen to both parties separately
2. Identify if a community rule is being violated
3. If yes: enforce the rule uniformly (see Section 7)
4. If no: "We understand this is frustrating. As a community manager, we can enforce community rules, but we aren't able to mediate personal disagreements. We'd encourage you to [local mediation resource]."
5. Document all interactions

---

## 11. AI-Safe Communication Patterns

### 11.1 What Sunny AI Can Do

Sunny AI (the resident-facing chatbot at sunny-cm.suncom.work) handles certain resident interactions. The following are SAFE for Sunny to handle:

| Safe for AI | Example |
|-------------|---------|
| Provide office hours and contact info | "Our office is open Mon-Fri 9-5. You can reach us at..." |
| Accept maintenance requests | "I've submitted a maintenance request for [issue]. A team member will follow up within [timeframe]." |
| Share community rules (factual) | "Community quiet hours are 10 PM to 7 AM." |
| Confirm payment methods | "You can pay rent by check, money order, or online at..." |
| Provide general community info | "Trash pickup is on Tuesdays and Fridays." |
| Direct to resources | "For questions about your lease, please contact [Manager] at..." |
| Share newsletter content | "The community cookout is scheduled for July 4th at the clubhouse." |

### 11.2 What Sunny AI Must NOT Do

| Not Safe for AI — Must Escalate to Human | Why |
|------------------------------------------|-----|
| Discuss specific rent amounts or increases | Legal notice requirements; must be in writing |
| Make promises about maintenance timelines | Creates enforceable commitments |
| Respond to discrimination or Fair Housing complaints | Legal exposure; requires trained human response |
| Discuss individual account balances | FDCPA and privacy concerns |
| Make statements about lease terms or legal rights | Unauthorized practice of law risk |
| Respond to accommodation requests (disability, ESA) | Requires interactive process per FHA |
| Discuss eviction status or legal proceedings | Must be handled by counsel |
| Make statements about other residents | Privacy and liability |
| Offer payment plans or financial arrangements | Must be authorized by management |
| Respond to threats or hostile messages | Safety concern; escalate to management |

### 11.3 Sunny AI Escalation Triggers

Sunny must immediately escalate to a human when it detects:
- Keywords: "lawyer," "attorney," "sue," "discrimination," "fair housing," "disability," "accommodation," "eviction," "harassment," "threatened"
- Sentiment: anger, distress, or threatening language
- Requests for specific financial information
- Any question it cannot answer with pre-approved content
- Repeated questions suggesting the resident is not getting adequate help

**Escalation response:** "I want to make sure you get the right help with this. Let me connect you with [Manager Name]. You can reach them directly at [Phone/Email], or I can have them call you. Which would you prefer?"

### 11.4 AI Communication Audit Requirements

- Review Sunny AI conversation logs weekly for Fair Housing compliance
- Flag any conversation where Sunny provided information about protected classes, family status, or occupancy standards
- Quarterly audit of AI response patterns for disparate treatment
- Annual review of AI training data and response templates
- Maintain audit trail for 3 years minimum

---

## 12. Multilingual Requirements

### 12.1 Legal Framework

**Federal:** Title VI of the Civil Rights Act of 1964 requires federally-assisted housing providers to provide meaningful access to persons with Limited English Proficiency (LEP). While private housing not receiving federal assistance is not directly covered by Title VI, the Fair Housing Act's national origin protections apply to all housing.

**HUD Guidance:** Housing providers must take "reasonable steps" to ensure LEP persons have meaningful access. This includes providing interpreters and may include translating vital documents.

**Fair Housing Act:** Refusing to rent or imposing different terms because of national origin (including language) is illegal. Language-related housing restrictions can constitute national origin discrimination.

### 12.2 Sunrise LEP Communication Standards

| Situation | Requirement |
|-----------|-------------|
| **Lease signing** | Offer reasonable time for resident to have lease translated; consider providing key lease summary in resident's language |
| **Rent increase notice** | If community has a significant LEP population (10%+), provide notice in primary non-English language |
| **Emergency notice** | Always provide in English + primary non-English language of community |
| **Community rules** | Make available in primary non-English language if significant LEP population |
| **Maintenance requests** | Accept in any language; use translation services to understand and respond |
| **Eviction/legal notices** | English required for legal validity; provide translated courtesy copy |

### 12.3 What NOT To Do

- Do NOT refuse to rent to someone because they do not speak English
- Do NOT require English proficiency as a condition of tenancy
- Do NOT refuse to communicate with someone because of their language
- Do NOT use children as interpreters for official business (use professional services)
- Do NOT charge residents for translation services
- Do NOT assume a resident's language based on their name or appearance

### 12.4 Translation Resources

- Professional translation services (for vital documents)
- Staff members with language skills (document which staff speak which languages)
- Language line services (for phone interpretation)
- Google Translate or similar (acceptable for informal communications ONLY; never for legal notices)
- Community volunteer interpreters (acceptable with resident's consent; not ideal for sensitive matters)

---

## 13. Digital vs Physical Delivery

### 13.1 State-by-State Delivery Requirements for MH Parks

| State | Required Delivery Method | Electronic Notice Allowed? |
|-------|-------------------------|---------------------------|
| **OH** | Written notice | Not specified; default to mail/hand delivery |
| **IN** | Written notice | Not specified; default to mail/hand delivery |
| **MD** | **Certified or registered mail** + posted in community | No (for rent increases and ownership changes) |
| **MI** | Written notice (specified new amount + effective date) | Not specified |
| **FL** | Written notice to each homeowner + HOA board | Not specified; 90-day notice is non-waivable |
| **WV** | Written notice (month-to-month) | Not specified |
| **PA** | Written + posted in community + mailed | No (must be posted AND mailed) |
| **AL** | Written notice | Not specified |
| **GA** | Written notice | Not specified |
| **AR** | Written notice | Not specified |
| **MN** | Personal delivery, mail, or delivery to home | Certified mail effective even if refused |
| **ND** | Written notice | Not specified |
| **WI** | Written notice | Not specified |
| **MO** | Written notice | Not specified |
| **IL** | Written notice | Not specified |

### 13.2 Best Practice Delivery Protocol

**For ALL formal notices (rent increases, rule changes, lease violations):**

1. **Primary:** First-class mail to resident's address on file
2. **Secondary:** Hand-deliver with signed acknowledgment (keep copy)
3. **Tertiary:** Post on resident's door (photograph with date-stamp)
4. **Backup:** Post in community common area / office
5. **Supplemental:** Email and/or text (NEVER as sole delivery for formal notices)

**For MD:** Use certified mail with return receipt requested. This is mandatory, not optional.

**For MN:** Certified mail is effective even if the resident refuses delivery. Delivery to the home (left with someone of suitable age or in a secure, conspicuous location) is also valid.

### 13.3 Proof of Service Documentation

For every formal notice, maintain a file containing:
- Copy of the notice as sent
- Date sent/delivered
- Method of delivery
- Proof of mailing (USPS receipt, certified mail return receipt, or Certificate of Mailing)
- Signed acknowledgment (if hand-delivered)
- Photograph of posted notice (if door delivery)
- Name of person who delivered (if hand-delivered)
- Retain for minimum 3 years (5 years recommended)

### 13.4 Electronic Communication Guidelines

Email and text messaging are acceptable for:
- Maintenance updates and reminders
- Community event notifications
- Newsletter distribution
- Payment reminders (non-legal)
- General community information

Email and text are NOT acceptable as sole delivery for:
- Rent increase notices
- Lease violation notices
- Rule change notices
- Legal notices of any kind
- Eviction-related communications

**Consent requirement:** Obtain written consent before sending any electronic communications. Include opt-out mechanism in every message. Maintain record of consent.

---

## 14. Fair Housing Guardrails

> **Cross-reference:** See the `fair-housing` skill for comprehensive Fair Housing compliance guidance. This section covers communication-specific guardrails only.

### 14.1 Protected Classes (Federal)

Race, Color, Religion, National Origin, Sex (including sexual orientation and gender identity per Bostock/HUD), Familial Status, Disability

**Many Sunrise states add:** Age, ancestry, marital status, source of income, military/veteran status, sexual orientation, gender identity (varies by state and locality)

### 14.2 Communication-Specific Rules

| Rule | Application |
|------|-------------|
| **No steering language** | Do not describe community demographics ("family-friendly," "quiet community for retirees," "great schools nearby") |
| **No selective communication** | Same notice must go to all affected residents; do not send different versions based on any characteristic |
| **No familial status references** | Do not reference children, family size, or household composition unless directly relevant to an occupancy standard based on objective criteria |
| **No disability assumptions** | Do not reference or ask about disabilities; respond to accommodation requests through the interactive process |
| **Neutral language** | Use "resident," "household," "person" — not "man/woman," "family," "couple" |
| **Equal Housing Opportunity** | Include logo/statement on all printed formal notices, advertising, and community signage |
| **Consistent enforcement** | Document that rule enforcement is applied uniformly |

### 14.3 Words and Phrases to Avoid

**Never use in any resident communication:**
- "Family-friendly" / "adult community" (unless legally designated 55+)
- "Walking distance to church/mosque/synagogue"
- "Near [ethnic] restaurants/shops"
- "English-speaking community"
- "No Section 8" or "No vouchers" (check state/local source-of-income protections)
- "Able-bodied"
- "Christian community" / "family values"
- References to "those people," "that element," "the wrong crowd"
- "Master bedroom" (use "primary bedroom" — industry trend, not legally required, but risk-reducing)

### 14.4 FHA-Compliant Advertising Language

**Approved:** "All are welcome." "We comply with Fair Housing laws." "Reasonable accommodations available upon request."

**Required on all advertising:** Equal Housing Opportunity logo or statement.

---

## 15. Template Library

### 15.1 Template Index

| Template | Section | Use Case |
|----------|---------|----------|
| Rent Increase Notice | 2.4 | Annual or mid-year lot rent adjustment |
| Acquisition Welcome Letter | 3.3 | Post-closing introduction to residents |
| Emergency Notice | 4.2 | Immediate safety/service disruptions |
| Scheduled Maintenance Notice | 4.3 | Planned infrastructure work |
| Late Payment Notice | 6.4 | Past-due rent collection (internal) |
| First Written Warning | 7.3 | Courtesy notice for rule violation |
| Formal Violation Notice | 7.4 | Second notice / escalated enforcement |
| Utility Rate Change Notice | 8.3 | Sub-meter or RUBS rate adjustment |
| Lease Renewal Letter | 9.3 | Annual renewal invitation |
| Rent Increase Closing Paragraph | 15.2 | Empathetic closing for any rent increase |
| Community Event Invitation | 15.3 | Resident events and gatherings |
| Policy Update Notice | 15.4 | Community rule or policy changes |
| Move-Out Acknowledgment | 15.5 | Confirming resident departure |

### 15.2 Rent Increase Closing Paragraph (Standard)

```
We understand that any increase impacts your household budget, and
we do not make this decision lightly. We remain committed to
maintaining [Community Name] as a quality, well-maintained community
you are proud to call home.

If you have any questions or would like to discuss this change,
please do not hesitate to contact us at [PHONE] or [EMAIL]. Our
door is always open.

Thank you for being part of our community.
```

### 15.3 Community Event Invitation Template

```
[COMMUNITY LETTERHEAD]

You're Invited!

[EVENT NAME] at [COMMUNITY NAME]

WHEN:    [DATE] from [START TIME] to [END TIME]
WHERE:   [LOCATION — e.g., "Community Clubhouse", "Lot 42 common area"]
WHAT:    [DESCRIPTION — e.g., "Summer cookout with hamburgers, hot dogs,
         and games for all ages"]

[FOOD/DRINK DETAILS — e.g., "Food and drinks provided" or "Please
bring a dish to share"]

RSVP to [Name] at [Phone/Email] by [DATE] so we can plan accordingly.

We hope to see you there!

— [Community Name] Management
```

### 15.4 Policy Update Notice Template

```
[COMMUNITY LETTERHEAD]

[Date]

NOTICE OF COMMUNITY POLICY UPDATE

Dear [Community Name] Residents,

Effective [DATE], the following change to our community [rules /
policies] will take effect:

WHAT IS CHANGING:
[Clear, specific description of the policy change]

WHY:
[Brief, honest explanation — e.g., "To improve community safety" or
"In response to resident feedback"]

WHAT YOU NEED TO DO:
[Specific resident action, if any — or "No action is required on
your part"]

The updated community rules are available [at the office / online at
URL / posted on the community bulletin board].

If you have questions, please contact [Name] at [Phone/Email].

[SIGNATURE BLOCK]
```

### 15.5 Move-Out Acknowledgment Template

```
[COMMUNITY LETTERHEAD]

[Date]

[Resident Name]
[Forwarding Address if available]

RE: Move-Out Confirmation — Lot [NUMBER], [Community Name]

Dear [Resident Name],

This letter confirms your move-out from Lot [NUMBER] at [Community
Name], effective [DATE].

[FOR TOH:] Please ensure all personal property and your manufactured
home are removed from the lot by [DATE]. The lot must be returned to
a clean, level condition in accordance with your lease agreement.

[FOR POH:] Please return all keys to the office by [DATE]. A final
inspection will be conducted on [DATE/TIME]. Your security deposit
will be processed in accordance with [STATE] law.

Final account status:
    Rent through [DATE]:    $[AMOUNT]
    Outstanding balance:    $[AMOUNT]
    Security deposit:       $[AMOUNT] (disposition within [STATE-REQUIRED DAYS])

We wish you well in your next chapter. If you have any questions
about your final account, please contact [Name] at [Phone/Email].

[SIGNATURE BLOCK]
```

---

## 16. Decision Trees

### 16.1 Which Notice Type Do I Need?

```
Is a resident's financial obligation changing?
├── YES: Is it a rent increase?
│   ├── YES → Rent Increase Notice (Section 2)
│   │         Check state notice period (Section 2.1)
│   │         Check MD post-acquisition cap (Section 2.3)
│   └── NO: Is it a utility rate change?
│       ├── YES → Utility Rate Change Notice (Section 8)
│       └── NO: Is it a new fee or charge?
│           └── YES → Policy Update Notice (Section 15.4)
│                     Verify fee is permitted by lease + state law
├── NO: Is a community rule changing?
│   ├── YES → Policy Update Notice (Section 15.4)
│   │         FL: 90-day notice required for rule changes too
│   └── NO: Is a resident violating a rule?
│       ├── YES → Rule Enforcement Notice (Section 7)
│       │         Follow progressive enforcement (Section 7.1)
│       └── NO: Is it maintenance or emergency?
│           ├── YES → Maintenance/Emergency Notice (Section 4)
│           │         Determine urgency tier (Section 4.1)
│           └── NO: Is it community information?
│               └── YES → Newsletter (Section 5) or direct communication
```

### 16.2 Which Delivery Method Do I Use?

```
Is this a rent increase, lease violation, or legal notice?
├── YES: Check state delivery requirement (Section 13.1)
│   ├── MD? → Certified mail + posted in community (MANDATORY)
│   ├── PA? → Written + posted + mailed (ALL THREE)
│   ├── MN? → Any: personal, mail, or delivery to home
│   └── All others → First-class mail + hand delivery backup
│         Always retain proof of service (Section 13.3)
├── NO: Is this an emergency?
│   ├── YES → All channels simultaneously: door-to-door,
│   │         posted, phone/text blast, email
│   └── NO: Is this routine communication?
│       └── YES → Email/text (with consent) + posted in common area
│                 Print for residents without digital access
```

### 16.3 Escalation Path for Resident Issues

```
Resident contacts community with issue
├── Maintenance request → Log in system → Assign → Complete → Follow up
├── Payment question → Review account → Provide info → Document
├── Complaint about community → Log → Investigate → Respond within 48 hrs
├── Complaint about another resident → Log → Investigate both sides
│   ├── Rule violation? → Progressive enforcement (Section 7)
│   └── Personal dispute? → Facilitate, don't adjudicate (Section 10.5)
├── Fair Housing complaint → STOP → Escalate to legal IMMEDIATELY
├── Accommodation request → STOP → Escalate to compliance team
├── Threat of legal action → STOP → Escalate to legal IMMEDIATELY
└── Media inquiry → STOP → Escalate to corporate communications
```

---

## 17. Common Gotchas

### 17.1 Notice Period Errors (Most Common Compliance Failure)

| Gotcha | Impact | Prevention |
|--------|--------|------------|
| Sending FL/IL rent increase with 30-day notice instead of 90 | Notice is void; increase cannot be enforced until new 90-day notice is sent | Verify state BEFORE drafting; see matrix (Section 2.1) |
| MD increase exceeds 10% in Years 1-3 post-acquisition | $10K penalty to homeowners' org; potential legal action | Track acquisition date per community; flag in RM |
| MN: third rent increase in 12 months | Increase is invalid | Track all MN increases with date log |
| PA: increase during lease term | Unenforceable | Check lease expiration before sending |
| Counting notice days incorrectly (mailing date vs receipt date) | Notice may be short | Count from mail date + delivery standard (add 3-5 days for mail) |

### 17.2 Delivery Proof Failures

| Gotcha | Impact | Prevention |
|--------|--------|------------|
| MD rent increase sent by regular mail instead of certified | Legally insufficient delivery | Use certified + return receipt for ALL MD notices |
| No copy retained in resident file | Cannot prove notice was sent | Always retain copy + proof of mailing |
| Door hanger not photographed | Cannot prove delivery date | Photograph all door-hung notices with date-stamp |
| Electronic-only delivery for legal notices | May not satisfy "written notice" requirement | Always use mail/hand delivery as primary; electronic is supplemental only |

### 17.3 Fair Housing Violations in Language

| Gotcha | Impact | Prevention |
|--------|--------|------------|
| "Great neighborhood for young families" in newsletter | Familial status steering | Review all marketing/newsletter content against prohibited terms (Section 14.3) |
| Different tone in notices to different lots/sections | Disparate treatment claim | Use templates; same language for same notice type |
| Noise complaint letter referencing "your children" | Familial status discrimination | Use neutral language: "noise from your home" |
| Accommodation request handled by email instead of interactive process | FHA violation | Escalate ALL accommodation requests to compliance |
| Referencing resident's nationality when discussing language barrier | National origin discrimination | Focus on communication need, not the person's background |

### 17.4 Collections Communication Errors

| Gotcha | Impact | Prevention |
|--------|--------|------------|
| Discussing debt with resident's family member | FDCPA violation | Only discuss with resident, their attorney, or credit reporting agency |
| Threatening eviction before legal process begins | False representation | Use "further action" not "eviction" until proceedings are filed |
| Contacting resident at work after being told not to | FDCPA violation | Document workplace restriction; flag in resident file |
| Missing validation notice within 5 days of third-party collection | FDCPA violation | Use template with required elements; set calendar reminder |

---

## 18. Output Formats

### 18.1 When Aurora or the Resident Communication Specialist Drafts Communications

**Standard output format for notices:**

```
---
NOTICE METADATA
Type: [Rent Increase / Rule Violation / Maintenance / etc.]
Community: [Name]
State: [XX]
Notice Period Required: [X days per Section 2.1]
Effective Date: [DATE]
Delivery Method: [Per Section 13.1]
Fair Housing Review: [Pass / Flagged items]
---

[FULL NOTICE TEXT]

---
COMPLIANCE CHECKLIST
- [ ] State notice period verified
- [ ] Delivery method matches state requirement
- [ ] Fair Housing language review passed
- [ ] Equal Housing Opportunity statement included
- [ ] Alternative format offer included
- [ ] Contact information complete
- [ ] Dates and amounts verified
- [ ] Copy to be retained with proof of delivery
---
```

### 18.2 Newsletter Draft Format

```
---
NEWSLETTER METADATA
Community: [Name]
Issue: [Month Year]
Distribution: [Print / Email / Both]
Page Count: [X]
---

[NEWSLETTER CONTENT]

---
REVIEW NOTES
- [ ] No individual residents named negatively
- [ ] No Fair Housing risk language
- [ ] Contact information current
- [ ] Dates accurate
- [ ] Content appropriate for all audiences
---
```

### 18.3 Complaint Response Format

```
---
RESPONSE METADATA
Resident: [Name]
Lot: [Number]
Complaint Type: [Category]
Date Received: [DATE]
Response Due: [DATE — within 48 hours standard]
Escalation Required: [Yes/No — if yes, to whom]
---

[RESPONSE TEXT]

---
FOLLOW-UP
- [ ] Response sent by [date/method]
- [ ] Documented in resident file
- [ ] Follow-up scheduled for [date]
- [ ] Root cause addressed (if applicable)
---
```

---

## 19. References

### 19.1 State Statutes Cited

| State | Statute | Topic |
|-------|---------|-------|
| OH | ORC 4781.40, ORC 3733 | Manufactured home park operations, rent increases |
| IN | IC 32-31 | General landlord-tenant relations |
| MD | Real Property Code; MHMA (2023) | MH park sales, rent caps, notification |
| MI | MHCA (Act 96 of 1987) | Mobile home park regulation, rent notice |
| FL | Fla. Stat. 723.031, 723.037 | Mobile home lot tenancies, rent increase notice |
| WV | WV Code 37-6 | General landlord-tenant |
| PA | MHCRA (Act 261 of 1976) | Manufactured home community rights |
| AL | AL Code 35-9A | Uniform Residential Landlord-Tenant Act |
| GA | GA Code 44-7 | Landlord-tenant; rent increase notice |
| AR | AR Code 18-17 | Landlord-tenant |
| MN | MN Stat. 327C (327C.02, 327C.04, 327C.06, 327C.09, 327C.095) | Manufactured home park lot rentals, utilities, rent |
| ND | ND Century Code 47-16 | Landlord-tenant |
| WI | WI Stat. 710.15 | Manufactured/mobile home community regulations |
| MO | RSMo 700.600 | Manufactured homes, notice requirements |
| IL | 765 ILCS 745 | Mobile Home Landlord and Tenant Rights Act |

### 19.2 Federal Laws Cited

| Law | Citation | Relevance |
|-----|----------|-----------|
| Fair Housing Act | 42 U.S.C. 3601-3619 | Protected classes, discrimination, advertising |
| Fair Housing Amendments Act | 1988 | Familial status, disability protections |
| Fair Debt Collection Practices Act | 15 U.S.C. 1692 | Collections communication rules |
| CFPB Regulation F | 12 C.F.R. Part 1006 (eff. Nov 2021) | Modern debt collection rules |
| Title VI, Civil Rights Act | 42 U.S.C. 2000d | LEP access for federally-assisted housing |
| HUD LEP Guidance | 2014 Final Guidance | Language access in housing |

### 19.3 Cross-References to Other Skills

| Skill | When to Use |
|-------|-------------|
| `fair-housing` | Any communication touching protected classes, accommodation requests, advertising, or AI bias review |
| `mhp-regulatory` | State-specific MH park statutes, eviction procedures, rent cap details |
| `mhp-operations-expert` | Utility billing operations, maintenance protocols, POH/TOH management |
| `rm-accounting-expert` | Rent ledger verification, payment posting, late fee calculations |

### 19.4 Related Agents

| Agent | Role |
|-------|------|
| `resident-communication-specialist` | Executes drafting using this skill's framework and templates |
| `compliance-monitor` | Reviews communications for regulatory compliance |
| `financial-auditor` | Validates amounts referenced in financial notices |

---

## Revision History

| Date | Change | Author |
|------|--------|--------|
| March 2026 | Complete rebuild: expanded from 159 lines to expert-grade reference; added 15-state matrix, FDCPA framework, progressive enforcement, AI-safe patterns, decision trees, template library | Aurora |
| January 2026 | Initial version | Aurora |