Skills on AI

Active theme: Light

Property Management

Use when asked about the ongoing operational management of a rental property or portfolio on behalf of an owner — rent collection, maintenance, tenant communication, inspections — distinct from a [[lease-agreement]], which is the contract with one tenant, where this is the ongoing operational practice across the property's lifecycle and possibly multiple units and tenants.

Property management is the ongoing operational work of running a rental property or portfolio on behalf of an owner, across the whole lifecycle of ownership rather than any single tenancy. Where a Lease Agreement sets the terms with one tenant, property management is everything that happens around and between leases — collecting rent, handling maintenance, communicating with tenants, and keeping the property in good condition — often across many units and tenants over time.

Key components

  • Rent collection and arrears handling — a defined process for how rent is collected, what happens the moment a payment is late, and a consistent escalation path (reminder, late fee, formal notice) rather than an ad hoc response that varies tenant to tenant.
  • Maintenance request process with a realistic response-time expectation — a clear way for tenants to submit requests, and a stated target for how quickly each priority level (emergency, urgent, routine) gets acknowledged and resolved.
  • Tenant communication and turnover process between leases — how tenants are kept informed during the tenancy, and a standard sequence for what happens between one tenant moving out and the next moving in: notice, move-out inspection, repairs, re-listing, and move-in.
  • Routine property inspections — scheduled checks of the property's condition during the tenancy, not only at move-in and move-out, catching maintenance issues before they become expensive.
  • Financial reporting to the owner — income, expenses, and outstanding issues reported to the owner on a regular cadence they can actually act on.

Why a defined maintenance response process matters for tenant retention

Slow or unclear handling of maintenance requests is consistently one of the most common tenant complaints, and a real driver of tenants choosing not to renew. A tenant who doesn't know whether a "someone will look at it" request means tomorrow or next month has no way to plan around it, and experiences the delay as being ignored even if work is actually in progress. A stated response-time target, tracked and met, does two things at once: it gives tenants a concrete expectation instead of uncertainty, and it gives management a way to measure its own performance instead of relying on impressions.

Common pitfalls

  • Maintenance requests with no tracked response-time expectation — tenants have no idea what to expect, and management has no way to measure or improve its own responsiveness without a target to compare against.
  • Turnover handled reactively with no standard process — each vacancy is worked out from scratch instead of following a repeatable sequence, so units sit empty longer than necessary and repairs get missed or duplicated.
  • Inconsistent records of condition and repair history — without a documented baseline and repair log per unit, a later dispute over damage, a deposit, or a maintenance failure has nothing agreed to point to.
  • No escalation path for arrears — inconsistent, personality-driven responses to late rent instead of a process applied the same way every time.
  • Owner reporting that's irregular or after the fact — an owner who only hears about a problem once it's already serious has lost the chance to weigh in earlier.

Learn more

  • Lease Agreement for the contract with an individual tenant that property management operates around and enforces.
  • Home Inspection Checklist for the same inspection discipline applied at move-in, move-out, or during a routine property check.
  • Moving Checklist for the tenant-side counterpart to the turnover process managed from the property side.

View property-management/SKILL.md on GitHub