How to Rate the Places You've Been So the Stars Still Mean Something

Open any list of places you have rated over the years and count the stars. For most people the result looks the same: a wall of fours and fives, a handful of threes, and almost nothing below that. A five-point scale where only two points get used is really a two-point scale. It can tell you that you liked somewhere. It cannot tell you which of forty places you liked most, or where you would actually go back.

This matters more for a personal record than for a public review. A review is written for strangers and forgotten. Your own rating is written for you, ten years from now, trying to decide whether to return to Porto or finally try somewhere new. If every entry says "4", that future version of you gets nothing from it.

This guide covers why travel ratings drift upwards, how to build a scale that holds its meaning, and what the rating field in MapMyWorld does and does not do with it.

Why your ratings drift upwards

The drift is not carelessness. It comes from how memory treats experiences, and it has been measured.

Trips improve after you get home. In a 1997 study, psychologist Terence Mitchell and colleagues asked people about three real events, including a trip to Europe and a three-week cycling trip in California, before, during and after each one. Expectations were rosier than the experience itself, and the recollection afterwards was rosier again. The irritations that dominated the trip at the time (delays, rain, sore legs) faded within days. The researchers called it the "rosy view" (Mitchell et al., 1997, via PubMed).

Memory keeps the peak and the ending. Donald Redelmeier and Daniel Kahneman recorded patients' discomfort minute by minute during colonoscopies and lithotripsy, then asked them afterwards how bad the whole procedure had been. The retrospective judgement followed the worst moment and the final few minutes, not the total (Redelmeier and Kahneman, Pain, 1996). The same pattern turns up for pleasant experiences. A dull week in a city that ended with one spectacular dinner is remembered as the dinner.

Length barely registers. In earlier experiments, Barbara Fredrickson and Kahneman found that how long an experience lasted had very little effect on how people rated it afterwards. They named this "duration neglect" (Fredrickson and Kahneman, 1993, via APA PsycNet). Four rainy days and one good one can be rated as if the good day were the whole stay.

Put those three together and any rating you give weeks later is a rating of a slightly idealised memory, not the place.

Why public star averages are the wrong model

It is tempting to borrow the habits of review sites. That imports a second problem.

Nan Hu, Paul Pavlou and Jie Zhang studied product reviews and found that almost every product on Amazon showed a "J-shaped" distribution: a pile of five-star reviews, some one-star reviews, and very little in between. When they ran an experiment in which every participant had to write a review, the shape flattened into something close to a normal curve (Hu, Pavlou and Zhang, Communications of the ACM, 2009). The J-shape came from who chose to write reviews, not from the products themselves. People who felt strongly posted; people who felt "fine" mostly did not.

A personal record has the same weak spot if you only rate the places that moved you. Skip the forgettable ones and your list is made up of highlights, so the average climbs. The fix is simple and slightly boring: rate everything you record, including the places that were merely fine.

Step 1: Decide what a star measures

Most scales collapse because the question behind them keeps changing. On Monday a five means "the food was excellent". On Friday it means "the view made the trip". Neither is wrong, but a scale answering different questions cannot be compared with itself.

Pick one question and use it for every place. Three that work well:

• Would I go back? Forward-looking, and the most useful when you plan the next trip.
• Would I send a friend? Removes your own mood on the day from the answer.
• How good was it for what it is? Lets a roadside café and a cathedral both earn a five without competing.

There is no correct choice. What matters is that you choose one, and choose it before the ratings pile up. It is the same principle as deciding what counts as visiting a country before you start counting: a rule written down once beats a hundred judgement calls made on the fly.

Step 2: Give every star a fixed meaning

A number with no definition drifts. A number with a written definition mostly does not. If your question is "would I go back?", a scale might read:

• 5: I would plan a trip around going back.
• 4: I would go back if I were nearby.
• 3: Glad I went. I would not return.
• 2: Not worth the time it took.
• 1: I would steer someone away.

Notice that 3 is not an insult on this scale. It is the honest answer for most places a traveller passes through, and it should be the most common rating you give. If a 3 feels harsh, that is the review-site habit talking.

