How we score destinations

What goes into the V0 score

One input. Every neighbourhood on a destination's intel card carries a safetyRating on a 1–5 scale, set by the contributor who wrote the card. The destination score is the simple average of those ratings.

destination_score = avg(neighborhoods[].safetyRating)
                  // 1–5 scale, no transformation

For Goa today: neighbourhoods are Assagao (5/5), Anjuna/Vagator (3/5), Palolem (4/5). Avg = 4.0. The same number renders on every Goa trip report, every time the page loads.

When we hide the score

A score from one or two neighbourhoods is misleading. So:

• •Fewer than 3 rated neighbourhoods: we render “Not enough data yet” instead of a number.
• •No intel card for the destination at all: same — no number.
• •The “Show only safe destinations” filter on /feed hides destinations below the threshold rather than silently treating them as safe.

What this score is not

• •Not a verdict.A 4.2 doesn't mean “safe” in the absolute. Read the scams list, the Don't list, and recent beware reports for the real picture.
• •Not a 0–10 score.The earlier “Solo 8.4/10”-style numbers were a placeholder hash on the trip ID, not real data — they shifted across cards for the same destination. Removed.
• •Not weighted by beware reports yet.They're shown separately on the Beware Board. V1 brings them into the score; see below.
• •Not user-rated.Only contributors who wrote the intel card set neighbourhood ratings. Members can't change the number; they can flag a stale card via Feedback.

What V1 will add

The V0 number is intentionally narrow. As the dataset grows, the score moves to a documented composite formula:

v1_score =
    0.55 × neighbourhood_rating_avg          // 1–5 scale
  + 0.30 × (5 − beware_severity_index)        // recent + severity-weighted
  + 0.15 × verified_contributor_bonus         // capped at 5
                                              // → 1.0–5.0 displayed

• •Beware reports: severity (critical / high / medium) and recency (rolling 12 months) feed in. A surge of critical reports drops the score the same week.
• •Verified contributors: a small bonus (capped) for destinations vouched for by multiple contributors who have actually been there.
• •Per-destination, computed once: stored on intel_cards.safety_score and re-computed atomically when a beware report is approved. Same number everywhere it's shown.
• •Methodology stays here. Any change to the formula gets a dated changelog entry on this page.

Spot something off?

Numbers that don't match your lived experience are the most useful feedback we can get. Email trust@wanderwomen.in with the destination, the score you saw, and what you think it should be — we'll re-check the inputs and either correct the card or write back with what we're seeing.