Skip to content
Back to Resources
ClaudeProperty ManagementBeginnerGuide

Claude CoWork for Property Managers

A practical guide to using Claude as your AI co-worker in your property management workflow — from setup to daily use.

Claude CoWork for Property Managers

What is Claude CoWork?

Claude CoWork is the practice of using Claude as a persistent, knowledgeable co-worker embedded in your daily property management workflow. This is not about asking a chatbot to write a generic tenant letter. It is about configuring Claude with your portfolio context and communication standards so that every interaction produces output you can use with boards, tenants, and vendors.

Claude-native prompts. The prompts in this guide use Claude's native XML tag structure (<context>, <instructions>, <avoid>) for more precise, consistent output. These tags help Claude parse your intent with less ambiguity.

Think of Claude as the most reliable assistant manager on your team, one who drafts board reports, composes tenant notices, and prepares budget narratives without dropping a detail. This guide covers setup, the five highest-impact workflows, and the prompting techniques that separate generic output from professional-grade content.

Install the Property Manager Plugin

This guide works on three Claude surfaces. The plugin is the fastest path on two of them. Pick whichever you use:

If you're on Cowork (desktop or mobile app)

Claude Cowork is Anthropic's agentic workspace — Claude completes work autonomously and returns finished deliverables. The Property Manager plugin packages the workflows below as native skills and slash commands.

  1. Open the Cowork plugin directory in your desktop app.
  2. Filter by Cowork, search for "Property Manager", and click Install.
  3. The plugin's slash commands and ambient skills are now available in any Cowork task.

If you don't see the plugin in the directory yet, install via custom marketplace: paste https://github.com/alexclowe/awesome-claude-cowork-plugins in your Cowork plugin settings.

If you're on Claude Code (CLI)

Install from your terminal:

claude plugin add alexclowe/awesome-claude-cowork-plugins/property-manager

The plugin's slash commands and skills load on next session.

If you're on Claude.ai (web chat only)

Plugins aren't directly installable on the web chat surface. You have two options:

  1. Use the prompts in this guide directly in a Claude Project (covered in the next section). Same outputs, more typing.
  2. Upload the plugin's skills as a zip via Settings → Features → Custom Skills (Pro/Max/Team/Enterprise plans). Higher friction; only worth it if you want the auto-activating skills, not the slash commands.

What the plugin gives you (any surface)

Slash command What it does
/tenant-notice Draft violation notices, lease renewals, move-in/out letters, and tenant correspondence
/board-report Generate board meeting minutes and management reports with financial summaries
/vendor-email Create vendor outreach emails, bid requests, and service coordination messages
/budget-narrative Write budget presentations and financial summaries for board review

Auto-activating skills (no command needed — Claude applies them when relevant):

  • Property Management — Fair housing compliance, lease administration, HOA governance, maintenance coordination, and tenant relations
  • Board Communication — Professional board reporting, financial presentation, compliance documentation, and stakeholder updates

The plugin works standalone for one-off tasks. Pair it with the surface-specific setup below for persistent context across every task — that combination is the full Claude CoWork setup.

Setting Up Claude for Property Management Work

Surface note: The Project setup below is for claude.ai web users. Cowork users have their own task-context mechanism (set context once when starting a Cowork task). Claude Code users get the plugin's ambient skills automatically — no Project setup needed. The workflows themselves are surface-agnostic — paste the prompts wherever you're working. The key to getting consistently useful output is using Claude Projects. A Project lets you set custom instructions that persist across every conversation.

Step 1: Create a Property Management Project. In Claude, click "Projects" and create one called something like "My PM Desk."

Step 2: Set your custom instructions. In the Project settings, add:

You are my property management assistant. Here is my context:

<business-profile>
- Name: [Your Name], [Your Company]
- Portfolio: [X properties, Y total units — residential / commercial / HOA]
- Markets: [City/Region(s)]
- Management software: [AppFolio / Buildium / Yardi / etc.]
- Communication tone: [Professional and measured / Firm but fair / Approachable]
- State: [Your State] (for landlord-tenant law references)
</business-profile>

<rules>
- All tenant communications must comply with Fair Housing guidelines.
- When referencing landlord-tenant law, note the jurisdiction and recommend verifying with legal counsel.
- Never provide legal advice. Frame legal references as general information.
- Board reports must be factual, data-driven, and transparent about positives and negatives.
</rules>

Step 3: Upload reference documents. Add your standard notice templates, board report formats, vendor agreement outlines, and property-specific procedures to the Project knowledge base.

Step 4: Start every session inside this Project.

Your Top 5 Workflows with Claude

1. Board Reports

Board meetings require clear, data-driven reports. Claude turns raw numbers into polished narratives the board can act on.

<task>Draft a monthly board report for this HOA property.</task>

<context>
- Property: Riverview Commons, 96-unit condo association, February 2026
- Financial: operating budget 94% on track, reserves $842K (target $900K YE), special assessments 87% collected
- Maintenance: parking lot resealed ($18.5K, under budget), elevator Phase 1 on schedule, 14 work orders closed (2.1-day avg)
- Issues: 2 units 90+ days delinquent (liens filed), noise complaints Building B (3 incidents, same unit)
- Upcoming: pool prep March 15, insurance renewal April (8-12% increase expected)
</context>

<instructions>
- Sections: Financial Summary, Maintenance & Capital Projects, Compliance, Upcoming Items
- Lead each section with the key takeaway, frame insurance increase as prep item
- Include recommended action items at the end
</instructions>

<avoid>Naming owners (unit numbers only), editorializing on complaints, burying bad news.</avoid>

Before Claude: 60-90 minutes compiling and drafting. After Claude: 10 minutes to input data, 10 minutes to review.

