August 4, 2024
10 min read

FedSubK Feature: Lowest Price Technically Acceptable (LPTA) - What is it Good For? Absolutely Nothing When Not Used Correctly.

FedSubK Features
FedSubK Features

Who needs a quiet Sunday? I guess I decided I didn’t since I got a slew of questions related to my response to Jackie Robinson-Burnette’s post on LPTA a while back where she posted a picture of a partial started house addition with a blue tarped roof with the tag line “Covered Deck. Lowest Priced Technically Acceptable”.  (By the way, great picture, Jackie. It illustrated the concept most people have about LPTA perfectly. You can find Jackie’s post and my comment here.)

If you know anything about me it’s--

(1) I love a chance to talk about the FAR, and

(2) source selection is one of my favorite topics because it was my favorite thing to do as a Contract Specialist and Contracting Officer.

And I did A LOT of source selections. So much so I was THE person that reviewed and critiqued all evaluation criteria written for service contracts within my branch, division, or business line at the three agencies where I worked. I was able to write evaluation criteria that were protest-proof, and I trained evaluation teams on how to evaluate criteria correctly and document their evaluation in such a manner that there were no protest gaps. I was good at it because I always wrote / reviewed solicitations from the perspective of not only the Government but the industry perspective and how it could be interpreted. This allowed us to shore up gaps before moving forward.  

And this takes me back to one of the most controversial and polarizing things in source selection, use of the Lowest Price Technically Acceptable (LPTA) evaluation method. If you’ve been in the Federal marketplace for any amount of time you know what it is and the history behind its popularity and bad rap. For those that don’t, let’s go over it quickly.  

What is LPTA?

FAR Subpart 15.101-2 covers the LPTA process and states LPTA is a source selection process that is right for use when the best value is expected to result from selection of the “technically acceptable proposal with the lowest evaluated price”.  In the case of LPTA, cost tends to be the driver in the selection since technical superiority is not desired, only that the contractor meets a minimum acceptability threshold as set in the solicitation. The solicitation will also specify the award will be made on the basis of the lowest evaluated price of proposals meeting or exceeding the acceptability standards for non-cost factors.

What does that mean? Ultimately, if you meet the technical thresholds set across the board and your price is the lowest, you win! It’s a way to verify that a company can meet minimum technical requirements though budget is the true driver for the acquisition.

So, let’s break that down a little more.

Technical Acceptability.  The level of technical acceptability is determined by the Government and evaluation factors must describe technical acceptability in terms of objective measures and/or standards. When evaluating only “Pass/Fail”, “Go/No Go”, or “Green/Red” scores are used. To be among offerors considered for contract award, an offer must receive a “Pass”, “Go”, or “Green” in every factor and subfactor. Those offers move forward for the evaluation of price. It only takes one “Fail”, “No Go”, or “Red” rating and the offer is eliminated from further consideration. Because there is no subjectivity in this type of evaluation method, offers are not ranked in terms of technical superiority.

Conversely, when using the tradeoff method, factors are written such that subjective analysis and review results in various degrees of technical acceptability which are expressed as adjectival ratings, colors, or numeric scores within a range. A Competitive Range is established and only those offers with the most likelihood of award continue on into negotiations with the Government.

While there is no room for subjectivity in the LPTA technical review, trust me, evaluators will try to sneak it in. For example, they will use ratings like “Pass++”, “Go – “, and “Bright Green”.  And you guessed it, that doesn’t fly. They get sent back to the evaluation room to do it all again and put offers clearly into one of the two categories for every factor.

In LPTA, those offers that meet the technical acceptability thresholds then moved on to the price evaluation.

Lowest Evaluated Price.  Notice the word “evaluated”. This means that the agency may review the price along with any other price factors as stipulated in the solicitation for those offers that achieved a “Pass”, “Go”, or “Green” in all technical factors.

In some instances, the term “evaluated price” means the actual price offers. But in other instances, the Government may add other price factors into the mix (and as disclosed in the solicitation) to arrive at an evaluated price, or a price that may not reflect the actual price(s) proposed but is used to determine the awardee.

Evaluated prices are ranked in order from low to high. The technically acceptable offer with the lowest evaluated price is the apparent contract awardee.

When is LPTA Used?

It differs for Department of Defense (DoD) and non-DoD agencies. Section 880 of the John S. McCain National Defense Authorization Act (NDAA) for Fiscal Year (FY) 2019 states that, except for DoD, LPTA shall only be used when ALL the below are met—

(1)  The minimum technical acceptability requirements can be comprehensively and clearly described.

(2)  There is no realized, or only minimal, value from a proposal that exceeds the minimum technical or performance requirements.

