A 100-shipment freight forwarding operation spends roughly 35 to 53 hours per month moving data from emails into the TMS, before any actual freight decision gets made. A single pre-alert takes 12 to 14 distinct steps to process: locating the email, opening each attachment, reading the bill of lading field by field, cross-checking the commercial invoice, finding the lot in the TMS, and keying every value in. A clean email runs 8 to 12 minutes; a messy one, 20 to 30. The total is almost always larger than the operator’s estimate, because it has never been measured per step. Automating the read-and-key loop, while keeping a person on every approval, is what recovers those hours.
Most freight forwarding ops managers can answer “how many jobs do we run per month” without checking anything. Very few can answer the follow-up question: how many hours per month does your team spend moving data from those jobs’ emails into the TMS?
The number is almost always larger than the estimate. Not because anyone is slow. Because the question has never been measured per step.
This post names every step in the manual process, puts a time figure on each, and shows what changes when the loop runs with an automated layer instead.
What is the inbox-to-TMS loop?
The inbox-to-TMS loop is the gap between a shipment email arriving in your ops inbox and the corresponding TMS record being updated with the data inside that email.
Every ocean import job generates a sequence of inbound emails from parties you do not control: booking confirmations from carriers, pre-alerts from overseas agents, arrival notices, LFD assertions, and trucking coordination messages. Each one contains structured fields that belong in the TMS. None of them land there automatically. A person bridges that gap.
The loop exists in every lane: ocean import, ocean export, air, domestic trucking. The document names change. The steps do not.
For a detailed map of which email types appear at which job stage, see The Freight Forwarder Email Infrastructure Problem.
Every manual step on a single pre-alert
A pre-alert is the highest-cost email type in the ocean import inbox. It arrives from the overseas agent before the shipment, carries the most fields, and often includes multi-page PDF attachments that require scanning, not just reading.
Here is every step a person takes to process one pre-alert into a TMS lot, from the moment the email lands:
-
Notice the email. In a shared ops inbox, this is not instant. The email arrives at some point during the workday. If the ops person is mid-task, it may sit for 15 to 45 minutes before someone opens it.
-
Read the subject line and sender. Identify: is this a pre-alert or something else? What shipment is this likely for?
-
Open the body. Read the agent’s message for context, reference numbers, and any notes about the shipment.
-
Open the attachment. A pre-alert typically has 2 to 5 attached documents: the house B/L, master B/L, commercial invoice, packing list, sometimes a packing certificate or fumigation certificate. Open each.
-
Locate the MBL and HBL. The master bill of lading number and house bill of lading number are the primary identifiers. They may appear on different documents, under different label names (“Master Reference,” “M/BL No.,” or just “Reference” depending on the agent’s format).
-
Extract vessel and voyage details. Read: vessel name, voyage number, ETD (estimated time of departure from origin), ETA (estimated time of arrival at destination). These appear on the B/L but the format varies by carrier and origin.
-
Extract container and seal numbers. These usually appear on a second page of the B/L or on a separate equipment list. If there are multiple containers, each line requires reading.
-
Extract party details. Shipper name and address, consignee name and address, notify party. Each value must be read and verified against the booking record already in the TMS.
-
Cross-check the commercial invoice. Does the shipper on the invoice match the shipper on the B/L? Does the commodity description match? Does the declared value look correct? Discrepancies here require a follow-up email before proceeding.
-
Open the TMS in a separate window. Navigate to the ocean import module. Search for the correct lot by MBL, reference number, or customer name. Locate and open the job record.
-
Key each field individually. MBL number, HBL number, vessel, voyage, ETD, ETA, container number, seal number, container type, commodity, package count, weight, shipper, consignee, notify party, freight charges. Each field is a separate input. Typos in reference numbers create reconciliation problems later.
-
Verify the ISF status. If ISF has not been filed yet, this is the moment to confirm the field list is complete. Missing manufacturer or HTS code triggers a follow-up before the ISF can be submitted.
-
Save the record. The lot is now updated with the pre-alert data.
-
File or archive the email. Move the pre-alert to a job folder or archive for reference. If this step is skipped, the inbox becomes a search problem the next time someone needs to find the original document.
That is 14 steps. On a clean pre-alert from a well-organized agent, this takes 8 to 12 minutes. On a messy one, 20 to 30 minutes. Both are routine. For a detailed breakdown of the full pre-alert workflow including ISF implications, see Pre-Alert to TMS Lot: The Ocean Import Workflow.
What each email type costs in minutes
Pre-alerts are not the only email type requiring TMS updates. Every job milestone sends at least one email. Here is the manual time per type, labeled as illustrative figures based on ops team feedback from active forwarding operations:
| Email type | Key fields to extract | Manual time per email |
|---|---|---|
| Pre-alert | MBL, HBL, vessel/voyage, ETD/ETA, container, parties | 8 to 12 min (clean) / 20 to 30 min (messy) |
| Booking confirmation | Booking number, vessel, ETD, port of loading, container type | 5 to 8 min |
| Arrival notice | Container available date, terminal, charges confirmed, free time start | 5 to 10 min |
| LFD notice | Container number, last free day date, detention rate | 3 to 5 min |
| Trucking coordination | Pickup appointment, chassis, driver, release number | 5 to 8 min |
At 100 ocean import jobs per month with 3 to 4 emails per job requiring TMS updates, that is 300 to 400 emails per month. At an average of 7 to 8 minutes per email (illustrative), the total is 35 to 53 hours per month. Per ops staff member. On data entry before any actual freight decisions happen.
The manual workflow vs an AI-assisted workflow
The distinction between these two paths is not about the judgment calls — those stay with the ops team regardless. The distinction is about the preparation work that happens before the judgment call.
Manual workflow: An email arrives. Someone on the team opens it, reads it, identifies the shipment, opens the TMS, finds the lot, and keys in each field. 14 steps, 8 to 30 minutes depending on document quality.
TIO-assisted workflow: TIO reads the inbound email the moment it arrives. It identifies which shipment the email belongs to using reference numbers, vessel details, and sender patterns. It extracts each field from the body and attachments, assigns a confidence score to each one, and pre-fills the TMS record. Your ops person opens a pre-filled review screen instead of a blank record. They verify the extracted fields, correct anything flagged as low confidence, and approve the write. For a clean pre-alert, the review takes under 2 minutes. For a messy one, 4 to 6 minutes.
The 14-step manual sequence becomes a 2-step review: check the pre-filled fields, approve. The judgment is still there. The typing is not.
What this compounds to at volume
The time cost scales linearly with job volume. At 50 jobs per month it is a nuisance. At 100 it starts to constrain throughput. At 150 it becomes the ceiling that forces a hire.
At $35 to $50 per hour in fully loaded ops staff cost (illustrative range, varies by market), 40 hours per month of data entry runs between $1,400 and $2,000 per month. Per ops person. The work is not skilled. It is necessary and accurate, but it requires no judgment. The labor cost of doing it manually is not justified by what the task actually is.
For the broader case on reducing back-office hours without adding headcount, see Cut Freight Forwarder Back-Office Hours in 2026.
What to measure before deciding
The most useful number to have before evaluating any inbox automation tool is your actual per-email processing time. Not an estimate — a timed sample.
Pick one day. Have someone on the ops team log the time they start and finish processing each inbound shipment email. Count the steps. Note the email type and whether the documents were clean or required follow-up.
After one day you have: emails processed, minutes per email by type, and a rough monthly projection. That number, set against your current ops cost, is the right input for any build-vs-buy decision.
A freight forwarder AI software layer that closes the inbox-to-TMS gap does not require switching TMS platforms or retraining your team. It adds the extraction and pre-fill layer on top of what you already have. Your team reviews and approves every write. The 14 manual steps become 2.
Request a demo to see TIO run a real pre-alert through the inbox-to-TMS workflow end to end.
Frequently asked questions
How many manual steps does it take to process one pre-alert email into a TMS record?
A clean pre-alert with complete documents takes 12 to 14 distinct steps: locating the email, opening attachments, reading the B/L for each field, cross-checking against the commercial invoice, opening the TMS, finding the correct lot, and keying each field individually before saving. On a clean email from a well-organized agent, this takes 8 to 12 minutes. On a messy one — mismatched values, non-English attachments, or a missing field — it takes 20 to 30 minutes. Both are routine.
What is the inbox-to-TMS loop in freight forwarding?
The inbox-to-TMS loop is the gap between a shipment email arriving and the matching TMS record being updated with the data inside it. Every booking confirmation, pre-alert, arrival notice, and trucking coordination email contains structured fields that belong in the TMS. None of them arrive in a structured format, and none land in the TMS automatically. A person bridges that gap: reading, extracting, and keying. At high job volume, that loop is the primary source of ops hour bleed in a freight forwarding operation.
How much time per month does a 100-shipment operation spend on email data entry?
An operation running 100 ocean import jobs per month generates roughly 300 to 400 inbound emails requiring TMS updates across the job lifecycle (booking confirmations, pre-alerts, arrival notices, LFD and trucking coordination). At an average of 7 to 8 minutes per email — illustrative, based on ops team feedback from active forwarding operations — that is 35 to 53 hours per month in email data entry before any actual freight decisions get made. This estimate does not include the time to triage unread emails or handle exceptions.
Does TIO need access to my TMS to automate email data entry?
TIO is TMS-agnostic. It does not require replacing your TMS or adding an integration that changes your team's workflow. TIO reads your inbox and pre-fills records for your team to review and approve. The connection to the TMS is a write that happens only after a human on your team approves the pre-filled record. TIO works alongside CargoWise, Magaya, GoFreight, and any other TMS your team currently uses.