GovCon Glossary

An official change an agency issues to a solicitation after release, correcting an error, answering a Q&A, revising requirements, or shifting the proposal due date. Solicitations typically require offerors to acknowledge each amendment for their proposal to remain responsive, so missing one can put an otherwise compliant submission at risk.

The final proposal revision an offeror submits after the government closes discussions in a negotiated procurement, incorporating any last changes to price, terms, or technical approach. Once BAFOs are in, the contracting officer evaluates them against the stated criteria and makes the award decision; no further revisions are typically allowed.

A DoD competitive acquisition method, authorized under 10 U.S.C. 3458, that solicits innovative commercial products or services through a general solicitation instead of a traditional RFP. Submissions go through a streamlined, merit-based review rather than full FAR Part 15 negotiation, and any resulting award must use a fixed-price contract type.

A preview version of a solicitation that an agency releases before the official RFP, giving industry a chance to review draft requirements, terms, and evaluation criteria and submit comments or questions. Agencies typically use it to surface ambiguities, gauge competitive interest, and refine the final RFP before formally issuing it.

The contracting officer's formal written notification to a selected offeror that its proposal has been chosen for award, typically identifying the contract number, value, and scope. It signals selection but isn't itself the binding contract: that's created once the award document is executed by both parties.

The person on a proposal team responsible for the physical and electronic production of proposal deliverables: managing templates, formatting, page limits, graphics integration, and final assembly for submission. The PPM works closely with writers and the review team to make sure the document ships on time and meets every formatting requirement in the solicitation.

The discipline of building quality checkpoints into proposal development (compliance matrices, structured color-team reviews, and style/consistency checks) so the final submission meets every solicitation requirement and reads as one coherent document. PQM is meant to catch compliance gaps and weak content before they cost the company a shot at award.

A solicitation used by federal agencies (most often HHS, NIH, and other grant-making bodies) to invite applications for funding under a grant or cooperative agreement rather than a procurement contract. RFAs are governed by grants law rather than the FAR, with the government acting as a funding partner rather than a buyer of goods or services.

A market research tool agencies use to gather information about industry capabilities, potential solutions, or rough pricing ahead of a formal solicitation. Responding to an RFI isn't competing for a contract (there's no evaluation or award), but it's a real opportunity to shape requirements before the RFP is written.

A formal solicitation in which an agency describes its requirement and asks offerors to submit a detailed proposal (technical approach, management plan, past performance, and price or cost) for evaluation and negotiated award. RFPs are used for complex procurements where price alone can't determine best value.

A solicitation requesting price and delivery terms for a specified supply or service, most common in simplified acquisitions and against GSA Schedule or IDIQ vehicles. A response to an RFQ is a quote, not a binding offer; it's the government's subsequent purchase order or task order that actually forms the contract.

Shorthand for the family of formal solicitation and inquiry documents (RFP, RFQ, RFI, RFA, and similar vehicles) that agencies use to research the market or solicit offers. Capture and BD teams use 'RFx' as a catch-all when referring to any of these documents without specifying which type.

The cover page of a federal solicitation, typically the SF 33 or SF 1449, identifying the solicitation number, issuing agency, proposal due date, and basic administrative details. Upon award, this same form becomes Section A of the executed contract, carrying the signatures that make it binding.

The part of a solicitation and contract that lists the contract line items (CLINs): the specific supplies or services being bought, along with quantities, units, and pricing structure. It's where offerors enter proposed prices and where the resulting contract reflects exactly what the government is paying for each line item.

The technical heart of a federal solicitation, containing the Statement of Work, Performance Work Statement, or specifications that describe exactly what the government needs delivered or performed. Contractors build their technical and management proposal volumes directly against the requirements laid out here.

The part of the schedule that spells out packaging, packing, preservation, and marking requirements for deliverables, covering things like container specs, labeling, and shipping documentation. It matters most on supply and hardware contracts where physical goods must meet specific handling or transit standards.

Defines how the government will inspect and accept the goods or services delivered under the contract, including quality assurance standards, inspection location, and who holds inspection authority. It sets the bar a contractor's deliverables must clear before the government will pay for them.

States the delivery schedule or period of performance, place of performance, and the timing requirements a contractor must meet, whether that's shipping dates for supplies or completion milestones for services. Missing these dates without an approved extension can trigger default remedies.

Lays out the administrative mechanics of running the contract after award, such as accounting and appropriation data, invoicing instructions, and who serves as the Contracting Officer's Representative. Contractors reference it for how to submit invoices and route contract administration questions.

A catch-all for contract terms specific to this procurement that don't fit anywhere else in the Uniform Contract Format, such as organizational conflict of interest rules, security requirements, key personnel provisions, or option terms. It's often where the most consequential nonstandard requirements live.

Lists the FAR, DFARS, and agency-specific contract clauses that will govern the resulting contract, either in full text or incorporated by reference. It's the legal terms and conditions a contractor is bound by once awarded, separate from the technical requirements described in Section C.

An index of every attachment, exhibit, and standalone document incorporated into the solicitation, such as the full Statement of Work, wage determinations, CDRLs, or sample deliverable formats, each identified by title, date, and number of pages. It's the map to everything referenced but not printed inline.

Where offerors complete self-certifications and representations required by the solicitation, such as small business size status, tax matters, and compliance statements, many of which are now satisfied through an offeror's current SAM.gov registration rather than retyped into the proposal.

The instructions offerors must follow to prepare and submit a compliant proposal, covering volume structure, page limits, formatting rules, required content, and submission deadlines. Proposal teams treat it as the literal outline for building the proposal, since noncompliance here can get an offer rejected outright.

States the evaluation factors and subfactors the government will use to judge proposals, along with their relative importance, and describes the basis for award, whether lowest price technically acceptable or a tradeoff among price and non-price factors. Every proposal should be written to directly answer these factors.

The group of government evaluators, drawn from technical, cost, and contracting disciplines, who score proposals against the criteria in Section M and document their findings for the source selection authority. On some procurements this team performs the combined duties of a separate evaluation board and advisory council.

A person with deep, specific expertise, technical, programmatic, or domain, whose knowledge shapes a proposal's solution, differentiators, or technical content. Capture and proposal teams pull SMEs into solutioning sessions, technical writing, and reviews because their credibility and detail are hard to fake on paper.