(3)  Technical proposals will require no, or only minimal, subjective judgment by the source selection authority as to the desirability of one offeror's proposal versus a competing proposal.

(4)  There is a high degree of confidence that reviewing the technical proposals of all offerors would not result in the identification of characteristics that could provide value or benefit.

(5)  The lowest price reflects the total cost, including operation and support, of the product(s) or service(s) being acquired.

(6)  The Contracting Officer determines in writing the circumstances that justify the use of the LPTA process.

In the same law, except for DoD, Contracting Officers are directed that they shall AVOID, to the maximum extent practicable, the use of LPTA for procurements that are predominantly for the acquisition of—

  • Information technology services,
  • Cybersecurity services,
  • Systems engineering and technical assistance services,
  • Advanced electronic testing,
  • Audit or audit readiness services,
  • Health care services and records,
  • Telecommunications devices and services,
  • Knowledge-based professional services,
  • Personal protective equipment, or
  • Knowledge-based training or logistics services in contingency operations or other operations outside the United States, including in Afghanistan or Iraq.

The Defense FAR Supplement (DFARS) Subpart 215.101-2-70 states the same rules apply within DoD but adds* that the use of LPTA shall also only be when—

  • No, or minimal, additional innovation or future technological advantage will be realized by using a different source selection process,
  • Goods to be procured are predominantly expendable in nature, are nontechnical, or have a short life expectancy or short shelf life.
  • The contract file includes a determination that the lowest price reflects full life-cycle costs of the product(s) or service(s) being acquired.

*(as amended by Section 822 of the NDAA for FY2018 (Pub. L. 115-91))

In addition, DoD outlines the following prohibitions:

  • Contracting Officers shall not use the lowest price technically acceptable source selection process to procure items designated by the requiring activity as personal protective equipment or an aviation critical safety item, when the requiring activity advises that the level of quality or failure of the equipment or item could result in combat casualties.
  • In accordance with section 832 of the National Defense Authorization Act for Fiscal Year 2018 (see 10 U.S.C. 4232), contracting officers shall not use the lowest price technically acceptable source selection process to acquire engineering and manufacturing development for a major defense acquisition program for which budgetary authority is requested, beginning in fiscal year 2019 and beyond.
  • Contracting Officers shall make award decisions based on best value factors and criteria, as determined by the resource sponsor (in accordance with agency procedures), for an auditing contract. The use of the lowest price technically acceptable source selection process is prohibited (10 U.S.C. 240f).

Is Past Performance Evaluated under LPTA?

Unless the Contracting Officer documents the file in accordance with FAR Subpart 15.304(c)(3)(iii) that past performance is not an appropriate evaluation factor for the acquisition, it will be evaluated. ed not be an evaluation factor in lowest price technically acceptable source selections.

If the Contracting Officer elects to consider past performance as an evaluation factor, it will be evaluated like any other solicitation in accordance with FAR Subpart 15.305 but there will be no comparative assessment made. The same ratings of "Acceptable", "Unacceptable" (or similar), and "Neutral" (for no record of past performance) will be used.

If the Contracting Officer determines that a small business’ past performance is not acceptable, the matter shall be referred to the Small Business Administration (SBA) for a Certificate of Competency (COC) determination, in accordance with the procedures at FAR Subpart 19.6.

How an LPTA Evaluation is Conducted.

As is standard for all source selection procedures, the technical and price evaluations are conducted separately by different teams called the Technical Evaluation Board (TEB) and the Price Evaluation Board (PEB), who combined are known as the Source Selection Evaluation Board (SSEB). The TEB and the PEB do not show the findings of their team to the other and non-disclosure agreements are signed by all evaluators and non-voting board members (i.e., advisors).

After the Boards receive their training on how to conduct the evaluation, in accordance with the Source Selection Evaluation Plan (SSEP) (which is developed prior to the receipt of proposals), the TEB will receive copies of each offer and worksheets to document an independent review and assessment of each offer in terms of meeting the technical acceptability thresholds of each factor (and subfactor). TEB members will individually document their rationale and write down the pages of the offer and quote offer language to substantiate their position.

Once the individual reviews by TEB members are completed, the TEB will meet as a group and discuss their individual ratings and rationales until they come to a consensus evaluation rating and agree on the supporting documentation within the offer (or missing from the offer) for their findings. Typically, when using the LPTA method, once a “Fail”, “No Go”, or “Red” rating is received by an offer it is documented and the offer removed from further review and consideration for award without the remaining factors / subfactors being evaluated.  Review of all factors continues for the remaining offers until all offers remaining are either eliminated from further consideration or they have received  “Pass”, “Go”, or Green ratings on all factors.

