What a Unit Selector Shows That a List Cannot

Most developments could publish their availability as a table. Unit number, bedrooms, area, floor, price, status. It would be accurate, cheap, easy to maintain and considerably faster to build than any selector.

Many should. The question worth asking before commissioning a selector is what the spatial version adds that the table does not, because the answer varies enormously by building and by buyer, and for some developments the honest answer is very little.

This guide sets out what a selector genuinely adds, where a list is better, and how to tell which situation you are in.

What a list does well

Worth starting here, because lists are underrated in a category that sells interfaces.

Filtering and sorting. A table sorted by price, filtered to two bedrooms, is the fastest possible way to narrow a large inventory. Selectors frequently make this harder rather than easier.

Scanning. Twenty units in a table can be absorbed in seconds. Twenty units distributed across a building diagram cannot.

Comparison of numbers. Area against price against floor is a numerical comparison and tables were invented for it.

Maintenance. A list is a spreadsheet with styling. It is close to impossible to break and trivial to update.

Accessibility and portability. Screen readers handle tables. So do printers, email clients and every device ever made.

What a selector adds

Four things, and they are all spatial.

Position within the building

Which floor, which side, corner or interior, near the lift core or at the end of a corridor. A table can state floor and unit number and cannot convey position, because position is a relationship rather than a value.

For buildings where position matters, and it usually does, this is the primary contribution.

Aspect and view

Which direction a unit faces and what it looks at. Expressible in a table as a word, and far more legible when a buyer can see the building oriented in its context and understand that this side faces the park and that side faces the road.

Relationships between units

What is above, below and beside. Buyers care about being next to a lift, over a loading bay, below a roof terrace. None of that is visible in a list and all of it is visible in a stacked diagram.

Understanding what remains

The pattern of availability across a building tells a buyer something a count cannot. Whether the good floors have gone, whether one line is selling faster, whether the remaining inventory is concentrated in a less desirable stack.

That is information buyers use and developers are sometimes ambivalent about showing, which is a commercial decision rather than a design one.

When each format wins

The comparison problem, which both handle badly

Worth naming because it is the task buyers actually perform and almost nothing supports it.

A buyer with a shortlist of two or three units wants to hold them side by side: layouts, areas, aspects, prices, floors. A table lets them see the numbers but not the plans. A selector lets them see one unit at a time and requires them to remember the other.

Very few implementations offer explicit comparison, and it is the clearest available improvement in the category. A compare view holding two or three units with their plans, key figures and aspects visible together does the thing buyers are trying to do rather than making them do it from memory.

This applies equally to lists and selectors, which is why the best answer for many developments is both: a filterable list for narrowing and a spatial view for understanding, with a comparison view connecting them.

What buyers actually ask that neither format answers

Useful to know, because it defines the boundary of what a selector can do and where the sales team still has to be.

What is the light like? Aspect gets you part way and nothing shows how a room feels at four in the afternoon in December.

How noisy is it? Proximity to a road or a lift shaft is inferable from position and the actual experience is not.

What will the view be after the next building goes up? A genuine question in dense markets and one selectors almost never address.

Is this a good price? Relative value judgement, which requires context the tool does not have.

What is included? Specification, appliances, parking, storage. Frequently varies by unit and frequently absent from both formats.

That last one is worth fixing, because it is answerable and it is the question most likely to send a buyer to a phone call.

Designing for the actual sequence

Buyers move through a predictable sequence and tools that mirror it perform better than tools organised around the building.

Narrow. Price, bedrooms, availability. Filtering, which lists do best.

Understand. Where is it, what does it face, what is around it. Spatial, which selectors do best.

Compare. Two or three against each other. Which neither does well.

Commit. Enquire, book a viewing, reserve. Which most tools treat as an afterthought at exactly the moment interest peaks.

A tool that supports all four beats one that does the second beautifully and the others not at all, which describes a lot of expensively produced selectors.

The honest recommendation

For a large inventory of comparable units, particularly in leasing, publish a good list. It will outperform a selector, cost a fraction and never break.

For a building where floor, aspect and position drive substantial price differences, build the selector, because the price differences are otherwise unexplained and the sales team explains them manually to every buyer.

For most developments of any scale, do both, connected: filter in the list, understand in the selector, compare across a small shortlist, and make the next step obvious at the point a buyer has decided.

And in every case, make sure the availability underneath is true, because a beautifully designed selector showing units that sold last month is worse than a plain table that is right.

One boundary worth stating

Neither format sells units. Selectors and lists support a sales process, they do not obtain approvals and no vendor obtains approvals or can guarantee them, and they do not replace a sales team.

