Facilities security clearances are a common requirement for Department of Defense procurements. While important for national security reasons, these solicitation requirements can also create confusion with respect to evaluation.
A recent GAO decision demonstrates how confusion can arise when a contractor holds multiple CAGE codes, only one of which corresponds to a cleared facility.
As our readers well know, a good proposal for a federal government procurement is an exercise in persuasive writing. You muster your creative powers to convince the source selection authority that you offer the best product or service, that your price is competitive, and that your past performance is stellar. So you invest heavily in your proposal writers; you review your proposal repeatedly to polish and ensure that it compels; you agonize.
But while the artistic portion of your proposal is, without dispute, extraordinarily important, don’t neglect the seemingly mundane–like CAGE codes. Get that wrong, and GAO just might sustain your competitor’s protest.
This week I had the pleasure of speaking at the 20th Annual Government Procurement Conference in Arlington, Texas. It was a great event and I was glad to see so many familiar faces. Next up, I’ll be in Des Moines on August 23rd for the Iowa Vendor Conference, where I’ll be joined by my friend Guy Timberlake for a great day of networking and information sessions.
But even as I log miles on the air and on the highways, there’s no mistaking the fact that we’re in the last days of the government fiscal year–and that means a busy week of government contracting news. This week, SmallGovCon Week In Review takes a look at stories involving an update to CAGE codes, some Milwaukee businesses under investigation for wrongly portraying themselves as veteran-owned and minority-owned, a lack of oversight allowed contractors to overbill a government customer, a look at the uptick in government spending as the fourth quarter winds down, and much more.