AI Skill Report Card

Polishing Property Management Emails

A-87·Oct 20, 2026·Source: Web
14 / 15

Take the forwarded draft and rewrite it following this priority order:

  1. Fix spelling/grammar errors
  2. Simplify sentence structure (short sentences, common words)
  3. Ensure tone is polite but firm (no apologetic hedging, no aggressive language)
  4. Keep it short — cut anything not essential to the message
  5. Return the corrected email ready to send

No need to ask clarifying questions — make reasonable judgment calls and flag any assumptions briefly if needed.

Recommendation▾
Add a third example showing a bad output (e.g., over-softened or overly aggressive) contrasted with the corrected version to reinforce pitfalls
14 / 15

Progress:

  • Read draft fully; identify recipient type (supplier vs. tenant) and purpose (request, complaint, reminder, notice, confirmation)
  • Correct spelling, grammar, and punctuation
  • Simplify vocabulary and sentence length for non-native readers
  • Adjust tone: remove excessive softening ("maybe", "I was wondering if") AND remove harshness/rudeness
  • Ensure firmness: clear deadline, clear action requested, no ambiguity
  • Check structure: greeting → context (1-2 sentences) → request/action → closing with next step → sign-off
  • Trim to shortest version that keeps all necessary information
  • Output final email only (unless asked for explanation of changes)
Recommendation▾
Include an edge case example, such as an already well-written draft needing minimal changes, to show calibration
16 / 20

Example 1: Input: "Hi, i wanted to ask if maybe you could possibly come and fix the heating in apartment 4B sometime soon because the tenant has been complaining a lot and its getting kind of urgent now. Let me know when you can. Thanks"

Output: "Dear [Name],

The heating in apartment 4B is not working and needs urgent repair. Please schedule a visit within the next two business days.

Kindly confirm a date and time by tomorrow.

Thank you for your prompt attention to this matter.

Best regards, [Your Name]"

Example 2: Input: "Dear Mr. Keller, unfortunately I have to inform you that your rent payment for last month has still not arrived on our account, this is now the second time this has happen and we would appreciate if you could transfer the ammount as soon as possible to avoid further steps. Best, [Name]"

Output: "Dear Mr. Keller,

Your rent payment for last month has not yet been received. This is the second late payment.

Please transfer the amount by [date]. If payment is not received, we will have to take further action.

Thank you for your understanding.

Best regards, [Your Name]"

Recommendation▾
Consider a brief note on handling ambiguous recipient type (supplier vs tenant) when it's unclear from the draft
  • Use short sentences (max ~15–20 words). One idea per sentence.
  • Prefer simple, common words over formal/complex vocabulary (e.g., "fix" not "rectify", "send" not "dispatch").
  • State the action or deadline explicitly and near the top or in its own sentence — never bury it.
  • Use neutral, factual phrasing instead of emotional language ("is not working" instead of "is completely broken and awful").
  • Always close with a clear next step (confirmation needed, deadline, consequence if relevant).
  • Keep standard structure: greeting, 1–2 sentence context, clear request/action, polite closing line, sign-off.
  • For tenants: firm but respectful, especially on payment/behavior issues — state facts, state required action, state consequence if applicable, no blame language.
  • For suppliers: firm on timelines and quality expectations, professional and transaction-focused.
  • Preserve all factual details from the original (dates, amounts, apartment numbers, names) — never alter content, only clarity and tone.
  • Don't add excessive politeness that weakens firmness ("I was just wondering", "sorry to bother you", "if that's okay with you").
  • Don't use idioms, phrasal verbs, or culturally specific expressions that confuse non-native speakers ("get the ball rolling", "down the line").
  • Don't make emails longer while "improving" them — cut, don't pad.
  • Don't soften deadlines into vague terms ("soon", "when possible") — always push for a specific date/timeframe if one is missing, or flag it.
  • Don't change the factual content or add assumptions not in the original draft.
  • Don't make tenant emails sound threatening — firm ≠ aggressive; state consequences factually, not as a threat.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
14/15
Examples
16/20
Completeness
14/20
Format
15/15
Conciseness
14/15