A recruiter sends a note addressed to a title two levels below what you do. A client asks to be put in touch with 'whoever runs this,' and it's you, and you have to explain that. You're on a panel where every other person's title makes their scope obvious and yours makes you sound like support.
Your pay might be fine. Titles do a different job than pay does. They're how people who have never worked with you decide how seriously to take you, and how quickly, and that includes the hiring manager reading your profile three years from now.
Most people assume the fix is a reorg, an annual cycle, or a move to another company. Some of the time it's a document and two conversations.
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.