What if your bid promises more than the draft contract?

Keep the two statements intact before explaining the difference

Open the proposal and the current draft agreement side by side. Preserve each exact passage, file identifier, version, question or clause, and page or cell. Include the applicable amendment or official clarification. Record whether the proposal is still an internal draft, already submitted, under negotiation or being assembled into the final contract. That stage changes which corrections are available. Do not replace a submitted file in the record with a cleaner local copy.

Define the disputed proposition narrowly. A paragraph may contain a present fact about a support team, a proposed service level and an aspirational improvement target. Separate them if they can change independently. Preserve qualifications such as normally, within, at least, during service hours and subject to buyer access. If the apparent conflict exists only after removing one of those conditions, the shortened comparison is misleading.

Then look for other occurrences. An executive summary, architecture diagram, staffing table, optional-service note or presentation may repeat the commitment in stronger language. Record those locations as an affected-artifact list. A demonstration statement or meeting note may also need legal review, but do not silently treat an oral statement as an incorporated schedule. Its source and status remain distinct.

The discrepancy record needs enough context for another reviewer to reach the source. Keep privileged advice, internal cost details and protected buyer material in the authorized review environment. A public example should use invented facts. This record is an internal control over the offer, not a document to send to the buyer merely because it explains the problem.

A stronger commitment can coexist with the stated minimum

Compare the actor, action, object, quantity, quality, place, trigger, measurement interval and completion condition. Ask whether the statements cover the same scope and whether both can be satisfied. A promise to restore within two hours can also satisfy an eight-hour maximum. That is a potential additional or stronger commitment, not necessarily a contradiction. Whether it becomes binding still needs the contractual review.

Other differences cannot be ranked by their numbers. Acknowledging a ticket within one hour does not establish restoration within four hours. A weekly average is not the same as a per-incident maximum. A date measured from award cannot be compared directly with a duration measured from a later approved start. Preserve both clocks until their triggers and completion events have been reconciled.

A genuine contradiction may concern permission rather than performance. A mandatory restriction on exporting a dataset can conflict with a method that sends that dataset to an external service. Calling the method faster does not resolve the restriction. Similarly, a statement that the buyer performs a task may conflict with a clause assigning it to the supplier. Identify the incompatible act or allocation instead of using a broad label such as contract risk.

Where the contract is silent, do not infer either that the proposal commitment is excluded or that it automatically binds. Investigate how the proposal enters the agreement and whether the statement defines the offered method or an additional obligation. A target described as guaranteed elsewhere needs reconciliation even if no contract clause mentions it. Missing information stays unresolved; the reviewer should not invent an interpretation that makes the package appear consistent.

Read the whole precedence mechanism, including its exceptions

Locate the provisions identifying the contract documents. Check exact filenames or document descriptions, versions, schedules, accepted clarifications and any express exclusions. Then identify the order-of-precedence rule and what activates it. An inconsistency rule and a rule selecting the best supplier commitment are different mechanisms. Record any authority given to a named party to decide, and do not exercise that authority on its behalf.

US FAR 52.215-8 provides a particular order for inconsistencies in the uniform contract format, placing the Schedule excluding specifications first and specifications last. That is not a universal hierarchy for all US procurements. Confirm the incorporated clause, document classification and applicable agency deviations before using it.

The current England and Wales Model Services Contract Front Sheet places Schedule 8 low in its ordinary order but includes an exception for a better commercial position for the Authority, determined at the Authority’s discretion. This model-specific exception requires review of the actual adopted text; lower placement alone is insufficient.

The French DAJ guidance on contractual documents explains the CCAG document hierarchy and the treatment of the technical offer. It also addresses changes to the list or priority through the special conditions. Read the selected CCAG and the market-specific documents rather than importing one standard list into every French contract.

Ask counsel to apply the relevant mechanism to the identified pair of statements, with the source versions and scope comparison attached. The answer should explain the disputed proposition and any remaining uncertainty, not merely repeat that the contract prevails. A ruling on one inconsistent sentence does not establish that unrelated lower-ranked commitments have disappeared. Entire-agreement and non-reliance wording also needs legal interpretation; it is not permission to make inaccurate statements during procurement.

Until that review is complete, distinguish the proposed contract effect from the business decision about what to offer. The team may already know that a two-hour promise is unsupported even while legal incorporation remains uncertain. That evidence is enough to stop unqualified release for review; it does not require the bid team to declare the future obligation unenforceable.

Test the stronger promise against a complete operating scenario

Use the disputed wording as the test specification. Collect the approved service design, coverage, dependencies, partner response obligations and relevant performance evidence. A successful pilot or an average completion time does not prove a maximum for every incident. Check the stated population, exclusions, measurement start and stop, night or weekend coverage and the conditions under which the evidence was obtained.

