How to reconcile conflicting instructions in an RFP

Diagnosis

Prove that the instructions actually conflict

Start with two complete propositions, not a note that says “page limit unclear.” One record might state: “RFP section 4.2 limits the technical response to 30 pages.” The other might state: “Annex B allows up to 10 pages for each of four technical criteria.” Record whether covers, tables, appendices and mandatory forms count. Many apparent contradictions disappear when the team identifies that one limit applies to the response as a whole and the other applies only inside an annex, or that one instruction governs a particular volume. If both rules still apply to the same material and cannot both be met, the conflict is real.

Keep the original words, including headings and cross-references. A paraphrase can remove the condition that resolves the issue. Record the file name shown to bidders, the internal checksum or version identifier, publication date, section, page and portal location. Add the response objects affected: compliance row, answer IDs, price cells, attachments, contract deviations and submission tasks. This is not clerical overhead. It establishes the evidence needed for a clarification and prevents a local interpretation from spreading without scrutiny.

Authority

Use the buyer’s hierarchy, not a hierarchy invented by the bid team

Look first for an explicit order of precedence and read its scope. It may apply to the future contract, the solicitation, the response instructions or only a named group of documents. Those are different jobs. The United States Federal Acquisition Regulation, for example, contains a Uniform Contract Format clause with a stated order for resolving inconsistencies. That clause is useful evidence when it is actually included and applicable; it is not a universal ordering rule for every RFP. The same caution applies to a phrase such as “the main document prevails.” Confirm which document says it, what it covers and whether a later buyer-issued amendment changes the position.

Build an authority chain from the procurement itself. An issued amendment can replace or modify an earlier requirement. An official clarification may explain how the buyer expects an instruction to be applied, subject to the procedure and its stated status. A portal notification may communicate the amendment but should not be treated as new substantive authority unless the procurement makes it so. File names, folder order, document size and the team’s preferred interpretation carry no authority. If the pack provides no rule that resolves a material contradiction, the honest result is “unresolved,” followed by clarification or approved risk treatment.

• Read the scope of every precedence clause before applying it.
• Confirm that a changed instruction was issued through the required channel.
• Distinguish a formal amendment from a message that only announces it.
• Keep “unresolved” as a valid state when the evidence does not decide the issue.
• Escalate legal interpretation to qualified counsel where the consequence requires it.

Decision

Make the resolution specific enough to execute

A usable decision record says more than “follow Annex B.” It states the selected instruction, the evidence for its authority, the exact work affected, the owner and approver, and any condition that would reopen the decision. If a clarification is needed, quote both source statements and ask one answerable question. Explain the practical ambiguity without arguing for the interpretation that benefits the bidder. A good clarification might ask whether the 30-page total includes the four criterion schedules, and request confirmation of the counting treatment. It should not hide three commercial questions inside one paragraph.

When the buyer does not answer before work must continue, separate the operating assumption from the claimed fact. State the assumption narrowly, model its consequences and assign an expiry or review trigger. A page-limit assumption may require two compliant layouts. A scope conflict may require alternative cost positions if the rules permit them. A contractual ambiguity may need counsel and commercial authority. The response should not quietly choose the cheaper interpretation and leave delivery to discover the gap after award.

Control

Propagate the decision beyond the sentence where it was found

Link each conflict record to the objects it can change. A revised service volume can alter the technical method, staffing model, implementation plan, service levels, price, risk register and contract position. A corrected deadline can alter internal approvals and the portal rota. A new attachment rule can change the file manifest and final review. Notify named owners with the decision and required action rather than broadcasting another document. The owner confirms completion against the new baseline; the conflict owner does not close the record merely because a message was sent.

Run a final conflict sweep against the issued document register and every amendment. Confirm that acknowledgements required by the procurement are present. Search repeated figures, dates and commitments across the final set, then compare the approved manifest with the files prepared for upload. The last check should be independent of the author who made the change. The result is not a perfect interpretation of an imperfect pack. It is a response in which uncertainty is visible, authority is evidenced and one controlled decision reaches every place that depends on it.

• Attach affected answer, price, form and upload identifiers to the conflict record.
• Require owners to confirm implementation, not receipt of the message.
• Reopen downstream approvals when the approved basis changes materially.
• Check amendment acknowledgement requirements before final submission.
• Use an independent reviewer to verify the final baseline.