CentriWebAn interactive estate map should do four things well: show lot availability that is current to the hour, give buyers the lot details they actually compare, send every enquiry to the right agent with the lot number attached, and give agents and builders one place to see current pricing. Before you look at designs or 3D flyovers, ask any vendor or developer exactly how each of those works and who keeps it up to date.
This guide is a requirements checklist for land developers and their sales teams. It doesn’t recommend a product. It sets out what to ask for, what usually goes wrong, and the questions that separate a map that sells lots from one that just looks good in the launch presentation. To keep it concrete, we’ll use a fictional estate, Banksia Ridge, releasing its third stage.
What an estate map is for
A buyer looking at an estate wants to know three things: what’s left, what it costs, and whether it suits them. The map’s job is to answer those questions faster than a phone call, then make it easy to ask for the next step.
For the developer, the map has two more jobs. It should become the single source of truth for availability, so the sales office, agents and builders aren’t working from different spreadsheets. And it should turn interest into enquiries you can track back to a specific lot.
A flattened masterplan image with coloured dots isn’t an interactive map, even if you can zoom it. If changing a lot from available to sold means emailing a designer to edit a file, the map will be out of date within a week of launch.
Live availability: who updates it and how
Stale availability is the fastest way to lose trust. A buyer who enquires about a lot that sold a fortnight ago tends to assume the rest of the map is wrong too. So the first question isn’t how the map looks. It’s who changes a lot’s status, from where, and how long it takes to show.
Agree your statuses before anything is built. A typical set looks like this:
| Status | What the public sees | Who can change it |
|---|---|---|
| Available | Lot details, price or “price on request”, enquiry button | Sales manager |
| On hold | Shown as held, still clickable for details | Sales manager or nominated agent, with an expiry date |
| Deposit taken | Shown as unavailable or under offer | Sales manager |
| Sold | Shown as sold, no enquiry button | Sales manager or admin |
| Future release | Greyed out with an expected release stage | Admin |
Ask the vendor:
- Can a sales manager change a status from a phone in under a minute, without a developer?
- Do holds expire automatically, with a reminder to the agent who placed them?
- Is there a log of who changed what and when?
- Can a status change in your CRM or sales system update the map, so nobody updates two places?
- What happens when a new stage is released: who loads the lots, and from what file?
At Banksia Ridge, the sales manager marks Lot 312 as deposit taken while standing in the sales office. Within a minute the public map, the agent view and the builder view all show it. That’s the standard to hold any product to.
Lot detail that buyers actually use
When someone taps a lot, they’re comparing it with two or three others. Give them the details that matter for that comparison, in the same order every time:
- Lot number, stage and street
- Area, frontage and depth
- Orientation, or at least which way the rear faces
- Price, price range or status (more on this in the FAQ)
- Expected titling timeframe
- Known constraints such as easements, fall across the block or a building envelope
- A downloadable lot plan and the estate design guidelines
- House and land packages linked to the lot, if you sell them
Filters help more than people expect. Buyers often arrive with a minimum frontage in mind because their preferred home design needs it. Letting them filter by frontage, area or price range saves them clicking through every lot.
Don’t leave anyone out
Maps are easy to get wrong on accessibility. The Web Content Accessibility Guidelines (WCAG) are the international standard here, and three points apply directly. WCAG says colour shouldn’t be the only way information is shown, so pair coloured lots with a label, pattern or legend text. It says all functionality should be available from a keyboard, so a buyer should be able to move between lots without a mouse. And it asks for text alternatives for non-text content, which for a map usually means offering the same lots as a plain list or table. That list view is also handy for buyers on small screens.
Enquiries tagged by lot, sent to the right agent
An enquiry that says “interested in your estate” is far less useful than one that says “Lot 312, Stage 3, wants a call after 5pm”. When the enquiry form opens from a lot, the lot number, stage and price shown at the time should travel with it automatically. The buyer shouldn’t have to type it.
Then decide where it goes. Common routing rules:
- By stage or precinct, where different agents look after different releases
- By roster, so weekend enquiries go to whoever is on
- To a builder, when the enquiry is about a specific house and land package
- To the sales manager, when the lot is on hold or the enquiry is about multiple lots
Every enquiry should land in your CRM as a contact with the lot, the source and the time attached, and the agent should be notified straight away. That gives you the record you need later: which lots attract interest, which agents respond quickly, and which enquiries became contracts. If your CRM can’t do this yet, sort that out first. A good map feeding a messy inbox doesn’t fix much. Our CRM setup work usually starts with exactly this routing.
Agent and builder access to current pricing
Most estates have more people selling than the developer’s own staff. External agents and builders with packages on the estate all need current availability and pricing, and the usual answer is a price list emailed as a PDF. By Wednesday it’s out of date, and someone quotes a sold lot to a buyer.
A logged-in view fixes most of this. Ask for:
- Separate logins for each agent and builder, not one shared password
- Different views for different roles, so builders see what they need for packages and agents see pricing and holds
- The ability for an agent to request a hold, with the sales manager approving it
- For builders, a way to submit or update house and land packages against a lot, so packages don’t go stale
- Removing access in one click when an agent or builder stops working on the estate
This is where a map turns into a portal, and the build-or-buy question gets more serious. Our guide to client portals: build or buy covers the trade-offs in more detail.
Mobile, speed and search
Mobile
Plenty of buyers look at estates on their phone, often in the evening after a drive past the site. Test the map on a mid-range phone, not just the agency’s desktop. Can you tap a single small lot without hitting its neighbour? Does the lot panel cover the whole map or sit underneath it? Is the list view easy to reach?
Speed
Large masterplan images and heavy 3D models slow a page down, especially on mobile data. Ask how the map loads: as one huge image, or in pieces as you zoom. Ask to see it on a slow connection.
Search
Many maps are built with JavaScript, and that raises a fair question about Google. According to Google’s JavaScript SEO guidance, Google can render JavaScript, but it can only discover links that are standard <a> elements with an href attribute, and it can only index content that appears in the rendered page. Google also recommends using the History API rather than # fragments for in-page routing, and says server-side or pre-rendering is still a good idea for speed. Its guidance on crawlable links lists links built only with onclick handlers as not recommended.
In practice, ask that each stage, and ideally each lot or a lot list per stage, has its own normal page with a proper URL, title and description, linked with ordinary links. The interactive map then sits on top of pages Google can read.
Buy a product or build your own: questions to ask
There are off-the-shelf estate map products, and there are custom builds. Neither is right for everyone. A product is often quicker to launch for a single estate. A custom build makes more sense when you run several estates, need the map tied closely to your own sales system, or want the agent and builder portal to work your way.
Whichever way you lean, ask these questions:
- Who owns the lot data and the enquiries, and can we export all of it at any time?
- What does it cost per estate, per stage and per year, and what happens to the map if we stop paying?
- How does it connect to our CRM, and who maintains that connection?
- How long does it take to load a new stage, and who does it?
- Can we see a live estate using it, on a phone, today?
- What accessibility testing has been done against WCAG?
- Do stage and lot pages exist as normal crawlable pages?
If the answers point towards a build, our page on custom software and portals explains how we approach projects like this.
Where to start
- Write down your lot statuses and who is allowed to change each one.
- List the lot details buyers ask about most often in the sales office.
- Map out where an enquiry should go for each stage, and check your CRM can receive it with the lot attached.
- Decide what agents and builders need to see, and what they shouldn’t.
- Take the question list above to every vendor or developer you speak with, and ask for a test enquiry.
A good estate map is less about the graphics and more about the plumbing behind it: accurate availability, clean enquiries and one version of the truth for everyone selling. If you’re planning a new release, our property page shows how we connect maps, portals and CRM for land sales teams.