Shadow Spreadsheets in Freight Forwarding

In most mid-size freight forwarding operations, at least one spreadsheet runs alongside the core system. The operations manager knows it exists, because in many cases that manager built it. The spreadsheet tracks what the ERP should track, fills gaps the system leaves open, and pulls together what no single screen can show. It holds up as long as volume fits inside it. The trouble is that volume grows, and the spreadsheet gives no warning when it stops keeping up.

The spreadsheet fills what the system does not deliver

The operator who keeps a spreadsheet next to the system is solving a real problem. In many forwarding companies, the ERP records the shipment, issues invoices, generates the Brazilian CE Mercante and feeds Siscomex, but it does not show the operator, on one screen, everything needed to run the day. Free time countdown per container, pending document status, the deadline the customs broker promised, each client’s preference for draft formatting, the terminal contact who handles after-hours scheduling: all of this sits outside the system.

The spreadsheet is born from that gap. Among freight forwarders in Brazil, operators who keep a shadow spreadsheet need information the system has not consolidated. When the ERP displays a shipment as a record with dozens of fields but does not show the day’s task calendar, the operator builds that calendar in a spreadsheet. When the system records the free time sold to the client but does not calculate how many days remain before the container enters demurrage, the operator runs that math in a spreadsheet.

The outcome is consistent: the most critical operational information of the day ends up in a file only that operator understands.

What lives in the spreadsheet and nowhere else

Shadow spreadsheets at mid-size forwarding companies tend to hold the same categories of data regardless of the company, a pattern that shows up in nearly every operational audit.

Free time tracking is the most common case. The system records the discharge date and the free days negotiated with the carrier, but the operator needs to cross-reference that with the free days sold to the client, the terminal calendar, and the pickup schedule. That cross-calculation is rarely automated in the ERP, and the operator redoes it every morning in the spreadsheet, container by container.

Pending document tracking is the second. A shipment involves eight to ten documents that arrive at different times, from different sources. The commercial invoice comes from the exporter, the packing list arrives with it or separately, the bill of lading comes from the carrier or the overseas agent, the certificate of origin comes from the chamber of commerce, and any required license comes from the regulatory authority. The ERP records whether a document has been attached, but the operator’s spreadsheet records who is being chased for each document, when the last follow-up was sent, and what the real deadline is for that specific shipment.

The third pattern is the client exception list. Every importer has preferences that do not fit into a standard registration field: client A wants the draft with a trade name in the consignee field, client B requires the packing list split by container, client C needs the invoice to include a purchase order number in the reference field. These rules live in the operator’s head and in the operator’s spreadsheet. When a new operator takes over the account, mistakes begin until someone hands over the spreadsheet, if the spreadsheet still exists.

The cost shows up when volume grows

An operator handling 30 shipments per month can keep the spreadsheet updated with reasonable accuracy. The daily effort is 20 to 30 minutes of manual updating, acceptable within a routine that already includes checking emails, consulting carrier portals, and entering data into the system. The spreadsheet works as an extension of the operator’s memory, and that memory still reaches.

When the same operator starts handling 50 or 60 shipments, the spreadsheet begins to fail before the operator notices. The container that entered demurrage without warning, the invoice issued with the wrong Incoterm because the client exception was outdated, the document that went unchased because its row scrolled off screen: all of these errors come from the gap between the last spreadsheet update and the moment the information was needed. A forwarding company that grows 20% in volume in a single quarter without hiring discovers that the spreadsheet, which worked until yesterday, is now the source of the errors it once prevented.

The breaking point tends to fall between 45 and 55 concurrent shipments per operator. Below that, the spreadsheet absorbs the volume. Above it, errors from stale data grow faster than the operator can correct them.

The spreadsheet hides operational risk

Data that lives in an operator’s spreadsheet carries three vulnerabilities that data inside the system does not.

