Cargo requirements and vessel position data

What a complete cargo requirement carries

• Commodity, quantity and tolerance
• Load and discharge ports (or ranges)
• Laycan — the laydays and cancelling window
• Stowage factor and any handling needs
• Gear or terminal constraints

What a complete vessel position carries

• Open port and open date
• Vessel type and DWT
• Grain and bale capacity
• Draft, gear and key particulars
• Recent trading, where it's relevant

Why missing information matters

A match built on an absent or ambiguous field is a guess wearing a confidence score. Surfacing what's missing early — before an option reaches a shortlist — keeps a near-fit from being mistaken for a strong one.

Clean data makes matching reliable

When both sides are structured, current and comparable, compatibility checks and voyage-economics comparisons rest on something solid. That's what turns a plausible list into a reliable shortlist.

You don't have to reformat anything

Requirements and positions rarely arrive as tidy records. The work of turning an email, a forwarded message or an attachment into clean structured data is exactly what the AI is for — so the data is good without you re-keying it.

The cost of thin data

Thin or stale data doesn't just slow things down — it produces confident-looking matches built on gaps. A missing gear flag, an out-of-date open date or an unstated draft limit can turn a 'strong' fit into a fixture that can't work the berth. Catching those before they reach a shortlist is cheaper than catching them at the load port.

Key takeaways

• A record is only as useful as the fields it carries
• The load and discharge fields that decide a fixture are the ones to get right
• Missing information is a result to surface, not a blank to guess
• Clean, current, structured data is what makes a shortlist trustworthy