Proposal compliance and contract risk
RFP assumptions and exceptions log: expose every condition before submission
A practical control for proposal, legal, commercial, and delivery teams that need to qualify a requirement without hiding risk or making the response internally inconsistent.
Published November 18, 2026
The short answer
Create one source-linked record for every assumption, exception, deviation, dependency, or requested alternative. Test whether the solicitation permits it, assess the responsiveness and delivery impact, obtain named approvals, and propagate the final disposition through every affected answer, price, schedule, and attachment. Never use an assumption to quietly replace an exception.
What you can use immediately
- A copy-ready 14-field assumptions and exceptions log
- A seven-test decision gate before a condition enters the proposal
- A fictional worked example that separates questions from exceptions
- A final release checklist for legal and proposal approval
Control principle
The log is a decision register, not a dumping ground
Public-sector instructions can treat conditional language as material. The Commerce Acquisition Regulation tells offerors to identify and explain exceptions, deviations, and conditional assumptions, and warns that exceptions can signal an inability or unwillingness to perform. The purpose of the log is therefore to force an explicit decision before risky language reaches an evaluator.
Question
What does the buyer mean?
Resolve through the authorized clarification process.
Assumption
What condition did we use?
Validate, disclose if permitted, and trace its impact.
Exception
What cannot we accept as written?
State the exact clause, reason, and proposed language.
This operating template is not legal advice. The issued solicitation, amendments, and authorized buyer answers control. Have qualified counsel review contractual positions.
Copy-ready structure
Use one record per condition
Do not combine unrelated clauses or leave the source implicit. A reviewer should be able to locate the requirement, understand the proposed position, see its consequences, and confirm the final decision without reconstructing an email thread.
| Field | What to record |
|---|---|
| Record ID | Stable identifier used in the proposal, legal review, pricing model, and final release check. |
| Source and version | RFP, attachment, clause, page, amendment, and the date the source was verified. |
| Record type | Assumption, exception, deviation, qualification, dependency, or requested alternative. |
| Exact requirement | The controlling buyer language copied accurately enough for a reviewer to locate it. |
| Bidder position | What the proposal assumes, cannot accept, must qualify, or proposes to change. |
| Proposed language | Precise replacement wording or a narrowly framed clarification where the RFP permits it. |
| Reason | Operational, technical, commercial, legal, security, schedule, or delivery basis for the position. |
| Response impact | Sections, solution decisions, staffing, price, schedule, risk, and dependencies affected. |
| Buyer impact | What acceptance or rejection would change for the buyer, contract, evaluation, or delivery. |
| Responsiveness risk | Mandatory, material, negotiable, unclear, or prohibited, with the source for that conclusion. |
| Owner and reviewers | One accountable owner plus required legal, commercial, technical, and executive approvals. |
| Status and disposition | Draft, challenged, approved, removed, submitted, accepted, rejected, or superseded. |
| Decision date | Internal due date, buyer-question deadline, submission deadline, and final approval timestamp. |
| Change history | What changed, why, who approved it, and every proposal location updated as a result. |
Decision gate
Pass seven tests before submission
A condition should fail closed: if the team cannot show that it is permitted, necessary, specific, assessed, approved, consistent, and correctly placed, it is not ready to enter the response.
| Test | Release question |
|---|---|
| Permitted | Do the solicitation instructions allow assumptions, exceptions, or alternative language? |
| Necessary | Is the position truly required, or can the team comply without changing the buyer requirement? |
| Specific | Does the record identify one exact clause and one precise requested change? |
| Impact-assessed | Have delivery, price, schedule, compliance, and evaluation consequences been reviewed? |
| Approved | Have the named legal, commercial, technical, and executive reviewers signed off? |
| Consistent | Has the disposition been applied to every affected answer, table, price, schedule, and attachment? |
| Visible | Is the record placed exactly where the solicitation requires, including a no-exceptions statement if required? |
Operating workflow
Move from extraction to controlled release
1. Extract
Capture every explicit instruction, term, dependency, and apparent conflict from the current issued package.
2. Classify
Separate questions from assumptions, and assumptions from actual exceptions or deviations.
3. Challenge
Ask whether the position is necessary and whether it could make the proposal non-responsive.
4. Decide
Approve, narrow, remove, or convert the item into a timely bidder clarification question.
5. Propagate
Update all affected technical, management, pricing, schedule, and contractual response locations.
6. Release
Reconcile the final log to the proposal and obtain a timestamped submission approval.
Worked example
Treat an assumption as a hypothesis until the process permits it
This fictional example shows why the first draft of a condition should not automatically become proposal language.
| Record field | Illustrative entry |
|---|---|
| Source | Fictional RFP section 4.6, version 2: transition must complete within 20 calendar days |
| Type | Assumption under review, not yet approved for submission |
| Bidder position | Buyer provides current asset inventory and named system owners within two business days of award |
| Reason | The transition sequence depends on verified inventory and access ownership |
| Impact | If the input is late, discovery and migration dates move day-for-day; price is unchanged |
| Risk test | RFP is silent on bidder assumptions; legal and proposal leads must confirm whether disclosure is permitted |
| Disposition | Convert to a clarification question before the deadline; remove unless the issued answer permits the assumption |
| Affected locations | Transition plan, schedule, responsibility matrix, pricing notes, executive summary risk statement |
Final release
Reconcile the log against the assembled proposal
Approval of the log is not enough. The final document, price, schedule, and attachments must express the same position.
Common questions
Questions teams ask before using the tool
What is the difference between an assumption and an exception in an RFP response?
An assumption states a condition the bidder has used to build its response. An exception identifies solicitation language the bidder cannot accept as written or proposes to change. The solicitation may define these terms differently, so its instructions always control.
Can an assumption make a proposal non-responsive?
Yes. A condition that changes a mandatory requirement, shifts material responsibility, qualifies price, or conflicts with the solicitation can create evaluation or responsiveness risk. Some RFPs expressly warn that exceptions or conditional assumptions may be evaluated adversely or rejected.
Should clarification questions be kept in the same log?
Link them, but keep their states distinct. A question asks the buyer to resolve ambiguity before submission. An assumption or exception is a bidder position that may enter the proposal. Apply the buyer answer and any amendment before deciding whether the position remains necessary.
Who should approve proposal exceptions?
Use the approval path that matches the impact. Proposal leadership owns response consistency; legal reviews contractual language; commercial and finance review price exposure; technical and delivery leaders review feasibility; an authorized executive approves material residual risk.
What if the bidder has no assumptions or exceptions?
Follow the solicitation. Some public-sector RFPs require an explicit statement that no assumptions or exceptions are taken. Do not omit the section merely because the log is empty when the buyer requests that declaration.
Research basis
Sources were reviewed on November 18, 2026. Examples in this guide are Novilo working examples, not procurement advice or customer results.
- Commerce Acquisition Regulation 1352.215-70: proposal preparation
- Federal Acquisition Regulation 15.203: requests for proposals
- Wisconsin ETF Auditor RFP: Tab 4 assumptions and exceptions instructions
- Puerto Rico Medicaid Program RFP: assumptions must not replace exceptions
- CanadaBuys: how bids are evaluated and selected
Make every proposal condition visible, reviewable, and consistent.
Bring one active solicitation, its current amendments, and the conditions your team is debating. We will map the decision path, evidence, approvals, and release controls needed before submission.
Book a bid-lifecycle diagnostic