How to compare industry pay without overreading the data

Abstract

Employers often compare an executive assistant role with a single national salary figure, even when the work sits in a very different industry. This article reviews federal occupational wage data and explains how industry, location, and role scope change the comparison. It separates observed wages from projected starting salaries and warns against treating a national median as an offer. The method supports a more careful hiring conversation rather than a single benchmark [1][2][3].

Methodology

The review uses the Bureau of Labor Statistics Occupational Employment and Wage Statistics for executive administrative assistants, the Occupational Outlook Handbook, and O*NET occupational requirements. It treats industry and location as contextual factors rather than automatic pay premiums. The data describe broad occupation groups and cannot price an individual candidate or a specific job description. No new statistic is calculated by combining unlike series [1][2][3].

What the occupation data covers

The federal occupation 43-6011 covers executive secretaries and executive administrative assistants. The classification includes workers who provide high-level administrative support, prepare reports, conduct research, and may supervise clerical staff. It is broader than the title a single employer uses. A comparison should start by mapping the actual duties to the occupation [1][2].

The Bureau of Labor Statistics publishes employment and wage estimates by industry and area. Those estimates describe wages paid to workers in the occupation, not the starting salary an employer might offer. They also reflect the mix of experience, tenure, and responsibilities within each industry. The data are a reference point, not a quote [1].

O*NET provides a related summary with tasks, skills, and requirements for the occupation. Its requirements data can help an employer describe the role before comparing pay. The summary does not establish a pay premium for any single requirement. It adds context to the wage data rather than replacing it [3].

Why industry comparisons differ

Industries differ in the complexity of the work, the regulatory environment, and the value of the decisions the role supports. An executive assistant in a hospital, a law firm, and a software company may share a title but handle different information and coordinate different stakeholders. Those differences can affect pay without appearing in the occupation title [1][3]. Those differences are a reason to compare the actual duties, not just the industry label.

Industry averages also reflect the size and structure of employers. A large organisation may divide work among several support roles, while a small firm may combine executive support with office management. The average for the industry may therefore describe a different job than the one being hired. The employer should compare the role, not only the sector label [1][2].

Geographic pay differences can be larger than industry differences. A national industry average blends high-cost and low-cost areas, so it may not fit either one. The office should use the local estimate where it is available and note the date of the data. A local comparison is more useful than a national figure for a specific hire [1].

Use the occupation's task list to check whether the role includes supervision, research, or board support. Those duties may justify a different position within the range, but the employer should document the comparison. A title alone is a weak basis for a pay decision. The job description should carry the evidence.

Reading percentiles rather than a single number

Wage estimates are often published with percentiles, not only a median. The median describes the middle of the distribution, while the 25th and 75th percentiles show the spread. A hiring range should reflect the employer's required experience and scope, not the median alone. Using the full distribution makes the conversation more honest [1].

The 10th percentile is not an appropriate minimum for every role, and the 90th percentile is not a target for every senior assistant. The extremes can include unusual arrangements, long tenure, or responsibilities that differ from the typical job. Treat them as context rather than as anchors. A documented role profile should decide where the job sits [1][2].

Pay data also lag the market. The estimates describe a reference period, and hiring conditions may have changed since then. The office should note the reference period and avoid presenting the figure as current market truth. A recent local check can supplement the federal data without replacing it [1][3].

Separating wages from starting salaries

Observed wages and projected starting salaries answer different questions. Wage data describe what workers in the occupation are paid, including people with years of tenure. Starting salary projections describe what an employer might offer a new hire. Comparing the two without that distinction can make a reasonable offer look wrong [1][2].

A staffing or recruitment guide may publish projected ranges based on placements and job postings. Those ranges can be useful for a hiring conversation, but they are not official statistics. The employer should check the methodology and the date. The guide's role definition may also differ from the federal occupation [2].

The safest approach is to use both sources for their intended purpose. Use the federal data to understand the occupation and the distribution, and use a current hiring source to test the offer. Document the comparison and the assumptions. That record helps if the range is questioned later [1][2].

Read the local area estimates alongside the national figures when they are available. A metropolitan area with a tight labour market may sit above the national median, while a rural area may sit below it. The employer should not apply a national percentage adjustment without checking. Local data, even when thin, is more relevant than a national average.

Adjusting for scope, location, and total cost

A role that owns board logistics, supervises staff, or handles sensitive correspondence is not the same as a role limited to calendar administration. The employer should list the specific duties and compare them with the occupation description. A scope adjustment should be explained rather than applied as a vague premium. The more specific the role profile, the more defensible the range [1][3].

Location affects pay through labour market conditions, commuting patterns, and the cost of living. The employer should use the local estimate or a documented geographic differential rather than a national average. Remote work can complicate the comparison because the labour market may be wider than the office location. The policy should state which market the range reflects [1].

Salary is only one part of the cost. Benefits, payroll taxes, equipment, and management time add to the total. An outsourced support arrangement has a different cost structure. The employer should compare total cost and service scope rather than a single hourly rate. The right comparison depends on the model being considered [2].

Ask a recruitment or staffing source how its range was built and what role definition it uses. A range based on placements in a different industry may not fit the job. The employer should compare the scope and the location before using the number. A transparent methodology is more useful than a single headline figure.

A defensible hiring conversation

Prepare a short role profile with the core duties, the required experience, the reporting line, and the information the role will handle. Compare that profile with the federal occupation and the local wage distribution. Set a range and write down the reason for the position within it. The conversation with a candidate is easier when the reasoning is clear [1][3].

Check applicable pay transparency and equal pay rules before publishing a range. Requirements vary by jurisdiction and employer size. Keep the job-related rationale for the range and avoid relying on a candidate's salary history where the law restricts it. Qualified counsel should review the policy [2].

Review the range periodically rather than only at the point of hire. Market conditions, scope, and the local labour supply change. A range that was reasonable two years ago may no longer be competitive. The review should use current data and document the change [1][2].

Limits of the data

Federal wage data cannot capture every difference in responsibility, performance, or negotiation. They describe broad occupation groups and may lag current conditions. They also may not isolate the executive assistant role from related administrative titles. The employer should not treat a single percentile as a precise market price [1].

Industry averages can conceal differences in firm size, union status, and geographic mix. A national figure may be misleading for a specific city or a specialised sector. The employer should use the most local and most specific data available. When the data are thin, say so rather than inventing precision [1][2].

Pay is only one reason people stay or leave. Workload, schedule control, benefits, and management quality also matter. A competitive salary cannot compensate for a role that lacks backup or reasonable boundaries. The hiring conversation should include those conditions [2][3].

Consider the total package when comparing offers, including benefits, leave, flexibility, and development. A role with a lower base salary may be more competitive if the non-cash elements are stronger. The comparison should be documented and explained to the candidate. Pay is one part of a larger employment relationship.

Key findings

  • BLS occupation 43-6011 provides a national reference for executive administrative assistant wages [1].
  • Industry and location estimates describe different job mixes and should be compared with the actual role [1][2].
  • Percentiles show the distribution; the median alone is not a hiring range [1].
  • Observed wages and projected starting salaries answer different questions [1][2].
  • Pay transparency and equal pay rules require qualified review before publishing a range [2].

Sources

  1. Occupational Employment and Wage Statistics: Executive Secretaries and Executive Administrative Assistants (43-6011), U.S. Bureau of Labor Statistics
  2. Occupational Outlook Handbook: Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics
  3. O*NET OnLine Summary Report 43-6011.00, U.S. Department of Labor
  4. Equal Pay and Pay Transparency, U.S. Equal Employment Opportunity Commission

Return to the Research Content library