---
id: KB-CS-034
url: https://app.codecontract.io/help/use-cases-by-sector/property-management-and-communities
idioma: en
categoria: casos-por-sector
subcategoria: inmobiliario
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CS-011, KB-CN-003, KB-CS-036]
citadoPor: [KB-LE-017]
---

# Property management and communities

_Many communities, many suppliers, and owners who want to see things._

**Responde a:** property management documentation · managing agent paperwork · community meeting minutes and resolutions · community suppliers insurance

A managing agent runs dozens of communities at once, each with its suppliers, minutes, mandatory inspections and owners asking questions. It is the same work repeated many times, with the particularity that each community is a separate client and cannot see the others' material.

## What accumulates per community

| Block | What it includes | Who asks for it |
| --- | --- | --- |
| Minutes and resolutions | Meetings, votes, approved levies | Owners, and sometimes a court |
| Suppliers | Maintenance, cleaning, lifts, insurance | The community itself and insurers |
| Mandatory inspections | Lifts, fire systems, water safety, building surveys | Inspectors and insurers |
| Incidents | Breakdowns, claims, works | Owners and loss adjusters |

> [!IMPORTANT]
> The third block creates liability for the agent. A lapsed mandatory inspection in a community you manage is your problem as well as theirs, and warnings with margin are the only realistic way to control it across twenty communities.

## What solves the most

1. **One file per community, genuinely separated** — Each is a client: one cannot see another's.
2. **Due dates per community with an owner** — Lifts, insurance, inspections. That is where the risk sits.
3. **Supplier documentation requested and renewed automatically** — Insurance and certificates, once a year with automatic chasing.
4. **And what owners may consult, accessible** — It cuts calls and emails more than anything else.

> [!WARNING]
> Watch the minutes: they are the document most requested years later and the worst preserved, because they circulate on paper and by email. Minutes signed and kept in the community's file are found in seconds; hunting for them in a six-year-old archive is not.

## When the agent changes

**En corto**

- The documentation belongs to the community, not to you.
- An orderly handover to the next agent is both an obligation and a calling card.
- And being able to export the complete file avoids the argument about what was handed over.

That last point is also a commercial argument: arriving at a new community and finding an ordered, exportable archive says a lot about the previous agent, for better or worse.

> [!NOTE]
> The pattern is identical to a consultancy running compliance for several clients: many identical files, separated, each with its own calendar and a portion visible to the client.

**Can owners see everything?**

Whatever the community decides; usually their own and common material, not third-party data.

**What about levies and payments?**

Those live in your management system; documentation and its evidence live here.

**Does it suit a single large community?**

Yes, though the biggest saving appears with many.

## Ejemplos

**An agent manages twenty-two communities and tracks inspections in a spreadsheet.**

- Builds a file per community with due dates and owners
- Requests supplier documentation annually with automatic renewal

→ Stops discovering lapsed inspections when the inspector or the claim arrives.

**A property manager handles forty communities and an owner asks to see their building's lift contract.**

- Organises one file per community
- Gives read access to what belongs to each
- Records what was shared and with whom

→ The owner sees theirs without anyone stopping to hunt for it, and without reaching other communities.

**A supplier works across several communities and their documentation is requested four times.**

- Keeps their file once and links it to each community

→ The supplier delivers once and it serves all.

**An insurance policy expires in one community and nobody notices.**

- Records expiries per community

→ The warning arrives before the meeting.

**A meeting is called and documentation is missing.**

- Checks what is missing in advance

→ The meeting happens with everything on the table.

**An owner asks you to evidence a cost from two years ago.**

- Checks that community's file

→ You answer without searching cabinets.

**The chair changes and the context is lost.**

- Keeps the file independent of individuals

→ The handover does not restart the work.

**Information from another community is shared with an owner.**

- Checks the scope before sharing

→ Information does not cross.