Keep technical and commercial bid revisions aligned

Starting point

A shared baseline is a set of compatible versions

List the response components that together describe the offer: technical answers, delivery and staffing plan, internal estimate, buyer price schedule and any assumptions or option records that affect them. Identify the procedure, bidder, lot, service period and current buyer amendments. Give the set an internal baseline identifier and preserve each component’s own version. There is no reason the technical document and price workbook must both be version seven; they must describe the same selected offer.

“Accepted working baseline” needs a defined meaning. It may be a coordinated starting point for further preparation, not a fully compliant or externally approved offer. Record the unresolved conditions that remain. A draft can be internally aligned and still fail a mandatory requirement. Conversely, one individually approved document may be incompatible with the rest of the set. The baseline record makes these differences inspectable.

NASA’s configuration-management guidance identifies controlled items and baselines, then separates proposing and evaluating changes from incorporating approved changes and verifying implementation. Its context is systems engineering. The bid adaptation is to control an identifiable offer configuration; NASA’s lifecycle stages and internal boards are not prescribed approval structures for every response team.

Preserve the common parent of concurrent revisions. If the technical author worked from baseline B17 and the estimator from B16, the comparison must first account for the intervening change. Comparing only the two newest files cannot tell which difference is a new proposal, a retained old assumption or an accidental reversal. A filename ending in final gives no evidence of that history.

Parallel work

Compare each proposal with the parent before comparing them together

For each stream, record the old proposition, proposed replacement, reason, evidence, author and affected dependencies. Use stable references to the answer, resource assumption and price field. Preserve the words that define the commitment, not just its headline number. Changing two hours from business time to elapsed time can change the delivery model without changing the number two. A new place of performance can matter even when quantity and quoted price remain constant.

The joint comparison has three inputs: the common parent, the technical proposal and the commercial proposal. If only one stream changes a proposition, still inspect its downstream effect on the other. If both change it identically, confirm their definitions and evidence match. If they change different fields, check whether those fields interact. Quantity and rate are different spreadsheet columns but participate in the same multiplication.

Distinguish a conflict in wording from a conflict in validity. Two proposals may merge into a grammatically consistent answer while relying on incompatible resource arrangements. A discount may require a specific term, configuration or payment profile. A staffing reduction may depend on automation that the technical team has not included. Those conditions travel with the proposal; they cannot be discarded because they sit in another file.

Keep unclear relationships unresolved. An absent cost reference may require the separate coverage review. A source disagreement may require an evidence-owner decision. A change to mandatory buyer terms may require procedural or legal review. The integration task routes those questions and waits for their results. It does not create a right to qualify the offer or replace a customer requirement with whichever internal proposal is easier to implement.

Worked example

Two correct deltas can produce the wrong combined cost

Bellwater’s fictional working baseline contains four training cohorts, each requiring one trainer-day. The modeled internal cost is 900 currency units per trainer-day, giving 3,600 for this component. The technical proposal increases the scope to six cohorts without changing the rate. The commercial proposal uses 800 per day from an alternative delivery arrangement but was assessed against the original four cohorts. These are internal example costs, not customer prices, market rates or a complete delivery estimate.

Against the parent, the technical change adds 1,800: six times 900 is 5,400. The commercial change removes 400: four times 800 is 3,200. Adding those two deltas to the original 3,600 gives 5,000. But if both new assumptions are valid together, the combined component is six times 800, or 4,800. The delta shortcut overstates it by 200 because it omitted the effect of the lower rate on the two additional days.

The interaction term is the quantity change multiplied by the rate change: two additional days times minus 100 equals minus 200. The combined delta is therefore 1,800 minus 400 minus 200, or 1,200. That explains the difference; the operational rule is simpler: recompute the affected model from the selected joint inputs. More complex estimates can contain thresholds, minimum charges or resource steps for which adding separately reported savings is even less reliable.

Arithmetic does not authorize the combination. The delivery owner must verify that the alternative arrangement can provide six suitable trainer-days under the promised conditions, and the commercial owner must confirm the rate’s applicability. If only four days are covered by the new arrangement, 4,800 is not supported. Keep the candidate on hold or model an explicitly evidenced alternative. Do not choose the lower result merely because it makes the bid economics look better.

Semantic bridge

Agree the combined service before accepting its economics

Bellwater needs more than a revised total. The joint record carries six cohorts, one trainer-day per cohort, the delivery conditions, the performing resource arrangement, the applicable cost basis and the customer-price treatment. Identify preparation, travel or other components that this small example excludes, and send them to the relevant estimate review. A correct component multiplication cannot establish that the whole offer is adequately funded.

The GAO Cost Estimating and Assessment Guide ties estimates to a maintained technical baseline and documented assumptions, including updates for major changes. It addresses programme costs, not a supplier’s pricing entitlement. Its application here is to recalculate from the selected technical definition and keep each alternative identifiable rather than combining assumptions from incompatible cases.

