Which bid promises become delivery obligations?

Classification

A confident sentence is not always a contractual promise

Start with what the sentence does. “We operate four regional centres” is a statement about the bidder now. “We will operate four centres for this contract” offers a future state. “Four centres reduce travel time” explains a method. “Incidents will be restored within four hours” proposes a measurable performance level. Similar wording can therefore require very different review and treatment.

Classify the proposition before debating whether it is binding. Useful classes include current fact, evidence statement, offered method, future duty, performance level, named deliverable, buyer dependency, estimate, target, aspiration and illustrative example. A case study may support credibility without promising the same result. A forecast may become a commitment if the answer guarantees the number or makes it an acceptance threshold.

The classification is a bid control, not a legal conclusion. Contract status comes later from the final documents and applicable rules. At this stage, the purpose is to ensure that exact promises receive stronger scrutiny than background narrative and that apparently soft language does not hide a real undertaking.

Work product

Preserve the quote, then normalize the duty

Create one row for a proposition that can change independently. Preserve the exact statement, document, section, response question, page or cell, version, bidder entity, lot and scope. Do not replace the source with a summary. Reviewers will need to see whether “normally,” “at least,” “up to” or “subject to” changes the meaning.

Beside the quote, normalize the candidate duty. Name the actor, action and object. Add quantity, unit, quality level, location, time, trigger and condition where present. “Rapid reporting” is not testable. “The supplier sends a site-level incident report within two working days after a priority-one closure” is. Keep missing elements blank and assign them for resolution instead of inventing precision.

Link the row to the buyer requirement or award criterion it answers, the internal approval, supporting evidence, price element, proposed contract destination and every later external change. The map is not a second contract. It is an index that lets the team move from one submitted proposition to the evidence and decisions needed to understand its final status.

Bid control

A promise needs an owner before it needs elegant prose

The cheapest time to challenge a commitment is before it leaves the bidder. Ask the proposed delivery owner to test the whole proposition, including volumes, locations, term, dependencies and peak conditions. A method that worked in a six-month pilot may not support a five-year national service. A named expert may not be available on the proposed start date.

Trace cost and capacity into the commercial model. If the answer promises weekend coverage, a four-week transition or a monthly independent audit, identify the funded people, supplier cost, lead time and contingency. Confirm who has authority to offer the position. Evidence should support the capability claimed, while the operating plan should show how it will be repeated for this contract.

Reconcile related answers. Staff numbers must agree with the resource plan. Response times must match the service-level schedule. Deliverable dates must fit the implementation plan. If the team cannot make the proposition consistent, it should narrow it, state a permitted dependency, obtain the right approval or remove it before submission. Polished ambiguity is not a control.

• Confirm that a named delivery owner has read the exact proposed wording.
• Test normal, peak and failure conditions across the full stated scope.
• Locate the cost, resource and lead time in approved plans.
• Check third-party promises against current partner authority.
• Link evidence without converting an example into a guarantee.
• Block release when a material conflict or approval gap remains.

Contract route

Name where the promise is meant to land

A candidate commitment needs an intended destination even when the final contract is not yet available. Depending on the procurement, it may belong in the service description, supplier solution, performance regime, deliverables table, implementation plan, pricing schedule, data schedule or a specific annex. Record “proposed destination” at this stage. Do not state that the promise is contractually binding merely because the bid was submitted or scored.

Contract structures differ. UK government Model Services Contract guidance, for example, expects a detailed supplier solution and provides for it to be incorporated into Schedule 8. The US federal uniform contract format separates specifications, performance, attachments, representations and proposal instructions, and the award contract does not simply reproduce every solicitation part. French public-contract guidance explains that the contract documents determine whether a technical memorandum is contractual and where it sits in the order of priority. These are regime-specific examples of the same practical need: read the actual incorporation route.

At award, inspect the signed agreement, incorporated schedules, award or order letter, accepted clarifications, final-offer material and any clause that resolves inconsistency. Record the exact document and provision that includes, excludes or supersedes the candidate. If documents conflict or incorporation remains uncertain, assign legal review. The map should expose the question, not decide it by convention.

Change control

Later words must supersede the right earlier words

A buyer question can narrow, confirm or replace an offer. Capture the exact question, response, sender, recipient, date, authorized channel and affected commitment rows. Never overwrite the submitted source. Create a new version and state whether it clarifies the existing meaning or changes the proposition. A best and final offer needs the same treatment across every affected answer, price and schedule.