The TEB completes consensus rating sheets. A final consensus TEB report of findings is prepared to summarize the process, individual and consensus ratings, and any key discussions and decisions made by the TEB, any dissenting opinions, and to summarize the outcome. The consensus evaluation report with all supporting documentation (to include individual and consensus worksheets and notes) is provided to the Contracting Officer for review and feedback.  

The PEB will do its separate evaluation related to the price requirements of the solicitation similarly to the process used by the TEB (i.e., individual reviews, then by consensus, documented and a report written). Upon completion, a PEB consensus report is created and provided to the Contracting Officer, if the Contracting Officer did not take part in the price review directly.

The Contracting Officer then reviews both reports and the supporting documentation, discusses any discrepancies found, asks for more information or documentation where needed, and then writes the Source Selection Decision document outlining the process, each Boards’ findings, and the contract award decision. This decision document is then signed by the Source Selection Authority (SSA) which may be the Contracting Officer themselves but may be one level above the Contracting Officer when certain dollar thresholds are met.

Give Examples of LPTA Technical Evaluation Criteria.

“Vendor shall submit a copy of the certification documenting they are a current licensed KDHE UST contractor and tightness tester. Failure to submit this certification will cause the vendor to be rated technically.”

“Contractor shall name and provide for least one currently certified Diagnostic CT/Radiological Technologist available for the duration of the contract for the work hours shown. Include all required information as listed below with supporting credential documentation as listed in the Statement of Work. Failure to provide any document in the personnel package will result in this factor being rated as “Unacceptable.””

“The Altitude Simulation Unit to be provided must meet the following product specifications:

o   Interior dimensions (minimum dimensions): 15” x 15” 15”

o   Exterior dimension (maximum dimensions): 60” (W) x 30” (D) x 30” (H)

o   Pressure range (minimum): 1,000’ – 8,000’

o   Features a controller unit that will monitor pressure within the chamber, recognize when pressures have diverged from a given setting, and then re-pressurize as needed.

o   Chamber fitted with glove access for use while pressurized.

o   Whole system needs to include the pump, controller unit, and chamber.

Failure to provide a specification sheet for validation of these requirements will result in the elimination of your offer from further consideration.”

Can a Solicitation include both LPTA and Other Evaluation Criteria?

Yes, however, it is not a recommended practice. This occurs most often when a requirement must be verified through submission of a document such as a certain certification, insurance rating, or other industry standard.

Is the LPTA Evaluation Method Being Used Successfully by Government?

