Selections data goes in and nothing comes out
Nearly every residential construction platform has a selections module. Almost nobody uses it.
The reason is not that entering selections is hard. It is that entering them produces nothing. A builder who fills out a selections tab completely still texts the installer a photo of the spec sheet. Still forwards a vendor link. Still assembles the closeout package at the end of the job from purchase orders and memory. The record exists and it changes nothing about how the job runs, so on the next job it does not get filled in at all.
Reviews of the major platforms describe the same experience in different words. The selections section is called unfriendly. Users report entering the same item twice, once as an allowance and once as a selection, because the two lists do not talk to each other. One firm built its reputation on selections management and has now shut down, with its customers being migrated elsewhere.
What gets entered
Most selections tools are built on open text fields. Somebody types a product name, a manufacturer, and sometimes a model number.
Free text has a predictable outcome. The same manufacturer appears three ways across one project. Finishes get typed into the product name, or left out. Model numbers get transcribed with a digit wrong. Nothing in the system objects, because nothing in the system knows what a valid entry looks like.
By the middle of the job the list is internally inconsistent. Not wrong exactly, but not something anybody would order from without checking it against the original quote. So it gets checked against the original quote, which means the original quote is still the real record and the system is a copy of it.
An architecture firm publishing its own selections worksheet noted that most of the delays and issues it sees come from miscommunication about selections and from selections not reaching the builder on time. That is a description of a record that is not doing its job.
What does not come out
The two moments in a job where a specification record would be worth something are the day something gets installed and the day the client takes the house.
On the day something gets installed, the person doing the work needs the model number, the finish, the quantity, the room, and the install sheet. Not the whole project. Just the items belonging to that trade, on one document, correct.
At handover, the client needs every product in the house with its model, finish, warranty, manual, and care instructions. That document is what a homeowner opens two years later when a faucet cartridge fails.
Neither of those comes out of a selections tab, and the reason is what went in.
A document for one trade requires knowing which items belong to that trade. A closeout package requires every item grouped by category, with its finish separated from its name and its manual attached. Neither can be assembled from a column of free text, because free text cannot be sorted, filtered, or grouped by anything.
Three spellings of the same manufacturer are three manufacturers to a computer. A finish typed into the end of a product name is not a finish, it is more product name. A model number with a transposed digit is a different product entirely, and nothing catches it, because nothing was ever checking.
So the data goes in unstructured, and the only thing that can come back out is the same unstructured list. Which is why the only output most selections tools offer is a printed version of what was typed.
The entry format decides what the record can produce. A record entered as loose text can be read by somebody who already knows what it means. It cannot be assembled into anything.
Prephase Residential was built around this. The selections spec sheet is free to download and use in a spreadsheet. The packets it produces are here.