The permitted scope of change depends on the procedure. French Code Article R2152-13 allows the buyer and successful tenderer to fine-tune components before signature without modifying substantial characteristics of the offer or contract. FAR 15.504 requires both parties to sign when the award document differs from the selected offeror’s latest signed proposal as amended in writing. These rules do not create a universal amendment method; they show why the external event and authority must be recorded precisely.

Use explicit supersession links. If clarification 12 changes four local engineers to three engineers and a remote specialist, the old staffing promise remains historical but must disappear from the active view. Reopen price, solution, evidence and contract-destination checks. At final review, one current proposition should lead to one supportable contract position.

Worked example

A fleet proposal makes four different kinds of statement

A city tenders a five-year fleet support service for 72 depots. The response says the bidder has operated a 24-hour desk since 2022, will open the contract desk within 30 days, will maintain 98% monthly availability, will issue a monthly depot dashboard and will place four engineers in the region. A case study adds that another authority reduced vehicle downtime by 17%. All six statements sound favorable, but they do not carry the same function.

The existing desk and case-study result are evidence. They need proof and careful scope, but they are not automatically future duties. The 30-day opening, availability threshold, dashboard and staffing position are candidate commitments. Operations confirms the desk and dashboard. The service-level owner defines the availability formula and exclusions. Finance locates four engineers in the price. Each row points to the service description, performance schedule, reporting schedule or supplier solution where it is intended to sit.

During award clarification, the city accepts three local engineers plus one remote diagnostic specialist. The team versions the staffing row, revises the resource plan and links the clarification. The executed contract incorporates the supplier solution, performance schedule and reporting schedule, but not the case-study appendix. Its precedence clause places the performance schedule above the supplier solution. The final map therefore assigns the 98% calculation from the performance schedule, the revised staffing model from the incorporated solution, the dashboard duty and the 30-day milestone to delivery. The 17% result remains evidence, not a target.

The exercise also finds a conflict: an old implementation slide still says four local engineers. Because the superseded row identifies every affected artifact, the contract team resolves the inconsistency before handover. Delivery receives four confirmed controls, not six sentences stripped of context.

Delivery interface

Transfer the obligation, not the proposal paragraph

Once incorporation is confirmed, prepare the minimum operating record. Include the controlling contract source, normalized duty, accountable owner, performing team, trigger, first due date, recurrence, measure, input dependency, acceptance authority and evidence to retain. Link the original proposal and change history, but make the executed contract the delivery baseline.

Government commercial guidance treats final contracts, documented obligations, mobilisation responsibilities and contract-management plans as connected controls. The map supplies a reliable boundary between bid and delivery, but it is not the mobilisation plan, service management system or complete obligations matrix. Those teams decide how the work is scheduled, governed and reported after receiving the confirmed source.

Do not create duties from rows marked non-incorporated, superseded or interpretation review. Do not drop a confirmed duty because the proposal owner has left. If the business later wants to change the service, use the formal contract change route. Updating an internal plan or commitment map does not amend the agreement.

• Cite the controlling contract document and exact provision.
• Name both the accountable owner and the performing party.
• Record the commencement trigger, due date and recurrence.
• Define the measurement method and acceptance authority.
• State required inputs, dependencies and notice periods.
• Describe the performance evidence and where it will be retained.
• Link the remedy, escalation or formal change route where it applies.

Lifecycle

The status should say what is known today

Use lifecycle states that do not outrun the evidence. Candidate commitment means the proposition has been extracted. Approved offer means internal authorities accept the fixed wording. Submitted offer requires the released file and receipt. Evaluated position records relevant buyer feedback without claiming incorporation. Negotiation changed and superseded identify controlled replacements.

Contract incorporated requires a source in the executed agreement or an authorized incorporated document. Not incorporated needs an equally clear basis, especially when removing a statement from delivery control. Interpretation review holds conflicts, missing schedules and uncertain precedence. Delivery baselined means the confirmed obligation has an owner and operating control. Preserve dates, actors and prior states so the team can reconstruct the path without treating the newest spreadsheet as proof.

Review the map at response approval, after each authorized external exchange, at final-offer release, before signature and during award handover. Close every candidate with an incorporated, not-incorporated, superseded or formally unresolved outcome. A row left at “submitted” after contract signature is not harmless backlog; it is an unanswered question about what delivery owes.