Labor Categories in Federal Contracts: How to Build a Competitive Rate Structure

A labor category — usually written as LCAT — is the building block of every professional services government contract. It defines a job role, the minimum qualifications a person in that role must have, and the hourly rate the government pays for that work. Nothing else in the pricing structure matters until you get your LCATs right.

Think of an LCAT as a contract between you and the government about who you can bill. You commit to delivering people who meet the stated qualifications. The government commits to paying the stated rate. If you bill a person who doesn't meet the category's qualifications, you've got a compliance problem — potentially a False Claims Act problem.

Labor categories appear across every major service contracting vehicle: GSA Multiple Award Schedule, OASIS+, CIO-SP4, SeaPort NxG, and almost every agency-specific IDIQ. They also define the cost structure inside task order proposals. When an agency asks you to propose on a task order, they're asking you to map labor categories to their requirements and price the hours.

The government doesn't buy people. It buys defined outputs from qualified labor. LCATs are how it specifies what "qualified" means — and how it controls what it pays.

Every LCAT has three core components: a title, a seniority level, and a set of minimum qualifications. Government solicitations vary in how detailed they get, but these three elements are always present in some form.

Here's what a standard LCAT definition looks like in practice, drawn from typical federal professional services contracts:

The qualifications are the hard constraint. If a solicitation says a Senior Program Manager requires a PMP and 10 years of project management experience, you can't staff that role with someone who has 8 years and no certification — even if they're excellent at their job.

Many solicitations include substitution language that lets you swap education for experience (or vice versa). A common formula: each additional 2 years of relevant experience can substitute for a bachelor's degree, or each relevant graduate degree reduces the experience requirement by 2 years. When that language exists, use it. When it doesn't, don't assume it's available.

On GSA Multiple Award Schedule, the LCATs are yours to define — within SIN guidelines. You propose titles, qualifications, and rates, and GSA negotiates whether those rates are fair and reasonable. On structured IDIQs like OASIS+ or CIO-SP4, the government provides the LCAT structure and you price to their framework.

Nearly every LCAT structure uses seniority tiers. The names vary — I/II/III, Entry/Mid/Senior, Junior/Journeyman/Senior — but the concept is the same. Each tier defines a band of experience, education, and responsibility. OASIS+, for example, uses Junior, Journeyman, and Senior explicitly.

These tiers do two things: they let the government buy the right level of expertise for each task, and they give you a way to price a workforce pyramid rather than always pricing your most expensive senior staff.

The experience-education tradeoff shows up in every tier. The contract usually states minimums — but the actual market for these people is tighter than the minimums suggest. A person who barely clears the junior threshold is not going to look the same as one who exceeds it by two years and holds a relevant certification. Contracting officers know this. Technical evaluators know this. Price your workforce accordingly.

One practical issue that trips contractors up: a person who was hired as a mid-level employee inside your company may not qualify as mid-level under the contract's LCAT definition. Internal titles mean nothing. The contract's qualifications are what matter. Before you staff a task order, run a qualification check against the actual LCAT language.

The other trap is the opposite: pricing a senior person into a junior LCAT to win on price. Technically allowable in some circumstances — but if the government later discovers your "junior" is billing at senior qualifications without the senior rate, you've created a misrepresentation issue and you're leaving money on the table that justified the higher rate in the first place.

The hourly rate you bill the government is not the hourly rate you pay your employee. The difference is your indirect cost structure — fringe, overhead, G&A, and profit — stacked on top of direct labor. This stacked number is your fully burdened rate, also called the wrap rate when expressed as a multiplier.

Getting the math right matters enormously. The rates are not simply added together. Each applies to the accumulated cost beneath it. Here's how a typical cascade works:

In this example, an employee earning $65/hour fully burdened costs the government $140.54/hour — a wrap rate of approximately 2.16x. That's on the higher end of competitive. Most winning government service contractors maintain wrap rates between 1.6x and 2.2x. Below 1.6x and you're likely not covering your actual costs. Above 2.2x and you're at a persistent pricing disadvantage on price-sensitive awards.

The variables that move your wrap rate most are fringe and overhead. Fringe scales with your benefits package — a company offering rich health insurance, strong retirement matching, and generous PTO will carry a higher fringe rate than a leaner shop. Overhead scales with your facilities and support infrastructure. Remote-first companies with minimal office space tend to have lower overhead rates.

On DCAA-audited contracts — which includes most Cost Plus and Time & Materials work above the Simplified Acquisition Threshold — you'll need to disclose your indirect rates and support them with an accounting system that tracks costs correctly. If you're pursuing this work seriously, the time to get a DCAA-compliant accounting system is before you win, not after. See our guide to DCAA-compliant accounting systems for what that requires.

If your contract includes service workers — janitors, security guards, food service staff, administrative assistants, IT help desk — the McNamara-O'Hara Service Contract Act (SCA) probably applies. The SCA requires you to pay at least the prevailing wage for each labor category in each geographic area where work is performed.

"Prevailing wage" is determined by the Department of Labor's Wage and Hour Division. For each SCA-covered contract, the agency obtains a Wage Determination (WD) — a document listing minimum wages and fringe benefits for dozens of specific occupations in that location. That WD gets incorporated into your contract. You must pay workers in covered occupations at least those minimums.

