Automated Ocean Freight Cargo Claim Tracking
Every Monday, WebRun opens the cargo claim register in Google Sheets, cross-references each open claim's container and B/L against Terminal49 shipment records to confirm damage or shortage details, updates claim statuses and days outstanding, and posts a digest to Slack highlighting claims at risk of missing filing deadlines.
How do I automatically track open cargo claims and flag ones at risk of missing deadlines?
WebRun reviews your cargo claim register in Google Sheets every Monday, cross-references each open claim's container and B/L against Terminal49 shipment records, flags claims that are stale or approaching carrier deadlines, and posts a prioritized digest to Slack. Your team handles all carrier negotiations and filings after reviewing the weekly summary.
- Deadline-at-risk claims are flagged every Monday before filing windows close and recovery is forfeited
- Stale claims with no carrier response in 14 days are surfaced for follow-up before they age out
- Total open claim exposure is visible in Slack each week so management can track recovery progress
Built for ocean freight importers · logistics claims managers · freight forwarders · supply chain risk teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
docs.google.com/spreadsheetsin a real browser with your saved login - no setup, no API keys. -
1
Google Sheets - review open cargo claim register for stale and deadline-at-risk items
google.com
WebRun opens Google Sheets to review open cargo claim register for stale and deadline-at-risk items. - Open the Cargo Claim Register sheet
- Review all rows with a status of filed, pending, or under review
- Flag claims where more than 14 days have passed since the last status update with no response from the carrier
- Flag claims within 30 days of the carrier's claim filing or response deadline
- Capture claim ID, container number, B/L, carrier, claim amount, date filed, current status, and deadline date
Done when Every open claim is categorized as on track, stale, or deadline-at-risk with days outstanding calculated.
-
2
Terminal49 - cross-reference shipment data for each claim
terminal49.com
WebRun opens Terminal49 to cross-reference shipment data for each claim. - Open Terminal49 and look up the shipment for each open claim by container number or B/L
- Confirm the delivery milestone, discharge date, and any customs holds or exceptions noted at discharge that are relevant to the damage or shortage claim
- Note the carrier and port of discharge to verify the responsible party on each claim
Done when Each open claim is matched to its Terminal49 shipment record with discharge date and milestone details confirmed.
-
3
Slack - post weekly claim status digest with deadline flags
slack.com
WebRun opens Slack to post weekly claim status digest with deadline flags. - Post the weekly cargo claim digest to the freight operations Slack channel
- Lead with claims marked deadline-at-risk, including days remaining and claim amount
- Follow with stale claims where the carrier has not responded in over 14 days
- End with a total count of open claims and aggregate amount outstanding
Done when The ops team has a Slack digest with deadline-at-risk claims highlighted and total open claim exposure summarized.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it file cargo claims or contact carriers automatically?
No. WebRun tracks and surfaces claim status. All carrier communications, formal filings, and settlement negotiations are handled by your team after reviewing the weekly digest.
Where does the claim register live?
You maintain it as a Google Sheet with one row per claim. Add columns for claim ID, container number, B/L, carrier, amount, date filed, status, and deadline. WebRun reads and updates it each Monday.
What if a claim is settled mid-week?
Update the status to settled in the Google Sheet when settlement is confirmed. The next Monday run will skip that row and exclude it from the open claim count.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.