RFP Module 1 cheat sheet

An RFP (Request for Proposal) is a formal solicitation document that states requirements and invites vendors to submit proposed solutions, pricing, and qualifications; it is distinct from an RFI (information-gathering) and an RFQ (price-focused quotation).

Standard RFP lifecycle stages in order: needs identification, requirements definition, RFP drafting, issuance, question/clarification period, proposal receipt, evaluation, vendor selection/award, contract negotiation, and post-award review.

Evaluation criteria and their relative weights must be defined and documented before proposals are opened; changing weights after receipt undermines fairness and is a common audit finding.

A weighted scoring model computes each proposal's total as the sum over criteria of (criterion score × criterion weight); weights should sum to 100% or 1.0.

Mandatory (pass/fail) requirements are screened before scored evaluation; a proposal failing any mandatory requirement is disqualified regardless of its weighted score.

The clarification/question period allows all bidders to receive identical written answers; answers are typically issued as an addendum to all participants to preserve equal information.

Conflict-of-interest and confidentiality controls apply throughout: evaluators must declare conflicts, and proposal contents are restricted to the evaluation team until award.

Bid responsiveness means the proposal conforms to the RFP's required format, forms, deadlines, and submission instructions; non-responsive bids can be rejected without evaluation.

Requirements should be written as measurable, verifiable statements (specific, testable criteria) rather than vague adjectives; each requirement should map to a method of verification.

Separate requirements into functional (what the solution must do) and non-functional (performance, security, availability, compliance, support) categories to avoid gaps in evaluation.

Use a consistent scoring scale (e.g., 0–5) with defined anchors for each score level so multiple evaluators apply the same standard and scores are defensible.

Consensus scoring (evaluators discuss and reconcile divergent scores) reduces individual bias compared with simple averaging of independent scores.

Best-value award considers price and non-price factors together; lowest-price award selects solely on price and is appropriate only when requirements are fully commoditized.

Total cost of ownership (TCO) evaluation includes license/subscription, implementation, training, support, and exit/transition costs - not just the quoted first-year price.

Reference checks and proof-of-capability (case studies, demos, pilot results) verify vendor claims that cannot be confirmed from the written proposal alone.

Award decisions should be documented with a rationale linking scores to criteria, supporting auditability and any subsequent debrief or protest process.

A clear governance structure assigns roles: RFP owner (process accountability), evaluation panel (scoring), procurement/compliance (fairness and rules), and approver (award sign-off).

Key RFP risks include scope ambiguity, unrealistic timelines, vendor lock-in, inadequate evaluation expertise, and leakage of confidential information; each should have a named mitigation.

Vendor lock-in is mitigated by requiring data export/interoperability, documented APIs, exit-assistance clauses, and ownership of data and configurations in the contract.

Contract terms should be derived from the RFP requirements and the winning proposal; the proposal can be incorporated by reference so commitments become contractual obligations.

Service levels (SLAs) should specify measurable targets, measurement method, reporting cadence, and remedies/credits for misses - not just aspirational language.

A structured debrief gives unsuccessful bidders feedback against the published criteria; it supports transparency and reduces the basis for formal challenges.

Post-award lessons-learned review captures what worked in requirements, evaluation, and negotiation to improve the next RFP cycle.

Core RFP sections typically include: background/purpose, scope, requirements, submission instructions, evaluation criteria and weights, timeline, terms and conditions, and required response forms.

Every RFP should state a single point of contact and prohibit direct vendor contact with other staff; violations can be grounds for disqualification.

Addenda are the formal mechanism to correct or amend an RFP; they must be numbered, dated, issued to all recipients, and acknowledged in the proposal.

Deadlines for questions and for proposal submission should be explicit with time zone; late submissions are handled per a stated rule (typically rejected).

A pre-proposal conference/site visit, if held, should be documented and its Q&A issued to all bidders as an addendum.

Quality review before issuance checks internal consistency: requirements align with evaluation criteria, weights sum correctly, dates are coherent, and referenced forms are attached.

Version control (document ID, revision number, issue date) prevents bidders from responding to superseded RFP versions.

Vendor qualification screening (financial stability, certifications, past performance, capacity) should occur before or during evaluation to avoid awarding to an incapable supplier.

Contract management after award tracks deliverables, milestones, invoices, and SLA performance against the agreed baseline.

Performance reviews should be scheduled and evidence-based, using the same metrics defined in the SLA rather than ad hoc impressions.

Change control: scope changes after award should follow a documented change-request process with impact assessment on cost, schedule, and risk.

Relationship management separates day-to-day operational contact from escalation paths for disputes and performance failures.

Exit/transition planning should be agreed at contract start (data return, knowledge transfer, parallel running) so termination does not create service gaps.

Distinguish the instruments: RFI = gather information/market scan; RFQ = price quotation for defined goods; RFP = proposed solution to a stated need; ITT/tender = formal bid often price-led.

Watch for qualifier words in questions: 'mandatory' implies pass/fail screening; 'weighted' implies scored evaluation; 'best value' implies combined price and quality.

When a question describes changing criteria or weights after bids are received, the correct answer is typically that this breaches fairness/transparency principles.

Sequence questions: identify the stage that must logically precede the one described (e.g., requirements definition precedes RFP drafting; evaluation criteria precede proposal opening).

If two answers seem valid, choose the one that best preserves equal treatment of bidders and documented, auditable decision-making.

Know the difference between an addendum (amends the RFP for all) and a clarification (explains without changing requirements).