Back to Insights

Insight

How to detect exclusions in vendor proposals

2026-03-30

Exclusions are usually not the loudest part of a vendor proposal. They are the part buried in contracts, appendices, exclusions tabs, and side notes that change the real evaluation picture after a tidy response summary has anchored the comparison.

Where exclusions usually hide

They often appear in contracts, appendices, terms and conditions, assumptions sections, or response tabs that procurement teams only revisit once something looks inconsistent.

That makes them easy to miss in manual comparison, especially when each supplier structures the submission differently.

What to review systematically

Look for excluded permits, detention and demurrage assumptions, minimum-volume conditions, scope carve-outs, service qualifiers, and references to future confirmation or route-dependent conditions.

The important point is not just to flag an exclusion, but to understand how it changes the buyer's comparison.

What a better review process does

A better review process shows exclusions in the same place as requirement status, with source links attached. That lets the team review risk before the award, not after the contract has exposed it.

When that works, hidden risk stops being hidden.