What the public record shows
Most federal contract opportunities above a modest dollar level must be posted publicly on SAM.gov. States run their own procurement portals. Cities and counties publish requests for proposals on bid boards and approve contracts in council agenda packets anyone can download. Read enough of these in a year and a set of buying patterns becomes plain, not from any survey or dataset, but from the documents themselves: what is being bought, how it is being evaluated, and how the work is packaged.
This piece describes the patterns that stand out in 2026 for analysis, technical review, research and mixed technical and expert work. It is a qualitative reading of public solicitations and award notices, not a statistical study. For each pattern it explains what the buyer is doing, why, and what it asks of the program office writing the requirement and the firms responding to it.
Five patterns recur. Simplified acquisitions and direct awards carry a growing share of analysis and technical services. Lowest-price technically acceptable awards are common for services the buyer can define tightly. Local governments buy specialist review on call. Health agencies buy forecasting and economic analysis as distinct services. And programs increasingly pair community outreach with the data systems that track it.
Simplified buys for analysis and technical services
A great deal of federal analysis and technical work is now bought through simplified acquisition procedures: a request for quotes, a short technical submission, a fast evaluation and a purchase order. These procedures let a contracting officer award in weeks rather than months, with far less documentation than a full source selection. Since October 1, 2025, the federal simplified acquisition threshold has been $350,000 and the micro-purchase threshold $15,000, which puts a meaningful amount of analytical work inside the simplified band.
The solicitations themselves tend to be short. A statement of work of a few pages, a list of deliverables, a period of performance under a year, and an evaluation that weighs a brief technical approach, relevant experience and price. Many are set aside for small businesses, because federal purchases in this range are generally reserved for them when at least two capable small firms are expected to compete. Others are direct awards to a responsible source after limited competition, with a justification posted where the rules require it.
The rewrite of the Federal Acquisition Regulation that began in 2025 points the same way: fewer required steps, plainer language and more room for contracting officers to use judgment. Whatever its final shape, the direction encourages program offices to scope work in pieces that can be bought quickly.
What it means for program offices. A simplified buy is only fast if the requirement is clear. The time saved on procedure is lost if quotes come back incomparable because the deliverables were vague. Define the outputs, the decisions they support and the data available, and say how quotes will be compared.
What it means for firms. Short solicitations reward short, specific answers. A two-page technical response that restates the problem in the agency's words, names the people, lays out the method and commits to dates will outscore a ten-page capabilities brochure. Speed matters too: quote windows are often one to two weeks.
Lowest price technically acceptable, for work that can be defined
Where a service is well understood, such as a standard data migration, a defined set of dashboards, a routine technical review against published criteria, or a survey with a fixed instrument, many buyers evaluate on a lowest price technically acceptable basis. Each offer is judged pass or fail on technical factors, and the lowest-priced acceptable offer wins. The regulation lists conditions for using this method, among them that the government would gain little or no value from a proposal that exceeds the minimum requirements.
The method works when the minimum is truly the goal. It goes wrong when the work involves judgment that the requirement cannot capture in pass or fail terms, and the buyer receives a technically acceptable product that does not answer the real question.
What it means for program offices. Write acceptability standards that a technical evaluator can apply without guessing. If a methodology must meet a specific standard, name it. If certain experience is required, define it. Anything you leave undefined will be met at its cheapest interpretation, and that is the bargain this method makes on purpose.
What it means for firms. Read the evaluation section first. If the award is decided on price among acceptable offers, the work is to be clearly acceptable on every factor and priced to win. Extra features earn nothing. A firm that cannot do the work profitably at a competitive price for the defined scope should not chase the award with a proposal it knows will lose.
Local governments buying specialist review on call
Towns, cities and counties face a steady flow of technical submissions they are obliged to review: development applications with traffic and drainage studies, wireless facility applications on federal shot clocks, utility and infrastructure proposals, data-heavy grant reports and technology procurements. Few local governments employ every specialist those reviews require. The public record shows them responding with on-call arrangements: a qualified list or a set of master agreements, followed by task orders issued as each review comes in.
These solicitations typically ask for qualifications, hourly rates by role, turnaround commitments and conflict-of-interest disclosures, rather than a full technical approach. Some states require qualifications-based selection for certain professional services, which shapes how price enters the decision. Many arrangements are funded through applicant deposits or fees, so the review cost passes to the applicant rather than the general fund.
What it means for local buyers. On-call works when the task order process is fast and the scope of each review is clear. Define the turnaround you need against the statutory or policy deadline, the format of the review memo, and who the reviewer answers to. Require disclosure of any work for applicants in the same jurisdiction.
What it means for firms. Getting on the list is only the first step. Task orders go to the reviewers who answer fast, write memos a planner can put in front of a council, and never miss a shot clock. Reliability on the first three orders decides the next twenty.
Health agencies buying forecasting and economics
Public health agencies at every level are buying forecasting and economic analysis as distinct services rather than as a section of a larger evaluation contract. Solicitations ask for disease and demand forecasts with stated uncertainty, cost-effectiveness and budget impact analyses for programs and interventions, and models of uptake under different outreach strategies. Many specify the analytic perspective, such as health system or societal, and the standards the work should follow.
The shift reflects how these analyses are used. A forecast that informs staffing or supply decisions, or an economic case that supports a budget request, needs to be timely, transparent and reproducible, and it often needs to be updated as new data arrive.
What it means for program offices. Specify the decision the analysis supports, the perspective, the time horizon and the update cadence. Ask for code and documentation as deliverables so the work can be rerun and reviewed. Require that assumptions and data sources be stated in plain language for non-technical readers.
What it means for firms. Methods matter, but so does communication. A forecast with honest uncertainty and a clear explanation of what drives it is worth more to a health officer than a precise number with no context. Show reproducible work and name the analysts who will do it.
Outreach and data systems in one program
A growing number of programs combine people working in communities with the systems that record and measure that work. Workforce programs, housing assistance, public health outreach, benefits enrollment and transportation programs all show the pattern. A single solicitation may ask for navigators or outreach staff, a case management or tracking system, reporting dashboards and an evaluation of results.
Buyers combine these because the parts depend on each other. The outreach generates the data, the system shapes what outreach staff record, and the evaluation depends on both. When they are bought separately, the definitions drift and the evaluation ends up measuring what the system happened to capture.
What it means for program offices. Write the requirement around the program outcome, then name the cross-cutting deliverables explicitly: a shared data dictionary, an integrated schedule and an end-to-end check of the reported numbers. Ask offerors how outreach staff will use the system in the field, not just what the system does.
What it means for firms. These awards favor teams that can integrate fieldwork and technology under one accountable lead, with named specialists for each discipline. Show how the pieces connect, who owns the seams, and how data quality is maintained from first contact to final report.
The patterns at a glance
| Buying pattern | What the solicitation looks like | What it asks of the buyer |
|---|---|---|
| Simplified acquisition or direct award | Short statement of work, request for quotes, fast evaluation, purchase order | Clear deliverables and a stated basis for comparing quotes |
| Lowest price technically acceptable | Pass or fail technical factors; lowest acceptable price wins | Acceptability standards precise enough to apply without judgment calls |
| On-call specialist review | Qualifications, rates, turnaround and conflict disclosures; task orders as needed | A fast task order process and a defined review format and deadline |
| Forecasting and economic analysis | Stated decision, perspective, horizon and update cadence | Reproducibility requirements and plain-language documentation of assumptions |
| Outreach paired with data systems | One program covering field staff, a tracking system, reporting and evaluation | Named integration deliverables and a single accountable lead |
What this means for program offices writing requirements
The common thread across all five patterns is that the requirement document carries more weight than ever. Faster procedures and simpler evaluations shift the burden of clarity onto the statement of work. Use this list when drafting.
- State the decision the work supports, not just the tasks
- Choose the evaluation method to fit the work: LPTA only when the minimum is the goal
- Define deliverables by content and format, with review periods built into the schedule
- Say what data and access the government will provide, and when
- For mixed work, name the integration deliverables and ask who owns them
- Ask for named people and hours on the roles that require judgment
- Run market research first, such as a request for information or sources sought notice, to test whether the scope is buyable as written
What this means for firms responding
Read the evaluation criteria before anything else, and build the response around them. For simplified buys, answer quickly and specifically. For LPTA, be clearly acceptable on every factor and priced to win. For on-call lists, invest in reliability on the first orders. For forecasting and economics, show reproducible methods and plain explanations. For mixed programs, show how the pieces fit and who owns the whole.
In every case, name the people who will do the work and show their hours. Buyers across all five patterns are asking, in one form or another, who exactly they are hiring.
Answer the early notices as well. A sources sought notice or a request for information is the program office testing whether its scope is buyable and who can do it. A specific, short response, naming the method, the people and any risk in the draft scope, often shapes the final requirement. Firms that wait for the solicitation inherit whatever the early respondents helped write.
Where these patterns are visible
Federal opportunities and award notices are on SAM.gov, searchable by product and service code, NAICS code and set-aside. Federal obligations by recipient and agency are on USAspending.gov. State procurement portals post solicitations and awards, and city and county council agendas publish the contracts they approve, often with the staff report that explains why. Reading a dozen recent solicitations in your own subject area is the fastest way to see how your buyers write requirements.
What has not changed
For all the movement in procedure, the fundamentals of buying expert work are the same. A clear requirement gets better offers. An evaluation that matches the work picks the right firm. Named, experienced people do better work than unnamed ones. And the program office that invests a few days in a good statement of work saves weeks in performance.
The buyers who get the best results in every pattern do the same three things. They talk to the market before they write, they describe the decision the work supports in plain words, and they ask, by name, who will do it.
The patterns in 2026 make those fundamentals more important, not less. When procedures are faster and evaluations are simpler, the requirement is what stands between the buyer and an award that meets the letter of the document but not the need behind it.
Frequently asked questions
Streamlined federal buying methods for purchases up to the simplified acquisition threshold, which has been $350,000 since October 1, 2025. They allow requests for quotes, shorter evaluations and faster awards than a full source selection, usually ending in a purchase order.
When the requirement can be defined precisely and the government gains little or no value from an offer that exceeds the minimum. It works for defined services and goes wrong for work that depends on judgment the requirement cannot capture in pass or fail terms.
Often through on-call arrangements: a qualified list or master agreements awarded on qualifications and rates, followed by task orders for each review. Many are funded by applicant deposits or fees, and turnaround is set against the deadline that applies to the application.
Because the parts depend on each other. Outreach generates the data, the system shapes what staff record, and evaluation depends on both. Buying them together keeps definitions consistent and gives one lead responsibility for the whole result.