Skip to main content

Best practices

Real Estate Best Practices (EN)

Operational guidelines for real estate agents, AI application developers for the real estate sector, and real estate professionals.

> Disclaimer: This content is for informational purposes only. For legal or tax decisions, consult licensed professionals. Sources: Italian Revenue Agency, Banca d'Italia, RICS (2024).

---

BP-01: Always verify cadastral and urban planning compliance before the deed

Before proceeding to the deed, mandatorily verify: (1) correspondence between the cadastral floor plan and the actual state of the property, (2) presence and validity of building permits (permesso di costruire, SCIA, regularization grant), (3) absence of unsanated building violations. The notary performs these verifications, but agent and buyer must explicitly request them. A non-compliant property cannot be validly sold.

BP-02: Always register the preliminary contract in the Property Registers

Registration of the preliminary contract protects the buyer from mortgages, foreclosures, and multiple sales occurring after signing the preliminary but before the deed. The cost is minimal compared to the risk avoided. For properties under construction, registration is legally mandatory (Legislative Decree 122/2005).

BP-03: Include clear suspensive conditions in the preliminary contract

If the purchase is contingent on obtaining a mortgage, include an explicit suspensive condition in the preliminary contract with a deadline. Without this clause, a buyer who fails to secure a mortgage would forfeit their deposit. The condition must specify: mortgage amount, deadline for obtaining it, consequences if not obtained.

BP-04: Always request a mortgage survey before purchase

The mortgage survey (issued by the Italian Revenue Agency) reveals mortgage registrations on the property, foreclosures, and adverse registrations. It is one of the key due diligence documents. The notary checks it before the deed, but agents and buyers can request it at any time.

BP-05: Photograph and document the actual state at the time of the preliminary contract

Attaching an inspection report with photographs of the property's state (floors, fixtures, systems, etc.) to the preliminary contract protects both parties from disputes at the time of the deed. Explicitly describe any discrepancies, damage, or works to be carried out.

BP-06: Use cadastral data as the source of truth for software integrations

In real estate software applications, the cadastral code (municipality, sheet, parcel, sub-unit) is the unique identifier of a property. Use it as the primary key in integrations with the Italian Revenue Agency, valuation systems, and listing platforms. Do not use the postal address as a key (ambiguous, not normalized).

BP-07: Model property states as explicit state machines in applications

In property management applications, use an explicit state machine for the property lifecycle: available → negotiation → preliminary contract → deed → sold / free → rented. Avoid multiple boolean flags (isForSale, isRented, isSold) that create inconsistent states. State transitions must be validated at domain level.

BP-08: Separate cadastral information from commercial data in the data model

In the data model, separate: (1) Property entity with stable cadastral data (parcel, category, income), (2) Listing entity with volatile market data (asking price, description, photos), (3) Contract entity with negotiation data (agreed price, conditions). This separation reflects domain reality and facilitates maintenance.

BP-09: Store monetary values as integers in cents in applications

All monetary values (prices, rents, deposits, commissions) must be stored as integers in cents to avoid floating-point rounding errors. Example: €350,000 = 35,000,000 cents. Apply the rule throughout the entire chain: storage, API, calculations, exports.

BP-10: Include a tax disclaimer in every section with fiscal content

Any fiscal data (IMU rates, flat-rate rental tax, capital gains, cadastral income, registration taxes) must be accompanied by: (1) disclaimer "informational purposes only - consult a licensed professional", (2) institutional source (Italian Revenue Agency, specific law), (3) reference year. Never publish fiscal rates without this information.

BP-11: Validate geographic coordinates and OMI data in integrations with the Italian Revenue Agency

OMI valuations (Real Estate Market Observatory) are available for homogeneous zones identified by geographic coordinates and zone codes. In integrations, validate that: (1) coordinates fall within the correct OMI zone, (2) min/max values by type and condition are updated (new OMI campaign every 6 months). Source: https://www.agenziaentrate.gov.it

BP-12: Document the provenance of valuation data in automated appraisals

In automated valuation model (AVM) applications, document for each estimate: (1) calculation method (comparative, income, cost), (2) sample of comparable transactions (number, dates, distance), (3) OMI sources used, (4) confidence interval, (5) disclaimer that the estimate does not replace a professional appraisal. Essential for compliance with banking regulations (Banca d'Italia, EBA).