What they do is let a buyer answer their own questions at the moment they are engaged. Which format does that best depends on which questions your buyers are actually asking, and that is worth establishing before commissioning either.

Building type changes the answer substantially

The list versus selector question resolves differently depending on what is being sold, and the pattern is fairly consistent.

Tall residential towers

The strongest case for a selector. Height is the product, view varies enormously by floor and aspect, and the price difference between floor eight and floor twenty eight in the same line is entirely spatial.

A list showing those two units side by side makes them look like the same apartment at different prices, which is exactly the impression to avoid.

Low rise and garden apartments

Weaker case. Fewer floors, less view variation, and units differentiated mainly by layout and aspect. A list with a good plan library frequently serves better.

Mixed use with commercial below

Selector, because the vertical relationship matters. Residents care what is beneath them, and a buyer on the second floor above a restaurant has a legitimate question a list will not surface.

Single family and townhouse developments

Neither, usually. This is a site plan problem rather than a unit selector problem, since the relevant variables are position on the site rather than position in a building.

Student and co-living

List, almost always. High unit counts, minimal variation, fast turnover, and buyers optimising on price and availability date rather than on aspect.

The specification question, which is worth solving

Of everything neither format handles well, specification is the one most worth fixing because it is entirely answerable and it drives a large share of enquiries.

Buyers want to know what is actually included in the unit they are looking at: appliance package, flooring, whether the balcony is included in the stated area, parking allocation, storage, whether the finish tier varies by floor.

That information exists, it varies by unit or type in most developments, and it is frequently absent from both the list and the selector, which sends the buyer to a phone call at the exact moment they were ready to enquire.

Adding it costs almost nothing during a build and considerably more as a retrofit, because it touches every unit view.

A note on how buyers arrive

Worth knowing because it affects which format they encounter first.

Many buyers reach a development through a listing portal, which shows a specific unit rather than the building. They arrive on the developer site already interested in one apartment and wanting to see it in context.

That argues for a selector that can be deep linked to a unit, opening on the relevant apartment with the building around it rather than at a generic overview requiring the buyer to find their way back to what they came for.

Lists handle this trivially. Selectors frequently do not, and it is a small technical requirement with a disproportionate effect on whether a portal referral converts into an enquiry.

What to show about availability

A question that looks technical and is commercial, and it applies to both formats.

Showing everything, including sold. The most informative and the most revealing. A buyer sees the pattern: which lines went first, which floors remain, how far the building has progressed. Confident developments do this and it builds urgency honestly.

Showing only available. Cleaner and less informative. It removes the urgency signal and it also removes the impression of a building that is not selling, which is why struggling schemes prefer it.

Showing counts rather than units. Six two bedrooms remaining, without saying which. Preserves negotiating position and frustrates buyers trying to picture a specific home.

There is no universally correct answer and there is a wrong process, which is inheriting the default from a tool rather than deciding deliberately. The choice says something to every buyer who visits and it should say what you intend.

A practical test before commissioning either

Take your current availability information, in whatever form it exists, and give it to somebody outside the project with a realistic brief: find a two bedroom under a threshold, facing away from the main road, available before a date.

If they can answer from a spreadsheet in two minutes, a well presented list will serve your buyers and a selector is discretionary.

If they cannot answer because position and aspect are not in the data, that is the gap a selector fills, and it also tells you what the selector has to carry.

And if they cannot answer because nobody is sure what is available, neither format is the next purchase.

That test takes ten minutes, requires nothing from a vendor, and answers the commissioning question more reliably than any demo, because it uses your actual data and a realistic buyer question rather than a curated sample building designed to make an interface look good.

Frequently asked questions

Is a unit selector always better than a list?

No. For large inventories of comparable units, particularly in leasing, a filterable list outperforms a selector, costs a fraction and never breaks. Selectors win when floor, aspect and position drive substantial price differences.

What does a selector show that a table cannot?

Position within the building, aspect and what a unit faces, relationships to units above and beside, and the pattern of what remains. Those are relationships rather than values, which is what tables cannot express.

What do both formats handle badly?

Comparison. Buyers shortlist two or three units and want them side by side with plans, areas, aspects and prices visible together. Almost no implementation supports that, and it is the clearest available improvement in the category.

What questions can neither format answer?

Light quality through the day, noise, what the view becomes after neighbouring development, and whether a price is good. Specification and what is included is also frequently missing, and unlike the others that one is answerable.

Should a development have both?

For most developments of any scale, yes. Filter in the list, understand in the selector, compare across a shortlist, and make the next step obvious at the point of peak interest.