👉 Book a free 30-minute Bitrix24 demo

Ask three people in a brokerage what “the listing is live” means and you may get three answers. The agent thinks it means the ad is on Property Finder. The listing coordinator thinks it means the permit is attached and the record is approved. The manager thinks it means it is on every portal you pay for. When a team does not share the same vocabulary, CRM-to-portal workflows break in small, expensive ways.

This glossary explains the terms UAE brokerages run into when they list properties from a CRM to Property Finder, Bayut and Dubizzle. Use it to onboard new agents, to brief an integration partner, or simply to settle arguments about who owns what. Where a term is a portal or government feature, we describe it in general terms; always check the current rules with the portal or regulator.

Core CRM listing terms

Master property record

The single record in your CRM that holds the truth about a unit: location, size, bedrooms, price, status, media, permit details and the responsible agent. Every portal ad should be generated from this record, not typed separately. If you only adopt one idea from this glossary, make it this one.

Listing reference number

Your internal ID for a listing. Keep it identical in the CRM, in portal ads and in lead records, so an enquiry can be traced back to the exact unit without guesswork.

Field mapping

The agreed translation between your CRM fields and each portal's fields. “Community”, “sub-community”, “property type” and “completion status” may be named or structured differently on each portal. A field mapping document stops surprises when an integration goes live.

Listing status

The operational state of a unit in the CRM, for example Draft, Approved, Published, Reserved, Sold or Leased, and Withdrawn. Good status rules decide what is pushed to portals and what is removed. Our earlier post on keeping listings synced across Property Finder, Bayut and Dubizzle covers how status changes should flow outward.

Publish, unpublish and archive

Publish sends the listing to a portal. Unpublish takes it offline but keeps the record. Archive retires the record in your CRM once the unit is no longer marketable. Teams that confuse these three often end up with ghost ads or with lost history.

Listing feed or integration

The technical connection that carries listing data from your CRM to a portal. Depending on the portal and your setup, this may be a feed, an API connection or a connector app. The method matters less than the rules around it: what triggers an update, who sees errors, and how failures are fixed.

Sync error log

The record of listings that failed to publish or update, usually because a required field was missing or invalid. Someone must own this log. An unread error log is how a unit stays at last month's price for weeks.

Compliance terms in Dubai

Trakheesi permit

Trakheesi is the Dubai Land Department (DLD) system for real estate licences, permits and broker cards. In Dubai, property advertisements need a valid advertising permit issued through Trakheesi, and portals such as Property Finder, Bayut and dubizzle ask for the permit number before a Dubai listing goes live. Store the permit number and its expiry date as fields on the master record so nothing is published without them.

Form A

The marketing agreement between a property owner and a broker for a resale unit in Dubai. Trakheesi uses the Form A details when a broker applies for a permit for a ready property for sale. Your CRM should record whether a valid Form A exists before a sale listing can move to Approved.

NOC (No Objection Certificate)

A letter from the owner (or developer, depending on the case) giving permission to market a property. Leasing listings commonly rely on an owner NOC. Treat it like Form A: a document attached to the record, with a date you can check.

Other emirates have their own regulators and rules, so if you list outside Dubai, add the relevant permit fields for each emirate rather than forcing everything into one Dubai-shaped field.

Want these terms built into your CRM as real fields and rules? Book a free 30-minute Bitrix24 demo and we will walk through a listing workflow with you.

Portal quality and trust terms

Quality score

Both Property Finder and Bayut give listings a quality score that reflects how complete and well presented the content is, such as description, location details and photos. Higher-quality listings tend to rank better in each portal's results. Each portal publishes its own guidance, so check it directly and build the important items into your CRM's mandatory fields.

Location tree

Property Finder's structured location hierarchy, from emirate down to building or community level. An incomplete location means a listing can miss searches that filter by area. Map your CRM location fields to it carefully.

Verified (Property Finder)

A badge Property Finder shows on listings whose documents have been checked by its quality team. Verification relies on documents such as the title deed or Form A, so a CRM that already stores those documents makes the request much easier.

Checked and TruCheck (Bayut)

Bayut's Checked badge appears once a listing's documents are validated. TruCheck goes further: an agent visits the property and uploads on-site photos through Bayut's Profolio app to confirm it is still available. Bayut describes Profolio as the listing management system for Bayut and dubizzle.

Duplicate listing

The same unit advertised more than once on the same portal, often by different agents in the same office. Portals generally discourage it and buyers find it confusing. A master record with a single listing owner is the simplest prevention.

Lead-side terms

Lead source tag

The value on a CRM lead that records which portal, campaign or channel produced the enquiry. Without it, you cannot compare portal performance. Our guide to capturing Property Finder, Bayut and Dubizzle leads in Bitrix24 explains how to bring those enquiries in cleanly.

Listing agent vs responsible person

The listing agent is the person named on the portal ad. The responsible person is whoever owns the lead or deal in the CRM. They are often the same, but not always, for example when a call centre qualifies enquiries first. Decide the rule up front so routing does not fight your ads.

Inventory-to-lead match

Linking an incoming enquiry to the master property record it came from. This is what lets a manager answer “which units are generating enquiries but no viewings?” and is the bridge between listing work and sales work.

How to use this glossary in your team

Add it to your onboarding pack for new agents and listing coordinators.
Turn the compliance terms into mandatory CRM fields with expiry dates.
Make listing status values match the terms above exactly, so reports read the same way for everyone.
Name one owner for the sync error log and one owner for listing quality.
Review the glossary when a portal changes its rules or badges.

If you are still deciding how publishing should work end to end, start with our overview of publishing listings from CRM to Property Finder, Bayut and Dubizzle, then come back here to agree the language.

Where Closerholic fits

Closerholic implements Bitrix24 CRM and portal listing integrations for UAE real estate teams. We help you design the master property record, map fields to each portal, add permit and document checks, and connect listing activity to the leads it produces. Shared words come first; reliable automation follows.