Every median on this site is quoted before tax, and that is deliberate. A pre-tax figure is the only version that can be lined up fairly against another neighbourhood, because it strips out a layer that shifts with the calendar, the room type and the booking channel. The cost is honest confusion at checkout, when the number you settle is larger than the number you planned around. This piece explains what the exclusion means in practice, why the site holds to it anyway, and how to compare two neighbourhoods without letting tax quietly scramble the ranking.
Why every figure here is pre-tax
A neighbourhood median is a comparison tool, not a quotation. The moment you fold tax into it, you are no longer comparing Midtown with Downtown; you are comparing one set of dates with another, because the amount added on top moves with the season, the event calendar and the length of the stay. Strip it out and the same $142 sits beside the same $118 no matter when you read the page. That stability is the whole point. The figure answers which neighbourhood costs more before the extras, and that question has a durable answer in a way the final bill does not.
The medians here exist so you can rank places rather than shop for rooms. West End at $98 and College Park at $94 are close enough that tax could reorder them on a given night, and the site would rather show you the gap clearly than bury it. Once a tax-inclusive number enters the table, the ranking becomes a snapshot of one booking window and stops being useful the following month. A pre-tax median is the version that survives the calendar, and it is the version the site can defend without guessing at rates it has no business inventing.
Keeping the figure pre-tax also keeps the site out of territory it cannot verify. Tax treatment depends on jurisdiction, property classification, length of stay and the channel you book through, so a single all-in number would be a claim about a specific transaction the site never sees. The pre-tax median is a statement about the neighbourhood relative to its neighbours, which is checkable and stable. Anything beyond that belongs on the venue's own page or the relevant authority's schedule, where it can be read against your actual dates rather than borrowed from an average.
Think of the medians as the fixed part of a moving total. The pre-tax number tells you what the neighbourhood costs before the add-ons; everything else is a function of when you go and how you book, and that is where the variation lives. Using the stable part for comparison and the variable part for budgeting keeps the two jobs separate. If the site printed an all-in figure, it would be blending a neighbourhood characteristic with a booking characteristic, and the resulting number would be accurate for almost nobody while looking authoritative to everyone.
How to read a quoted rate
What the pre-tax figure leaves out
The pre-tax figure tells you the neighbourhood, not the total. What gets added on top depends on where the property sits, how it is classified and which authority collects what, and none of that is knowable from a neighbourhood median. The site does not print a rate because a rate printed here would be wrong for most readers and stale for the rest. Read the applicable rate on the venue's own page or on the schedule published by the relevant authority, and read it against your specific dates rather than a general season. That is the only place it is current for you.
Tax is not the only omission. Resort or amenity fees, parking, cleaning charges on short lets and per-night levies all sit outside the median as well, and some of them are quoted separately even on the property's own booking page. A pre-tax neighbourhood figure cannot tell you which of these apply to the room you are considering, because those are property-level facts and the site ranks neighbourhoods, never properties. Budget upward from the median and treat every additional line as something to confirm directly with whoever is taking the booking.
The pre-tax approach also assumes you know roughly what proportion of the total the add-ons represent, and that assumption fails for cheap rooms. The lower the base rate, the larger the share that fixed per-night charges and fees take, so a $94 median in College Park can end up proportionally further from its final figure than a $158 median near Piedmont Park. That does not make the cheaper neighbourhood the wrong choice, but it does mean the gap between two medians in the nineties is less meaningful at checkout than the same gap higher up the table.
What the piece cannot do is resolve your particular booking. It cannot tell you whether your dates fall under a special event assessment, whether your property classification changes the treatment, or whether a platform bundles charges differently from booking direct. It cannot tell you the total. What it can do is give you a defensible ranking of neighbourhoods on the part of the cost that does not move, and a clear instruction to attach the variable part yourself from a source that knows your dates. Anything more specific would be invented, and the site does not invent figures.
How to compare two neighbourhoods
Compare like with like. Take two medians from the list, hold them side by side as pre-tax numbers, and resist the urge to mentally add a guessed percentage to each before deciding. That addition is not neutral: it tends to compress the differences and make mid-table neighbourhoods look closer than they are. Downtown at $118 against Midtown at $142 is a real gap in the pre-tax comparison, and it stays a real gap as long as you are comparing the same way on both sides. Add tax to only one column and you have compared nothing.
Do the comparison one pair at a time, not across the whole table at once. Pick the two neighbourhoods you are genuinely choosing between, check that both medians are pre-tax, and decide on that basis. If the neighbourhood you prefer loses on the pre-tax figure by a margin you care about, that is useful information. If it wins, you have learned something the all-in number would have hidden behind a rate that may not even apply to your booking. Repeat with the next pair only after you have settled the first question.
Once the neighbourhood is chosen, switch jobs entirely and build the budget upward from the median. Read the applicable rate at the venue or the authority, then add anything else the property lists, and arrive at your own total for your own dates. Keep that total in a separate column from the medians. The ranking and the budgeting answer different questions, and mixing them produces a number that is neither a fair comparison nor an accurate forecast. The medians stay clean; your total is yours.
Re-check the variable part close to your dates, because rates and fees change and event calendars shift demand. The ranking is unlikely to move much between now and then, since it rests on the stable part of the cost. The total certainly will. If you are choosing between West End and College Park, the pre-tax gap is small enough that a single additional per-night charge could decide it, so confirm the property-level costs before you commit rather than after. The medians tell you where to look; the checkout page tells you what you will pay.
This piece is compiled from the venue's or the operator's published information and the site's own neighbourhood checks rather than from a visit. Prices, hours and anything that moves week to week are not printed here: read the applicable rate at the venue or the relevant authority for your dates. One thing that cannot be measured from a desk is how a specific booking engine bundles its charges, which only appears at the final step. Nothing on this page is paid placement.
Read the method ↗
