FedSubK Feature: Are Capabilities Statements Worth the Effort?
Updated Jan 2026
I'm about to challenge some common assumptions below. Buckle in.
Many GovCon professionals claim that an excellent capabilities ("cap") statement will attract calls from Federal buyers. When you hear this, you might think, "A quick way to build relationships with buyers? Great, count me in!" So, you rush around, create a cap statement (maybe paying someone thousands to do it) and begin sending it out to every Government email address you can locate.
Today, let's get real about capabilities statements.
And here is the real REAL part -- I was a Contracting Officer and Chief of Contracting for a very long time as a Fed. In the offices I worked in and managed, not once did a capabilities statement prompt a call from a Government Contracting Officer for the purpose of offering a company a contract.
Sure, a Small Business Specialist might call to learn a little more about your company. That's their job. Requirements folks might call as part of early market research. It might get you a micro-purchase (read more about those here). But a Contracting Officer calling your company based solely on a capabilities statement is, frankly, not very likely to happen. If you do get a call it will most likely happen because:
1) the office is in a contingency and emergency buying situation, or
2) the Government needs to scare up companies to make up a competition pool because they are trying to get to a particular company, they can't justify a sole source, and the need to ensure the Rule of Two will be met to justify getting to the competitive pool they want.
That's the truth.
So...should you put the effort in to create a capabilities statement for your business? Read more and decide for yourself. I'm giving you the real insider perspective of how the Government views what the rest of GovCon tells you is a must. Decide for yourself after learning more about:
- What information it should contain,
- Who it should be sent to, and
- What to expect from the Government after it is received.
What Information Should Be Included in a Capabilities Statement?
Of course there are the basics:
- Business name (and logo)
- Business address
- Company website URL
- Unique Entity Identifier (UEI) and Commercial and Government Entity (CAGE) (or NCAGE, or NATO CAGE) code
- Point of contact name and information (email and phone number)
- Primary and secondary NAICS
- Product and Service Code (PSC) and Federal Supply Class (FSC) code
- Business certification logos (i.e., SBA certifications like 8(a), those required for the industry, or affiliation with prominent business associations)
Then there are the things that set your company apart:
- A succinct summary of the products and/or services provided. Don't be overly generic. Think of it as your 1-minute elevator pitch in writing and focus on your value proposition. Company history is fine but keep it very very brief.
- Discriminating characteristics or factors that set your business apart from others in your industry. Don't over-generalize, boast, or overpromise. Make sure you have the receipts to back up claims here. Certifications such as SBA socioeconomic certifications are great but should not be relied upon as an important discriminating factor.
- Names of recent key customers, projects, and/or current contracts, to include project titles, dollar values, and your role (if not the prime). Showcase the depth and breadth of your experience.
Some don'ts commonly found by Contracting Officers when reading capabilities statements are:
- Poor use of the real estate available on a single page. Use narrow margins and shorter headers and footers
- Logos and headers that are too big.
- Fonts that are too small.
- Long paragraphs versus short sentences, bullets, or graphics
- Providing information that the Government already has like the title of a NAICS code.
- An over-reliance on SBA certifications or business associations
- Omitting dollar values of contracts or projects
- Summaries that focus too much as company origin and history
- Failing to tailor it to the mission of the agency or the types of products or services they buy
There are a lot of GovCons who can help you prepare a capabilities statement... for a price. My advice is open PowerPoint or Canva and create a cheap and eye-catching cap statement yourself in a few hours. Don't pay thousands to have one created for you. If the reason you should save that money is not already apparent, the reason will be clearer as you read on.
Who Should Receive Your Capabilities Statement?
This goes against the advice of most GovCon advisors but...DO NOT send the Contracting Officer your capabilities statement unless one of these two conditions are met:
- They ask for it
--OR--
- You've done your homework, and you know based on historical purchase data for the procurement office in which the Contracting Officer resides that the agency or office routinely purchases the types of products or services you are trying to sell.
Sending your cap statement to every Contracting Officer whose email you have on the off chance they may be buying what you are selling is a big "No Bueno". While you think you're being proactive with your marketing, what you are really saying to the Contracting Officer is:
1) "I don't understand your role or how the procurement process works, but I'm super excited about the fact I have the email address of a real person who might be able to give me a Federal contract."
- Contracting Officers don't decide WHAT to buy. They decide HOW to buy. The "WHAT" is decided by the Requesting Activity. If you what to market an innovative product or service, instead try to find out who the Requiring Activity points of contact are and send your capabilities statement to that person / group. This gets your business cred directly to the technical experts and, possibly, the end users.
- Contracting Officers primarly use the SBA's Small Business Search (SBS) database, SAM.gov, and/or Requests for Information (RFIs) or Sources Sought synopses, to locate small business information. It is a better use of your time making sure your SBS and SAM registration reflect your business information correctly than hunting down Contracting Officer names to email your cap statement to.
- While you are maximizing the information in your SBS record, be sure to add your website URL AND ensure your website matches what your SAM and SBS reflect. You don't want your SBS to say you do IT services but your website to reflect janitorial services.
2) "Although I didn't do my due diligence to learn more about your office, agency, or buying trends before firing off this capabilities statement, please take your valuable time to open this attachment and provide a response."
If data "ain't your thang" and you don't want to pay for a tool or someone to do it for you, then you are better off sending your capabilities statement to the following people other than the Contracting Officer:
- Small Business Specialist or Office of Small Disadvantage Business Utilization (OSDBU) for the procurement office. It is the job of Small Business Specialists to:
- Collect information on the pool of eligible small businesses that can support the agency's mission.
- Know who is in that pool and their qualifications.
- Provide input on available small businesses to the Contracting Officer as part of the Project Team during the market research phase.
- Serve as an advisor during the formulation of the Government's acquisition strategy.
- Perform small business outreach on behalf of the agency.
- Program or Project Manager for the Requiring Activity
- These are the people often the closest to the work either because they are the end-user and/or they will be managing the contract after award on that party's behalf.
(Psst! If you need to know more about the roles in Federal procurement, check out my blog post "Hate the Game, Not the Players - Know the Roles in Federal Contracting".)
What Should I Expect After Sending My Capabilities Statement to the Government?
This is where it gets real. The true answer? It depends on where the Government is in its procurement cycle and who you send it to. Most of the time, it will sit with no action taken. That's the honest to goodness truth.
Conferences. If you hand a copy of your capabilities statement to someone in person at a conference, the likelihood is that it will sit in a general file that is cleared out periodically to keep it current or end up in the circular file. Only the Small Business Specialist or possibly the Requiring Activity will follow up and then, only if your differentiators make you really standout from the crowd. (Those differentiators are KEY.) Feds are not likely to make a follow up call based on a capabilities statement.
Contracting Officers. If you sent it to a Contracting Officer and they didn't ask for it, don't expect an answer or response. They get a lot of these docs. The email will either go in an email folder for possible later use ONLY if the Contracting Officer knows about upcoming purchases and it's a possible match. They are not required to keep source lists.
- If it is not deleted, it may be forwarded to the Small Business Specialist, OSDBU, or the requirements activity, if the agency makes purchases like what you offer.
- If the agency doesn't buy what you are selling, they likely will not respond, and your cap statement and email will be deleted. Frankly, that's on you for not doing your homework. Don't waste your time or theirs. ALWAYS. DO. YOUR. HOMEWORK.
- The chance of a Contracting Officer passing your email along to other agencies or friends / colleagues that are also buyers are very very low. If anyone tells you this happens, they don't know any Contracting Officers. Nobody has time to worry about another agency's buys.
Requiring Activity. The Project Manager is interested in one thing; can you deliver a quality product on time and within budget. If there is a current acquisition, they can't talk to you. If there isn't, this is your best point of contact to start a conversation about future requirements. If you want your cap statement to grab them, tailor it to them.
Small Business Specialists and OSBDUs. Let's say your cap statement makes it through at its easiest entry point for interest and possible action -- the Small Business Specialist. You still might not hear anything, but your cap statement will get filed because this person is required to keep tabs on their outreach efforts and have a ready list of small business sources not only for the Contracting Officer but for large business primes who are not meeting their goals. You have a chance of achieving a follow up call or meeting with the Small Business Specialist more than the other because of their need to track their own due diligence of tracking small businesses.
What type of info might you get as part of follow up with a Small Business Specialist? They can--
- Talk to you about upcoming acquisitions; they are involved in the forecasting process.
- Talk to you during the acquisition cycle when Contracting Officers and technical Subject Matter Experts or Project Managers can't due to potential conflicts of interest.
- Tell you who the Requiring Activity is and make introductions.
- Answer procurement questions and provide insights into agency buying trends.
- Introduce you to primes with subcontracting plan requirements looking for small business subcontractors.
This builds a relationship with THE internal advocate for small businesses. They get to know your company and IT'S THEIR JOB TO DO IT. Even though they are only advisory in nature, the Contracting Officer must conduct coordination with them on every action over a specific dollar value that is procured, including those set-aside for small business and obtain their concurrence. They are a gatekeeper for small business participation.
Isn't that the person you want to talk to? YES, you do. Because they WILL remember you. They will keep your cap statement. And it is their job to help.
So, after all that...
Are Capabilities Statements Worth the Effort?
Yes, but only when...
- Done without spending tens of thousands on the effort.
- It easily differentiates your company from your competitors.
- Tailored to target agencies and their buying history and trends.
- Sent to the right person at the agency and at the right time.
- YOU follow up to build relationships and market how you can help THEM (not ask for a contract or information).
Capabilities statements are not a check-the-box exercise that is then rapid-fired to all the Government email addresses you have in order to ask for a contract or information. If you use it...
- It must look professional.
- Make it meaningful.
- Be intentional on who receives it.
- Have realistic expectations about the outcomes they can generate.
It's not a MUST to create a capabilities statement. It is only one tool in the marketing tool box. While it may not get you quick wins or call backs, it can be a useful tool to:
- Help you hone your elevator pitch.
- Stick to a script of talking points when talking to Feds.
- Aid in finding and focusing on your business's core capabilities.
- Identify key discriminators that set your business apart from your competitors.
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)