2. Tenant Notices

Notices need to be clear, compliant, and appropriately toned.

<task>Draft a lease violation notice for a noise complaint.</task>

<context>
- Property: Riverview Commons, Unit 214
- Violation: excessive noise after quiet hours (10 PM-8 AM), documented Feb 12, 19, 26
- Lease clause: Section 8.3 — Quiet Enjoyment (repeated violations may result in non-renewal)
- This is the first formal written notice
</context>

<instructions>
- Reference specific lease clause and documented dates
- State expected behavior, outline consequences if violations continue
- Include a path to resolution (contact management to discuss)
- Firm but respectful, maintain the relationship, one page
</instructions>

<avoid>Threats beyond lease terms, characterizing behavior, naming complainants, legal interpretations of eviction.</avoid>

Before Claude: 20-30 minutes drafting a compliant notice. After Claude: 3 minutes to describe the situation, 5 minutes to review.

3. Vendor Emails

Vendor relationships are built on clear communication. Claude drafts emails that set expectations and negotiate terms.

<task>Draft an email to a landscaping vendor requesting a revised proposal.</task>

<context>
- Vendor: GreenScape Landscaping, 3-year relationship, generally good performance
- Current: $3,200/month basic grounds maintenance
- Their renewal: $4,100/month (28% increase, citing labor costs)
- Our position: comparable bids at $3,400 and $3,600, open to moderate increase
- Goal: negotiate to $3,500-$3,700 or get enhanced scope for higher price
</context>

<instructions>
- Acknowledge relationship and service quality
- State the increase exceeds budget, reference competitive bids without naming vendors
- Ask for revised proposal (lower price or additional services), 10-day deadline
- Professional, firm, not apologetic
</instructions>

<avoid>Naming competitors or their pricing, threatening termination in first ask.</avoid>

Before Claude: 15-20 minutes drafting a tactful negotiation email. After Claude: 3 minutes to outline, 3 minutes to review.

4. Budget Narratives

Numbers tell the story, but narratives explain it for boards and homeowners.

<task>Write a budget narrative for the upcoming fiscal year.</task>

<context>
- Property: Riverview Commons, 96 units, FY July 2026 - June 2027
- Proposed: $1,248,000 (up 6.2% from $1,175,000)
- Key drivers: insurance $142K to $162K (+14%), utilities $186K to $198K (+6.5%), landscaping $38.4K to $42K (+9.4%), reserves $180K to $200K (per study)
- Savings: renegotiated elevator contract saving $8,400/year
- Assessment impact: +$18/unit/month ($295 to $313)
</context>

<instructions>
- 400-500 words explaining the budget to homeowners
- Lead with overall picture before line items
- Explain increases with context (market conditions, not management choices)
- Highlight elevator savings as proactive cost management
- Frame assessment in monthly terms, close with financial health statement
</instructions>

<avoid>Financial jargon, apologizing for increases, comparing to other associations, promising no future increases.</avoid>

Before Claude: 45-60 minutes writing a narrative that pre-empts questions. After Claude: 5 minutes to compile numbers, 10 minutes to review.

5. Maintenance Documentation

Clear records protect the property and the management company.

<task>Write a maintenance incident report for a water damage event.</task>

<context>
- Property: Riverview Commons, Unit 312 (affected), Unit 412 (source), Feb 24, 2026
- Cause: failed supply line under Unit 412 sink, water shut off 8:30 AM
- Damage: Unit 312 ceiling drywall (4x6 ft), wet insulation; Unit 412 minor vanity damage
- Response: plumber 8:15 AM ($450), extraction team 10:00 AM (estimate pending), dehumidifiers
- Insurance: claim #RC-2026-0042; Unit 412 repaired same day, 312 drywall scheduled March 3
</context>

<instructions>
- Formal report: Incident Summary, Timeline, Damage, Response, Vendor Costs, Insurance, Next Steps
- Clear timeline from report to resolution, objective factual tone
</instructions>

<avoid>Assigning blame, speculating beyond confirmed causes, including tenant personal info.</avoid>

Before Claude: 30-40 minutes writing a thorough incident report. After Claude: 5 minutes to document facts, 5 minutes to verify.

Prompt Engineering Tips for Property Managers

1. Always specify the audience. "Write for the board" produces different output than "write for tenants." Tell Claude who reads it.

2. Include the jurisdiction. Landlord-tenant law varies by state. Always mention your state and city in prompts involving notices or compliance.

3. Set the tone explicitly. Specify "firm but respectful" or "transparent and reassuring" depending on the context.

4. Provide your templates. Upload standard notice formats and board report templates. Claude matches your formats.

5. Use unit numbers, not names. Protect privacy by using unit numbers when describing tenant situations.

6. Draft talking points for difficult conversations. Before rent increases or violation conversations, ask Claude to prepare talking points.

Privacy & Compliance

Fair Housing compliance is non-negotiable. All tenant communications and marketing must comply with federal, state, and local Fair Housing laws. Never generate content that discriminates based on any protected class.

Verify landlord-tenant law references. Claude cannot verify current law in your jurisdiction. Confirm notice periods, required language, and procedures with legal counsel before issuing formal notices.

No legal advice. Claude is a drafting tool, not an attorney. Formal notices and eviction communications should be reviewed by qualified counsel.

Tenant and owner data privacy. Do not paste Social Security numbers, bank accounts, or financial records. Use summaries: "Unit 214, 90+ days delinquent, $2,400 balance" rather than uploading ledger screenshots.

Going Further

Ready to build on this foundation? Check out these resources:


Get weekly AI prompts for Property Management professionals

Join professionals already saving hours every week. Free. No spam.