Briarcombe’s fictional schedule requires acknowledgement within four elapsed hours and restoration within eight elapsed hours of a priority-one incident. Its draft technical answer instead guarantees restoration within two elapsed hours, 24 hours a day. All clocks in this example run continuously from the same incident event; there are no assumed clock pauses or excluded incidents. The case is a scenario supplied for review, not a service benchmark.

An incident begins on Friday at 17:00. Acknowledgement arrives at 18:00, and restoration completes on Saturday at 00:30. The acknowledgement takes one hour against a four-hour limit. Restoration takes seven hours and thirty minutes: it meets the schedule’s Saturday 01:00 deadline by thirty minutes, but misses the proposal’s Friday 19:00 deadline by five hours and thirty minutes. A green schedule test therefore does not validate the written offer.

The reviewer now needs a decision on the two-hour promise. One route is to retain it only after an approved operating model, partner obligations and appropriate evidence support its defined scope. Another, while the bid is still editable and the procedure permits, is to remove the discretionary guarantee and state the intended compliant service precisely. Check whether the stronger commitment is required for compliance or has been offered for evaluation; deleting it can change more than prose quality.

Do not solve the case by changing restoration to acknowledgement in the plan while leaving restoration in the answer. Nor should the team silently exclude weekends from a continuous promise. A legitimate correction must identify the revised measure, trigger, coverage and conditions in every affected place. The delivery owner confirms the method; commercial reviewers assess the consequences for price and risk, without assuming that an unchanged selling price means unchanged exposure.

The correction route depends on what has already been submitted

For an internal draft, identify whether the disputed wording is mandatory, a chosen improvement, a factual error or an unauthorized qualification. Correct drafting only within the actual requirements. Retaining a stronger promise needs delivery and commercial approval. Narrowing a discretionary promise needs review of compliance, scoring and consistency with the rest of the offer. If the baseline itself is unclear, prepare a neutral question through the designated clarification process, subject to authority to send it.

Once an offer has been submitted, preserve it. Determine which clarification, revision, negotiation or withdrawal route is available under the actual procedure. Internal approval of replacement wording does not authorize its transmission or make it part of the buyer’s record. A buyer’s question about meaning is not necessarily permission to change the substance of the offer. Keep requested clarification and proposed alteration separate for procedural review.

The UK Procurement Act guidance on modifying a competitive procurement distinguishes stages and requires affected documents and timing to be handled under the applicable section 31 rules. It concerns the authority’s modification powers, not a supplier’s unilateral right to repair an offer. A clarification request cannot be assumed to amend the procurement.

French Public Procurement Code Article R2152-13 permits fine-tuning with the selected bidder before signature but prohibits changing substantial characteristics of the offer or market. This bounded route is not a general opportunity to retract a promise after selection. Qualified review must determine what the proposed correction changes.

Record the chosen treatment and the event needed to make it effective: a revised internal answer, an official clarification applied to the pack, a permitted departure accepted by the appropriate party, or a supported decision to retain the promise. If none is available, hold release or escalate the bid decision. Do not rely on a hidden assumption that the customer will overlook the phrase or that delivery can negotiate it away after award.

Close the discrepancy only after the released files show the decision

The decision record should preserve the original statements and classify their relationship. Add the applicable incorporation and precedence provisions, legal review reference, delivery test, commercial consequence, permitted treatment and exact approved wording. Name the approving roles and any conditions. A generic note saying reviewed is insufficient when the next reviewer cannot identify which version was approved.

Use the affected-artifact list to implement the decision. Check answers, summaries, diagrams, method statements, partner commitments, pricing assumptions, options and portal fields. Inspect the exported files as well as the editable source. An old two-hour guarantee in an image survives an ordinary text replacement. Preserve the previous version and its history rather than deleting evidence of what was submitted or discussed.

If a correction changes a material partner duty, obtain the necessary partner confirmation against the revised wording. If it changes a resource or price assumption, reopen those approvals. A legal view on precedence cannot establish available night-shift staffing, and a delivery manager cannot authorize a prohibited tender qualification. The final release owner needs all required decisions against one coherent package.

Before contract signature, compare the assembled agreement with the approved resolution and any permitted negotiation record. Verify which technical response version is incorporated and whether an older promise has returned in a schedule. Unresolved incorporation or substantive-change questions remain with the authorized legal and procurement reviewers. After signature, use the applicable contract process for a newly discovered issue; do not overwrite the executed baseline.

An agent can locate competing statements, draft the comparison, calculate disclosed scenarios and search authorized artifacts for superseded wording. It must not decide disputed enforceability, invent a buyer acceptance or treat silence as approval. Contacting the buyer, changing a submitted offer, sharing protected material, accepting a contractual variation, signing and submitting require explicit authority. The useful handoff is a source-linked discrepancy packet with the requested decision and the exact remaining release conditions.