The SCA floor matters for your pricing in two ways. First, it sets a hard cost floor that you cannot undercut on covered positions — so your competitive pricing floor is the government's own wage determination, not your preference. Second, new determinations are issued periodically. When your contract exercises an option year, a contracting officer can incorporate a revised WD, which may increase your required wage floor and squeeze your margin if your pricing assumed stable labor costs.

On top of SCA, a second federal wage floor exists under Executive Order 13658, which still applies to some multiyear service contracts. The hourly floor under that order has been adjusted to $13.65/hour as of 2026 for non-tipped workers on covered contracts. (Executive Order 14026, which had raised the floor to $15.00, was rescinded by Executive Order 14236 in March 2025 — so the legacy order's lower rate is now the relevant floor for most affected contracts.)

The SCA also affects how you define your LCATs on covered contracts. The government uses its own occupational classification system for wage determinations — a Security Guard I, for example, is a specific SCA category with its own WD rate. Your proposed LCAT titles and duties must correspond correctly to the SCA occupation classification or you risk miscategorizing workers and creating a compliance gap.

On the GSA Multiple Award Schedule, you propose your own labor categories and rates. GSA negotiates whether those rates are fair and reasonable by comparing them to commercial pricing, other schedule holders, and market data. Once approved, those rates become the ceiling for task order pricing — you can always propose less, but never more than your approved schedule rates.

The range of schedule rates across the market is wide. Based on publicly available 2025 GSA Advantage price lists and contractor disclosures, IT professional services rates for the most common SIN (54151S, IT Professional Services) run roughly:

These ranges reflect what contractors actually approve on their schedules — they include the Industrial Funding Fee (IFF) that GSA charges and factor in annual escalation across multi-year contract terms. The 0.75% IFF is built into every GSA schedule purchase price, so your approved rate is technically all-in from the buyer's perspective.

Real task order prices often come in below these approved ceilings. Agencies use competitive ordering procedures — putting a requirement out to multiple schedule holders and selecting the best value — which creates downward pricing pressure. Your approved GSA rate establishes your ceiling; where you actually price within that ceiling is your competitive decision on each task order.

Annual escalation clauses matter here. Most GSA schedule contracts allow you to escalate your approved rates annually — tied to the Bureau of Labor Statistics Employment Cost Index or a negotiated fixed escalation percentage. On a five-year contract, the difference between a 2% and a 4% escalation rate compounds into a significant margin difference by year five. Negotiate your escalation rate as seriously as your base rates.

Not all contract vehicles let you define your own LCATs. Structured vehicles like OASIS+ provide the labor category framework and require you to price within it. Understanding how each major vehicle handles LCATs affects both your onboarding strategy and your task order pricing.

Here's how the major professional services vehicles handle labor categories:

On OASIS+, the vehicle expanded to 13 service domains, with five additional domains phased in through 2026. Labor categories under OASIS+ are intended to provide a standardized crosswalk across all domains, which simplifies the government's ability to compare task order proposals but requires contractors to know exactly which SOC classification their proposed personnel fall into. See our detailed OASIS+ contract guide for the onboarding requirements.

Labor category errors are among the most common reasons technically capable contractors lose proposals — or win them and then face post-award compliance problems. These are the mistakes that show up repeatedly:

Most technical proposals require you to write up key personnel — specific individuals you're committing to put on the contract. How you write those sections directly affects whether evaluators score you at the top or in the middle.

The goal of every key personnel write-up is to make it undeniable that this person exceeds the LCAT requirements. You're not checking boxes — you're making a case. That means leading with the result of their experience, not just the duration.

Here's the structure that works:

On task orders where no specific personnel are required, you're proposing a labor mix — a staffing plan that shows how many hours at which LCAT levels you're proposing to allocate to the work. The key here is realism. Proposing 90% senior staff looks impressive but signals padding. Proposing 80% junior staff looks cheap but signals under-resourcing. The right mix matches the actual complexity distribution of the stated requirements.

CapturePilot's proposal intelligence tools can help you analyze past award data to see what labor mix winning contractors have used on similar task orders — giving you a data anchor instead of a guess.

A labor category structure that wins today may not win in two years. Markets move. GSA Advantage gives buyers access to every approved schedule holder's published rates. Agency contracting officers benchmark your rates against historical awards. The pricing intelligence flowing through the federal market is better than most contractors realize.

Building a competitive long-term rate structure requires three disciplines:

The contractors who consistently win on rate-sensitive vehicles aren't always the cheapest — they're the ones whose rates look defensible. An agency evaluator who sees your rates and thinks "that's reasonable for this level of work" is much more likely to select you than one who sees rates that look like a puzzling outlier in either direction.

Use market intelligence tools to track what agencies are actually awarding — by vehicle, by SIN, by NAICS code. What a competitor proposes is visible through FPDS if you know how to read the data. And our pipeline management tools can help you track which upcoming opportunities are likely to be rate-sensitive versus quality-weighted, so you can calibrate your pricing strategy per pursuit.

Finally: get ahead of option year repricing. If your wrap rate increases materially between the base year and option year 2, you need to know that before you exercise the option — not after. Build a simple model that runs your actual indirect rates against your proposed rates for each option year and flags the gap. A margin squeeze you see coming is manageable. One that blindsides you at option exercise is painful.

Related Reading