When I first set out in federal contracting over 15 years ago, I remember feeling underwater, swimming in a vast ocean of foreign terminology. Abbreviations like “IDIQ” and phrases like “Firm Fixed Price” were constantly volleyed around my office. I was just supposed to know what they meant!
As I quickly learned, the type of contract used by the Government in executing a program impacts many aspects of the work itself. Most importantly, there must be a balance between incentivizing the contractor to work efficiently and cost-effectively, while hitting all the vital benchmarks for the federal government customer.
For the uninitiated, every Federal Government opportunity will fall into a pre-selected type. The Federal Acquisition Regulation (FAR) defines a dozen different contract types. The contract type dictates how the work is performed, how payment to the Prime contractor is delivered, and how the Government anticipates receiving the goods or services they are seeking through the program. Almost always, contracting boils down to a question of risk. What is the Government willing to take on regarding performance risk? Is the schedule proposed attainable? Is the goal achievable?
Here are five of the most conventional contracting types and how they impact both the Government and contractors:
Firm Fixed Price (FFP): This contract sets a cost for the work performed prior to the work beginning. This places the largest risk on the contractor performing the work, as there will be no reimbursement for costs incurred exceeding that budgetary threshold. This type of contract is often used in the commercial space where costs can be fairly estimated and assumption of risk reasonably forecasted. Best used when: Requirements are clearly defined.
Firm Fixed Price (FFP) Level-of-Effort (LOE) : If the work prescribed is quite vague, and the Government isn’t assured the task is achievable, this approach may be best applied. It allows the set cost parameters of FFP while the Government must assume the risk associated with the administrative burden of tracking the contractor’s best level of effort to achieve the desired results within the specified LOE. Best used when: Requirements can be somewhat defined and the Government is willing to assume some administrative obligation.
Cost Reimbursement: Within this framework, the incurred costs are reimbursed as described in the contract language. The contractor may not exceed the pre-established ceiling without the approval of the contracting officer. This type of contract places emphasis on expediency in starting the work, thus placing markedly more risk on the government’s side. Best used when: Requirements are unclear, and success isn’t guaranteed.
Time and Materials: If the Government’s goals and required approach is vague and the timeline or goals are equally undefined, this is the optimal approach. It allows for flexibility in defining labor types but does require a more precise knowledge of the cost for any billable labor. The Government will pay for hours worked and any Other Direct Costs (ODCs) incurred all at cost pursuant to accepting a Statement of Work (SOW) that gives some outline to the anticipated work. Best used when: No other contract type is suitable, and it is possible to estimate labor rates (as well as overhead/profit), but not hours or material required to satisfy the goal.
Indefinite-Delivery Indefinite-Quantity: When the Government isn’t sure about the specific number of ‘widgets’ they need for a project, but can create a basic contract upon which an indefinite number of delivery orders or task orders are placed. This allows the Government to attempt broad specialization with selection of a strong Prime, while simultaneously granting the government inherent risk in that gameplan. Best used when: the project is a service contract and works as a base year plus option-year structure.
The vital takeaway from any Government contracting discussion is to remember the assessment of risk. Who is taking on the most risk? What is the goal, and is it reasonably achievable? Ultimately those are the answers that will take you the furthest in your understanding and help you and your firm determine if the opportunity is worth pursuing.
Kazia Levin is an Assistant Director of Contracts at BZ. She is a federal contracting professional with extensive experience guiding program management, policy implementation and financial goal-setting.
BZ offers comprehensive contracts management and surge support services. Learn more here.
Do your homework
Get the basics in place
Point 1: They Have the Capabilities
Point 2: They are the Boss
Reason 1: Are You Technically Capable?
Reason Three: Can They Work With You?


The first clue to making our proposal focused on our clients is to use their language. This applies throughout your proposal. There are standard definitions in the industry for corporate experience (what you have done) and past performance (how well you have done it). However, that distinction is not always clear to everyone. Sometimes, clients ask for “past performance” when they actually mean corporate experience. In these cases, do not fix their terminology – use their terminology.
Too often, people rely heavily on prior write-ups when putting together your corporate experience examples. When developing your submission, however, taking boilerplate and putting it in the proper format is not an option. Just copying and pasting in a generic list of work performed and achievements does not speak to the individual needs of the client. Therefore, besides just using the client’s terminology, you need to select the portion(s) of the work you are currently doing that are clearly relevant to the solicitation. I have my teams talk in broad strokes in the opening paragraph with a two to three line summary of the overarching contract. Then, I have them specifically state how it is relevant in terms of the evaluation criteria and work expected. For the former, often in Federal Government bids we are asked to write to size, scope, and complexity. For the latter, we want to show alignment to the work required (the performance work statement/statement of work). In either case, a nice summary table can work wonders. Include all the PWS/SOW requirements and allow for a checkbox or a meatball chart to show that alignment.
As hard as our teams work to execute on all of our contracts, nothing is perfect. Things go wrong. Sometimes it’s something minor. Other times, it is a serious issue that results in escalation, cure notices, and egg on our face.
Tip 3 – Be Open to Mentoring in Your Career From All Types
Without a strong solution, our proposals are doomed to fail. A good solution explains our solution, focuses our writers, and makes sure we provide value to the client. If we do not have a strong solution, we are basically a rudderless ship. However, we cannot just will a great solution into being. It takes hard work, patience, and a focused team to articulate what we will do and why we are the best fit for the client. So how do we develop winning solutions that gives our team the tools to succeed? Here are four tips for proposal professionals on how to ensure we are on the right page.