4.2 Preparing Solicitations: RFI, RFP & RFQ (Task 1-A-9)

Task 1-A-9 asks you to prepare solicitations for competitive bids, quotations, and proposals. On CPSM Exam 1, that means selecting the right RFx instrument, writing requirements and terms that suppliers can price and propose against, disclosing how offers will be judged, and issuing a package that supports fair, comparable responses.

A solicitation is a controlled market conversation. If the document is vague, biased, or silent on evaluation rules, you do not get “creative supplier ideas”—you get non-comparable noise and fragile awards.

Choosing the Right Instrument: RFI, RFP, RFQ

Decision cues

• Use an RFI first when you do not yet know feasible approaches, typical lead times, or which suppliers can even perform. Do not treat RFI responses as final offers unless you explicitly convert the process with equal notice.
• Use an RFQ when “apples-to-apples” is achievable: same specification, same quantities, same delivery points, same Incoterms, same payment terms.
• Use an RFP when you need suppliers to propose how they will meet outcomes (staffing model, transition plan, quality system, innovation options) and you will score those elements—not only unit price.
• Avoid hybrid confusion: calling a document an “RFP” while evaluating only lowest price, or an “RFQ” while asking for open-ended solution essays, signals process immaturity.

Some organizations use RFx as the umbrella term and two-step processes (RFI → shortlist → RFP/RFQ). That is valid when gates and communications remain transparent.

Building the Content: Specs, SOW, and Terms

Specifications and requirements

Requirements should be:

• Complete — quantities, locations, service windows, quality metrics, acceptance tests, reporting, and interfaces.
• Clear — measurable language (“≤ 2% defect rate”) beats slogans (“world-class quality”).
• Necessary — avoid over-specification that locks an incumbent’s brand or proprietary method unless justified and approved.
• Consistent — drawings, BOM lines, and narrative SOW must not contradict each other.

Distinguish mandatory requirements (pass/fail) from desirable features (scored). Mixing them without labels creates disputes when a low-price bid misses a “nice-to-have” that evaluators secretly treated as mandatory.

Statement of Work (SOW)

For services and complex deliverables, the SOW describes scope, deliverables, roles, timelines, acceptance, and governance. Strong SOWs answer:

1. What work is in scope / out of scope?
2. Who provides what inputs (buyer data, access, equipment)?
3. How is progress measured and accepted?
4. What happens when scope changes?

Weak SOWs shift all ambiguity to post-award change orders—often destroying the savings case.

Commercial and legal terms

Include or attach the terms you expect to govern award: payment terms, Incoterms or delivery terms, warranties, liability, IP, confidentiality, insurance, audit rights, termination, and compliance clauses (labor, trade, data privacy, ESG where required). If certain terms are non-negotiable, say so. If redlines are allowed, define the process and deadline so commercial evaluation stays orderly.

Packaging checklist

A complete solicitation package typically includes:

• Cover letter / invitation and purpose statement
• Instructions to bidders (format, portal, page limits, languages)
• Timeline (intent to bid, questions due, answers published, submission due, presentations if any)
• Q&A rules (written only; answers shared with all; no private coaching)
• Requirements / specs / SOW / drawings
• Pricing schedule / cost breakdown template
• Evaluation criteria and relative importance
• Mandatory forms (conflict of interest, certifications, references)
• Draft contract or key terms
• Submission checklist and late-bid policy

Disclosing Evaluation Criteria

Fair competition requires advance disclosure of how offers will be judged. At minimum, state:

• Categories to be evaluated (technical, management, past performance, price/TCO, sustainability, etc.)
• Relative importance or weights (or a clear ranking such as “technical more important than price”)
• Any mandatory pass/fail gates (financial viability, certifications, site visits)
• Whether discussions, presentations, or BAFO rounds may occur

Disclosure does not mean revealing every sub-score formula in public-sector-style detail in every commercial setting—but hiding that “relationship” or “incumbency comfort” will decide the winner is unethical and exam-wrong. If soft factors matter, define observable proxies (reference quality, transition plan completeness, demonstrated capacity).

Common disclosure failures

• Publishing criteria after proposals arrive
• Using unpublished “gut feel” to override the scorecard
• Weighting price at 90% in the document but selecting on unstated “strategic fit”
• Allowing one bidder private clarifications that change requirements without issuing an addendum

When requirements change through Q&A, issue a formal addendum to all participants and adjust due dates if needed so equality of information is preserved.

Writing for Comparable Offers

Comparability is the hidden quality metric of solicitation design:

• Provide a mandatory pricing template so totals map to the same cost elements.
• State assumptions (volume forecasts, service levels, indexing formulas).
• Require exception logs: bidders list every deviation from specs/terms in one place.
• Separate base bid from options so evaluators do not mix scopes accidentally.

For global events, clarify currency, tax treatment, and Incoterms. For services, require named key personnel or role cards if continuity matters—and state whether substitutions need approval.

Ethics, Competition Integrity, and Market Signaling

Prepare solicitations that invite real competition:

• Do not tailor specs to a single brand without justification and approved exception.
• Do not share one bidder’s innovative idea with another mid-process without a structured, equal revision of requirements.
• Do not signal a predetermined winner through unrealistic timelines only the incumbent can meet—unless the timeline is a true operational constraint and disclosed as a mandatory requirement.

Market signaling cuts both ways: overly aggressive timelines or incomplete data cause serious suppliers to no-bid, leaving you with weak competition and a false sense of market testing.

From Draft to Release: Quality Gate

Before release, run a cross-functional review:

A 48-hour peer review that catches contradictions is cheaper than a failed competition.

Exam lens: Match instrument to ambiguity (RFI/RFP/RFQ), insist on clear specs/SOW/terms, and treat published evaluation criteria as part of the solicitation—not an afterthought.