Administrative Support Pay Benchmark for Hiring in 2026

Research question

How should an executive office use national pay data when setting a 2026 hiring range?

Evidence reviewed

The Bureau of Labor Statistics reports a May 2024 median annual wage of $47,460 for secretaries and administrative assistants. Its published outlook projects little or no overall employment change from 2024 to 2034 while estimating about 358,300 openings each year, mostly from replacement needs. Those national figures describe a broad occupation, not a quoted market rate for one executive assistant vacancy.

Read the primary public source for a local hiring range alongside the office's offer record. In offer calibration, the citation supplies the outside definition or statistic; the internal record supplies the case evidence.

What the source can and cannot establish

The external reference for a local hiring range is the linked public source above. During candidate comparison, we use its stated definitions and observation scope rather than borrowing the source's authority for a different claim.

The publication answers a public-policy question, while the office needs to decide range and role scope. The pay discussion and the published occupation data must remain separate. In particular, geography and seniority can move pay away from a national median.

Measurement design

Define the observation before counting

Start with the candidate, not a dashboard label. Define the event as accepted offer. The denominator is qualified candidates who reached the offer stage.

Write the candidate definition before calculating a local hiring range. A difficult result is not a reason to move the boundary later, and any exclusion should remain visible in the offer record.

The working record should contain base pay, location, years of comparable work. Keep executives supported, offer outcome, decline reason beside it when those fields explain the outcome. When reviewing location review, a short structured record is easier to audit than copied email threads or calendar descriptions, and it reduces the amount of executive information gathered for analysis.

As part of a local hiring range, label the observed candidate separately from the interpretation. That small discipline lets the hiring manager reconstruct the reasoning later.

Keep context beside the number

Choose a fixed review window for a local hiring range and keep the numerator beside the denominator. Experience weighting calls for the same discipline: record operational breaks when they occur; a holiday, migration, leadership change, or unusual deadline can make adjacent periods incomparable.

In decline analysis, keep the source record and the analyst's inference in separate fields. A reader should be able to see what happened to the candidate before reading why the team thinks it happened.

Ask the hiring manager to reconcile a sample of candidate cases to the source system. If reviewers disagree about inclusion, repair the rule before expanding the dataset or changing range and role scope.

Count candidate cases consistently; do not combine them with a different operational unit in the same series.

Review exceptions, not just averages

During range approval, compare the office with its own prior period before comparing it with another company. When reviewing requisition scoping, role scope, executive working style, and recording discipline differ enough to distort a cross-company ranking. Geography, seniority, industry, and responsibility can move a role far from the national median.

As part of compensation notes, write down the observed facts first, then the explanation being tested. This prevents a local hiring range assumption from quietly becoming a recorded event.

Before acting on a change in a local hiring range, inspect the cases that moved the result. Offer-stage review calls for the same discipline: a larger workload, better capture, or a temporary operating shock may explain the movement without showing that the underlying process worsened.

The offer record should show which details came from the source system and which came from review judgment. That distinction matters when the range and role scope are revisited.

Turn the result into one decision

In hiring evidence, set the decision rule as an investigation trigger rather than a universal pass mark. When the trigger fires, the hiring manager should review the cases and adjust the range, narrow the role, or change the sourcing plan. During salary discussion, the trigger is useful because it starts a review; it is not evidence that an employee, supplier, or support model failed.

The denominator remains the candidate. When reviewing role definition, changing that unit mid-review would make the comparison unreliable.

Data governance

Collect only the fields needed to review a local hiring range. The offer record should use reason codes and timestamps where possible, without copying message bodies, credentials, personal documents, or unrelated executive details.

As part of market context, separate the count from the story told about it. The hiring manager may change an interpretation without altering the underlying candidate evidence.

Access to the offer record should follow the ownership of the underlying process. Approval history calls for the same discipline: name the row-level reviewers, define who sees only an aggregate, and set a deletion date for the working extract.

In candidate records, mark estimates, exclusions, and reviewer judgments explicitly. Future reviewers should not have to guess which parts of the a local hiring range note were observed.

Interpretation rules

Read the cited source for the purpose it states, then compare that purpose with a local hiring range. Where the two differ, the hiring manager should rely on the offer record and state the limit plainly.

Carry the source's population, observation period, and definitions into the a local hiring range note. The office should not attach a public agency's authority to range and role scope when the agency did not study that local choice.

Set the review cadence from the number of candidate cases and the speed of the decision. During pay-band review, a low-volume office may need a longer window; an urgent control check may need a short operational review without claiming a trend.

A reproducible note preserves the raw candidate facts before offering a cause. When reviewing sourcing decisions, this also makes disagreements about interpretation easier to resolve.

When a local hiring range reaches legal, employment, security, finance, or safety judgment, the assistant should route the question to the accountable specialist. As part of offer outcomes, the operations record can document advice and ownership without pretending to make the specialist determination.

Range governance calls for the same discipline: use plain labels for observation, inference, and decision. They keep a local hiring range analysis from overstating what the offer record can prove.

Example review

In hiring follow-up, suppose the first reporting period produces a result outside the office's chosen trigger. During offer calibration, the reviewer should open the underlying cases, confirm the denominator, and note whether workload or capture changed. Only then should hiring manager decide whether to adjust the range, narrow the role, or change the sourcing plan.

After changing range and role scope, run the next review under the same definitions. When reviewing candidate comparison, if the workflow or collection method changes, mark the break instead of joining incompatible periods.

Before closing the review, sample ordinary candidate cases as well as exceptions. As part of location review, check for late records, work handled outside the normal system, and categories too small to support an interpretation.

Differences in documentation can make an exception look more serious than an ordinary candidate case. Experience weighting calls for the same discipline: record unresolved uncertainty in the decision log so a later review can add evidence without rewriting the earlier conclusion.

Limitations

In decline analysis, internal records can also be incomplete or influenced by the people doing the recording. During range approval, this framework supports an operating review, not a causal study or a universal benchmark.

End with a dated decision log for a local hiring range: what changed, who owns range and role scope, what evidence would show an effect, and when the team will review it. When reviewing requisition scoping, stop collecting a measure that has no live decision attached to it.

Every row in this analysis represents one candidate. As part of compensation notes, aggregate measures must preserve that definition.

Audit questions for this review

The hiring manager should be able to trace every reported candidate back to the offer record. Offer-stage review calls for the same discipline: start by checking whether the event definition was applied on the day the record was created or added later during analysis.

In hiring evidence, then compare included and excluded cases around the boundary. A rule that works only after a reviewer knows the outcome is not stable enough for a local hiring range.

During salary discussion, next, inspect missingness rather than treating an empty field as a negative result. When reviewing role definition, ask who normally creates the record, which channel can bypass that process, and whether a staffing or system change altered capture.

As part of market context, if those answers are unclear, report the count as incomplete. Do not convert missing candidate evidence into an estimate simply to keep a dashboard continuous.

Related guidance

Operational context on a local hiring range calls for the same discipline: review the service model, the relevant operating guide, and the research library. In approval history, use contact us when the evidence calls for a support-design discussion.