The first is the absence of backup. Most shadow spreadsheets sit on the operator’s desktop or in a personal drive that no one else can access. If the machine fails or the operator leaves without notice, the day’s operational information disappears with them. One pattern that comes up repeatedly at freight forwarding companies is the reconstruction of controls after a departure: the team spends two to three days rebuilding the spreadsheet of the person who left, working from emails, the system, and colleagues’ memory. Key-person dependency gains an additional layer when the person takes not only the knowledge but the control instrument itself.

The second vulnerability is the absence of history. The system records when a shipment was opened, when each milestone occurred, and when the invoice was issued. The spreadsheet records only the current state. When the operations manager needs to know how long client X’s shipment took from cargo arrival to delivery, the system can answer if the milestones were maintained. The spreadsheet holds only what is happening now, with no record of what already passed.

The third is the absence of an audit trail. Who changed a piece of data, when, and why: the system records it, the spreadsheet leaves that question unanswered. When a demurrage dispute hinges on knowing the date the operator received the free time expiration notice, the spreadsheet cannot serve as evidence. That lack of traceability surfaces most often in demurrage disputes and billing disagreements with clients.

How to bring the information inside the system

Eliminating the shadow spreadsheet starts with understanding what it solves, before attempting to ban it. Banning the spreadsheet without offering an alternative inside the system tends to produce one of two outcomes: the operator keeps the spreadsheet hidden, or the operator stops tracking the information the spreadsheet used to track. Neither outcome is better than the open spreadsheet.

The first step is the survey. The operations manager asks each operator for the spreadsheet they use. Most hand it over without resistance, because the operator knows the spreadsheet is extra work and would prefer not to need it. From the collected spreadsheets, the manager maps which information lives outside the system: free time tracking, client exception lists, document follow-ups, customs broker deadlines, terminal contacts.

The second step is classification. Some of that information fits into fields or rules the system already has but no one configured. Some requires a system change or an integration. And some entries are temporary controls that exist because the process is not yet standardized: in those cases, the missing piece is the procedure, not the field in the system.

The third step is gradual absorption. Each piece of information that migrates from the spreadsheet to the system eliminates one manual update from the operator and places the data somewhere visible to the entire team, with backup, history, and an audit trail. The operator who used to spend 30 minutes a day updating the spreadsheet gets that time back for operations. Across a team of ten operators, the gain is nearly 25 hours per week, the equivalent of half an operator.

How Tier2 Cargo absorbs what the spreadsheet tracks

Tier2 Cargo was built for freight forwarders, and much of what lives in the operation’s shadow spreadsheets already has a home inside it. Free time tracking per container, with a countdown of remaining days and expiration alerts, is part of the shipment workflow. The 13 operational milestones per shipment record the history the spreadsheet does not keep. Client exception rules sit in the business partner record, visible to any operator who takes over that account. Pending document tracking appears within the shipment itself, with the status and source of each document.

When the operator finds inside the system what used to exist only in the spreadsheet, the spreadsheet loses its reason to exist. The data lives in one place, with backup, history, and an audit trail, accessible to the operations manager and to whoever is covering an absence.

Learn more about Tier2 Cargo or get in touch.

Frequently Asked Questions

How can I tell if my team uses shadow spreadsheets?

Ask each operator to show how they organize their workday. In most forwarding operations, the operator opens the spreadsheet alongside the system first thing in the morning. The spreadsheet usually tracks free time, pending documents, and client exceptions. If the operator hesitates, ask specifically about demurrage tracking and the list of documents being chased: those two controls almost always live outside the system.

Is the shadow spreadsheet a system problem or a process problem?

It is both. The spreadsheet exists because the system does not show, in an accessible view, everything the operator needs to run the day. But it also exists because certain operating rules were never documented. Solving the problem requires mapping what the spreadsheet tracks and deciding, case by case, whether the solution is configuring the system, creating a procedure, or doing both.

How much time does an operator spend updating the shadow spreadsheet?

Among freight forwarders in Brazil, operators spend 20 to 40 minutes per day updating manual controls outside the system. Across a team of ten operators, that amounts to 17 to 33 hours per week, roughly the equivalent of one full-time operator doing work the system should handle on its own.