Subscribe Member Home

235 – It’s a Technicality

Members only

This episode is available with a Skyway membership.

See membership options Member login

If you work in the Government acquisition world, this podcast is for you. (not just for Contracting Officers!)

Government requests for proposals (RFPs) contain many explicit requirements.  They also include many “buried” requirements that, if not followed, result in non-compliance with the RFP instructions and potentially end a proposal’s chance for award.   

Kevin and Paul discuss proposal compliance and why losing on a “technicality” is still losing.  Learn why 100% compliance is mandatory and why the Government may or may not kick a proposal out of the running for award based on minor compliance issues.

Paul: Welcome to the contracting officer podcast. It's not just for contracting officers. If you work anywhere in the government acquisition world, this podcast is for you. Today, we're talking about requirements and compliance in the government source selection process. This episode is brought to you by Skyway Acquisition.

Becoming a Skyway community member makes it easier to navigate the complicated world of government contracting because you gain context from Skyway's team of former contracting officers. Go to skywaymember.com to get started with a personal membership because without context, you're likely overlooking problems that you don't see. Okay. Let's get started with today's episode. Government requests for proposals contain many clear requirements.

They also contain many, maybe hundreds, of compliance items.

Kevin: Hundreds. One of our clients, one of our customers, they they lost the competition because they failed to submit a letter, one letter from a government office that was required by the RFP as one of the compliance items, those hundreds of items. While proposal support is one of the things we help our customers with, not all of them use us all the time, nor should they. Some of them use us a little, some of them use us a lot. In this case, they had the capacity to handle the proposal themselves, which is why we found out about this after the fact.

Paul: During the post mortem, the proposal lead said something like, we didn't provide the letter, but rather included an explanation in our proposal. It was a technicality that we didn't have the letter, and they disqualified us based on that technicality.

Kevin: K. Okay. You may wanna explain what a postmortem is for folks.

Paul: Postmortem. Yes. So after you lose a competition, it's very common to gather the proposal team together and other experts to look at the feedback you got from the government. Figure out why you lost so you don't lose that way again. You might lose again, but don't lose for the same dumb reasons that you lost last time.

Kevin: And and I would argue that you should do a postmortem even when you win because you wanna do more of what works. But, yeah, the concept is really sound.

Paul: Exactly. Okay. Back to the technicality. To be clear, this client understands that their proposal wasn't compliant and that they lost fair and square. It's it's not a sour grapes kinda thing.

The point is important. Compliance items are requirements, and a proposal is unawardable if it's not compliant. Before we start arguing about that, let's stop and say thanks.

Kevin: What? Let's argue. The thanks this week goes to Mike Sutton and Zach Gosch. They're from, Bell Flight. Mike and Zach gave me great feedback.

It was really valuable feedback on the Contenting Officer Podcast. And, they scheduled a podcast feedback session at askskyway.com. And, during our chat, they explained how they found the podcast, how they use it, and what they'd like to hear more of. And they also joined the contracting officer podcast group on LinkedIn so we can connect with them more. The contracting officer podcast group on LinkedIn helps us see who's actually listening to the podcast, not who we think is listening.

And that way, we can serve people better.

Paul: Thanks, Mike and Zach. Today, we're talking about how compliance is a is pass fail in proposal evaluations. Let me give you a little more of the setup of how this situation that we're talking about happened. The request for proposals included a form with a whole bunch of yes or no checkboxes. 1 of those checkboxes said if you check yes here, you must submit a letter from a specific government entity that says everything is still okay.

Even though your answer is yes, it's all good. Our community member read the form and guessed that yes was the correct answer based on his understanding of the question. It was kind of a a complicated question. It's one of those government things where in in the nongovernment world, the answer might be this. In the government world, it might be this.

Kevin: Those are always the fun ones to answer.

Paul: He looked at it and said, I'm gonna I'm gonna say yes just to be safe, because I don't wanna be caught if the answer is no. There's a lesson to be learned here. Never guess at an answer, especially if your choice requires you to submit more documentation, if it creates more work for you. Research the proper answer or ask a question of the government during the draft RFP or RFP question and answer window.

Kevin: This is one of the reasons our customers use us for for compliance reviews or or red team reviews. Because if you're guessing or you think you might be guessing, ask us. That's what we help with.

Paul: Since our customer's yes wasn't a really strong yes, they didn't obtain the letter from the agency and instead submitted a a rational explanation in their proposal of why they checked yes based on their understanding of the question. As you would imagine, the government looked at it, noticed that there was no letter there as required, and disqualified their proposal as noncompliant without ever evaluating the rest of the proposal. Their notice, their notice to unsuccessful offer, the the you're you lost letter.

Kevin: We we have a podcast about that concept.

