Operations / Property Mgmt
Operations / Property Mgmt Track
Draft resident communications that are clear and compliant, triage your day, and look up any procedure in seconds — with Fair Housing rails on every step.
Property Managers
Regional VPs
Community Managers
Ops Leadership
You're on this track if
- You manage a community or a region day to day
- You write resident notices, handle complaints, and triage maintenance
- You re-look-up the same procedures and policies constantly
- You want AI help on comms — but resident-facing means compliance comes first
Your path through the 4 Levels
Everyone follows the same spine. Here's what each level means for community and regional operations.
L1
Better Conversations
Read the AUP, learn to prompt for reasoning instead of answers.
For you: learn the Fair Housing reflex first — what you can and can't ask AI to write for or about a resident.L2
Your Workspace
Set up your Claude Teams project and "interview your AI" so it knows your context.
For you: load your community's details and the resident-comms rules once, so every draft comes back on-policy instead of generic.L3
Run the Workflows
Use the sanctioned Workflow Skills and tools — your daily rhythm, on rails.
For you: Scanned Mail Routing plus Sunny AI for staff procedure lookup — answers without a call to Carlos.L4
Build New Workflows
Spot the next repetitive task and co-build a new skill for it.
For you: a make-ready checklist skill, a maintenance-triage skill — your repeating daily patterns are Level 4 candidates.Your Skills
Yours = a workflow you own. Start here = the one you read before anything resident-facing. Expert = knowledge you summon by topic. All in the Skills Catalog.
Protected classes, disparate impact, reasonable accommodation, ESAs, advertising compliance, AI in housing. The rail under every resident interaction — read this first.
Categorizes scanned-mail PDFs, redacts PII, routes urgent items as tasks, files the rest, sends the daily report.
Rent-increase notices, newsletters, complaint responses, maintenance notices, rule-violation letters, emergency notices.
Utility expenses, infrastructure, occupancy/fill rates, capex, deferred maintenance, make-ready, turnover, septic.
State rent-increase notice periods, eviction procedures, security deposits, utility-billing rules, tenant protections.
IVR menus, call queues, after-hours routing, voicemail, number porting, multi-site setup for your community phones.
For managers handling staff: Stratustime time tracking, PTO accrual, new hire / termination, multi-state tax basics.
Prompts to try in your voice
Start here, then make them yours. Every resident-facing draft gets a human read before it sends.
"Draft a notice to residents that water will be shut off Tuesday 9am–noon for a main repair. Clear, calm, no jargon, and don't reference any individual resident."
A maintenance notice you can post in minutes — that you still read before it goes out.
"A resident emailed this complaint about a neighbor's dog. Draft an empathetic reply that takes it seriously, explains our process, and promises nothing specific."
Acknowledges the concern without committing you to an outcome you can't guarantee.
"I have 14 open maintenance requests. Group them by urgency — safety and habitability first — and tell me which to dispatch today."
Triages your day so the water heater beats the squeaky gate.
"What's the rent-increase notice period for a manufactured-home lot in Ohio? Point me to the statute so I can confirm it."
Fast procedure lookup — then confirm it against the MHP Regulatory skill or counsel before you act on it.
What NOT to do (Ops / PM edition)
- Fair Housing is the line you do not cross. Never ask AI to screen, approve, deny, or score a resident or applicant (AUP §2.2). Never segment residents by protected class — race, color, religion, national origin, sex, familial status, or disability — or by proxies like income source, age, or neighborhood. If a draft drifts there, stop and call Carlos.
- Nothing resident-facing goes out unread. AI drafts; a human sends. Read every resident communication for tone and compliance before it leaves your hands.
- Don't draft eviction or rule-violation decisions with AI. AI can explain the process; the decision and the formal notice route through the proper channel, not a chatbot.
- Strip resident PII you don't need. Don't paste full names, unit-level payment history, or medical / accommodation details into a chat that doesn't require them.
- Sunny AI is for staff procedure lookup — not resident-facing yet. Use it to find a policy or process; don't point a resident at it.
Your first 30 days
A realistic ramp. You don't have to do it all in week one.
Week 1
Read the AUP and do Personal AI Setup. 30 minutes total. Then use Claude on five real ops tasks — a notice draft, a complaint reply, a policy lookup.
Week 2
Set up your Claude Teams workspace. Load your community details and the resident-comms rules so drafts come back on-policy. Skim the Fair Housing skill before you draft anything for a resident.
Week 3
Shadow the tools. Watch Scanned Mail Routing run, and try Sunny AI for a few procedure lookups so you learn what it knows.
Week 4
Draft a real resident notice solo — then route it through human review before it sends. That's the habit that keeps AI on the right side of the Fair Housing line.
Note for review: The prompt examples and 30-day ramp on this page are a first draft authored from how community and regional ops already run. PMs / RVPs (Cobi's team) should gut-check the specifics during the cohort walkthrough before this is treated as final.