PortPro Automated Empty Return Deadline Worklist
Every morning, WebRun opens PortPro, finds all unloaded containers pending empty return, reads each return deadline, and writes a prioritized worklist to Google Sheets so your dispatchers know exactly which empties need to move today to avoid detention charges.
How do I track empty-return deadlines across all my containers automatically?
WebRun opens PortPro every morning, finds every unloaded container awaiting empty return, reads the return deadline, and writes a prioritized Google Sheets worklist sorted by due date so your dispatchers schedule the most urgent empty moves before detention fees begin.
- Empty returns dispatched before detention fees start, not after
- One ranked sheet replaces manual tracking across multiple steamship lines
- Same-day returns highlighted so nothing slips through on a busy morning
Built for drayage carriers · port trucking companies · intermodal dispatchers · container operations 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
app.portpro.ioin a real browser with your saved login - no setup, no API keys. -
1
PortPro - identify unloaded containers pending empty return
portpro.io
WebRun opens PortPro to identify unloaded containers pending empty return. - Open PortPro and filter containers to status Unloaded and awaiting empty return
- Read the empty-return deadline, terminal, steamship line, and last known location for each
- Calculate days remaining to deadline and tag containers due today or tomorrow as urgent
Done when Every container pending empty return is listed with its deadline and urgency level.
-
2
Google Sheets - log prioritized empty-return worklist
google.com
WebRun opens Google Sheets to log prioritized empty-return worklist. - Open the Empty Return Worklist sheet and clear yesterday's data
- Write today's list sorted by return deadline ascending
- Highlight rows where return is due within 24 hours
Done when The sheet is refreshed with today's prioritized empty-return worklist.
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
How does it know where the empty container is right now?
It reads the last-known location recorded in PortPro. If the location is blank, the container is flagged for your team to confirm before scheduling the return move.
What happens when a container has already been returned?
It reads the live status from PortPro each morning. Any container already marked as returned is excluded from the worklist automatically.
Will it communicate with the steamship line or terminal about the return?
No. WebRun only produces an internal dispatch worklist. Any outbound message to a steamship line or terminal is drafted for your review before it is sent.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.