A no self-sabotage checklist for Q1 tender readiness

Q1 is when a lot of ocean freight conversations get serious. For Transpacific contracts in particular, many annual agreements are negotiated in Q1 and take effect around May 1, with TPM in Long Beach often treated as a major negotiation and relationship-building moment. (Even if your lanes renew on different dates, Q1 still shapes expectations, benchmarks, and commercial posture.)

This post is a practical checklist for forwarders. The goal is simple: avoid “winning” a tender that quietly guarantees margin leakage, exceptions work, and service disputes for the rest of the year.

It is not a legal guide, and it is not lane-specific. It is a set of sanity checks you can run before you commit to rates and promises you will later have to defend.

How to use this checklist

Run it before you send your final offer, not after you win.
Do not aim for perfect answers. Aim to surface hidden assumptions early.
If you cannot answer an item, either narrow scope, add a clear condition, or remove the promise.

1) Scope sanity: make sure you are quoting the same thing

Most tender pain starts with scope drift. If the scope is unclear, the “rate” becomes a placeholder for future arguments.

Lane and routing clarity: Are origin, destination, and acceptable gateways clearly defined (including alternates), or are you implicitly pricing a best-case route?
Volume reality: Are volumes expressed as a realistic band, or as a single number that becomes a weapon later?
Equipment and cargo constraints: Are equipment types and special requirements (reefer, oversized, hazmat) clearly stated, or left for “we assumed standard” surprises?
Incoterms and control points: Do you know who controls booking, documentation, and origin readiness, or are you inheriting delays you cannot influence?
Accessorial exposure: Do you have a clear understanding of what is included versus billed separately (documentation, chassis, storage, customs handling), in plain language?

Default move if scope is fuzzy: Narrow the offer. Quote the base case only, list assumptions, and price exceptions separately. “Bundling” uncertainty rarely pays you for the risk.

2) Price structure: avoid agreements that are impossible to reconcile

A low base rate can still be a bad deal if the surcharge logic is vague, inconsistent, or easy to dispute.

Fixed versus floating: Is it explicitly clear what is fixed (base ocean) and what will float (bunker-linked components, regulated lines like EU ETS, security-driven costs), with a stated update method?
Reference logic: Can you point to a consistent basis for pass-through (carrier-published tariff line items, agreed index, documented formula), or is it “we will advise as needed”?
Admin and handling: If you charge an admin margin on pass-through items, is it explicit, or hidden in a way that will be challenged later?
Invoice defensibility: If a shipper disputes a line item, do you have a clean way to show what changed and why, without email archaeology?

Default move if surcharge logic is not agreed: Put it on rails. “Pass-through based on carrier published lines, reviewed periodically” is better than ad hoc exceptions that train customers to dispute everything.

3) Service promises: do not sell what you cannot prove

Tender season rewards confident promises. Execution season punishes vague ones.

Transit expectations: Are you promising specific transit times as if the network is static, or are you framing them as targets that can move with routing and congestion?
Space and equipment: Are you implying guaranteed space or equipment availability, or are you conditioning the offer on carrier confirmation?
On-time KPIs: If the shipper asks for KPIs, do both sides agree on definitions and event timestamps, or are you heading toward disputes over what “on-time” means?
Exception handling: Is there a clear escalation path and response expectation when things go wrong, or will every disruption become a brand-new negotiation?

Default move if you cannot prove it: Rephrase promises into what you can control. For example, commit to fast communication, clear options, and evidence-based updates, rather than fixed outcomes.

4) Volatility tolerance: agree now on what happens when reality changes

In a year where routing and service networks can shift, contracts often fail because they treat change as an “exception” instead of a normal operating condition.

Material change language: Is there a shared understanding of what counts as a meaningful change (routing shifts, gateway changes, major schedule resets), without trying to predict every scenario?
Reset mechanism: When something materially changes, is there a calm process for resetting expectations and updating surcharges, or will it become a conflict?
Gateway flexibility: Is your offer allowed to use alternate gateways that still meet the customer’s intent, or are you locked into a single fragile option?
Allocation flexibility: If a carrier underperforms or changes service patterns, do you have room to rebalance volumes without breaching commitments?

Default move if volatility rules are missing: Add a simple governance clause. Not heavy. Just a clear path for review and adjustment when conditions shift.

5) Data and governance: stop disputes before they start

The best commercial terms still fail if there is no shared truth for milestones, surcharges, and performance.

System of record: Do you know what will be treated as “the truth” for events and timestamps (and is it accessible to ops, sales, and finance)?
Customer data obligations: Are shipper responsibilities for timely, complete shipment data stated clearly, including what happens when data is late or incomplete?
Review cadence: Is there a lightweight, predictable cadence to review performance, chronic exceptions, and surcharge tables, or will issues only surface as escalations?
Dispute workflow: Do you have a defined path for disputes that relies on evidence, not email threads?

Default move if governance is missing: Add a short quarterly review line and a shared source-of-truth statement. It is amazing how many disputes disappear when everyone agrees what “proof” is.

6) The “walk away” red flags

If multiple items below are true, you are likely buying exceptions work with your own margin.

Scope is vague, but the shipper wants hard promises.
Surcharge logic is “to be agreed” but disputes are expected to be handled ad hoc.
Transit and reliability commitments are demanded, but definitions and data sources are not agreed.
Routing must be fixed to one fragile path with no alternates.
The shipper pushes all change risk onto you, but will not accept a governance cadence.

A simple decision rule: If the contract would become a dispute machine the moment conditions change, the structure is wrong. Fix the structure or narrow the offer.

The missing layer: shared evidence

Most contract disputes aren’t philosophical. They’re evidentiary. If you can’t prove milestones and changes, you can’t defend surcharges, exceptions, or performance conversations. Tools like TRADLINX help by standardizing event timestamps across shipments and making it easier to reconcile “what happened” with “what was charged,” without rebuilding the story from inbox threads.