- A Practical Procurement Transformation Roadmap - September 8, 2026
- Purchase Requisitions and Purchase Orders Compared - September 8, 2026
- Spend Under Management Formula and Improvement Strategy - September 8, 2026
For U.S. federal acquisitions, the general micro-purchase threshold is $15,000 and the general simplified acquisition threshold is $350,000, effective October 1, 2025. Exceptions and special situations use different thresholds.
Which authoritative sources establish the applicable micro-purchase and simplified acquisition thresholds in 2026?
In practical terms, acquisition value sets the operating boundary, general threshold identifies what the organization is trying to protect or improve, and special exception provides the facts needed to test the opportunity. Competition rule should not be calculated or classified until the population, period, currency or unit, exclusions, and decision owner are explicit.
Decision boundary
- The effective federal thresholds only: Use the effective federal thresholds only to define the boundary and decision consequence; retain the dated source and explain why the evidence is sufficient.
- Official threshold-change notice: Use official threshold-change notice to define the boundary and decision consequence; retain the dated source and explain why the evidence is sufficient.
- The general thresholds from statutory or agency-specific exceptions: Use the general thresholds from statutory or agency-specific exceptions to define the boundary and decision consequence; retain the dated source and explain why the evidence is sufficient.
- Effective dates: Use effective dates to define the boundary and decision consequence; retain the dated source and explain why the evidence is sufficient.
- Acquisition value: Use acquisition value to define the boundary and decision consequence; retain the dated source and explain why the evidence is sufficient.
Evidence and application
A practical application makes the boundary visible. A contracting professional first identifies the acquisition type, place of performance, emergency or contingency status, and applicable FAR or agency supplement before selecting the method and documentation path. The decision file should distinguish observed facts from accepted assumptions, preserve rejected alternatives, and name the evidence that would reopen the decision about set-aside requirement.
The main failure is a decision built on the wrong population or evidence, not a shortage of terminology. Applying a general threshold without checking exceptions, aggregation rules, set-asides, funding, or agency policy can invalidate the purchasing approach. A reviewer should be able to trace acquisition value to set-aside requirement, identify the accountable owner, and see how the expected result will be verified after implementation.
Documentation can remain proportionate to acquisition value. Low-value and reversible general threshold work may use a lighter record, whereas material, regulated, safety-critical, or continuity-sensitive work needs deeper validation. Either treatment of general threshold must be justified by evidence that fits the actual conditions of this decision.
The current FAR text lists a general micro-purchase threshold of $15,000 and a general simplified acquisition threshold of $350,000. Those values became effective October 1, 2025 and remain visible in the 2026 FAR. Construction, labor-standard work, contingency operations, disaster response, humanitarian operations, and agency supplements can produce different thresholds, so the transaction facts must be classified before a value band is selected.
How do FAR definitions and Part 13 procedures interact with each threshold band?
The operating sequence converts acquisition value into agency supplement through explicit handoffs. At each general threshold stage, the record needs an input, responsible role, acceptance test, and usable output; an activity list without those four items is uncontrolled.
Operating sequence
1 — Acquisition value. Use acquisition value to connect the input to a named output and acceptance gate; retain the dated source and explain why the evidence is sufficient.
2 — General threshold. Use general threshold to connect the input to a named output and acceptance gate; retain the dated source and explain why the evidence is sufficient.
3 — Special exception. Use special exception to connect the input to a named output and acceptance gate; retain the dated source and explain why the evidence is sufficient.
4 — Competition rule. In practice, verify competition rule at the authoritative source and record its scope and effective date in the workflow. Mandatory pass-fail requirements tied to competition rule must remain separate from scored preferences.
5 — Set-aside requirement. Use set-aside requirement to connect the input to a named output and acceptance gate; retain the dated source and explain why the evidence is sufficient.
6 — Market research. For market research in the workflow, preserve the searched population, comparable requirement, response date, exclusions, alternatives, and supported decision. The retained search and response records make the market research assessment in this workflow independently reviewable.
7 — Agency supplement. Use agency supplement to connect the input to a named output and acceptance gate; retain the dated source and explain why the evidence is sufficient.
Figure: federal acquisition threshold workflow — evidence, decisions, owners, and outputs across the operating flow.
Handoffs and exceptions
One practical sequence works as follows: A contracting professional first identifies the acquisition type, place of performance, emergency or contingency status, and applicable FAR or agency supplement before selecting the method and documentation path. The sequence stops when evidence for general threshold is incomplete instead of passing ambiguity downstream. Rework tied to special exception is coded to its producing stage, separating capacity constraints from definition, approval, supplier-response, or data-quality defects.
Exceptions need their own route. Urgency around acquisition value may compress timing, but it does not erase authority, requirement clarity, commercial comparison, receipt, or post-award evidence. The person accountable for market research defines who can authorize a deviation, which minimum checks remain, and when work returns to the standard path.
Which competition, documentation, approval, and payment methods apply as purchase value increases?
A usable analytical layer makes special exception, competition rule, and set-aside requirement comparable. Options for competition rule must share one population, period, unit, currency basis, inclusion rule, and scenario logic; otherwise even a precise score can support the wrong choice.
Measurement and comparison
- A practical table for micro-purchases: Use a practical table for micro-purchases to make the evidence comparable across options; retain the dated source and explain why the evidence is sufficient.
- Acquisitions above the mpt through the sat: Use acquisitions above the mpt through the sat to make the evidence comparable across options; retain the dated source and explain why the evidence is sufficient.
- Acquisitions above the sat: Use acquisitions above the sat to make the evidence comparable across options; retain the dated source and explain why the evidence is sufficient.
- Documentation: Use documentation to make the evidence comparable across options; retain the dated source and explain why the evidence is sufficient.
- Competition: In practice, verify competition at the authoritative source and record its scope and effective date in the analysis. Mandatory pass-fail requirements tied to competition must remain separate from scored preferences.
Sensitivity testing should concentrate on variables capable of changing set-aside requirement: volume, mix, timing, price, utilization, recovery, risk, or threshold assumptions as applicable. Showing a base case, downside case, and competition rule break point reveals whether this choice is robust or depends on one optimistic input.
Interpretation and control
The analytical owner should lock the source version, retain calculation logic, and document overrides. A second reviewer reconciles the output to acquisition value and tests whether the criteria for set-aside requirement were applied as approved. If a small assumption shift changes the result, the recommendation about competition rule is conditional rather than certain.
Field or test | Required definition | Evidence | Acceptance control |
A practical table for micro-purchases | State scope, unit, owner, period, and permitted exceptions for a practical table for micro-purchases | Dated source record tied to special exception | Reject or escalate when evidence cannot support special exception |
Acquisitions above the mpt through the sat | State scope, unit, owner, period, and permitted exceptions for acquisitions above the mpt through the sat | Dated source record tied to competition rule | Reject or escalate when evidence cannot support competition rule |
Acquisitions above the sat | State scope, unit, owner, period, and permitted exceptions for acquisitions above the sat | Dated source record tied to set-aside requirement | Reject or escalate when evidence cannot support set-aside requirement |
Documentation | State scope, unit, owner, period, and permitted exceptions for documentation | Dated source record tied to market research | Reject or escalate when evidence cannot support market research |
Competition | State scope, unit, owner, period, and permitted exceptions for competition | Dated source record tied to agency supplement | Reject or escalate when evidence cannot support agency supplement |
Which effective-date, exception, agency-supplement, and audit checks keep threshold guidance current?
Control design begins with the failure that matters: Applying a general threshold without checking exceptions, aggregation rules, set-asides, funding, or agency policy can invalidate the purchasing approach. The response should combine prevention near acquisition value with detection in workflow, transaction, supplier, invoice, or performance data, and name the owner of correction.
Preventive safeguards
- Source ownership: The control design should assign source ownership to one accountable owner, identify consulted and informed roles, and define what the receiving role must accept. Documented acceptance for source ownership prevents an ownership gap in this control design.
- Effective-date tracking: Use effective-date tracking to pair prevention with an exception and escalation path; retain the dated source and explain why the evidence is sufficient.
- Annual review: Use annual review to pair prevention with an exception and escalation path; retain the dated source and explain why the evidence is sufficient.
- Agency-supplement checks: Use agency-supplement checks to pair prevention with an exception and escalation path; retain the dated source and explain why the evidence is sufficient.
- Templates: Use templates to pair prevention with an exception and escalation path; retain the dated source and explain why the evidence is sufficient.
Detection and correction
A material set-aside requirement exception needs four records: observed condition, expected value, authorized disposition, and closure evidence. Trend set-aside requirement exceptions by root cause instead of treating each as an isolated task. Repeated defects in set-aside requirement or market research indicate that process, master data, contract, training, or supplier action needs redesign.
Controls over market research must remain proportionate to this decision. Too many market research approvals can push users outside the process, while automatic approval can conceal bad master data. Monitor cycle time with compliance, sample approved and rejected cases, and test whether corrective actions changed agency supplement rather than merely closing a ticket.
How can federal buyers explore Hubzone Depot's Spotbuy service for eligible product requirements?
For the use case, Hubzone Depot describes SpotBuy as a route for one-off and non-catalog requests: the buyer submits a need, sourcing specialists compare available channels, and the buyer receives an itemized quote with cost and lead-time information. In practice, this discrete sourcing support does not transfer the buyer's policy, competition, approval, contract, funding, receipt, or risk responsibilities tied to set-aside requirement.
Service fit
- Defined scope: The request evaluated can be bounded using acquisition value and a clear completion criterion.
- Comparable evidence: The buyer can compare returned information against special exception on the same unit and time basis.
- Decision authority: An internal owner remains accountable for set-aside requirement and any exception or award related to this decision.
- Operational follow-through: Receiving, payment, credit, or performance evidence can confirm agency supplement after action under the approved approach.
- Proportionate route: The effort matches value, urgency, complexity, regulatory exposure, and reversibility.
Intake and buyer control
An intake package should include a precise item or service requirement, quantity, specifications, acceptable substitutions, delivery location, need date, budget context, approval status, and quote-comparison fields. Resolve missing fields in the intake before comparing quotes or audit findings, because different assumptions about acquisition value, service, timing, quantity, or eligibility can make similar-looking results non-comparable.
The next step is to review Hubzone Depot's SpotBuy page and request only the information needed to test the acquisition value use case. The buyer documents the evaluation method in advance, retains its own approvals, and confirms implementation or credit evidence before reporting an outcome.
Conclusion: What should federal buyers remember about procurement thresholds in 2026?
The practical conclusion is to connect the original need to an implementable, testable decision. That requires the boundary for acquisition value, the evidence behind special exception, the approval criteria for set-aside requirement, and the owner who will verify agency supplement.
Implementation priorities
- Define: In practice, state the population, period, inclusions, exclusions, and authority for acquisition value.
- Verify: In practice, reconcile special exception to a dated source and distinguish facts from assumptions.
- Decide: Apply set-aside requirement consistently and preserve the rejected alternative.
- Implement: Assign market research and specify the required acceptance evidence.
- Review: Measure agency supplement after implementation and reopen the decision when a material condition changes.
Treat the threshold as a routing checkpoint, not legal advice; verify the current FAR text, agency supplements, and facts of the acquisition. The recommendation is strongest when the current requirement, policy or contract, source dates, assumptions, and implementation capacity are verifiable. A material change affecting acquisition value, market availability, regulation, carrier rules, supplier capability, or data quality can change the conclusion.
Decision rule and sources
A final review of this decision should not rely on one score. The set-aside requirement record should explain why the chosen path is acceptable, identify residual risk and its owner, and set the next review date or trigger. The resulting record turns agency supplement into evidence for the next decision instead of forcing the organization to reconstruct its reasoning from email.
Sources
- Acquisition.gov, FAR Threshold Changes
- Federal Acquisition Regulation Part 2, Definitions
- Federal Acquisition Regulation Part 13, Simplified Acquisition Procedures
- Federal Acquisition Regulation Part 10, Market Research
- Hubzone Depot, SpotBuy
Decision checkpoint | Evidence to retain | Next action |
Acquisition value | Current, dated record showing acquisition value | Confirm scope and baseline before committing resources |
Special exception | Current, dated record showing special exception | Challenge alternatives and source quality |
Set-aside requirement | Current, dated record showing set-aside requirement | Approve only against explicit criteria |
Market research | Current, dated record showing market research | Assign implementation and exception ownership |
Agency supplement | Current, dated record showing agency supplement | Review results and reopen the decision when conditions change |
