Same point analysis — comparing from the same point

In lesson 17 (Reading the booking pace) we opened the idea of the same-point. Now we go deeper: why raw YoY comparison misleads, how to align the “same point” precisely, and why the precision is critical.

Same point analysis looks simple from the outside (“let’s see what it was this time last year”), but the devil is in the details. A badly-aligned same-point comparison does more harm than good — it reassures you where you should worry, and panics you where calm is warranted.

The goal of this lesson is to learn the method of aligning the same-point precisely, and to recognize the traps of false same-point comparisons.

The trap of raw YoY (year-over-year)

The classic, beginner-level comparison is YoY (year-over-year) — “what’s occupancy on this day this year, and what was it last year.”

Hotel Peaqplus City’s November 25 (Saturday) YoY comparison:

A beginner RM panics immediately: a −16 pp shortfall is serious! But before we act, let’s think about what exactly we’re comparing:

• This year, November 25 is 7 days before check-in (today is November 18).
• Last year, November 25 had already happened — the 78% was the final value measured on the check-in day.

The two numbers stand on radically different time horizons! Last year the whole pickup curve had played out; this year there are still 7 days of pickup to come. The comparison is logically broken.

What the same-point is exactly

The same-point says: compare the two years at the same position. Not “the same calendar date,” but “the same number of days before check-in.”

Hotel Peaqplus City November 25 — same-point comparison:

Now the picture flips. The YoY −16 pp shortfall is actually a +4 pp same-point lead. Last year’s Saturday closed at 78% — but 7 days out it stood at only 58%. This year we’re at 62% 7 days out, so if the pace continues we could close at around 82-83% — above last year’s level.

The same point here isn’t a date but a position on the pace curve — where we stand at the same booking-window moment.

The three “same point” definitions

Same point analysis isn’t a single formula — three classic definitions exist:

1. Days-out (days before check-in)

The most common. The “same point” = the same number of days before check-in. If today we’re 7 days before November 25, the last-year same-point is last year’s November 18 state for the November 25 occupancy level (7 days out).

Days-out is the most widely-used definition across industries. The Peaqplus Same Point module uses it by default.

2. Days-of-week aligned

A refinement: not just “7 days out,” but “the same weekly position.” If today we’re 7 days before November 25 (Saturday), the last-year same-point is a last-year Saturday that was also measured 7 days out and was also a Saturday check-in.

Why does it matter? Because a Saturday’s and a Thursday’s pickup curve differ. A Saturday 7 days out stands at ~58% on average; a Thursday at 45%. If we also align the weekly position, we get a finer picture.

3. Comparable date (calendar-adjusting)

The finest. Here not only days-out and the weekly position are aligned, but the holidays, the events, and the within-season position too. If last year November 25 was Black Friday weekend, and this year it’s already the Saturday before Advent, the two dates aren’t directly comparable.

Comparable-date says: find the last-year date that best matches your within-season position. This year’s November 25 might compare better to last year’s November 18, because both are the Saturday after Black Friday.

Only mature organizations use this definition, and it requires manual calibration. The Peaqplus Insight Engine (lesson 52) flags in certain contexts when a days-out same-point comparison isn’t comparable-date — e.g. when there was an event in one year and not the other.

The two-season, two-year trap

The same-point is at its finest when the two years’ seasonal patterns are similar. But sometimes they differ dramatically — and then the same-point gives a falsely good or falsely bad picture.

A few classic traps:

Trap 1: An event in one year, not the other

If last year November 25 was a concert week (event-driven pace) and this year there’s no event, the same-point will naturally fall short. That’s not an RM problem — it’s a structural cause. The negative same-point number misleads here.

Trap 2: Calendar shift

Holidays and school breaks shift their calendar position year to year. Last year Easter was April 9, this year April 1. If you compare “the same date,” you’re comparing two completely different seasons. The same-point is only valid here if the season position is also accounted for (the comparable-date definition).

Trap 3: A COVID year as the baseline

The 2020 and 2021 data are anomalies for most hotels. Using them as a same-point baseline is misleading. A mature organization also looks back to pre-COVID 2019 data for context, or uses a 2-3 year average.

Trap 4: A new compset member in the market

If a new hotel opened in your area this year, it lowers your own pace (cannibalization). The same-point shortfall is then a market cause, not an RM error.

The same-point is a tool, not a definitive answer. Always read it in context.

Same-point as a forecast input

One of the same-point’s most important uses is raising forecast accuracy. If you know that:

• Today we’re 7 days before November 25 and stand at 62%.
• Last year 7 days out we stood at 58%.
• Last year the final occupancy was 78%.

Then a simple proportional extrapolation: this year 62 / 58 = 1.069 (6.9% higher pace). Applied to last year’s 78% close: 78 × 1.069 = ~83% expected final.

This is a simplified model, of course — it doesn’t assume the pace shape changes. In lessons 19 (Forecasting basics) and 20 (Simple forecast methods) we go deeper into how a mature forecast system uses the same-point.

How Daniel uses the same-point

An average Monday’s Daniel pace-analysis with the Peaqplus Same Point module:

1. Opens the pickup board — every date carries a “Last-year same-point” column.
2. Peaqplus aligns the basis automatically: days-out + days-of-week aligned. No need to look up by hand “what date was 7 days out last year.”
3. Reads the red / amber / green coding — the same-point flags significant (>5 pp) shortfalls.
4. Goes deeper on the flagged dates — segment-level same-point, historical pace curve.
5. Checks the comparable-date context manually — “was there an event that day last year? is there a calendar shift? was the same-point baseline a COVID year?” — this is where the RM’s own expertise comes in.

The Peaqplus Same Point module automates the first 3 steps and eases steps 4 and 5 by making the context data (events, calendar shift) available on the surface. The module’s key capabilities:

• Days-out and weekly-aligned automatic matching — no manual lookup.
• 2-3 years of historical same-point — not just last year, but two and three years ago too.
• Event-context flag — whether there was an event that day, and what kind.
• Segment-level same-point — not just total, but by segment.
• Pace-curve overlay — the same-point curves side by side, visually.

The same-point and budget relationship

The same-point and the budget together give a stronger diagnostic grid, in two dimensions:

The Peaqplus Pickup module shows this combined grid, and it’s the primary surface of the weekly revenue meeting (covered in detail in lesson 28).

Key takeaways

• Raw YoY comparison misleads — we’re measuring on two different time horizons (this year’s live value vs. last year’s final).
• The same-point says: compare the two years at the same pace position — not the calendar date, but the booking-window moment.
• The same-point’s three definitions: days-out (days before check-in), days-of-week aligned (the weekly position aligned too), comparable-date (the season and events aligned too).
• The same-point is a tool, not a definitive answer — read it in context (events, calendar shift, COVID anomalies, new compset members).
• The same-point is one foundation of forecast accuracy — a proportional extrapolation from last year’s pace curve.