jig
Free Time Watchtower  ·  built for your operations team
Prototype · sample container data
Money accruing now
-
demurrage + detention + port storage
At risk in next 72h
-
containers hitting last free day
Overdue today
-
already past a free time clock
Containers tracked
-
-
ContainerClientPortClock Next deadlineDays leftExposureOwnerStatus
Click any row to see the clock arithmetic: which date the free time started, how many days the carrier tariff allows, and what each day past it costs. Every figure below is calculated from the row data against the rate cards, not hard-coded.
Same data, second output. Each client gets a plain-English morning brief with the one thing that needs a decision today. This is the email your ops team currently writes by hand, one container at a time.
CarrierFree daysDay 1-5 /dayDay 6+ /dayCombined or split
Stevedore port storage (separate charge)
Terminal storage is billed by the stevedore, not the carrier, and stacks on top of demurrage.
Why this screen matters. Every forwarder's free time is different by carrier and by contract, and most of them live in a PDF tariff nobody reads until the invoice lands. Here they are configuration, so the clock is right for each line instead of being averaged into a spreadsheet formula.
Rate card values are illustrative defaults for the prototype. Nothing here is a quote from a carrier.
What this is
A working prototype of one narrow tool: it reads a container list, knows each carrier's free time and daily rates, and tells operations what is about to cost money and who has to act.
What it is not
Not a TMS and not a replacement for one. Your system of record stays where it is. This reads from it (CSV today, API next) and does the part the TMS does not do well: the deadline layer.
The arithmetic, in one line
Free time starts at vessel discharge, not at collection. Last free day is discharge plus the carrier's free days. Every day after that is billed per container. Detention is the same idea on the other clock, from gate-out to empty return.
Three things this version already does
1. Counts both clocks separately (demurrage while the box is in the terminal, detention once it is out).
2. Adds stevedore storage as a third, overlapping charge.
3. Generates a per-client morning brief from the same rows, so the client hears about a delay before the invoice does.
Next sprint, if it is useful
Carrier API or TMS feed instead of CSV, tariff effective dates, per-client SLA rules, and an alert that goes to the account owner rather than a dashboard nobody opens.
Built by jig
jig builds custom internal tools in one-week sprints, on a subscription you can pause. You own the code and the data. This prototype is the shape of the first sprint, not a mockup: the maths runs.
Email Manu
Try it with your own list
Export any open container report from your TMS as CSV, paste it into Import. If your port or carrier is missing, it still works: unknown carriers fall back to the default tariff.