1:1 Meeting Script for Asking a Promotion (Word-for-Word)

TL;DR

The script that works isn’t about the words—it’s about the 30-day pre-work that forces your manager to say yes before the meeting starts. Most candidates lose because they treat this as a conversation, not a closing argument.

Who This Is For

This is for the IC or manager who has delivered measurable impact in the last 6 months, has a manager who values logic over loyalty, and is willing to walk if the answer is no. If you’re relying on tenure or effort, this script won’t save you.

What’s the exact word-for-word script to ask for a promotion in a 1:1?

The script is irrelevant if you haven’t pre-wired the decision. In a debrief last Q2, a senior PM at Google walked in with a 10-slide doc—her manager had already approved the promo in Slack the day before. The words in the meeting were just theater.

Open with: “I want to align on my next step here. Based on [X metric], [Y feedback], and [Z market data], I believe I’m ready for [title].” Then stop talking. The mistake isn’t the script—it’s the assumption that the meeting is the decision point. It’s not. The decision happens in the 30 days before, when you control the narrative.

The real script is the email you send 4 weeks prior: “I’d like to discuss my growth at our next 1:1. Attached is a summary of my contributions and how they map to [next level’s] expectations.” This frames the conversation as a formality, not a negotiation. Managers hate surprises, but they respect inevitability.

How do you set up the 1:1 so your manager can’t say no?

You don’t. You set it up so they can’t say not yet. In a cal room at Meta, a director once blocked a promo because the candidate’s impact was “directionally correct but not quantified.” The fix wasn’t better delivery—it was a spreadsheet with $2M in attributed revenue.

The setup is a 3-part pre-read: (1) Your achievements, tied to business outcomes (not effort). (2) The gap between your current level and the next, with evidence you’ve closed it. (3) The risk of not promoting you (attrition, morale, lost leverage). Most candidates lead with (1). The ones who win lead with (3).

Not X: “I’ve been here 2 years.”

But Y: “If I’m not at the next level, we lose [client/team/project] because [specific risk].”

What data should you bring to the 1:1 to prove you deserve it?

Bring the data your manager already trusts. At Amazon, a principal PM’s promo packet was 15 pages—12 were screenshots of internal dashboards her manager checked weekly. She didn’t convince him; she reminded him.

The hierarchy of proof:

Metrics your manager already reports upward (revenue, OKR attainment, headcount leverage).
Peer feedback from stakeholders your manager respects (skip-levels, cross-functional leads).
Market data (Levels.fyi bands, offer letters—if you have them).

Most candidates bring (3) first. That’s a signal you’re negotiating from weakness. Lead with (1), then (2), then (3) as a tiebreaker. If your manager pushes back on (1), the problem isn’t the data—it’s that you haven’t been managing up for the last 6 months.

How do you handle pushback when asking for a promotion?

Pushback isn’t rejection—it’s the first sign the process is working. In a skip-level at Stripe, a candidate’s manager said, “You’re not ready for the scope.” The candidate replied: “What’s the smallest scope at the next level that I am ready for?” The answer was a stretch project that became her promo proof 90 days later.

The framework:

If the pushback is about time: “What would need to be true in the next [X] days for this to be a yes?”
If the pushback is about scope: “Which part of the next level’s expectations am I not meeting, and how do we measure progress?”
If the pushback is about budget: “What’s the process to request an exception, and who else needs to be involved?”

Not X: “I disagree—I think I’m ready.”

But Y: “Help me understand what ‘ready’ looks like so I can close the gap.”

The psychology here is simple: Pushback is a test of ownership. Managers reward those who treat the “no” as a problem to solve, not a verdict to appeal.

When’s the right time to ask for a promotion in a 1:1?

The right time is 30 days after you’ve delivered a result that your manager already bragged about to their boss. At Microsoft, a senior SWE’s promo was approved the day after his manager mentioned his work in a skip-level. The candidate didn’t even have to ask—the manager brought it up first.

The timing hierarchy:

After a major win (ship, deal, cost save) that your manager has publicly credited.
During a lull in your manager’s stress cycle (avoid asking when they’re fire-drilling).
60–90 days before comp planning starts (ask in July if your company’s cycle is October).

Not X: Asking when your manager is distracted.

But Y: Asking when your manager’s manager is in the room (even virtually). Promos are political—momentum matters.

How do you follow up after the 1:1 if the answer is “not yet”?

“Not yet” means “not ever” unless you treat it like a bug in production. In a debrief at Uber, a candidate’s manager said, “Come back in 6 months.” The candidate replied: “What’s the one thing I can deliver in the next 30 days to move that up to 3 months?” The answer was a high-visibility OKR. She hit it in 25 days. Promo approved in 8 weeks.

The follow-up script (send within 24 hours):

“Thanks for the feedback. To confirm, the gap is [X], and the next step is [Y] with a target of [Z date]. I’ll own this and check in weekly. Does that work?”

Not X: “I’ll work on it.” (Vague.)

But Y: “I’ll own [specific action] by [date], and I’ll loop in [stakeholder] for validation.” (Forces accountability.)

Preparation Checklist

Map your contributions to the next level’s expectations (use your company’s internal docs, not Glassdoor).
Gather 3–5 data points your manager already cites in their own updates (revenue, OKRs, headcount leverage).
Pre-wire the conversation with a 1-page pre-read sent 48 hours before the 1:1.
Script your opening line to frame the ask as a formality, not a request.
Prepare for pushback with a “gap-closing” plan (30/60/90-day milestones).
Identify the risk of not promoting you (attrition, morale, lost leverage).
Work through a structured preparation system (the PM Interview Playbook covers real debrief examples of promo asks that failed and why).

Mistakes to Avoid

BAD: “I’ve been here 18 months and taken on a lot of responsibility.”
GOOD: “I’ve increased team output by 30% (measured by [X]), which aligns with the expectations for [next level]. Here’s the data.”

BAD: Asking for a promotion without tying it to business outcomes.
GOOD: “Promoting me to [title] would allow me to own [Y initiative], which is currently a risk because [Z].”

BAD: Accepting “not yet” without a concrete next step.
GOOD: “What’s the one deliverable that would change this to a ‘yes’ in the next 30 days?”

FAQ

What if my manager says “we don’t have budget”?

Budget is rarely the real issue. The judgment is that your impact isn’t worth the cost. Counter with: “What would I need to deliver in the next quarter to justify the exception?” If they won’t engage, start interviewing elsewhere.

Should I mention competing offers?

Only if you’re prepared to leave. At Netflix, a candidate dropped a competing offer in a 1:1—his manager matched it the same day. But the moment you play that card, you’re signaling you’re already halfway out the door. Use it as a last resort, not a first move.

How do I ask for a promotion if I’m remote?

The medium doesn’t matter—the pre-work does. In a fully remote team at Dropbox, a candidate’s promo was approved because her pre-read included a Loom video walking through her impact. The key is making it effortless for your manager to say yes. If they can’t see your work, they won’t reward it.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.