Ventelistevalg: a dated decision about a housing waiting list

Which list is worth joining?

A home seeker encounters a fee, an open-list notice, an old association page and a signup provider. They need to know which facts still hold before spending money.

Ventelistevalg puts that decision in front of the directory. The product distinguishes saving a list to a plan from actually joining it. A source check stays attached to the status, and an unknown fee remains unknown.

A decision with a date and a source

On the A/B Carla profile, the public interface shows when the open status was last checked and lets the reader open the association's source. It warns that the status may have changed. An annual fee that has not been confirmed is labelled as such.

The screenshot on the homepage was captured from this live profile. Its date is the product's source-check date, not a claim that I verified the association today.

The choices have different consequences:

• Save keeps a list in the reader's plan.
• Join opens the external provider, where the reader checks the current conditions.
• Already joined records something the reader has already done.
• Skip excludes a list from their current consideration.

None of these choices promises a home or estimates a chance of receiving one.

What I chose not to build

No "join every list" button.

The Kort tab is address context beside the list. The main task is deciding what to do with a particular list. A button that joined every list would hide different eligibility rules, fees and unknowns behind one action.

Before / after / why: naming the decision

Before: AndelsPlan - a housing map that refuses to invent a queue.

After: Ventelistevalg: a dated decision about a housing waiting list.

Why: A map describes a surface. A dated decision describes what a home seeker can do with the facts. The earlier heading is preserved in the previous case version.

My work and the evidence boundary

I set the product direction, data methodology and interaction decisions, and worked on implementation. The public site supports the choices described here. No paying users yet. This case makes no claim about housing outcomes, queue success or willingness to pay.

The next question is whether people managing several lists can explain a decision using the source, date, fee and unknowns the interface shows. That needs observation of real decisions, not another feature in the catalogue.