Write your scale somewhere you will see it when you rate. One line is enough. The point is that the you of 2031 reads a 4 exactly the way the you of today meant it.

Step 3: Rate on the day, not at the end

Because memory rewrites trips so quickly, the best time to rate is before it has had the chance. The same evening is ideal. The last night of the trip is acceptable. A month later you are rating the rosy version.

This fits naturally with the short daily routine in our guide to logging a trip while you are still on it: a place, a date, a price, and now a number, all while the details are still available.

For trips you are reconstructing from years ago, be honest with yourself. A rating given in 2026 for a 2004 visit is a rating of a memory, and that is fine, but it deserves a note saying so. Our guide to logging travel history retroactively makes the same argument about dates: a known gap is more truthful than a confident guess.

Step 4: Write one line of reason next to the number

A star rating on its own is a conclusion without the evidence. "3" tells you that a place was middling. It does not tell you whether that was the place's fault, the weather, the jet lag, or the argument you had on the way there.

Add one sentence. "3 — beautiful old town, overrun by cruise groups by 10am." "4 — food was the reason to be there, the hotel was not." That line is what lets a later version of you decide whether the rating still applies. Cruise schedules change. Your tolerance for crowds changes. The reason travels well; the bare number does not.

Step 5: Re-rate out loud, never silently

Opinions change. A place that felt ordinary at 25 can turn out to be the one you keep thinking about at 40. When that happens, change the number, but record that you changed it: "Re-rated 2031, 3 to 4: kept coming back to it." Overwriting silently destroys the original judgement, and the original is part of your history too.

Step 6: Check the distribution once a year

Once a year, count how many places sit at each rating. You are looking for one warning sign: if most of your ratings are 5, the scale has collapsed again and a 5 has stopped meaning anything. A healthy personal record usually has a middle heavier than its top. If yours does not, reread your written definitions and ask whether you have been answering the question you set, or a kinder one.

How this works in MapMyWorld

Every place you record has a Rating (1–5) field alongside the date, status and notes, on both the add and edit forms (client/src/components/add-place-dialog.tsx, client/src/components/edit-place-dialog.tsx). The rating is stored as a whole number (shared/schema.ts, places.rating is an integer column), so there are no half stars. If you want finer distinctions, that is a sign your definitions need tightening rather than your scale needing more points.

The notes field on the same form is where the one-line reason and any re-rating history belong. It is free text, so the format is up to you.

Ratings leave the app with the rest of your record. The bulk JSON export, available on every plan including Free, includes every place with its rating and notes. The CSV export, a Pro feature, has a dedicated Rating column next to Visit Date and Notes (server/routes/subscription.ts). If you keep a backup of your travel record, your ratings are in it.

Where it falls short

Some honest limitations, as of September 2026:

• The Places list's "Rating" sort does not sort by rating yet. The option appears in the sort menu, but the server does not implement it, so choosing it falls back to the default most-recent order (server/storage.ts, getPlacesPaginated). Until that is fixed, the export is the reliable way to see your places ranked: open the CSV or JSON in a spreadsheet and sort there.
• Ratings are not shown on place cards or the map. You see a rating when you open the edit form and in exports, not at a glance.
• Ratings are per place only. There is no rating for a trip or a country as a whole. If you want one, write it in the trip's notes.
• The per-trip PDF export does not include ratings (client/src/components/export-trip-modal.tsx).
• Free accounts have five places, and that is a lifetime allowance: deleting a place does not free the slot. A rating scale needs enough entries to be worth calibrating, so it earns its keep over a long record rather than a short one.

None of this changes the method. The scale lives in your head and your notes, not in the software. The app just keeps the numbers from getting lost.

What you get back

A rating system with fixed meanings, applied to everything and written on the day, gives you something review sites never can: a ranking of places by your own standard, stable enough to compare 2019 with 2029. When you are choosing between two cities for a long weekend, the answer is already in your record, with the reason next to it, written by the only reviewer whose taste exactly matches yours.

Start with the one-line scale. Everything else follows from that.