Salary Ranges for Construction Back-Office Roles: Admin, PM, and Bookkeeping
The office side of a construction company — admins, coordinators, bookkeepers — gets overlooked in trade-focused pay data. Here's how to build their ranges correctly.
Rovaryn Digital · October 30, 2026 · 7 min read

Your Framing Carpenters Have a Rate Card. Your Office Manager Doesn't.
It's budget season, or maybe your general contractor just asked you to post the salary range for an open project coordinator role before a job board will even accept the listing. You go looking for comp data the way you'd look up a prevailing wage for an electrician or a wage determination for a laborer, and you hit a wall. Trade occupations have decades of union scales, certified payroll rates, and Davis-Bacon determinations behind them. Your project coordinator, your office administrator, and the person who reconciles your AIA billing every month have none of that. They're not on a prevailing wage schedule. They're not in your subcontractor rate sheets. They're in a completely different data universe, and most construction companies have never had to go find it before.
This article walks through where that data actually lives, why it's thinner than you'd expect for construction-specific back-office titles, and how to build defensible salary ranges for admin, project coordinator, and bookkeeping roles anyway — without inventing numbers to fill the gap.
Why the Job Title on Your Org Chart Isn't the Occupation Code You Need
The first mistake most construction companies make isn't underpaying their office staff — it's mapping the wrong occupation code to the job in the first place. "Project Coordinator" at a 40-person general contractor might functionally be an administrative support role (scheduling, document control, subcontractor paperwork) or it might be a junior construction management role (field coordination, change-order tracking, owner communication). Those are two different occupations with two different wage bases, even though the business card says the same thing.
The same confusion shows up constantly with "bookkeeper." Some construction-company bookkeepers really are performing bookkeeping-clerk-level work: AP/AR, payroll entry, job-cost coding. Others are functioning as a de facto staff accountant — reconciling retainage, managing WIP schedules, preparing financials for the bank or the bonding company. The U.S. Bureau of Labor Statistics treats Accountants and Auditors (SOC 13-2011) as a separate, higher-skill occupation from Bookkeeping, Accounting, and Auditing Clerks — and the national median for Accountants and Auditors was $81,680 as of May 2024 (BLS). That figure is a real, cited number — but it only applies if the actual day-to-day duties match the accountant occupation, not the bookkeeping-clerk occupation. Pulling an accountant's wage data to set a bookkeeper's range because the title on the org chart says "bookkeeper" is exactly the kind of mismatch that produces an indefensible range if anyone — a board member, a departing employee's lawyer, a state labor office — ever asks how the number was built.
This is the single most useful discipline in setting salary ranges for construction back-office roles: map the actual duties to the correct occupation code before you look at a single wage figure. If you haven't done that mapping exercise yet, it's worth working through systematically rather than guessing.
What BLS OEWS Actually Publishes — and Where It Gets Thin for Construction
The Occupational Employment and Wage Statistics (OEWS) program is the backbone of almost any legitimate, free salary-range exercise in the U.S. It covers roughly 830 detailed occupations, built from a rolling sample of about 1.1 million establishments collected over a three-year survey cycle (BLS). It's published annually with a May reference date and covers the nation, every state, D.C., the territories, and roughly 530 metropolitan and nonmetropolitan areas (BLS). Response rates for the combined semiannual panels run 65.7% by establishment and 65.9% by weighted employment, together covering about 55% of total national employment (BLS) — solid coverage, but not a census, and a reminder that estimates (especially narrower ones) carry real sampling uncertainty.
Here's where it gets thin for a construction company specifically: OEWS publishes wage data by occupation and, separately, by industry, but a detailed cross-tab of "office and administrative support occupations employed specifically within the construction industry" isn't always available at a useful level of geographic or occupational granularity — especially in smaller states or metro areas. The national, occupation-level wage for an administrative assistant or an office manager exists and is free to look up; what's harder to get is a construction-industry-specific slice of that same occupation. That's a real, structural gap in the data, not a reason to substitute a guessed number — when the industry-specific cut isn't available, the honest move is to anchor on the national or state occupation-level figure and note that the construction-industry context is a judgment layer on top, not a separately published statistic.
Setting Salary Ranges for Construction Back-Office Roles: A Worked Example
Once an occupation code is correctly matched, building the actual range is mechanical. Here's a worked example using round numbers to illustrate the method — not a published wage for any specific construction back-office title:
Say a correctly-mapped occupation's national median wage comes back at $65,000 (an illustrative figure for this example, not a cited statistic). A typical approach is to treat that median as the range midpoint, then apply a spread percentage appropriate to the job family — individual-contributor administrative and clerical roles usually warrant a tighter spread than people-manager or project-leadership roles, because the latter carry wider variation in scope and tenure.
- Range minimum = midpoint × (1 − half the spread)
- Range maximum = midpoint × (1 + half the spread)
At a 30% total spread: minimum ≈ $55,250, maximum ≈ $74,750, midpoint $65,000.
Now substitute a real, cited anchor: for a role genuinely performing accountant-level duties, the May 2024 BLS median of $81,680 (SOC 13-2011, Accountants and Auditors) becomes the defensible midpoint instead of a guessed number. Everything downstream — minimum, maximum, and where a specific employee's current pay falls inside that band — follows the same arithmetic, applied to a real, sourced figure rather than an invented placeholder. That distinction — a worked method applied to a cited number, versus a worked method applied to a placeholder — is the difference between a range you can defend and one you can't.
Admin, Coordinator, and Finance Roles Don't Move the Same Way
Range spread shouldn't be a single company-wide setting. A non-field construction salary structure typically needs at least three distinct spread patterns: tight bands for individual-contributor administrative and data-entry work where the job scope is fairly fixed; moderate bands for project coordinator roles, where scope and autonomy expand with experience even without a title change; and wider bands for office-manager or controller-level roles, where tenure, scope, and sometimes direct-report count vary significantly between a 25-person shop and a 150-person one.
This is also where job leveling earns its keep. A "Project Coordinator I" fresh out of an administrative role and a "Project Coordinator III" running document control across four concurrent jobsites shouldn't share one flat range — they're different levels within the same family, each deserving its own band. Working through how job families and levels interact before finalizing spreads avoids the common failure mode of a range so wide it fails to signal anything meaningful about where a given employee actually sits.
Putting a Construction Office Pay Structure on Paper
None of this requires expensive data or a compensation consultant on retainer. It requires correctly mapping each back-office title to its occupation code, pulling the real published wage for that code (not a stand-in from the wrong occupation), and applying a spread appropriate to the job family rather than one default percentage across admin, coordinator, and finance roles alike.
If you're building this for the first time, a structured workbook that walks through the same mapping-to-spread sequence — one row per role, one set of inputs per job family — is usually faster than rebuilding the logic from scratch in a blank spreadsheet. The Salary Range Builder Workbook is set up to pair with exactly this process for a small construction back office: title-to-code mapping, spread configuration, and a documented range you can bring to the next budget conversation or job posting without reverse-engineering the math under deadline.
Get new guides in your inbox
One email when a new article goes live. Unsubscribe with one click.


