8.1 Building the Solicitation Package

8.1 Building the Solicitation Package

Quick Answer: A solicitation package is the Government’s complete request for offers—requirements (SOW/PWS/SOO), evaluation factors, instructions to offerors, representations and certifications, and clauses/provisions—written so sections are internally consistent. Defects (ambiguous SOWs, factors that do not discriminate, conflicting instructions, missing or mismatched clauses) create protest risk and poor awards. CON 3990V tests whether you can assemble a package that elicits comparable, evaluable offers.

After acquisition planning and market research shape what and how to buy, Request Offer (FAI competency 2.1.2, about 12 questions) is the craft of turning strategy into a solicitation offerors can understand and respond to. The package is not a pile of templates—it is a single coherent instrument that defines the requirement, the competition rules, and the contract terms that will bind the winner.

What belongs in a solicitation package

Exact Uniform Contract Format (UCF) section letters appear most often in formal Part 15/Part 14 packages, but the substance is what CON 3990V cares about across methods:

Exam cue: If a stem says “the package is missing evaluation factors” or “instructions conflict with the SOW,” the defect is in package assembly, not merely “bad luck at award.”

SOW vs PWS vs SOO — choose the right requirements voice

Requirements documents tell industry what success looks like. Using the wrong form creates either micromanagement or unmeasurable outcomes.

Performance-based service acquisition themes push teams toward PWS/SOO when outcomes can be defined. Design or process-heavy work (construction sequences, tightly controlled manufacturing steps, safety-critical procedures) may still need SOW-style specificity.

Scenario — SOW written as a vendor’s brochure. A requiring activity pastes an incumbent’s marketing language into the SOW, naming proprietary tools. Correct CO response: rewrite for competition; use brand-name-or-equal only with justification; prefer performance outcomes when feasible.

Scenario — “PWS” with no standards. The document says “provide excellent help desk support” with no metrics. Correct response: define measurable standards (e.g., first-call resolution %, ticket aging, availability) and methods of surveillance—otherwise evaluation and later quality assurance collapse.

Evaluation factors structure

Evaluation factors answer: How will we distinguish among offers? They must:

1. Relate to the requirement — technical factors map to real discriminators in the SOW/PWS/SOO.
2. Be disclosed — offerors know the factors and relative importance (or the LPTA rule set).
3. Be applied consistently — same standard for all offerors.
4. Support a defensible selection — tradeoff documentation or LPTA pass/fail logic later in Award phase.

Common factor families (illustrative, not a mandatory menu):

Relative importance language matters in tradeoffs: if technical is “significantly more important than price,” the file must actually trade value against price—not ignore price, and not secretly reverse the stated hierarchy.

Exam trap: Factors that do not create meaningful distinctions (“excellent communication skills” for every commercial commodity buy) waste evaluation resources and invite challenges that factors were unreasonable or unrelated to the acquisition.

Instructions to offerors

Instructions (often Section L in UCF) tell industry how to package the response:

• Volumes (technical, past performance, price) and page limits
• Required formats, fonts, file types, electronic portals
• What to address under each evaluation factor (proposal outline)
• Oral presentation rules if used
• Questions deadline and amendment process
• Representations required with the offer vs maintained in SAM

Consistency rule: If instructions ask for a 10-page technical approach but evaluation factors include five deep subfactors that cannot fit, the package is defective. If the PWS demands monthly reports but instructions never request a staffing or quality approach tied to reporting, evaluators will invent criteria or under-evaluate risk.

Representations and certifications

Reps and certs establish legal and socioeconomic status, responsibility-related statements, and compliance assertions (e.g., small business status, Buy American/Trade Agreements themes when applicable, debarment certifications, taxpayer identification, ownership). Many are collected through SAM and incorporated by reference, but the CO still ensures the solicitation requires what the award decision and clauses depend on.

Exam themes:

• Relying on SAM does not excuse ignoring an obvious misrepresentation or a missing required representation for the acquisition type.
• Socioeconomic set-asides require offerors to represent status consistent with the set-aside.
• False certifications raise integrity issues (ties to Part 3 / standards of conduct)—not “just paperwork.”

Attaching clauses and provisions

Provisions govern the solicitation phase; clauses become contract terms. Selecting clauses is driven by:

• Dollar value and procedure (commercial Part 12 vs noncommercial; simplified vs formal)
• Contract type (fixed-price vs cost-reimbursement changes clause sets)
• Work nature (services, construction, R&D, IT, security)
• Socioeconomic and labor requirements
• Agency supplements (DFARS for DoD—awareness level; see Section 8.3)

Use the FAR matrix / prescription logic conceptually: include clauses that apply; do not dump the entire FAR into every buy. Missing a mandatory clause (e.g., changes, disputes, termination, inspection for the work type) can invalidate assumptions about Government rights. Including inapplicable heavy clauses on a commercial simplified buy can chill competition and conflict with Part 12 commercial terms preferences.

Consistency across sections (the protest magnet)

Protests and evaluation failures often stem from internal inconsistency, not from exotic legal theories:

Quality control habit: Crosswalk the package—requirement → factors → instructions → CLINs → clauses—before release. Peer review by someone who did not write the SOW catches “tribal knowledge” omissions.

Common package defects that create protests

CON 3990V-style recognition list:

1. Ambiguous or impossible requirements — offerors cannot know what “compliant” means.
2. Unduly restrictive specifications without justification — limits competition.
3. Unstated evaluation criteria applied later — classic fairness violation.
4. Changing the basis of award midstream without proper amendment/process.
5. Unequal access to information — one firm gets clarifications others do not.
6. Misleading or conflicting instructions on due dates, formats, or mandatory content.
7. Failure to amend when Q&A reveals a material defect in the package.
8. Evaluation factors unrelated to meaningful distinctions among offers.

Scenario A — Hidden preference for incumbent tools. Evaluation factor “familiarity with Agency X’s legacy System Z” when the PWS could allow equivalent approaches. Risk: protest for unequal treatment / restrictive criteria. Fix: evaluate approach to meeting outcomes, not loyalty to incumbent tools, unless true sole-source technical constraint is justified elsewhere.

Scenario B — Price only in the narrative, not in the factors. Package lists only technical factors but award is made on price. Risk: failure to follow stated evaluation scheme.

Scenario C — Incomplete attachments. Wage determination or key drawing missing at release; only the incumbent has the prior version. Risk: unequal information; amend and extend as needed.

Team roles in package building

The CO owns the solicitation as a business instrument. Technical ownership of the SOW does not authorize releasing a package that fails competition or evaluation fairness.

CON 3990V closed-book anchors

• Package = requirements + rules of the competition + future contract terms.
• SOW (tasks) / PWS (performance standards) / SOO (objectives for industry solutions).
• Factors must relate to meaningful distinctions and match instructions.
• Crosswalk sections before release; amend when material defects appear.
• Defects that chill competition or hide evaluation rules are protest fuel.

---

Bottom line: Building the solicitation package is how Request Offer becomes operational. Align SOW/PWS/SOO, evaluation factors, instructions, reps/certs, and clauses into one consistent story. On CON 3990V, recognize package defects—ambiguity, inconsistency, unstated criteria, and restrictive requirements—as failures of pre-award craftsmanship that courts and GAO see long before award documentation is written.