FedSubK Feature: Navigating Federal Contract Opportunities Notices
Updated: May 4, 2024
Federal agencies use various types of contract opportunities notices throughout the acquisition cycle. Federal Acquisition Regulation (FAR) Part 5, Publicizing Contract Actions, provides the guidelines and methods for these announcements. Each has a distinct purpose and place to maintain transparency, ensure a level playing field for potential contractors, and standardize and streamline the procurement process.
There are two types of notices the Government uses to collect information for the purposes of market research.
Request for Information (RFI). This notice is one of the first steps in the federal acquisition cycle for larger or more complex acquisitions, or when the Government has no purchase history that compares its current need. RFIs are a form of market research (as required in FAR Part 10). They are used to gather market intelligence, obtain information from industry experts, and refine the Government’s requirements before issuing a formal solicitation. RFIs are also used to inform the Government’s acquisition strategy decision-making process.
Responses to RFIs are usually in the form of an email or questionnaire in which the entity provides basic information about their business and other market or industry information on a specific question or set of questions the Government has about a product or service. RFIs do not commit the Government to any future contract and responses should not contain proprietary or confidential information such as trade secrets or pricing.
RFIs are publicized in the System for Award Management (SAM) but are not expressly titled as such under the types of notices for which businesses can search in SAM Contract Opportunities. The most effective way to find RFIs in SAM is to use the Contract Opportunities advanced search function for an exact keyword search on “Request for Information”. This search may also pull in Sources Sought Notices.
Sources Sought Notice. A Sources Sought Notice is an early-stage market research tool in the federal acquisition cycle. It summarizes the Government’s requirements enough that businesses can determine interest and eligibility. It is used on a wide variety of acquisitions in terms of dollar value and complexity. The purpose is typically to test the interest and availability of qualified businesses in the market, but are used primarily to determine the number and types of interested small businesses, small disadvantaged businesses (SDBs), or businesses in specific socioeconomic categories (i.e. 8(a) Program participants, Historically Underutilized Business Zone small businesses (HUBZone SBs), Women-Owned Small Businesses (WOSBs), Economically- Disadvantaged WOSBs (EDWOSBs), and Service-Disabled Veteran-Owned Small Businesses (SDVOSBs)) in the market. Sources sought notices help agencies gauge the potential level of competition in each socioeconomic category and identify possible full or partial set-aside opportunities and their viability to avoid one-offer/ no-offer situations.
The Government typically requires a specific format for response to a sources sought notice and will limit the response to only the information requested within a specified page-length. Think of a response to a sources sought notice as a quiz on how well you follow instructions for a proposal submission later; because the Government also looks at them that way. Do not submit marketing materials or capabilities statements as your response to a sources sought synopsis unless the Government expressly requests that information. Follow the instructions in the notice to the letter.
Neither RFIs nor Sources Sought Notices commit the Government to solicit or award the requirements summarized. They also do not constitute an offer or proposal to the Government for performance of the work under which the Government is required to act.
Are RFIs and Sources Sought Notices a Mandatory Notice for Each Contract Action?
No. They are not required notices. The extent of market research completed using each will vary, depending on such factors as urgency, estimated dollar value, complexity, and the Government's history of same/similar purchases. Solicitations may be issued without an RFI or Sources Sought Notice being published.
Once the acquisition strategy has been determined and approved, there is a mandatory notice that signals the public that a proposed Federal contract opportunity is forthcoming.
Pre-Solicitation Notice. A Pre-Solicitation Notice is the first notice used in the solicitation phase of the acquisition lifecycle. A pre-solicitation notice is required before a Contracting Officer can issue any resulting solicitation. It is published in SAM.gov at least 15 calendar days prior to the release of the formal solicitation. This notice provides a high-level overview of the upcoming procurement, including key requirements, deadlines, and contact information. Interested businesses can use this notice to determine their structure to perform the work (prime, prime/sub, joint venture, or teaming arrangement) and begin preparing for release of the formal solicitation. There is no action required from potential contractors in response to a pre-solicitation notice.
After the Pre-Solicitation Notice is issued, the solicitation will be announced by one of the following methods:
Request for Quote (RFQ). A Request for Quote (RFQ) is used to announce a contract opportunity when the Government’s needs are relatively straightforward and well-defined. RFQs are used for actions valued over the micropurchase threshold (see FAR 2.101) and less than or equal to the Simplified Acquisition Threshold (SAT), presently $250,000 (with some exceptions). RFQs solicit price quotes from interested eligible sources for the delivery of products or services. RFQs streamline the acquisition process and typically require less time for entities to prepare a response (i.e., quote) back to the Government.
An RFQ response time is determined by the Contracting Officer as a length of time that will afford potential offerors a reasonable opportunity to respond. Entities interested in providing a quote must follow the Government’s instructions to submit their quote before the date and time set for receipt.
Request for Proposals (RFP). A Request for Proposal (RFP) is a comprehensive solicitation document used for complex acquisitions. It outlines detailed requirements, evaluation criteria, and allows entities to submit proposals that may include technical qualifications, experience, key personnel, past performance, and price/cost elements, among others. RFPs are used over the SAT and can be lengthy in terms of the description of the scope and/or instructions to offerors in the preparation of proposals.
The minimum RFP response time is 30 calendar days or more, as determined by the Contracting Officer. The more complex the proposal, the longer the response time. Entities interested in providing an offer must follow the Government’s instructions to submit their proposal before the date and time set for receipt. The receipt, handling, and evaluation of offers is governed by FAR Part 15, Contract by Negotiation.
NOTE: Draft RFPs may be issued as a form of market research for the purposes of getting industry comment on the Governments requirements, planned acquisition strategy, pricing structure, terms and conditions, and/or compliance requirements. Agencies are not required to issue draft RFPs. They are most often used on highly-visible and highly-complex services contracts either at the agency level or Governmentwide where new or innovative methods for the solicitation, evaluation of offers, or performance of the work are proposed. Responses to draft RFPs are considered by the Government and may be used to finalize the RFP for formal solicitation.
Invitation for Bid (IFB). An Invitation for Bid (IFB) is a notice that requests a sealed bid from interested entities and is used typically for straightforward, low-complexity procurements, most often for supplies, materials, and general construction activities where the Government is most interested in obtaining the lowest price. IFBs are not used when the Government may need to negotiate terms and conditions, scope, level of effort, or price with contractors prior to award; RFPs are used in that case.
The minimum IFB response time is 30 calendar days. Entities interested in providing a bid must follow the Government’s instructions to submit their bid documents before the date and time set for receipt. FAR Subpart 6.4 and FAR Part 14, Sealed Bidding, governs the handling, public opening, and announcement of winning bids.
IFBs are publicized in the System for Award Management (SAM) but are not expressly titled as such under the types of notices for which businesses can search in SAM Contract Opportunities. The most effective way to find IFBs in SAM is to use the Contract Opportunities advanced search function for an exact keyword search on “Invitation for Bid”.
FAR Subpart 12.603 also outlines a streamlined notice and solicitation process for commercial products and commercial services.
Combined Synopsis/Solicitation (CSS). The Combined Synopsis/Solicitation (CSS) involves combining in a single notice the solicitation notice (RFQ, RFP, IFB) and the solicitation itself. A CSS must identify itself as a CSS in the language of the announcement to ensure clarity to interested parties so it is understood no further written solicitation will be issued. The CSS includes information about the contract requirements, evaluation criteria, and submission instructions in a single notice. Again, it is important to remember that no other written solicitation documents will be issued after issuance of a CSS.
CSS notices are typically announced for 30 days but that timeframe can be significantly shorter at the discretion of the Contracting Officer. The CCS will provide any notice of a set-aside and the associated NAICS code and small business size standard applicable to the action. CSS instructions will indicate if the entity response is classified as a bid, quote, or offer. Failure to follow instructions may render a response ineligible for further consideration, depending on that classification.
Federal buyers must formally announce the contract awards to the public when the total value is over the micropurchase threshold.
Award Notice. An Award Notice is issued after the contract has been awarded to the selected vendor. It provides information about the successful bidder, contract terms, and other pertinent details. These notices inform unsuccessful bidders and the public of the contract award, promoting transparency in the federal procurement process. They can be used by entities looking for subcontracting opportunities within a specific industry or with a specific agency.
There are other types of notices that may be of interest to entities, depending on their industry. These notices also serve specific purposes and can be searched in SAM Contract Opportunities.
Justification and Approval (J&A) Notice (aka “Justification” in SAM Notice Types). A Justification and Approval (J&A) document is not a solicitation but a required notice that must be made to the public when an agency intends to award a contract without full and open competition. This document explains the reasons for the non-competitive procurement, such as sole-source awards or emergencies. The use of these notices ensure transparency and accountability when contracts are awarded without competition.
Special Notices. Special Notices are used by the Government to–
● Transmit Government interest in potential Research & Development (R&D) programs whenever market research does not produce enough concerns to obtain adequate competition.
● Establish a Federally Funded Research and Development Center (FFRDC) or before changing an FFRDC’s basic purpose and mission (see FAR Part 35).
● Advertise business fairs, prebid or preproposal conferences, and meetings.
● Provide long-range procurement estimates.
● Notify industry of the availability of draft solicitations or draft specifications for review.
Federal contract opportunities notices play a crucial role in the acquisition lifecycle, ensuring transparency, competition, and efficiency in the procurement process. By understanding the various types of notices and their purposes, Government agencies and businesses can navigate the complex world of Federal contracting more effectively. Whether it's an early-stage Request for Information (RFI) or a comprehensive Request for Proposals (RFP), each notice serves a unique function, contributing to the successful acquisition of products and services by the Federal government.
View related posts
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
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
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

.webp)

