The revenue analyst's first 90 days: a week-by-week plan

You got the offer. Now the clock that matters is the credibility clock: in your first 90 days the GM, the DOS and your revenue manager are quietly deciding whether your numbers can be trusted and whether your voice belongs in the daily meeting. Both are earned in a specific order. Here's the plan.

Weeks 1โ€“2: learn the machine before touching it

Resist the urge to produce. Your only deliverable is a map: which systems hold which truth (PMS for reservations and history, RMS for recommendations, S&C for group blocks, the benchmarking report for the comp set), how the segments are defined at this hotel โ€” every property carves transient/corporate/group/contract differently โ€” and where every number in the morning report actually comes from. Shadow the daily revenue meeting silently and write down each decision made and the reasoning offered. Learn the comp set as it stands and keep any opinions about it to yourself โ€” you don't yet know why those hotels were chosen, and week-one criticism of an inherited set is a classic credibility burn (more on that below). Ask every "dumb" question now; the license to ask expires quickly.

Weeks 3โ€“4: own the pickup report

Take over producing the morning pickup report โ€” the daily record of what every future date gained or lost overnight. Before you distribute your first one, tie it out against the source systems yourself; the fastest way to lose trust is a report whose total doesn't match the PMS. Owning this report is strategically perfect: it forces you through the numbers every morning, it makes you useful immediately, and it hands you the raw material for your first insight. Share one small, verified observation in your second week of ownership โ€” "the Tuesday after the fair is picking up double its usual pace" โ€” offered as an observation, not a recommendation.

Month 2: own a segment, run your first analysis

Ask to own one segment of the forecast โ€” transient is the natural first, since the pickup report already lives in your head. Forecast it, track your misses, and say your miss out loud before anyone else finds it; self-reported variance builds more trust than accuracy does. When the first group displacement question crosses the desk, volunteer to run the numbers even if the revenue manager makes the call. Aim for a rhythm of one presented insight per week โ€” small, verified, and ideally ending in a proposed action someone can take.

Month 3: the forecast, your first rate call, month-end

By now you should own the weekly forecast update mechanics โ€” roll the pickup, re-run the segments, flag the event dates โ€” with the revenue manager reviewing rather than rebuilding. Propose your first rate action this month, and make it modest and fully reasoned: the date, the pace evidence, the comp position, the math, the risk, the rollback trigger. Whether it's accepted matters less than the quality of the reasoning on display. Then draft the month-end commentary โ€” forecast vs actual, segment by segment, honest about the misses. If your revenue manager sends your draft to the GM with light edits, your first 90 days worked.

The political map

Quick wins and credibility burns

Wins: a pickup report that ties out to the penny; a forecast miss you flagged yourself; a displacement analysis delivered within the hour; a fixed recurring report everyone hated. Burns: an overconfident rate recommendation in week two, before you know the market's rhythm; criticizing the inherited comp set before you know its history; insights that never end in an action; and quietly patching a number you got wrong instead of saying so. The pattern behind all four: credibility comes from verified smallness before ambitious bigness.

If you're prepping for the seat rather than already in it: the Interview Prep Pack rehearses exactly the scenarios these 90 days will throw at you, the Skills Drill Workbook trains the pickup/pace/displacement math you'll run daily, and the Career Roadmap Guide includes the full first-90-days plan with the weekly checklists.