What the public wage record can and cannot establish
Abstract
Public wage series describe the occupation and its pay distribution at a point in time, but they do not measure an individual's progression or an office's internal equity. This review explains how the occupational wage data is constructed, what it can show about executive assistant pay, and where the published record stops. It then sets a bounded local method for reviewing pay bands without inventing a market benchmark [1][2][3].
Methodology
The review uses public occupational and wage sources as context and treats local payroll records as the primary evidence. It distinguishes occupational averages from seniority-based progression and separates base pay from bonus, overtime, and benefits. Every local figure is reported with its source, date, and scope. The method is descriptive rather than a compensation recommendation, which requires qualified review [1][2][4].
The question and why it matters
A leadership team asks whether an executive assistant's pay is progressing at a normal rate, and the question sounds simple until the data is examined. Public wage series report an occupation at a point in time, while progression is a change within a role, a person, or a pay band. The two are related but not the same measurement. A useful review states which question it is answering before it quotes a number [1][2]. The question matters because pay decisions are often made with a single market figure and a memory of the last raise. That combination can hide compression between junior and senior support roles. It can also hide a gap between the official band and the actual offers the office makes. Public data provides context for those local observations, not a replacement for them [1][3].
A useful test is to ask two questions separately: whether the office pays within its local band, and whether people move through that band over time. The first is a market comparison, while the second is a design question about levels and checkpoints. Combining them into one number makes both harder to answer. Keep the two findings side by side in the report.
How the occupational wage series is built
The Occupational Employment and Wage Statistics program surveys employers and reports employment and wages by occupation and area. It publishes mean and median wages, along with percentile cutoffs, for broad occupational groups. The series is designed to describe the labor market, not to track one employee over time. Its definitions and survey period matter when a reader compares a local salary to a published figure [1]. The occupation itself covers a range of seniority and responsibility. An executive assistant supporting one manager and an assistant coordinating a board cycle may share a title but not a pay level. The published distribution reflects that mix across employers. A local review should compare like with like before drawing a conclusion from the average [1][2].
Before quoting a published figure, check the occupation code and the survey year. A code that covers a broader administrative group will not describe executive support precisely. A survey from an earlier year may not reflect the current local market. The source note should make both limits visible to the reader.
What progression looks like in published data
Public data can show how pay differs across percentiles at a point in time. A wide gap between the median and the top decile suggests that the occupation contains roles with very different scope. It does not show whether the same person moved from one percentile to another. That distinction is important when a team uses the data to justify a progression policy [1][3]. The series can also show broad wage growth between survey years, but the comparison is affected by changes in the occupation, the sample, and the geography. A rising average may reflect a shift toward senior roles rather than a raise for the same work. A careful review notes those possibilities instead of treating the change as a pure price signal [1][4].
A useful local comparison uses the same level definition for every person in the band. If one assistant is classified as senior because of tenure and another because of scope, the comparison mixes two ideas. Write the level criteria before looking at the salaries. That order reduces the risk of fitting the levels to the desired answer.
Where the published data stops
The data does not report tenure, performance, or the value of institutional knowledge. It does not distinguish a base salary from a bonus, an overtime payment, or a housing allowance. It also does not describe the non-cash elements that often matter in executive support, such as flexibility or access to development. Those gaps are not defects; they are the boundary of the series [1][2]. Geography adds another limit. National figures can differ substantially from a local market, and the published area data may be suppressed when the sample is small. A team that uses a national median for a local hire may be either overpaying or underpaying without knowing it. The review should name the geography and the date before comparing [1][4].
Published data also lags the market. A survey collected last year may describe a labor market that has already changed. The office should date the comparison and avoid presenting it as a current offer recommendation. Local recruiting experience can update the picture without replacing the source.
Why local pay bands diverge
Local pay bands diverge because the role is shaped by the executive, the industry, and the complexity of the calendar. A support role in a regulated firm may carry compliance duties that a similar title elsewhere does not. A role covering multiple principals may require coordination that is not captured in the job description. Those differences justify a local band rather than a single market number [2][3]. Internal equity also matters. If a new hire enters above an experienced assistant's pay, the team has a retention problem even if both salaries are within the market range. A progression review should look at the band, the actual offers, and the time people spend at each level. The public series cannot see that internal pattern [1][3].
Geography is not the only local factor. Industry norms, the number of principals, and the amount of confidential work all shape the band. Record those factors next to the pay data so a later reviewer can see why two similar titles differ. The explanation is part of the evidence.
A bounded method for a local review
Start with the current role descriptions and the actual duties performed. Map each role to a level based on decision rights, scope, and the number of principals supported. Then collect the base pay, the last increase, and the time in level for each person in the band. Use payroll records rather than memory [2][4]. Compare the local band with the published distribution only after the roles are mapped. Report the comparison as a range and state the geography and survey year. Do not present a single percentile as the correct rate. The result should show where the office sits and which roles need a closer look [1][4].
Keep the role map separate from the salary data until both are reviewed. A role may be mis-levelled, and a salary may be outside the band for reasons that are not visible in the spreadsheet. Discuss the exceptions before adjusting the band. That sequence prevents a data exercise from becoming a surprise for the team.
What to report to leadership
Report the mapped levels, the current base pay ranges, and the observed time in level. Add the market context with its source and date, and separate it from the local findings. Note any retention or equity risk that the data suggests but cannot prove. A one-page summary with an appendix is usually enough [2][3]. Recommend one decision, such as adjusting a band, defining a progression checkpoint, or collecting better role data. Give the decision an owner and a review date. Avoid recommending a blanket increase from a national average. The local pattern should drive the action [1][4].
A short appendix with the role map and the salary ranges lets leadership check the summary without reopening the analysis. Remove individual names and report by level. State the date of the data and the date of the review. The appendix should be usable a year later.
Limits and responsible use
This review cannot establish a fair salary for a specific person or prove that a pay level causes turnover. It cannot account for performance, negotiation history, or the full value of benefits without local records. It also cannot substitute for legal or compensation advice. The output is a structured way to ask better questions [1][3]. Protect privacy by reporting at the level and band rather than identifying individuals. Keep the source dates visible so a later reader can judge whether the comparison is current. Review the band annually and after any significant change in the role. The method is a planning aid, not a verdict [2][4].
Finally, avoid using the review to justify a decision that has already been made. If the conclusion is fixed, the analysis becomes decoration. State the decision question first and let the data answer it. That discipline protects both the team and the credibility of the review.
Key findings
- Occupational wage series describe a distribution at a point in time and do not measure one person's progression [1][2].
- A wide percentile range within the occupation reflects different levels of scope and responsibility [1][3].
- Public data does not separate base pay, bonus, overtime, benefits, tenure, or performance [1][2].
- Local role mapping and payroll records are needed before comparing a band with a published figure [2][4].
- Report local findings as ranges and use them to plan a review, not to set a single correct salary [1][4].
Sources
- Occupational Employment and Wage Statistics, 43-6011 Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics
- Occupational Outlook Handbook: Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics
- O*NET OnLine Summary Report 43-6011.00, O*NET OnLine
- Consumer Price Index, U.S. Bureau of Labor Statistics