RFP Module 1 common mistakes
RFP Module 1 · Understand the traps and how to avoid them.
Treating 'RFP' as a single document type and answering questions about proposal writing, bid evaluation, or contract negotiation without first pinning down which stage of the request-for-proposal lifecycle the question is placed in.
Candidates skim the stem, see familiar procurement vocabulary, and import knowledge from adjacent areas (tender evaluation, contract law, project delivery) rather than anchoring on the lifecycle stage the question actually tests.
What to do instead
Before answering, write one word for the stage the stem describes (planning, drafting, issuing, clarifying, evaluating, awarding, debriefing). If the stem does not make the stage explicit, treat that ambiguity as the point of the question and choose the option that is correct across the widest range of stages.
Confusing the roles of the requesting organisation, the procurement function, and the evaluation panel, and attributing decisions to the wrong party.
Module 1 content introduces governance and responsibility boundaries early, and candidates rely on workplace habit ('procurement decides everything') instead of the role definitions the exam uses.
What to do instead
Build a one-page responsibility map: who approves the requirement, who owns the RFP document, who scores responses, who signs the award, who handles clarifications. Test every option against that map before selecting.
Selecting the most comprehensive-sounding option in questions about RFP content, instead of the option that is mandatory, proportionate, or fit for purpose.
Real RFP templates are long, so candidates equate 'more requirements' with 'better RFP' and pick answers that add scope, criteria, or documentation without need.
What to do instead
Look for the qualifier in the stem ('minimum', 'proportionate', 'sufficient to'). Where a question asks what an RFP must contain, answer from mandatory elements only; where it asks what is good practice, prefer the option that matches effort to risk and value.
Mixing up mandatory, desirable, and scored requirements, and answering as though a desirable criterion can disqualify a bidder or a mandatory one can be traded off against price.
The words 'must', 'should', 'will be evaluated', and 'pass/fail' are used loosely in everyday writing, and candidates map them onto their own organisation's habits rather than the exam's definitions.
What to do instead
For each option, label it must-pass, scored, or informative. Eliminate any option that lets a desirable item exclude a bidder or lets a scored item act as a gate. Practise by rewriting ten requirement sentences into pass/fail versus weighted form.
Ignoring the timeline and process rules around clarifications and questions - deadlines, whether answers are shared with all bidders, and whether late questions can be answered.
Candidates focus on document content and treat process questions as administrative trivia, so they choose the courteous answer (answer the individual bidder privately) over the fair one (share with all).
What to do instead
Adopt one rule and apply it consistently: information that could affect a bid must reach every bidder equally, and deadlines exist to preserve equal opportunity. Use that rule to resolve any clarification scenario, including late-question and one-bidder-asks cases.
Answering fairness and conflict-of-interest questions by choosing the option that removes the appearance of bias at any cost, such as excluding an incumbent bidder or restarting the process.
Candidates over-apply the precautionary instinct; the exam generally tests managing the conflict (declaration, recusal, documented evaluation) rather than avoiding the situation entirely.
What to do instead
Distinguish managing a conflict from avoiding it. Prefer options that disclose, document, and isolate the conflicted person while keeping competition open; reject options that exclude a legitimate bidder or cancel the RFP without a stated justification.
Treating evaluation criteria and their weightings as something that can be adjusted once responses are received, or as something that need not be published in the RFP.
In practice criteria are sometimes refined during evaluation, and candidates transfer that experience to the exam, where the published criteria are binding.
What to do instead
Memorise the principle: criteria and weightings are fixed at issue and disclosed to bidders; changes after the deadline invalidate comparability. Any option that introduces post-submission criteria, retroactive weighting, or undisclosed sub-criteria is wrong.
Misreading questions about specifications - choosing brand names or over-specified technical requirements when the stem asks for an outcome-based or non-restrictive specification.
Candidates equate precise specifications with good specifications, and brand-name examples feel concrete and therefore correct.
What to do instead
Check whether the stem is testing competition or clarity. If competition, reject brand names and unnecessarily restrictive requirements unless a justified equivalent clause is present. If clarity, prefer measurable outcomes over vague quality language.
Confusing the RFP with the related documents in the same family - RFI, RFQ, ITT, and contract - and answering with the rules of the wrong instrument.
The instruments overlap in content and vocabulary, and candidates answer from the label in the stem rather than from the purpose each instrument serves.
What to do instead
Learn one differentiator per instrument: RFI gathers information with no award, RFQ prices a defined requirement, ITT invites tenders against defined terms, RFP seeks a proposed solution and approach, contract governs performance after award. Identify the purpose in the stem first, then apply that instrument's rules.
Rushing multi-statement questions and stopping at the first true statement rather than evaluating every statement, and failing to flag the ones that are true only in some circumstances.
Time pressure and the 'best answer' habit lead candidates to accept a plausible statement without checking the others, while the question requires counting or ranking statements.
What to do instead
For statement-based items, mark each statement T, F, or 'true only if' before looking at the options, then match your pattern to the choices. Where an option is conditionally true, treat it as false unless the stem supplies the condition.