How to document deviations in a technical bid evaluation

A clear deviation record can make the difference between a defensible procurement decision and an overlooked offshore project risk. Each difference needs an accountable resolution.

During a Technical Bid Evaluation, evaluators need to identify where each offer differs from tender requirements, assess the technical and delivery implications, and track clarifications through to resolution.

This guide explains how to document deviations consistently, link them to supporting evidence, and communicate outstanding risks to procurement and engineering teams before a contract is awarded.

What should a deviation record show?

A useful deviation record connects the tender requirement, the bidder’s offer, the difference between them, its consequences, and the decision made by an authorized reviewer.

Use a controlled deviation register alongside the Technical Bid Evaluation report. The register provides traceability; the report explains the overall assessment and significant unresolved issues.

Record differences even when a bidder describes its offer as compliant. A statement of compliance does not override a drawing, qualification, assumption, or test exclusion that says otherwise.

Do not treat every difference as equally serious. Assess whether it affects safety, regulatory compliance, performance, interfaces, schedule, cost, maintainability, or the validity of bid comparisons.

A deviation is not closed simply because the bidder has answered a clarification. Close it only when the response is verified and the required decision is documented.

Which differences belong in the register?

Start with the issued tender documents and their amendments. Compare each relevant requirement against the bidder’s technical proposal, drawings, datasheets, exceptions, assumptions, and clarification responses.

Include explicit exceptions, proposed alternatives, missing evidence, and conflicting statements. Distinguish a confirmed departure from an apparent gap that still requires clarification.

For example, an installation vessel may meet the stated crane capacity but propose an operating limit below the tendered sea state. Record the limit and its project impact.

Likewise, a cable supplier’s proposed test sequence may omit a specified qualification test. The issue is not merely missing paperwork if acceptance depends on that test.

Commercial qualifications can also affect technical delivery. Flag an excluded installation tool or a longer manufacturing lead time, then coordinate their treatment with procurement and planning.

Where tender requirements conflict or lack detail, document the ambiguity separately. Do not label a bidder noncompliant until the evaluation team establishes the applicable interpretation.

What fields should every deviation entry contain?

Give each entry a unique identifier and link it to one bidder, package, and requirement. Separate materially different issues so each can be assessed and closed independently.

Use exact document references, including revision, section, and page where available. Quote the relevant requirement and offer accurately enough that another evaluator can reproduce the comparison.

The following fields provide a practical minimum. Add project-specific approval, interface, or regulatory fields where the procurement procedure requires them.

• Identification: Deviation ID, bidder, package, discipline, and evaluation date.
• Requirement: Tender document, revision, clause, and the applicable acceptance criterion.
• Bid position: Proposed value or approach, supporting document reference, and any stated condition.
• Difference: A concise, factual comparison; identify whether the issue is confirmed, apparent, or an information gap.
• Impact: Affected performance, interfaces, safety, compliance, schedule, cost, and assumptions requiring verification.
• Disposition: Clarification reference, proposed action, responsible owner, due date, approval, and current status.
• Evidence: Links to controlled bid documents, calculations, test reports, correspondence, and decision records.

Preserve units and operating conditions. A load rating without outreach, vessel motion assumptions, environmental limits, or a reference standard may not support a meaningful comparison.

Keep factual observations separate from evaluator judgments. Record “bid states 1.5 metres” separately from “the lower limit may reduce available installation windows.”

How do you assess technical and delivery impacts?

Evaluate the departure against the actual duty, not a generic specification. Identify which project assumptions make the difference material and which remain uncertain.

For offshore equipment, check water depth, seabed, metocean conditions, load cases, interfaces, installation method, maintenance access, and local requirements where relevant to the package.

Then follow the consequence through project delivery. A changed foundation tolerance, for example, may affect fabrication, transport, installation equipment, survey procedures, and offshore rework.

Assess schedule effects with the planning team. A lower operating limit may constrain weather windows, but its effect requires a defined location, season, activity duration, and weather dataset.