Keep cost, price and evaluation amount separate. A lower internal cost need not change the quoted price, and a lower quoted price need not change the delivery scope. Both can require renewed commercial decisions under the actual mandate. A margin decision is not technical proof that the cheaper delivery arrangement works. Nor does technical acceptance authorize the estimator to change a customer-facing rate or condition.

Use the same discipline for non-numeric promises: response versus restoration, receipt versus validation as a trigger, remote versus on-site work, calendar versus working time, base scope versus optional scope. Record who does what, for whom, under which conditions and during which period. Only then compare resource and price implications. Two documents can use the same noun while assigning different responsibilities to the buyer.

An internal connection between the streams does not require placing financial information in the technical submission. Maintain the restricted reconciliation record internally and populate the buyer’s prescribed volumes or fields according to their instructions. Do not conceal a material offer condition, but do not copy internal rates, margins or partner terms into an unauthorized audience merely to demonstrate that the documents were reconciled.

Joint disposition

Approve a combination, not two disconnected edits

Give the responsible owners the common parent, both proposals, interaction findings and candidate treatment. A disposition can accept the combination, accept one proposal while rejecting the other, request a different joint solution, or defer the change pending evidence. Record the reason and the precise surviving assumptions. “Technical approved” and “commercial approved” are insufficient if the approvals concern different versions or conditions.

GovS 002 version 2.1 calls for changes to interrelated deliverables to be controlled together, with impact assessment, authorization and updated information before closure. This is UK government project guidance. Applied to bid preparation, it supports a coordinated change record without granting the response integrator unilateral authority over delivery, price or external commitments.

The integrator assembles and checks the decision; the technical owner confirms the delivery meaning and evidence; the commercial owner confirms the economic treatment within mandate. Other authorities remain necessary where the change affects partner commitments, legal terms, disclosure or release. One person may hold several valid roles, but role consolidation must be evidenced rather than inferred from seniority or meeting attendance.

Keep candidate, accepted-for-working-use and release-authorized states distinct. A joint working decision may permit detailed drafting while a later approval is still required. If the decision is conditional, show the condition, owner, deadline and prohibited downstream actions. A pending confirmation of the six-day delivery arrangement cannot be displayed as an unconditional acceptance of Bellwater’s 4,800 component.

Concurrent updates

Check the starting version again before advancing it

While the joint candidate is being reviewed, another author may change the current response. Record the baseline the candidate expects to replace, then verify it still is the current one at adoption. If B18 has already replaced B17, a candidate prepared from B17 cannot silently become B19 by overwriting B18. Compare the intervening change, re-evaluate the combination and obtain any affected decisions again.

RFC 9110 section 13.1.1 defines If-Match for conditional HTTP operations and prevention of accidental parallel overwrites. It is a protocol mechanism, not a bid-approval rule. The limited analogy is to reject a stale starting state before applying a change. A successful version check cannot prove semantic compatibility or authorize the change itself.

The actual control may be a verified repository operation, document-management workflow or disciplined single-owner adoption process. Do not claim atomic multi-document protection because one file has a lock. A candidate manifest can identify the full set while component updates are staged; the authoritative pointer should advance only after the required set and decisions are verified. Where the tooling cannot enforce this, state the procedural control and its limitations.

If adoption is interrupted, inspect the authoritative state before trying again. Determine which components and baseline pointer changed, which approvals still apply and whether the attempted operation already completed. Do not create a second current version just because an acknowledgement was lost. Preserve the last complete known state and the partial candidate separately. Recovery requires evidence of state, not a guess from the last visible message.

Verification and handoff

Re-read the offer that the joint decision produced

Trace every accepted change to its implemented answer, resource record, estimate and price treatment. Then inspect the candidate in reverse for unsupported changes that did not appear in the disposition. Check dependent diagrams, schedules, tables and permitted portal fields, not only the main narrative. A rejected proposal can survive in an attachment even when the master document is correct.

W3C PROV-DM represents revision relationships and links activities with responsible agents and plans. It provides a way to describe how the joint candidate derives from prior material and review work. Provenance does not certify the reviewers’ authority or the candidate’s accuracy; those require the decision and verification evidence retained alongside it.

Test the final alignment with concrete counterexamples: a new technical revision after commercial acceptance, a rate conditional on the old quantity, two changes starting from different parents, and an unchanged total hiding a changed service definition. The expected result is a specific affected scope held for reconciliation. Unrelated work need not stop where its independence is established, but the integrated candidate must not be labelled fully aligned while a material conflict remains.

An assistant may compare authorized versions, extract candidate deltas, calculate their interactions and draft a proposed disposition. It cannot choose the commercial trade-off, accept an unsupported technical promise or infer authorization from a clean merge. External messages, commitments, protected disclosures, signatures and submission require separate permission. Handoff identifies the current parent, proposed combination, unresolved evidence and next competent decision, with no claim that preparing the record has executed that decision.