Paul: It specifically cited the fact that they did not submit the letter, therefore, they're noncompliant. So that's lots of time and money writing this proposal down the drain. Why did the government disqualify this proposal based on such a minor issue?

Kevin: Because they could. That's a cynical answer, but the reality is they need to thin the herd. And the compliance is where where they start. As a contracting officer, this is where I would start. Is did everyone meet all the compliance requirements of the RFP?

Paul: Now it's unlikely that the omission of this letter in any way reflects on the company's ability to perform the work. It's not a significant risk factor.

Kevin: It's not a key performance requirement. This wasn't gonna make or break the performance of the contract.

Paul: Right. This is way buried in the in the pages and pages of of RFP besides the actual requirements of the contract. So why disqualify? 1st, if if if the government received multiple compliant offers, there's no reason to spend the time evaluating any additional proposals. Make the job faster and easier.

Make the source selection faster and easier by not even looking at the ones that aren't compliant.

Kevin: And before folks get judgy, it's very easy to be judgy here and think, well, they just kicked us out. Ask yourself what you would do. We'll go back to building the deck. You know, let's go back to if you're building

Paul: My favorite.

Kevin: If I asked a couple companies for quotes on building a deck, and I wanted it built out of cedar, Cedar wood, so it smelled great. Right? And someone sent me a quote, and said, hey, I can build it out of plywood. I could go back to them and say, no, I said cedar. We need to do it out of cedar.

If I had 4 proposals that said they could make it out of cedar, why would I go back to the guy that made it out that said he would make it out of plywood?

Paul: Right.

Kevin: It's human nature. I'm trying to thin the herd.

Paul: And even if it was something more simple, if you ask them to submit their certificate of insurance with their proposals when they build their deck, to make sure that they're they're insured, and they didn't submit the certificate of insurance. If you got 5 proposals and 4 of them submitted that and the 5th one didn't, you'd say, forget those guys. If you only got one proposal, you might want to check a little harder to see if they're actually insured. Looking at this from a different direction, why would the government disqualify the proposal? If the government has a favored offeror if they have a favored, if they have somebody they want to win

Kevin: An incumbent, for example? Yeah.

Paul: You just made it foolproof for them to award to that company because you missed a requirement. You were noncompliant. You can't even protest that kind of thing. You're done. You made it easy on them.

So why would they disqualify you? To make it easy on the evaluation team and get the award done quickly. Another angle, what if the government actually wanted to evaluate and potentially award to the offer who didn't submit the letter with their proposal?

Kevin: That's why this is a thinking job.

Paul: Which brings us to far time. We're in far part 15, contracting by negotiation. This is 15 dot 306, exchanges with offers after receipt of proposals. 15306 b is communications with offers before establishment of the competitive range. It says, communications are exchanges between the government and offers after receipt of proposals, leading to the establishment of the competitive range.

If a competitive range is to be established, these communications and there's a whole list of things here. Put number 2, these communications, 15 dot 306b2, these communications may be conducted to enhance the government's understanding of proposals, allow reasonable interpretation of the proposal, or facilitate the government's evaluation process. Here's the important part. Such communication shall not be used to cure proposal deficiencies or material omissions.

Kevin: And the key judgment call, the thinking job part of this, is it says May, first of all. And then a definition of material omissions is a judgment call. So this is the part of the FAR, the assistant contracting officer gets to decide how important that form really was. They can decide it's really important, because they really, really want you to win and need somebody to do it, or they can decide, this is the reason to get you out of the way, because we have other companies that can do this, as harsh as that sounds.

Paul: We'll talk about how that could play out in a minute. 1st, let's link this to the acquisition and execution time zones.

Kevin: And if you're not familiar with the acquisition time zones, we cover those in episode number 3. And the execution time zones, we cover in episode 84.

Paul: Today, we're talking about the RFP zone, the the third of the acquisition time zones. The RFP zone is where the proposal writing happens and where contractors are reviewing their proposals to make sure they're compliant. It's also where you're asking questions of the government after you've seen the RFP. We're also talking about the source selection zone, the 4th and last of the acquisition time zones. This is where the government's evaluation of the proposals takes place.

Let's get back to why this is important. Technical requirements and request for proposals are usually clear.

Kevin: Usually, they're clear. How about this? The government's trying to make them clear, but they're not always successful. It's not easy.

Paul: It's not. Sometimes it seems easy, and then you find out it's a lot harder when you're actually trying to evaluate it. But think about the technical requirements for an all terrain vehicle. You you've had these before. Right?

The range, it has to be able to go a certain amount of miles on a tank of gas, or it has to have a top speed of 22 miles an hour. That that's that's clear. You either meet that or not. Sometimes the the compliance requirements aren't so black and white in the RFP. They're buried in there amongst the pages and pages of clauses and checklists and other forms.

