A Title Is a Lever, Not a Vanity Item
A title is one of the five levers I teach, and it's the one people apologize for wanting. Title and positioning is how you are leveled and described. The right title travels with you to your next role and resets the base every future offer gets benchmarked against.
So a title ask is not vanity. It's the lever with the longest tail on it, and it's often available in a year when the salary line is closed.
What a Title Is Inside Your Company
Outside the building, a title is shorthand. Inside, it's a slot in a system.
WorldatWork describes job architecture as the hierarchy of jobs within an organization, covering job levels, job titling conventions, grades, career paths, spans of control, and the criteria for career movement, along with the pay programs built on top of job value [1]. A well-built one gives an employer consistent, enterprise-wide criteria for assigning levels and titles, which is the machinery your request has to travel through [1]. SHRM publishes parallel guidance for employers on running job evaluations to support fair pay structures [2].
Two things follow from that. Your manager probably can't grant a title alone, and the criteria your request will be judged against already exist in writing somewhere. Your job is to find them and answer them.
Find the Leveling Criteria Before You Write Anything
Ask your HR business partner for the job architecture, the leveling guide, or the job family documentation for your function. That phrasing matters. 'Can I get promoted' and 'can I see the leveling criteria for my job family' get routed to different places and produce different answers.
If your employer doesn't publish one, or won't share it, build the comparison from what you can see: internal job postings for the level above yours, the job descriptions of peers who hold that title, and standard leveling definitions for your function in your industry.
Then map yourself against it, line by line, instead of in your head. Most leveling guides turn on the same handful of dimensions.
- Scope. What you're accountable for, and how far it reaches past your own team.
- Complexity. Whether the problems you own are defined when they arrive or defined by you.
- Autonomy. How much of your work gets reviewed before it's real.
- Span. People, budget, vendors, systems. Direct reports and dotted lines both count.
- Impact. What changes in the business when your work goes well or badly.
Where you meet the criteria, name the evidence: the decision, the budget, the system, the people. Where you don't, write that too, and name what would close it. A document that admits one gap reads as someone working the same rules the committee works. A document that claims everything reads as a pitch.
How to Frame It With Your Manager
Lead with the external friction, not with your standing. When a client, vendor, or partner sees a mid-level title on the person making the call, the work slows down while everyone figures out who actually decides. That's a business cost your manager recognizes, and it's usually the true reason the request is worth their political capital.
You're not asking for a vanity label. You're asking for the record to match the job you're already doing.
Then say what you're asking for in one sentence: a level and title review against the published criteria, on a date. Give your manager the one-page map, and let them read it before they respond.
Bring HR In Early, and Keep the Money Separate
HR is not defensive about your title. They're defensive about what your title costs, because the two are wired together. So separate them out loud, and separate them first.
Ask for the level review on its own, on a date. Then ask what the band change would mean and when it would apply. That order matters. A frozen salary budget can kill a level review that costs nothing this quarter if the two arrive as one request, and it stops your manager from hearing 'give me money' when you said 'fix the record.'
It also gives you a lever if the money is closed: a written agreement to revisit compensation on a set date, tied to specific results. That's how a 'no budget right now' becomes a scheduled yes.
If the Level You Want Doesn't Exist
Sometimes the answer is that your job doesn't map cleanly to anything in the architecture. Small companies and fast-growing teams run into this constantly, since the structure was built for the org chart from two years ago.
Ask what it would take to define the level, who owns job architecture decisions, and whether other people are sitting in the same gap. A title request that turns into a structural fix for four people is a much easier yes than a title request for one.
Whatever comes back, drive the follow-up email yourself, the same day, with the criteria and the review date in it. A soft yes becomes a real one in writing or not at all. And no amount of preparation compels approval: title changes run through your employer's compensation architecture and approval chain, and nobody can invent their own level around a committee.