Understanding the Bids And Awards Committee Workflow
I spent about three years managing procurement for a mid-size logistics company before we outsourced it. One of the first things I had to learn was how the Bids And Awards Committee actually functions under government contract rules. It is not as complicated as some people make it sound, but there are edge cases that will trip you up if you do not pay attention. In practice, it is the body responsible for evaluating bids and recommending or approving contracts. Different organizations structure it differently, but the core function stays the same: receive proposals, score them against set criteria, and document the decision. In public sector settings, especially under acts like the MFDP or local equivalents, the committee must follow strict procedural requirements or the entire award can be challenged. I remember one case where a vendor appealed because their bid was technically non-responsive due to a missing page in an appendix, but the committee chair had initially overlooked it and passed it through anyway. The challenge succeeded on procedural grounds even though the vendor's price was clearly the lowest. After that, I started requiring a compliance matrix signed by every committee member before any bid could move to evaluation.
How the Process Actually Works
Typical workflow runs through several stages. First, bids are received at a set deadline. Late submissions are rejected outright unless an extension was formally approved. Then the technical evaluation happens, where each proposal is scored against the terms of reference. After that comes the financial evaluation on only the technically qualified bids. The committee then recommends the lowest computed bid or the most advantageous proposal depending on the procurement method used. One thing beginners often miss is the difference between responsiveness and eligibility. A bid can be eligible if the bidder meets the legal requirements, but responsive if the submission itself complies with every material term. I have seen bids thrown out for failing to include a signed declaration of no conflict of interest, even when the pricing was competitive. That document is usually listed as a mandatory requirement, and missing it makes the bid non-responsive regardless of how good the numbers look. The awards phase involves preparing a committee report that documents the evaluation scores, the recommendation, and the rationale. This report then goes to the accounting or finance unit for verification of funds availability. If there are no funds, the procurement cannot proceed even if the committee made a valid recommendation. This is one of the most common bottlenecks I encountered, especially in smaller organizations where budget cycles are not well coordinated with procurement timelines.
Common Pitfalls I Learned to Watch For
Scope creep in the evaluation criteria is a real problem. If the terms of reference are vague, evaluators will interpret requirements differently, and the scoring becomes inconsistent. I had one project where the spec said the vendor must provide reliable service, and two evaluators gave wildly different scores based on their personal definition of reliable. We fixed this by breaking every qualitative requirement into observable, scoreable indicators. Another issue is when the committee expands its mandate during evaluation. Some members start asking for additional information or modifications that were not part of the original request. This can create challenges from unsuccessful bidders who argue the evaluation was not conducted fairly. Once a bid is opened, the committee should only clarify ambiguities, not request changes to the proposal itself. If you are setting this up from scratch, I would recommend using a standardized evaluation rubric with weighted criteria. This cuts down on disputes and makes the process defensible. The tradeoff is that it takes more upfront time to develop, but it saves significant time later when someone inevitably challenges the award.
Get the Full Details
