---
title: "How to reconcile conflicting instructions in an RFP"
description: "Identify the real conflict, establish which buyer document controls, obtain clarification where needed and propagate one approved decision through the bid."
canonical: "https://zephior.com/insights/reconcile-conflicting-rfp-instructions"
last-updated: 2026-09-02
---

# How to reconcile conflicting instructions in an RFP

> Identify the real conflict, establish which buyer document controls, obtain clarification where needed and propagate one approved decision through the bid.

By [Tony Kim](https://zephior.com/authors/tony-kim). Published 2026-09-02; updated 2026-09-02. 11 minute read.

## Definition

A conflict in an RFP exists when two buyer-controlled statements cannot both be followed in the same response. The conflict may concern a deadline, page limit, required attachment, technical threshold, pricing basis, contract term or submission channel. A difference is not automatically a conflict: one document may define the requirement while another explains the evidence, or a general instruction may be narrowed by a question-specific rule. Reconciliation means identifying the exact propositions, determining whether the buyer has supplied a controlling rule, seeking an authoritative clarification where the answer remains uncertain and applying the approved interpretation consistently.

## Problem

Teams often resolve contradictions by instinct. The newest file is assumed to win, the main RFP is treated as superior to every annex, or a portal notice is copied into the plan without checking whether it formally amended the request. Different authors then make different choices. One follows the pricing workbook, another follows the narrative scope and a reviewer silently edits a third interpretation into the executive summary. The response can become internally inconsistent even when each contributor acted reasonably. A bidder-created hierarchy also creates false confidence: a precedence clause may govern contractual documents but say nothing about response instructions, and a familiar rule from one procurement regime may not apply to another.

## Point of view

Treat a contradiction as a controlled decision, not a copyediting nuisance. Record both statements verbatim with their document, section, version and date. Test whether they apply to the same circumstance and cannot both be followed. Use only the precedence, amendment and clarification rules supplied by the buyer or applicable procedure. If those rules do not settle a material issue, ask the buyer before the question deadline. When no answer is available, document the residual assumption, obtain the right commercial or legal approval and avoid presenting uncertainty as fact. The decision is not finished until every affected answer, price, attachment and submission control reflects it.

## 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.

**Conflict triage record**

| Field | What to record | Why it matters |
| --- | --- | --- |
| Statement A | Exact text and condition | Preserves the first proposition |
| Statement B | Exact text and condition | Shows why both may not be possible |
| Source | File, version, section and date | Establishes traceability |
| Affected work | Answers, price, forms and upload tasks | Defines propagation scope |
| Materiality | Eligibility, score, price, contract or administration | Sets urgency and 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.

## 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.

**Resolution states**

| State | Meaning | Next control |
| --- | --- | --- |
| Not a conflict | Both instructions can be satisfied | Document the scope distinction |
| Resolved by authority | Buyer rule identifies the controlling text | Apply and cite the authority |
| Clarification open | Buyer answer is required | Track deadline and affected work |
| Assumption approved | Work proceeds with explicit residual risk | Monitor trigger and disclose where required |
| Bid blocked | No responsible response is possible | Escalate the bid decision |

## 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.

## Useful outcomes

- Every material contradiction has a traceable record rather than an informal chat decision.
- Apparent conflicts are separated from valid general-and-specific instructions.
- Document authority comes from the buyer or applicable procedure, not team habit.
- Clarification questions identify the exact statements and the decision they block.
- Residual assumptions receive visible ownership and the appropriate approval.
- One resolution propagates through technical, commercial and submission work.
- Final reviewers can verify both the interpretation and its downstream application.

## Workflow

1. **Capture the two propositions.** Quote each statement exactly and record its file, section, version, publication date and affected response item. Avoid summarizing before the conflict is understood.
2. **Test whether both can be true.** Compare scope, condition, audience and timing. Decide whether the texts conflict, one qualifies the other, or they govern different parts of the procurement.
3. **Find the buyer-controlled authority.** Check explicit precedence clauses, amendments, portal notices and clarification rules. Never import an order of precedence from another buyer or jurisdiction.
4. **Resolve or escalate the issue.** Apply the controlling instruction where it is clear. Otherwise submit a precise clarification or approve a documented assumption with its commercial and compliance consequences.
5. **Propagate and verify the decision.** Update every linked requirement, draft, price, attachment, review check and portal task. Close the record only after an independent reviewer confirms consistency.

## Key decisions

- Do the statements apply to the same item, bidder, time and circumstance?
- Does one text add detail to the other, or is simultaneous compliance impossible?
- Which buyer-issued clause, amendment or clarification establishes authority?
- Is the conflict material to eligibility, evaluation, price, contract risk or submission?
- Can the issue wait for clarification, or does it block work on the critical path?
- Who has authority to accept any remaining assumption or deviation?
- Which response components must change when the resolution changes?

## Risks

- The team may mistake additional detail for a contradiction and discard a valid requirement.
- A contract order-of-precedence clause may be misapplied to proposal instructions.
- The newest timestamp may be treated as authority even when no amendment was issued.
- An informal buyer message may be relied on outside the permitted clarification channel.
- Technical and pricing teams may resolve the same conflict differently.
- An assumption may be buried in prose instead of approved as a material bid position.
- A late resolution may update the answer but leave the price or uploaded attachment unchanged.

## Metrics

- material conflicts open by response milestone
- conflicts with exact source and version references
- time from conflict discovery to authoritative resolution
- clarifications submitted before the buyer deadline
- approved residual assumptions by risk level
- downstream items verified after each resolution
- final-review defects caused by inconsistent interpretations

## Frequently asked questions

### Does the newest RFP document always take precedence?

No. A later formal amendment may change an earlier instruction, but a newer file name or portal timestamp does not by itself establish authority. Apply the precedence and amendment rules of the procurement.

### Should the main RFP override its annexes?

Only if the buyer’s documents or applicable procedure establish that result. An annex may contain the specific rule for a question, price schedule or submission file and can be fully compatible with a more general main document.

### What if the clarification deadline has passed?

Use any permitted channel, but do not assume a late question will be answered. Record the uncertainty, assess materiality and obtain the required commercial, compliance or legal decision before relying on an assumption.

### Can proposal software decide which instruction controls?

Software can find conflicting passages, preserve versions and propagate an approved resolution. Authority still comes from the buyer’s documents, procedure and accountable human judgment, not from the software.


## Primary sources

- [FAR 15.203, requests for proposals](https://www.acquisition.gov/far/15.203), U.S. General Services Administration
- [FAR 15.206, amending the solicitation](https://www.acquisition.gov/far/15.206), U.S. General Services Administration
- [FAR 52.215-8, order of precedence](https://www.acquisition.gov/far/52.215-8), U.S. General Services Administration
- [Directive 2014/24/EU on public procurement](https://eur-lex.europa.eu/eli/dir/2014/24/oj), European Union


## Related articles

- [Which number controls when tender thresholds conflict?](https://zephior.com/insights/reconcile-numeric-thresholds-in-a-tender)
- [Which RFP document controls when the pack disagrees?](https://zephior.com/insights/identify-the-controlling-rfp-document)
- [Which internal source wins when proposal evidence conflicts?](https://zephior.com/insights/resolve-conflicting-internal-sources-for-a-proposal)
- [What if a clarification answer conflicts with the original RFP?](https://zephior.com/insights/reconcile-clarification-answers-with-the-rfp-pack)