Avoid presenting an unverified consequence as a calculated delay. State the uncertainty, the analysis needed, its owner, and when the result is required for the award decision.

Where an alternative could be acceptable, establish the conditions: engineering verification, interface changes, additional testing, revised procedures, or approvals from the relevant project authority.

Record any cost estimate separately from the technical finding, with its basis and owner. Procurement can then apply the approved commercial evaluation method without obscuring technical risk.

How should deviations be classified and prioritized?

Use the project’s established evaluation rules wherever possible. Define classification criteria before comparing bidders, and apply them consistently to equivalent requirements and evidence.

A practical distinction is between mandatory requirements, material technical departures, minor departures, and information gaps. These categories support review but do not replace project-specific acceptance criteria.

Mandatory requirements deserve particular attention because the tender may prescribe rejection or another defined consequence. Confirm the applicable procurement rules before drawing a conclusion.

Prioritize remaining issues by credible consequence and likelihood, using the project’s risk method. Record the rationale and uncertainty rather than relying on a color alone.

For example, a missing drawing may be easily resolved, while an unsupported fatigue life could affect structural integrity and require substantial analysis before acceptance.

An alternative design is not automatically unacceptable. Assess it against the required outcome, verification evidence, interface compatibility, and any tender restrictions on alternatives.

If an issue spans disciplines, assign a lead owner and identify contributing reviewers. Engineering, marine operations, quality, planning, and procurement may need to agree its disposition.

What does a complete deviation entry look like?

The following fictional example illustrates the level of detail needed. Its limits are illustrative and must not be used as offshore operating criteria.

The entry identifies the departure without claiming that a lower limit is inherently unsafe or that a particular schedule impact has already been established.

If the bidder later proposes a different lifting arrangement, retain the original record and link the revised method, its evidence, and the resulting assessment.

How do you manage clarifications without losing traceability?

Issue a focused clarification that identifies the requirement, conflicting bid statement, and information needed. Ask for evidence or a revised proposal, not simply a compliance confirmation.

Set a response deadline consistent with the tender process. Use the authorized communication channel and preserve the question, response, attachments, dates, and document revisions.

After receipt, check whether the answer resolves the original issue or introduces another departure. Update the register and refer to the exact response supporting the assessment.

Possible statuses include open, clarification pending, under review, accepted subject to conditions, rejected, and closed. Define them locally so users understand what each status permits.

For closure, document who verified the response, what evidence was checked, and who approved the disposition. Acceptance subject to conditions remains actionable until those conditions are incorporated.

Control changes to the register after evaluation meetings. A revision history should show what changed, who changed it, and which decision or evidence prompted the update.

How do you carry unresolved risks into the award decision?

Before recommending an award, reconcile the deviation register with the evaluation report, clarification log, risk register, and proposed contract documents. Resolve discrepancies between these records.

Summarize material open items for decision-makers: the requirement affected, credible consequence, uncertainty, recommended action, responsible party, and decision deadline. Highlight any mandatory requirements still unmet.

Compare bids on a consistent basis. If one offer excludes testing or requires buyer-supplied equipment, make the scope difference visible before applying the approved commercial normalization method.

Do not assume that an evaluation note automatically changes the contract. Procurement and legal teams should incorporate accepted limits, deliverables, tests, and responsibilities into the agreed documents.

For accepted deviations, identify residual risks and transfer actions to the relevant project owner. Specify when evidence is due and what happens if acceptance criteria are not met.

A pre-award technical qualification should clearly distinguish verified compliance, conditional acceptance, and unresolved exposure. The decision authority can then judge the offer with its actual limitations visible.

Conclusion: make the decision traceable

A strong Technical Bid Evaluation deviation record is a decision trail, not a list of exceptions. It shows the requirement, evidence, impact, ownership, and authorized disposition.

For offshore projects, its value lies in connecting bidder claims to the conditions of delivery. Keep unresolved assumptions visible until they are verified or expressly accepted.

Use the register through clarification and contract preparation, then hand remaining actions to project teams. That continuity makes the procurement decision more transparent and easier to execute.