Availability status is only useful if you know what each state means and how far to trust it. Here's how to read the screen.
The states you'll see
Available: Open for your queried dates per current data. The state you can act on.
Hold (primary): Reserved pending a decision, and you're first in line. See the holds article.
Hold (backup): Someone else holds it and you're next if they release. Holds expire, so backup positions do convert.
Booked: Contracted for the dates queried; unavailable for that window, possibly open before or after.
Unavailable: Not currently offered, whether from an owner pause, a listing gap, or maintenance. Not the same as booked, and sometimes recoverable by request.
Status is date-dependent
Availability is always relative to a date range: the same unit is booked for March and open for May. When a status surprises you, check the dates the view is querying before concluding anything; a large share of "the platform is wrong" moments are date-range moments.
How much to trust the screen
Use status as a strong planning signal: build plans from available units, treat booked as booked. The confirmation step at booking is the ground truth (see the availability accuracy article for the data-freshness mechanics), which means the practical risk of trusting the screen is a revision, never a bad contract. For must-have units, the move is a hold, which converts screen-trust into an actual reservation.
When to ask instead of trusting the UI
Three cases: a unit you need shows unavailable (ask; it may be recoverable), a whole area looks empty (unlisted local supply may exist), or status appears to contradict something a rep told you (the human answer is fresher). Verbal confirmation isn't a workflow failure; it's the right tool for exactly these cases and unnecessary for the rest.