Acceptable is a pass, not a grade
When a request for quotations says award will go to the lowest priced technically acceptable quote, or that quotes must be acceptable before any tradeoff is considered, it sets a bar. A quote either clears it or does not. There is no extra credit for clearing it by a wide margin, and no partial credit for nearly clearing it. That simple structure is the source of most surprises, on both sides of the table.
Firms are surprised when a strong quote is found unacceptable for one missing element. Program offices are surprised when a quote they consider weak has to be rated acceptable because it met every written criterion. Both surprises come from the same fact: acceptability is judged against the words in the request, not against anyone's sense of quality.
The choice between a lowest-price-acceptable award and a tradeoff is a separate topic. This piece is about the bar itself: how it is applied, why quotes fail it, and how agencies and firms can make the result clear.
Judged only against the stated criteria
The governing rule is short. An agency evaluates quotes against the criteria it stated in the request, and only those. It cannot fail a quote for missing something the request never asked for, and it cannot pass a quote that misses something the request required.
That rule cuts both ways. A program office cannot reject a quote because the proposed analyst lacks a certification it privately expected but never wrote down. Equally, a firm cannot argue its way past a requirement the request stated clearly, however minor the firm thinks it is.
There is some room at the edges. Evaluators may consider matters that are reasonably related to or encompassed by a stated criterion. If the criterion is "a feasible approach to each task," an evaluator can consider whether the proposed schedule makes the approach feasible, even though schedule is not named. What evaluators cannot do is add a new requirement under cover of an old one.
How evaluators read a technical quote
Most technical evaluations of services quotes follow the same pattern. The evaluator has the request open on one side, usually reduced to a list of criteria and required elements, and the quote on the other. For each criterion, the evaluator looks for where the quote addresses it and writes down whether it does.
The evaluator is not supposed to fill gaps from outside knowledge or from what the firm probably meant. The burden is on the firm to submit a quote that demonstrates compliance. A firm that has done excellent work for the same office still has to show it in the quote. Acceptability is a reading test, and the quote is the only thing the evaluator is allowed to read.
That has practical consequences. An element addressed in an attachment the request did not ask for may not be read. An element addressed indirectly, across three paragraphs in different sections, may not be found. A page limit that was exceeded may mean the excess pages are not evaluated at all. Evaluators reading a stack of quotes under time pressure find what is easy to find.
Evaluators also write findings that will be read by others: the contracting officer, a reviewer, and sometimes a firm that asks why it lost. Every unacceptable finding needs a reason tied to a criterion. That discipline protects firms, because a finding without a criterion behind it is hard to defend.
The four usual reasons a quote fails
Across services quotes, the reasons for an unacceptable rating fall into a small number of groups.
A required element is missing. The request asked for a quality control plan, a staffing table, a resume for each key role, or a response to each task, and the quote does not contain one. This is the most common reason and the most avoidable. It often happens when a firm adapts a previous response and does not check it against the new request.
The quote takes exception to the terms. A quote that conditions its price on different payment terms, a different period of performance, a cap on liability, or assumptions that contradict the statement of work is not agreeing to what the agency asked for. An exception to a material term generally means the quote cannot be accepted as written. Assumptions sections are where this usually hides, because an assumption that says "the government will provide all data within ten days" can quietly rewrite the requirement.
Proposed personnel do not meet the stated qualifications. The request said the study lead must have led at least two comparable evaluations, and the proposed lead's resume shows one, or shows two that are not comparable, or does not say. If a qualification is stated as a requirement, failing it fails the criterion. Vague resumes fail here as often as unqualified people, because the evaluator cannot infer experience the resume does not state.
The approach does not answer the requirement. The quote describes a sound approach to a different problem, or a generic approach that never engages the specific tasks. A data modernization quote that describes the firm's standard methodology without addressing the agency's named legacy system, data volumes or migration window can be found to lack a feasible approach, even if every sentence in it is true.
A checklist of acceptability failures
These are the specific failures we would check for before any services quote goes out, and the ones an agency evaluator is trained to catch.
- A task in the statement of work with no corresponding response
- A required plan, form, certification or attachment not included
- A key role without a resume, or a resume that does not state the required experience
- A named person who does not meet a stated degree, clearance or experience requirement
- An assumption, condition or cover letter term that conflicts with the request
- A period of performance, delivery date or place of performance different from the one stated
- An approach described in general terms that never touches the specific requirement
- A response over the page limit, or in a format the request excluded
- A price schedule that changes line items, units or quantities the agency set
- Material sent late, to the wrong address, or missing a required acknowledgment of an amendment
Most of these are clerical, not technical. That is the uncomfortable truth about acceptability: firms with strong technical capability fail it far more often from an unchecked document than from a weak approach.
What an acceptable response shows
The clearest way to understand the bar is to take a criterion and ask what, specifically, an evaluator needs to see to mark it met. The criteria below are illustrative, written the way many services requests phrase them.
| Sample criterion | An acceptable response shows | A response at risk |
|---|---|---|
| Technical approach: the quote describes a feasible approach to each task in the statement of work | A heading for each task using the agency's numbering; for each, what will be done, by whom, with what data or tools, and when | A methodology overview that covers the tasks in aggregate, so the evaluator cannot point to where task three is answered |
| Understanding: the quote demonstrates an understanding of the requirement | The specific problem restated in the firm's own words, with the constraints and risks that matter for this work | The background section of the request repeated back, or a general description of the field |
| Key personnel: the lead has led at least two comparable projects | A resume naming two projects with dates, scope, the person's role, and why each is comparable | A resume listing years of experience and skills, with no project the evaluator can count |
| Quality control: the quote describes how deliverables will be reviewed before submission | Who reviews what, at what stage, against what standard, and how errors are tracked and corrected | A sentence stating the firm is committed to quality |
| Schedule: the approach meets the delivery dates stated in the request | A schedule tied to the stated dates, showing the dependencies on government actions | A schedule on different dates, or one with no dates at all |
The pattern in the middle column is the same in every row: the criterion's words, answered where the evaluator expects to find them, with specifics that can be checked. The right column is not always wrong in substance. It is hard to mark as met.
Acceptability is not the same as responsibility
Technical acceptability asks whether the quote meets the stated criteria. A separate question, responsibility, asks whether the firm itself is able to perform: whether it has adequate resources, a satisfactory record of integrity and performance, and the ability to meet the schedule, and whether it is registered and not excluded from federal awards.
The distinction matters because the two are decided differently. Acceptability is decided from the quote. Responsibility is a determination the contracting officer makes about the apparent winner, drawing on registrations, records and other information. When a contracting officer finds a small business not responsible, the matter generally goes to the Small Business Administration, which can issue a certificate of competency. Agencies writing criteria should keep the two questions apart rather than folding general capacity into a technical pass or fail.
How agencies should write acceptability criteria
Because acceptability is binary, the criteria do all the work. A criterion that an evaluator cannot apply consistently produces findings that are hard to defend in either direction.
Write each criterion as something a reader can find. "Describes a feasible approach to each task" can be checked task by task. "Demonstrates excellence" cannot be checked at all, and does not belong in a pass or fail evaluation.
Say exactly what is required versus helpful. If a certification or degree is a requirement, say "must." If it is a preference, either drop it from a pass or fail evaluation or move to an evaluation that can give credit for it. A preference stated as a requirement eliminates firms that could have done the work.
Keep the number of criteria proportionate. A $120,000 analytic study does not need twelve technical criteria. Three or four that define a competent response, plus the key personnel requirements, are usually enough. Every additional criterion is another way for a capable firm to fail on paper.
Align the instructions with the criteria. If the evaluation looks for a quality control plan, the instructions should ask for one, in a named section, within a stated page count. When the instructions and the criteria use different words for the same thing, firms answer the instructions and evaluators look for the criteria.
Plan for clarity, not for rescue. Clarifications let an agency resolve minor issues, such as an obvious clerical error, without opening discussions. They are not a way to let a firm supply a missing required element. Criteria written clearly enough that nobody needs rescuing are the real fix.
How firms should map every criterion
The single most effective habit for clearing the bar is a compliance matrix built before writing begins. List every instruction, every evaluation criterion and every "shall" in the statement of work, give each one a row, and record where in the quote it is answered.
Then structure the quote to mirror the request. Use the agency's section numbering and task names in your headings, so the evaluator's list and your table of contents match. Put the answer to each criterion in the first sentences of its section, in the criterion's own language, and put the supporting detail after it.
The cold read
Give the request and the finished quote to someone who did not write it, and nothing else. Ask them to mark each criterion met or not met and to note the page where they found it. That reviewer is doing exactly what the evaluator will do, and anything they cannot find in a few minutes, the evaluator will not find either. Fix every gap they report, then check the fix against the matrix.
Finally, read your assumptions section as if you were the contracting officer. Every assumption that changes a government obligation, a date or a scope is a potential exception. Keep the ones that are true and necessary, word them as clarifying rather than conditioning, and remove the rest.
Price reasonableness, briefly
Clearing the technical bar is necessary but not sufficient. Before award, the contracting officer must also determine that the price is fair and reasonable. In a competitive buy, that determination is often based on comparison with the other quotes received. It can also draw on prior prices for similar work, an independent government estimate, or market research on rates.
Reasonableness is mainly a test of whether a price is too high. Whether a price is too low to perform, often called price realism, is a separate analysis, and on fixed-price work agencies generally apply it only when the request says they will. For firms, the practical point is that a price far above the other quotes or the government's estimate needs a reason the contracting officer can see, usually in the staffing and hours the quote already shows.
Frequently asked questions
It means the quote meets every technical criterion stated in the request. It is a pass or fail rating, not a score. A quote that meets every criterion is acceptable regardless of how much better it might be, and a quote that misses one required element is generally unacceptable, however strong the rest of it is.
No. An agency must evaluate against the criteria it stated. Evaluators may consider matters reasonably related to or encompassed by a stated criterion, but they cannot add new requirements. If a requirement matters, it has to be written in the request.
A missing required element: a task with no response, a missing plan or attachment, or a key personnel resume that does not show the stated experience. These are usually document control failures rather than technical ones, and a compliance matrix checked by someone who did not write the quote catches most of them.
Generally not through clarifications, which are limited to minor issues such as clerical errors. Supplying a missing required element would usually amount to revising the quote. The reliable approach is to make sure every element is present and easy to find before the deadline.