What the occupational data can and cannot say about local demand

Abstract

Public occupational statistics describe where administrative support employment is concentrated by industry and area, but they do not describe the demand for a single executive office. This review explains how the occupational series is constructed, what the published concentration measures show, and where the data stops. It then sets a bounded local scan that uses public data as context rather than as a hiring forecast. The scan is deliberately descriptive and leaves the hiring decision to the people who know the role [1][2][3].

Methodology

The review uses the Occupational Employment and Wage Statistics program, the Occupational Outlook Handbook, and O*NET as public context. It separates employment counts from location quotients and treats local job postings and recruiting experience as separate evidence. No local figure is inferred from a national average without stating the gap. The method is descriptive and does not produce a staffing recommendation [1][2][4].

The question behind the occupation code

A leadership team asks where administrative support talent is concentrated, usually because it is opening an office or changing a support model. The question sounds geographic, but it also depends on industry, firm size, and the mix of duties. Public data can show broad patterns across employers. It cannot say whether a particular executive will find the right assistant in a particular city [1][2].

The occupation code matters before any comparison. Executive secretaries and executive administrative assistants sit within a broader administrative support group, and the published figures may combine roles with different levels of responsibility. A code that includes general office clerks will not describe an executive support role precisely. The first step is to check which occupations the published table actually covers [1][3].

The team should also ask whether the question is about hiring, retention, or cost. Each one uses the public data differently. A hiring question needs current local evidence, while a cost question needs a pay range and a benefits comparison. Writing the question first prevents the data from being used to answer something it was never designed to describe.

How the published series groups employers

The Occupational Employment and Wage Statistics program surveys employers and reports employment and wages by occupation and area. It publishes counts, means, medians, and percentile cutoffs for defined occupation groups. The survey is designed to describe the labor market across employers, not to track a single firm or a single hire. Its definitions and survey period limit how precisely it can describe a niche role [1].

Industry detail is available for many occupations, but the level of detail varies with the sample. Small occupations may be grouped or suppressed in a local area to protect confidentiality. A missing figure is not evidence that no one does the work; it may mean the sample was too small. The reviewer should read the footnotes before treating a blank as zero [1][2].

The survey's industry categories are broad, and a single establishment may be classified by its main activity rather than by every function it performs. An executive assistant in a manufacturing firm may be counted under manufacturing even though the work resembles a professional services role. That classification affects how the industry tables should be read. A comparison across industries should use the published category definitions rather than an informal sense of the sector.

Where the employment is concentrated

Administrative support employment appears across every industry, which is part of what makes the occupation hard to summarize. Professional services, healthcare, finance, education, and government all employ assistants in different proportions. The published location quotient compares an area's share of an occupation with the national share. A quotient above one suggests a relative concentration, not an absolute shortage [1][2].

Concentration can reflect the presence of large employers, a regional industry cluster, or a high ratio of support staff to other workers. It does not show whether those workers are available to a new employer, whether they have executive-level experience, or what they are paid. A city with many administrative jobs may also have many applicants and a competitive market. The measure describes the shape of employment, not the ease of hiring [1][3].

A high location quotient can also reflect a small total employment base. If an area has few jobs overall, a modest number of administrative roles can produce a large quotient. The reviewer should report the underlying counts beside the quotient. A ratio without the base is easy to overread.

What concentration does not tell you

Public data does not report the number of assistants who support a single principal, the complexity of the calendar, or the confidentiality requirements of the role. It does not distinguish a shared support pool from a dedicated executive assistant. Those differences affect the skills required and the salary band, even when the occupation code is the same. The published average hides the variation that matters most to a hiring decision [1][3].

The data also lags the market. A survey collected in one year may describe a labor market that has already changed by the time it is published. Remote work has altered the geography of some support roles, and the published area totals may not reflect a team that hires across regions. The reviewer should date the comparison and avoid presenting it as a current forecast [2][4].

Public data also cannot show whether the local market values executive support experience or treats the role as general administration. Those expectations appear in job postings and in the questions candidates ask during interviews. A small sample of current postings can reveal more about the local standard than a national average. Keep the sample dated and note how it was selected.

Reading local demand against the national picture

A useful local scan starts with the actual work the office needs, not with the national average. Write the duties, the number of principals, the time zones, and the confidentiality level. Then look at the public data for context on the occupation and its broad pay range. The local scan should also include current job postings and the experience of people who have hired in the area [2][4].

Compare the local evidence with the national picture and record the differences. If the local market is tighter than the national data suggests, say so and explain the evidence. If the office is hiring remotely, the relevant market may be wider than the city. A short written comparison is more useful than a single location quotient [1][4].

Remote hiring changes the comparison in a practical way. If the office can hire outside the city, the relevant labor market is the set of places it is willing to employ from, not the commuting radius. The public data can describe each of those places, but the office must decide which ones count. That decision belongs in the written scope of the scan.

A bounded method for a local scan

Define the role and its level before collecting data. List the duties, the decision rights, and the number of executives supported. Then collect public employment and wage figures for the closest occupation codes and the relevant geography. Add current postings and a small number of conversations with local recruiters or peers. Keep each source dated and separate from interpretation [1][2][4].

Report the result as a range with its limits. State which occupation codes were used, which geography was examined, and what the public data could not show. Do not present the national median as a local offer, and do not treat a high location quotient as proof of supply. The output should support a conversation about the role, not replace it [1][3][4].

The scan should end with a short list of open questions rather than a single answer. Questions about candidate supply, pay expectations, and competition for experienced assistants are better answered by local conversations. The public data tells the office what to ask and how the answers compare with the national pattern. It does not replace the conversation.

Key findings

  • The occupation code determines what the data describes, so check it before comparing [1][2].
  • Location quotients show relative concentration, not the number of available qualified assistants [1][2].
  • Small-area figures may be suppressed, and a blank is not evidence of zero employment [1].
  • Public data cannot see principal count, confidentiality, or dedicated versus shared support [1][3].
  • A local scan should combine public context with current postings and dated local evidence [2][4].

Sources

  1. Occupational Employment and Wage Statistics, 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, O*NET OnLine
  4. Industry and Occupation, U.S. Census Bureau

Return to the Research Content library