An opaque pay range makes it hard to prepare a useful review conversation. With your assigned level and your employer’s current compensation documentation in hand, you can work out what your salary band means and ask a more precise question about your position in it. Start with the written range, then connect it to the expectations and evidence that apply to your role.
A salary band is a pay range an employer associates with a role or level. Its boundaries alone do not tell you how pay decisions are made, what counts toward the range, or whether strong work changes your position within it. Those details depend on your employer’s policies, so use its current documentation rather than assuming a general definition settles your case.
Step 1: Confirm what your salary band includes
Find the range tied to your assigned role and level in an official compensation document or ask the appropriate internal contact for it. Check whether the figures refer to base salary or a broader form of compensation. If location or employment arrangement affects which range applies, confirm the version associated with your position.
Write down the range, its effective date if provided, and what the figures measure. You should be able to explain what each number refers to before drawing conclusions about where you sit. If a review document shows your compa-ratio, which divides your pay by the range midpoint, check that it uses the same pay measure and range you just recorded. A range for base salary, for instance, cannot answer a question about total compensation on its own.
Step 2: Match the band to your actual level
Read the role expectations attached to your assigned level. Then identify the expectations for the next level if your employer makes them available. Keep the distinction clear. Your current salary band describes a pay range for a level; a promotion case concerns evidence that your work meets a different level’s expectations.
For an analyst, that distinction may show up in the work itself. Producing a reliable recurring analysis demonstrates craft and ownership. Defining a measurement approach that other teams adopt may demonstrate broader scope, depending on the role criteria. Neither example proves a promotion by itself, but comparing them with written expectations tells you which evidence to gather.
At this point, you should know which level the range belongs to and which expectations you are using to evaluate your work.
Step 3: Collect evidence against those expectations
Choose a few pieces of work that show your ownership, the complexity you handled, and what changed because of it. Record when the work happened and what supports the outcome. Useful proof might include an agreed definition, a decision informed by your analysis, or a process that others continued using. Describe the result you can verify rather than assigning a number from memory.
Group the entries by the expectation they address. This makes a pattern easier to discuss than a long list of tasks. It also shows gaps. If the next-level criteria emphasize influence across teams and your examples are all individual deliverables, you have a concrete development question to bring to your manager.
If your examples do not yet show a next-level pattern, this guide to meeting the criteria for the next level explains how to select and test stronger evidence.
Keep your personal record free of sensitive internal documents, restricted figures, and customer-level information. A clear account of what you did and how the outcome was checked is enough to prepare the conversation.
Step 4: Ask which process applies to your question
Take the band definition, the level expectations, and your evidence into your review discussion. Ask your manager how pay movement within the current level is evaluated and how that differs from a promotion decision. You can also ask what evidence would make your next-level case clearer and when that evidence would be considered.
This conversation may reveal a policy you had not seen or a gap in your examples. It does not promise a pay change. The useful result is a specific understanding of the process and a next action you can take, rather than an assumption based on where one number falls in a range.
Keep the evidence ready for the next conversation
After the review, record the criteria your manager named and the work you plan to use as proof. Revisit the record as projects finish so your next discussion draws on completed work rather than memory. ImpactLogr can hold those accomplishment notes for reuse when you prepare a review or promotion case.
To make that follow-through easier, keep a working record for your next review conversation.