If you're writing a proposal and you're you're reading that RFP and and it isn't clear you don't understand, ask questions.

Kevin: And that's why Skyway is here, to help you understand when to ask the questions, how to ask the questions. If you can ask certain questions in certain time zones. And that's also why targeting is so critical, is knowing what questions to ask when makes a big difference. Because if you ask some of these questions in the RFP zone or the source selection zone, it's too late.

Paul: Yeah. I was gonna talk about that part. Formal and informal questions to the government are allowed depending on the timing. Early in the process, prior to the final RFP release, informal questions may be allowed. You may be able to pick up the phone and get a question answered.

But after the final RFP is released, it's a formal process that makes it a little bit more difficult to get important information back and forth. If you can't ask questions and you don't understand the request for proposal, you may wanna consider walking away from this one. You may wanna consider no bid.

Kevin: It's a hard decision to make, but it should always be in the back of your mind. Up to the moment where you submit your proposal, at any point along that process, you can disqualify the opportunity. And if you don't clearly understand some critical piece of it, and the definition of clericality is is a judgment call, that might make sense to walk away.

Paul: Bottom line, if the RFP says to submit a document, submit it. No explanations for noncompliance are allowed. You can't just say, I didn't submit this, and here's why I didn't submit it. It doesn't work that way. But as we touched on before, per the FAR, it doesn't have to be a fatal proposal flaw.

The contracting officer's judgment of the materiality of the omission is required.

Kevin: I go back to the sales axiom of people do what's in their own best interest. And the best interest of the government is to move on to the next offer, assuming that there is more than one to pick from. There's almost always more than one offer to pick from. So the best interest of the government is to find a reason to take you out of the competition unless there's a unique scenario where they wanna keep you in.

Paul: More than one time as a contracting officer, I had a source selection where an offer failed to submit something very minor, and I asked a clarification question. It I didn't make it a deficiency yet. I asked a very simple question. It appears that the letter required by was omitted from your proposal. Did you intend to submit the letter with your proposal?

And that leaves them with a yes or no, and they can say, yes, I did, and here's that letter, and then we all just move on. It's just a minor clarification. But that's the that judgment call. Was the omission material to them being able to do the job or not do the job, or was it just a minor paperwork exercise? Right?

If I really wanted them or if they were the best offer or I probably haven't looked at the other ones yet. But if they have a very compelling offer that that's very awardable, does it make sense? Is it in my best interest to kick them out for something super, super minor? Probably not. But if I have 20 proposals and I already know I have 3 compliant ones, maybe I don't bother past looking at this and saying, oh, they missed something.

They're out.

Kevin: Yeah. I've gone both ways. I've I've kept people in by allowing them to to answer our clarification question. K. Clarification question.

And I've also used this to thin the herd. So, again, it's a judgment call. But the best way to avoid it is don't put yourself in that spot in the first place.

Paul: Right. Specifically on the government side, know what you're asking for in the RFP and why you're asking for it. In the case we're talking about, did that letter actually help the government assess the offeror's ability to do the job or meet the requirements? Maybe, maybe not.

Kevin: But it helped them thin the herd, which was in their best interest.

Paul: Sometimes the the why you're asking for it isn't because it helps you assess whether or not they can do the job. It's because the FAR or some other rule says you have to ask for it. It may not provide any apparent benefit to you.

Kevin: Yeah. There are lot there are lots of things in the FAR that don't provide any apparent benefit to anybody, but they're still in there.

Paul: As we've been talking about, government folks can use noncompliance to limit the number of proposals that they have to evaluate if they have enough compliant proposals. And that may be just one just one compliant proposal in a in a competition where many people competed is enough to evaluate an award.

Kevin: Wendy Freeman and I talked about that in a recent episode. The idea of deconstructing the RFP is what the industry calls it. And that compliance review, or a compliance checklist is what I called it as a contracting officer. But that same idea is there. In order to do that compliance review, industry's looking at that first.

Both sides are looking at it. Just make sure you don't miss anything.

Paul: Government folks, use your judgment to work through things like this where it's allowed by the FAR. Remember that we are trying to get our users whatever they need, be it products or services, on time and on budget every time.

Kevin: And remember that FAR 15306 b 2, I think it was you found, it says communications may effectively result in them staying in or out. Yeah. It's a judgment call. This is the thinking part of the job.

Paul: Moving to the industry side. Why does industry care about this? Obviously.

Kevin: Yeah. Losing sucks.

Paul: Yeah. There are no technicalities. There are just RFP requirements. You can't explain your way around noncompliance. When in doubt about the requirement, be it something blatant in the RFP or something buried in the pages and pages of clauses, if you have a doubt, ask a question of the government or choose not to submit.

