Fixed price, time and materials, or staff augmentation: choosing a contract structure

Reference article · 8 min read

Every technology contract answers one question before it answers any other: who absorbs the cost when the work takes longer than someone expected. Fixed price puts that on the vendor. Time and materials puts it on the agency's budget. Contracted staff put it on the agency's own managers.

The choice is difficult because each structure fails in a predictable way when it is applied to the wrong work. Fixed price applied to scope nobody can describe produces either a padded price or a low price followed by change orders. Time and materials with nobody tracking the burn rate reaches its ceiling and asks for more. Contracted staff placed where the agency cannot direct them produce hours rather than outcomes. None of the three is inherently safer than the others; each is safer for a particular kind of work.

Fixed-price deliverables

The vendor commits to defined deliverables for a set price, usually paid against milestones or on acceptance.

What it gives the agency: a number that does not move, delivery risk carried by the vendor, and comparatively little day-to-day supervision.

Where it fits: scope that can be written down and tested. Migrating a known dataset, integrating two systems with documented interfaces, a bounded assessment with a defined report.

What it costs: precision, paid up front. Someone with subject-matter knowledge has to write requirements and acceptance criteria before the solicitation goes out. Prices generally include a contingency for whatever uncertainty the agency left unresolved, so the agency pays for the risk transfer one way or another.

Where it is the wrong choice: when requirements will be discovered during the work, or when the agency cannot state what "done" means in testable terms. It also does not release the agency from its own obligations. Late decisions, unavailable test environments, and slow reviews are ordinary grounds for a vendor delay or change claim.

Time and materials with a ceiling

The agency pays agreed hourly rates by labor category for hours actually worked, subject to a not-to-exceed ceiling, with work released through task orders.

What it gives the agency: the ability to change direction, reprioritize, or stop without renegotiating scope, and payment only for work performed.

Where it fits: discovery, modernization planning, production support, and engagements where priorities shift as the agency learns.

What it costs: management attention. It works with named key personnel, hours reported against a plan, invoices checked against work actually delivered, and an agency decision maker setting priorities week to week.

Rules to check: where federal award funds pay for the work, the uniform guidance at 2 CFR part 200 restricts time-and-materials contracting, generally permitting it only after a determination that no other contract type is suitable, requiring a ceiling price that the contractor exceeds at its own risk, and expecting a high degree of agency oversight. Federal agencies contracting directly work under the Federal Acquisition Regulation, which likewise treats this as a contract type to use only when nothing else is suitable. Many state and local codes add their own conditions. How any of this applies depends on the entity, the funding, and the jurisdiction, so confirm the current rules with your purchasing office and counsel rather than relying on a summary.

Where it is the wrong choice: when nobody has capacity to manage it, because the ceiling then functions as a target rather than a limit, and where a governing body will read any variance from the original figure as an overrun.

Contracted staff under agency direction

The vendor supplies and employs people who work at the agency's direction, billed hourly or monthly. The agency assigns tasks, sets priorities, and owns the result.

What it gives the agency: direct control over priorities and quality decisions, rates that do not carry a delivery risk premium, system knowledge that stays with agency staff, and a placement that can start and stop on notice.

Where it fits: a capacity gap rather than a capability gap. The agency knows what it wants built and how, and needs more hands or one specific skill for a defined period, such as a developer during a release push or an analyst during a conversion.

What it costs: the agency owns everything. Quality, schedule, and integration are its responsibility, and a supervisor has to spend real hours directing the work.

Rules to check: civil service, merit system, and collective bargaining provisions in many jurisdictions restrict contracting out work performed by classified employees, limit how long a placement can run, or require documentation that agency staff are unavailable. Worker classification and co-employment questions also arise. Ask human resources and counsel before the solicitation is written.

Where it is the wrong choice: when the agency does not know what to build, because this structure buys effort rather than accountability for an outcome. It also tends to drift. Placements renewed year after year become permanent staffing at contractor rates, which is a decision worth making deliberately rather than by default.

How to decide

Work through these in order. The first two are gates: a no at either one removes options regardless of what the later criteria say.

1. Can you write what "done" looks like and test it objectively, before the solicitation goes out? If yes, fixed price is available to you. If no, a fixed price will either carry a contingency for the ambiguity or produce change orders when the ambiguity surfaces, and no contract language written later supplies the clarity that was missing.
2. Who manages this week to week, and how many hours a week do they actually have? Time and materials needs someone to set priorities and check invoices against work delivered; contracted staff need daily supervision. If nobody has those hours, fixed price is the only structure that matches your capacity, which sends you back to the first question.
3. Is the gap capability or capacity? If the agency does not know how to do the work, it is buying a capability and should buy a result, whether fixed price or a managed hourly engagement with defined outcomes. If the agency knows how and only lacks hands, contracted staff fit, and a deliverable contract adds cost for risk the agency is already carrying.
4. How stable is the scope over the term? Look at how often priorities changed during a comparable past effort. Frequent change favors hourly structures or short fixed-price increments; stable scope favors a single fixed-price deliverable.
5. What funding source is paying, and what does it require? Grant periods of performance, federal procurement standards, and single-year appropriations narrow the field. A period of performance that ends on a fixed date argues for defined deliverables completed inside it.
6. How much cost variance can your governing body tolerate in public? If the answer is little, an hourly structure demands reporting discipline the agency may not have, and fixed-price increments are easier to explain.
7. Who operates the result afterward? If agency staff will run it, require knowledge transfer as a deliverable in a vendor-led structure, or weight agency involvement more heavily in the staffing plan.

When the criteria conflict, the first one usually governs. An agency that cannot define the work cannot buy a fixed price for it honestly, however much the budget process prefers a fixed number.

What this means for your solicitation

State the structure you have chosen and require pricing in that form, so that proposals are comparable.

• Fixed price: publish acceptance criteria, the milestone payment schedule, and the change process.
• Time and materials: require rates by labor category, resumes for key personnel, substitution approval, the ceiling, and regular burn reporting.
• Contracted staff: define the role, the named supervisor, the term, extension conditions, and the handoff.

Phased structures often fit a program better than one shape applied to all of it. A common pattern is a fixed-price discovery phase that produces requirements and acceptance criteria, followed by fixed-price increments for delivery, with a small hourly pool for work that cannot be predicted. The tradeoff is more contract administration and more decision points.

Two mistakes recur: asking vendors to fixed-price a scope the agency cannot define, and using time and materials to postpone writing requirements. Both move a planning problem into the contract, where it is more expensive to resolve.

Where HQT fits

Structure analysis before a solicitation is drafted, requirements and acceptance criteria written so they can be tested, task order and burn reporting practices for hourly work, and independent review of proposals against the structure selected.

Frequently asked questions