Well…that’s THE loaded question and where the LinkedIn post by Jackie Robinson-Burnette and my answer takes us. My opinion is--

  • The Government uses LPTA.
  • The Government currently awards contracts using LPTA methods.
  • BUT (and it's a big one) the Government isn’t doing it correctly.

What the Government labels as LPTA criteria really isn’t measurable simply using “pass/fail” ratings. This is why TEBs tend to play around with ratings to find a way to describe for the Contracting Officer the degrees in which offers vary. This is, as Randy Lange wrote in his comment to the post, “…LPTA disguised as “best value”.”  And it drives me crazy!

There are also several experiences on both sides of the fence -- industry and Government -- and takes on it. From the Government taking the easy way out, Contracting Officers not having the time to babysit Project Managers who cannot come up with objective measures, and industry bystanders who have been battle-worn by the process when it’s not deployed correctly.

Now what do you think?  What is LPTA good for? Absolutely nothing? There are still very good and reasonable use cases for LPTA, when done right!

Regardless of where you stand on the LPTA debate, now you know what LPTA is supposed to be good for and how it is supposed to work. But until the Government can use it correctly, LPTA should be used for absolutely nothing.  

(August 2024)

Share this post
FedSubK Features
Shauna Weatherly

View related posts

August 25, 2026

How Early is "Early"? (Weatherly the RFO - Part 5)

"We need to engage the agency early."

It's hard to argue with that.

But what does "early" mean, actually? I mean – in Government terms and from their viewpoint.

Most companies are going to say “early” means before the solicitation is released. A lot of GovCons on LinkedIn talk all about getting in there while acquisition planning is going on. They say that’s the window when key decisions are made about contract types, competition pools, and evaluation factors. Others say it has to be well before acquisition planning.  

Listen to those people!

They are the ones in industry that “get it”!

The best market research – and industry’s best opportunity to help inform the discussion – happens before acquisition planning formally begins.

Reading through the Revolutionary FAR Overhaul (RFO), and as a former KO/CO, I had hoped it would catch up and understand that “early" is too narrowly defined. Maybe I get it now from being out here in industry for a number of years fully immersed in the talk of capture and pipeline development.

Knowing the federal marketplace should be an ongoing acquisition competency, not an activity tied to a single procurement.

Technically, FAR Part 10 is gone but experienced contracting officers understand that market research and acquisition planning belong together. They influence each other constantly. From that perspective, integrating the regulatory text of FAR Part 10 into Part 7 recognizes that connection.

But putting market research in Part 7 may reinforce another problem; treating it as something that begins when acquisition planning begins. Market knowledge should lead acquisition planning, not begin with it.  

A good requirement starts with knowing the market well. It’s when your Program Manager starts talking to you a good six months before the purchase request hits that a project is coming, prepping you for the drop. They give you intel on who the major players are, how commercial buying might fit, and outside influences like economic conditions or materials shortages.

From there, I can start talking to the Small Business Specialist and looking at the likely small business pool. I can talk with the estimator about likely dollar values and start thinking about contract type, pricing structure, clauses, and ways to streamline the procurement.

Right there.

Did you see that?

I’m already thinking about the competition pool, contract type, and pricing structure and there isn’t any talk about a purchase request or acquisition strategy yet. That’s what EARLY is.  And when contracting is included in programmatic budget discussions, those wheels turn even earlier.  And even with that six-month head start, it’s only useful if I’m not starting from zero.

And one thing the RFO is telling us very clearly now is that there is no requirement to conduct market research using a specific method or set of methods.  There is no mandate to issue a Sources Sought or Request for Information (RFI).

The RFO doesn’t prescribe a method. It tells the acquisition team to conduct market research appropriate to the circumstances under certain scenarios, and to engage in responsible and constructive exchanges without creating an unfair competitive advantage or violating procurement integrity requirements. (Proposed rule RFO 7.201(b)).  

The method isn’t the point anymore. The quality of the information and the judgment applied to it is.  

With that I think a mindset shift needs to take place for the RFO to be successful. And when the FAR prescribes less about how to get that information, what the acquisition team already knows becomes more important, not less.

Look at market research as continuous learning, not a one-time action.

Industry watches markets continuously because it has to. Government acquisition teams tend to examine them one procurement at a time. Hopefully it's not just me that sees how that creates an information gap about the market before acquisition planning ever begins.

The market research contracting personnel are all familiar with is done to support an individual acquisition. It informs the strategy, contract type, commerciality determination, competition pool, pricing approach, and documentation supporting those decisions.

Continuous market learning does something different. It builds knowledge before there is an acquisition that demands it. It means understanding how an industry, its suppliers, technologies, pricing practices, and commercial business models are changing before a requirement forces us to ask.

So let’s get back to that word – “Early”

Earlier and more continuous engagement raises the obvious question about how does the Government keep it fair? The answer hasn’t changed. Engage ethically, document, protect procurement integrity, and don’t give individual firms an unfair competitive advantage.

Continuous market learning should never become continuous market favoritism.

In fact, broader and more continuous market awareness should make acquisition teams less dependent on what they learn from the handful of vendors who happen to show up for a particular procurement.

From the Contracting Officer's Chair

Using continuous market learning would create a focused ongoing procurement effort to understand industries, technologies, suppliers, and commercial business practices, whether or not an active procurement is immediately on the horizon.

Because of lumbering procurement timelines, many believe starting market research two years out is ample time to adjust to the market changes.

Yeah, I’ve fallen into that trap. It doesn’t work like that. Continuous market learning moves some of that discovery upstream, before changing direction becomes an acquisition problem. Or, as we call it in Contracting -- our problem.

Well-seasoned COs and KOs know instinctively continuous market learning is a much-needed best practice, but they aren’t always allowed to go to key industry events (because no travel funds), they don’t have time to meet with vendors (because of an end of fiscal year that goes on for an entire quarter), and they don’t have access to trade publications (because the Government won’t buy them a subscription). They try to pay attention to how markets are changing. But by the time the acquisition team discovers how much the market has changed, changing course can mean rethinking the solicitation, evaluation approach, competition strategy, and/or pricing structure. And anyone who has sat in the CO/KO chair knows the lift required to make those changes on an already compressed schedule.  

The RFO’s FAR Companion says that “…acquisition teams should approach market research as an incremental process that builds understanding step-by-step.” That’s still looking at market research tied to an individual acquisition. The RFO writers had an opportunity to take the next step and distinguish procurement specific market research from continuous market learning. And they didn’t.  

Ugh – heartbreaking!  

But by integrating market research into acquisition planning in the text, and by relying more heavily on professional judgment, it creates space for the acquisition workforce to -- themselves -- think beyond procurement specific research to the possibility of continuous market learning. That gives agencies and programmatic teams within agencies a lot of leeway to create their own best practices.

If / how that happens is something to watch. BUT…

What the RFO Missed

RFO writers put their confidence in the acquisition workforce. Less prescription in process = more reliance on professional judgment. But judgment doesn't develop automatically with a new reg; I’ve been doing this long enough to know and live that. It comes from trusted and experienced leaders across the acquisition workforce – and by workforce I mean Contract Specialists (CS), COs, KOs, Contracting Officer’s Representatives (CORs), PMs, and Small Business Specialists. Those leaders step up and teach newer team members how to ask better questions, recognize bias, separate market understanding from vendor preference, and remain curious without compromising fairness in their research and engagements.

But the tools the RFO FAR Companion suggests aren’t starting points, not market knowledge. SAM.gov, CPARS.gov, FPDS.gov (which is now SAM Contract Awards and SAM Data Bank Reports), SBS, and other tools and datasets on Acquisition.gov and the GSA Acquisition Gateway don’t fully hit the mark. Talking to counterparts in other agencies, reviewing existing contract databases, reading industry publications, and examining vendor websites or online product literature are sources of information. They aren’t a substitute for market knowledge.

Useful? Absolutely. Enough? Not even close.

Tools provide data. Engagement provides information. Experience turns both into market knowledge.

A couple of things…

The question “Have we conducted market research yet?" isn't the same as "What do we know about the current market?"

The first asks whether an acquisition step has been completed. The second asks whether the acquisition team is informed.

The first is a report. The second can change an acquisition.

See the difference?  

One of the unintended consequences of organizing market research as a separate FAR part was that it became easy to think of it as another acquisition milestone. Complete the market research, write it up, and move on and don't think about the market until the next buy.

The RFO has created an opportunity to break that habit. If we do break it, acquisition teams can begin acquisition planning informed by the market instead of using the start of acquisition planning to begin learning about it.

But, will we?

Acquisition Leaders – you have a challenge!

Five years from now, should market research still be something we conduct for an acquisition or will market knowledge finally be treated as a continuous learning acquisition workforce competency?  

-------------------------------------------------------------------------------

Author: Shauna Weatherly, President, Federal Subcontract Solutions LLC(dba FedSubK). Shauna is a small business advocate and owner of FedSubK. FedSubK exists to simplify federal contracting, empowering small businesses with practical, understandable resources. We bring first-hand experiences in Federal contracting from multiple perspectives derived from roles held both in and out of Government over almost four decades of Federal service.

Visit us at fedsubk.com to learn more about--

Getting Started in Federal Contracting: fedsubk.com/begin-your-journey-here

Solutions and Our Trusted Support Provider Network: fedsubk.com/solutions-services

Insights from a Contracting Officer: fedsubk.com/insights

Free Webinars and Resources: fedsubk.com/webinars-training

FAR News
August 12, 2026

Market Research Isn't About Checking A Box (Weathering the RFO - Part 4)

"I guess FAR Part 10 is gone."

I've seen statements like that in a few posts floating around LinkedIn. And yes, on the surface that's true.

But in practice, market research just became more important and has moved upstairs to live with FAR Part 7 where it belonged all along, in acquisition planning. It's now woven directly in there and no longer seen as a separate activity. I mean, as a Contracting Officer, this is how we have approached it for decades. Good acquisition planning always depends on good market research. You can't develop a sound acquisition strategy without understanding the marketplace you're buying from.

From my perspective, that's not a bad thing.

While acquisition planning encompassing market research is a change in structure, we really need to take it a step further and look at...Why did the Revolutionary FAR Overhaul (RFO) bring them together while simultaneously reducing much of the prescriptive language that historically guided how market research was conducted and documented?

For years, we taught acquisition planning and market research as two separate FAR parts. But they never really lived separately, though industry might think that:

First, the Government conducts market research then it plans the acquisition.

Not so quick.

If you’ve been around the inside of the Federal acquisition lifecycle as a member of the acquisition team – the requiring activity, the small business specialist, the end user, or in contracting – you know that's not how good acquisitions worked for real. Planning never stops once a need is put into the budget. It only ramps up on a trajectory that gets faster and steeper the closer to you to either the need date or the end of fiscal year. That trajectory includes market research throughout the pre-solicitation phase.

We used market research to shape, then adjust the acquisition strategy and acquisition plan with what we learned. And that learning didn’t always come in the form of an RFI. We refined requirements, reconsidered contract types, identified capable small businesses we hadn't previously considered, discovered commercial solutions that changed the direction of the procurement, and poured through acquisition history in our agency and others.

In other words, market research isn't one step.

It is always on your mind as the budget becomes known, the requirements start to materialize, and the opportunity becomes known to industry.

The RFO recognizes that reality by integrating market research now into FAR Part 7. That's a positive evolution. It reflects how acquisition professionals do the work.

But something else changed, too.

The rewritten framework is noticeably less prescriptive…intentionally. The FAR Council has been very clear that one of the objectives of the FAR re-write is to reduce unnecessary procedural requirements, simplify the regulation, and place greater reliance on professional judgment.

I understand that objective and I support it. BUT… I keep thinking about the fact that federal contracting isn't just about making good business decisions. It's about making decisions that are FAIR.

And those two things aren't always the same.

When people outside Government hear the word “process”, they often think “bureaucracy”. Federal employees like little hamsters on wheels running the cogs of a system where they are looking for ways to slow down, do less, take up more time, eat up more industry dollars, and short cut the system.

As a Contracting Officer, “process” to me meant “fairness”. And it provides certain tests you have to meet.

Could another company look at this acquisition and conclude it had a fair opportunity to compete?

Could GAO understand why we selected this acquisition strategy?

Could an Inspector General reconstruct our thinking?

Could my supervisor understand my rationale for this acquisition strategy?

Could I defend this decision six months from now if someone challenged it?

THAT STILL MATTERS.

Those questions are part of what makes federal procurement DIFFERENT from commercial buying, EVEN WHEN the Government's version of commercial processes are used.

It’s precisely why market research evolved into more than simply learning about the marketplace.

It also became one of the ways agencies demonstrated that acquisition decisions were informed, deliberate, and fair.

Not perfect, but fair.

From the Contracting Officer's Chair

One of the themes you'll continue to see throughout Weathering the RFO is a simple question: Why was this process or procedure there in the first place? That's very different from asking whether it was statutory.

Many of the historical procedures surrounding market research weren't created simply to generate more documentation. They evolved because they promoted thoughtful decision-making, encouraged agencies to explore commercial solutions, supported small business participation, and helped acquisition teams avoid unnecessarily restrictive requirements.

And most importantly, they created a record explaining how the Government arrived at its acquisition decisions.

Understanding why they evolved in the first place is equally important as putting process and procedure through a woodchipper. Because we all know – because it’s been said – that this is all about clearing perceived dead wood. But dead wood holds history. Trees grow through resilience. Every ring a year; a set of seasons that tested its endurance. The nonstatutory language shifted out of FAR holds years of lessons learned, protest wins and losses, shifting markets, and economic and national crises. While some may still be in the FAR Companion and Practitioners' Albums, they no longer carry the same weight.

It should carry some weight. It must inform judgement -- good judgement.

"Trust the acquisition workforce" is now basically what the RFO says.

The rewritten framework relies more heavily on judgment – but not professional experience, education, business acumen, and common sense.

Just less prescriptive lingo and little to no instruction.

Experienced Contracting Officers are capable of not missing a beat and exercising that good judgment. Many do daily. The larger question is how we develop that judgment across the workforce. Judgment doesn't appear because regulations shrink. It comes from experience, mentoring, training, discussion, successes, mistakes, and protests.

If we reduce regulatory prescription, we need equally strong investments in developing professional judgment. They go hand in hand.

As a Chief, I never just asked, “Did you complete your market research?"

This list of questions were almost always asked to at least one project manager in our Advanced Acquisition Planning Boards (AAPBs) in USACE and FAA.

What do we know about the differences in the market between this procurement and the last.”

“Who is in the market now and who has left? Who is emerging?”

“What economic factors could change this acquisition throughout its lifecycle?”

“What are current trends and market indicators in this industry telling us?”

“What don’t we know and how are we getting that information?”

If the answer was, "Nothing," I usually wasn't encouraged but I also didn’t just let it slide because good judgement and due diligence demands these questions be asked and the answers found and considered.  

Good market research should occasionally prove us wrong. It should challenge assumptions. It should make us rethink a requirement, reconsider a contract type, or discover capability we didn't know existed.

If market research never changes the acquisition strategy, we need to ask ourselves if we are really studying the right marketplace or simply documenting decisions we've already made to fit a solution we already know we want.

The VALUE of market research is that the "THINKING" piece of it MADE ACQUISITIONS BETTER. The report you spit out to check a box is not the value.  

What I see working through the RFO is that there is strength in integrating market research into acquisition planning. However…we need to pay close attention is the corresponding reduction in prescriptive procedures. Those procedures didn’t only historically tell contracting officers what to do. They promoted consistency, transparency, and fairness in how acquisition decisions were made and documented.

The question isn't whether procedures should remain. It’s whether acquisition teams will continue to approach market research with the same discipline now that the RFO has created a less prescriptive process.

If acquisition teams can maintain discipline, consistency, transparency, and fairness, then the RFO changes have real potential to improve acquisition planning. But if market research becomes something we document after the important decisions have already been made, we'll have missed the opportunity the RFO, I believe, intended to create.

Ultimately, success won’t be measured by deleting FAR Part 10 and shifting it to FAR Part 7 to say we eliminated redundancy for some quick Administration win. It needs to be measured by whether acquisition planning becomes more informed because market research is fully integrated into it and not treated as a compliance exercise that happens alongside it.

Some measures of RFO success related to market research include assessing if:

• Agencies create ways to encourage thoughtful market research while reducing costs for industry. No more RFIs that are mini-RFPs.

• Tools, training, and leadership develop the critical thinking skills needed for newer contracting professionals in a less prescriptive market research environment. Moving beyond checklists to business acumen.  

• Agency acquisition strategies demonstrate fairness and consistency.

• Market research is integrated into acquisition planning earlier, resulting in more meaningful engagement -- and new methods for that engagement -- with industry.

• Five years from now, acquisition professionals aren’t viewing market research as a report but an innate requirement for good acquisition planning.

It’s up to industry and Government to keep market research fair and real versus it being relegated to a claim of less pages or a shorter FAR.

What’s Coming Next -- When Judgment Carries More Weight

----------------------------------------------------------------------------------

Author: Shauna Weatherly, President, Federal Subcontract Solutions LLC (dba FedSubK). Shauna is a small business advocate and owner of FedSubK. FedSubK exists to simplify federal contracting, empowering small businesses with practical, understandable resources. We bring first-hand experiences in Federal contracting from multiple perspectives derived from roles held both in and out of Government over almost four decades of Federal service.

Visit us at fedsubk.com to learn more about--

Getting Started in Federal Contracting: fedsubk.com/begin-your-journey-here

Solutions and Our Trusted Support Provider Network: fedsubk.com/solutions-services

Insights from a Contracting Officer: fedsubk.com/insights

Free Webinars and Resources: fedsubk.com/webinars-training

FAR News
August 3, 2026

Where Good Procurements Really Begin (Weatherly the RFO - Part 3)

Before I got my first warrant (required to sign contracts), I was a Contract Specialist writing my first acquisition plan. It was for a large Total Environmental Restoration Contract (TERC) that included A-E, Services, and Construction terms and conditions. I was told, "follow FAR Part 7." I thought, "Okay, looks like I'll be doing a lot of these in the coming years. Figure it out." With a few years under my belt, I learned quickly that acquisition planning is the foundation for every successful procurement.

When I moved into leadership roles, we built acquisition planning into our entire program and project lifecycle.  We implemented Advanced Acquisition Planning Boards (AAPBs) before writing lengthy acquisition strategy and planning documents. We invited stakeholders like Contracting to attend the budget request preparation meetings for the next FY. We started shaping an understanding and a plan of action months and years in advance of analyses and research.  

Anyone who has spent time around acquisitions in the Federal space knows that most procurement problems begin at the beginning, before any procurement forecast goes into Acquisition Gateway or on the agency’s small business page, or any Sources Sought notice is issued in SAM. Long before a solicitation is issued and proposals arrive. And long before anyone files a protest.

You can almost always pin-point where, if you are going to have a problem, it will begin.

When an agency hasn't fully thought through what it's buying, why it's buying it, how the requirement should be structured, who might be capable of performing it, or what risks need to be managed before the acquisition ever reaches the marketplace.

Acquisition planning is preparation. If that’s not what we’re doing, we’re already creating problems for every acquisition phase that follows.  

And that's why this topic in federal acquisition and the proposed RFO rules deserves attention, especially now that FAR Part 10, Market Research, has been combined with FAR Part 7, Acquisition Planning. Combining acquisition planning and market research recognizes something practitioners have known for years -- they're inseparable.

But it also means that changes to planning now ripple directly into how agencies understand the marketplace before they ever write a solicitation.

Congress never cared whether agencies produced acquisition plans. Congress cared whether agencies made good acquisition decisions. They care about competition, stewardship of taxpayer dollars, thoughtful use of small businesses, commercial buying, performance-based acquisitions, and risk management.

Those are the objectives.

Acquisition planning has been the primary tool for achieving them. But the plan itself was never the goal. The effort behind the plan was. Acquisition planning is simply one of the first steps in the procurement process. It is the place where the most important decisions have already been made.

Consider the examples I gave above about the discussions in the AAPB and budget request preparation. All of that is well before anything was put into writing. And heck, by the time the RFI was released (if we released one), just about every big question was already answered.

• Will this be a small business set-aside?

• Have commercial solutions been considered?

• Should the requirement be bundled?

• What's the acquisition strategy?

• What contract type makes the most sense?

• How will proposals be evaluated?

• How much performance risk is acceptable?

Those decisions are a product of discussions very early in acquisition planning. By the time industry reads the solicitation, many of the biggest decisions have already been made. The solicitation simply makes those decisions visible. So that begs the question…

…If acquisition planning changes, doesn’t everything downstream change, too?

I have a ton of notes in the margins of my electronic copies of the RFO parts issued so far. Most center around... Where is the acquisition leadership expecting contracting specialists and contracting officers to learn how to think through these decisions? I'm not talking training sessions, listening sessions, leadership briefings, webinars, the FAR Companion, Practitioners' Albums.

We are overwhelmed by data these days -- there is no shortage.  Collection of data isn't the issue. it's what to do with it once we have it. What is meaningful and what isn't? That's a legitimate concern from the perspective of a contract specialist working different types of contracts in their cradle-to-grave office set-up. Or the specialist or contracting officer moved as a result of agency realignments and now buying something new, with no training whatsoever.

With the FAR Council is intentionally moving away from detailed procedural direction in favor of shorter regulations supported by guidance outside the FAR, we have to acknowledge that, historically, the FAR didn't just tell contracting officers what it needed to comply with, but often explained how to ensure compliance and answered questions about how to get it done.

From the Contracting Officer's Chair

Let’s start with a discussion about curiosity. Bring me a purchase requestion and I would have a list of questions ready for you. I know from experience that my answers and how this action continues hinges on what those answers are. That includes everything that goes right and wrong, long before I use any AI tool and ask questions.  

• What problem(s) are we trying to solve?

• Is there another way to buy this?

• Has it been purchased before?

• Who in industry might already be doing it and how is it procured?

• What risks are we creating and mitigating?

• What opportunities are we overlooking and creating?

• What is it that we don’t know yet but need answers for?

And then the standard "dollar value", "when do you need it", and "do you have money yet" questions.

Every profession has it and the contracting craft is no different. Knowing what questions to ask is part of the craft. Also part of the craft is learning how best to pass information from one experienced professional to the next. The RFO is forcing us to reconsider where and how that institutional knowledge should live going forward. And, how we preserve it in market research and acquisition planning.

Written acquisition plans preserve all discussion and decisions points. It is the ultimate fallback for the building of the solicitation and the justifications of what we are doing and why in the pre-award phase leading to the solicitation. It is never seen by industry but relied upon by acquisition. Making preservation discretionary means documentation practices could vary significantly across agencies, depending on each agency's implementation decisions and tolerance for risk.

What gets lost are rationales, alternatives considered, risk discussions, disagreements, lessons learned, why things changed from the last procurement, and what outside influences impacted current decisions. Acquisition plans in their written form allow that information to be inherited by future acquisition teams. This deserves more attention than it's receiving in the RFO.

The RFO made the changes in FAR Part 7 about the laundry list of what had to go in the plan.  

Wrong argument.

It is ALL about careful consideration of facts and circumstances before acting. How much consideration is required to make informed decisions, preserve those decisions so we have them as a guide moving forward, and actually use them to improve and streamline the process. Contracting officers know that their judgment can't be regulated. They stop relying on checklists and start recognizing patterns. They know the questions to ask end users, requiring activities, legal counsel, budget, and small business specialists because seeing the patterns for a poor acquisition form. That's because most know where acquisitions tend to go off track from living through it.

If the FAR is going to become shorter, the acquisition workforce needs a deliberate and consistent strategy across the board for preserving the judgment, rationale, and historical knowledge that good acquisition planning has always provided.

Otherwise, while we simplify the rulebook, it will -- for now -- make the profession harder to master.

What’s Coming Next -- Article Four: Market Research Isn't About Checking a Box

----------------------------------------------------------------------------------

Author: Shauna Weatherly, President, Federal Subcontract Solutions LLC (dba FedSubK). Shauna is a small business advocate and owner of FedSubK. FedSubK exists to simplify federal contracting, empowering small businesses with practical, understandable resources. We bring first-hand experiences in Federal contracting from multiple perspectives derived from roles held both in and out of Government over almost four decades of Federal service.

Visit us at fedsubk.com to learn more about--

Getting Started in Federal Contracting: fedsubk.com/begin-your-journey-here

Solutions and Our Trusted Support Provider Network: fedsubk.com/solutions-services

Insights from a Contracting Officer: fedsubk.com/insights

Free Webinars and Resources: fedsubk.com/webinars-training

FAR News

Stay Updated, Stay Ahead

Get timely, actionable insights delivered straight to your inbox.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.