Kevin: Don't count on the government to find a way to award your non compliant proposal. There may not be a way. I've had ones where the I know you have too. We've talked about them on this on this podcast. There are ones that the government customer absolutely wanted this company to win, and compliance issues, you just can't work around them.

They can't suddenly say, okay. Well, this was a requirement. This was a a need of the FAR. They didn't meet it, but they get a pass. There are scenarios where there we just can't get there from here.

Paul: Right. It's very important. Industry folks, if you can meet 99% of the requirements but you can't meet that last 1%, you have a few choices. If this is prior to the RFP release, communicate with the government and try to get them to change that 1% that you can't meet or remove it so that you can submit a 100% compliant proposal. And then remember, if you ask them to change it and explain to them that, hey, I can't meet that requirement, and then they don't change it and the final RFP comes out the same way, they don't want to award you.

Kevin: That's an indicator that what's important to you is not important to them. Right.

Paul: So at that point, you might as well not bid. You're not gonna win. Another thing you can do if you can't meet that last 1% or 10% or whatever is add a teammate who can meet the final requirements so that your team is compliant. And the ultimate choice is don't bid. If you can't meet all the requirements in an RFP, you don't get any credit for meeting 99% of the things that they've asked for.

If you can't meet it and you can't find another way around it, probably best to not submit a proposal.

Kevin: As you were saying that you can get credit for 99% performance if that's an evaluation criteria. But we're not talking about evaluation criteria. We're talking about compliance. And like you said, compliance is pass fail. So there's a difference between the evaluation criteria may say, how well can you do this?

Yeah. That's different. What we're talking about here is, can you do this? If you can't, or the process requires you to do a few steps to prove that you can and you don't do those steps, that's a compliance issue. It's it's go, no go.

Paul: Yeah.

Kevin: Just let's be clear on that.

Paul: Yep. If box is checked, yes, submit this letter. Is there a letter here? No, there's not. You fail.

Kevin: It's kinda like a tax form, since it's, you know, tax season. Maybe think of that.

Paul: Alright, Kevin. Let's wrap this one up.

Kevin: In the commercial market, in the business to consumer or business to business, it's often possible to work around compliance problems. Let's say my cousin submitted that proposal for the deck that had plywood. Well, it's my cousin. So I can say, you know what? I'll give him another chance.

Well, in the government market, it doesn't necessarily in fact, it often does not work that way. I mean, the process has a lot more weight because the far and lots of other regulations require a certain amount of process. So you can't work around this stuff.

Paul: Man, you would get in a lot of trouble if you gave your cousin's company a couple shots to fix their proposal when it was non compliant. There's so many things wrong with that.

Kevin: Just giving him another shot at it is 1, then the fact that it's my cousin. We have an episode about that too. Okay. On the industry side, consider the risk of non compliance. Losing on a, like, quote, unquote, technicality, it's still losing.

Don't take this lightly. Because like you said, if you can't do that 1%, and that 1% happens to be something that they can't award to you, you're in the same place, which is you lost. So this is not a this is not something to take, lightly. On the government side, same thing. Don't be flippant about eliminating an offer on a compliance issue.

I've done it. And I know for a fact somebody got fired over it one time. These are people, people get fired, their jobs are at stake. Offers may have trouble recovering if they bid outside their weight class, which, by the way, we have a weight class episode. It's episode number 16 explains what that is.

In this case, our customer was not outside their weight class. This was a learning lesson they just went on, because they were they were targeting well. But government folks, be aware that these are people submitting these proposals. Expect some frustration, like them calling it a technicality, because it feels like that to them.

Paul: In this case, it's a good thing. The company is mature, and they're able to get a little mad and say, they threw us out on a technicality, but they understand that technicality is noncompliant, and they lost fair and square. And they can take it as a lesson learned and moved on.

Kevin: My advice to the government folks to limit the number of or decrease the number of technicalities is to focus on the targeting of your language in your RFPs. If they clearly understand that they can't do things, they won't bid. As opposed to finding out, again, raising my hand because I was appalled the number of times this came up during a debriefing, when somebody said, hey, well, I couldn't do that. I'm thinking, then why did you bid? Well, they bid because they misunderstood the language, which I wrote.

So be aware that the more you target, the more crystal clear that requirement is, the fewer technicality complaints you're gonna get.

Paul: Yep. Totally agree there. And with that, I'll talk to you later, Kevin.

Kevin: Alright. See you, Paul.

Paul: Okay. That's it for this episode. Thanks for joining us. Thanks to our sponsor Skyway Acquisition. Skyway guides customers through the government source selection process.

Call 877-884-5280 or go to ask skyway.com to set up a time to learn more. We'll see you next week.