Key Person Risk in Freight Forwarding
With operator turnover above 50% in Brazil, every departure takes client knowledge and workarounds. The risk is keeping that know-how out of the system.
Brazil’s CAGED (the national employment registry) records over 7,500 hires and separations per year in the freight agent role, a turnover rate above 50%, according to salario.com.br based on official data. When a senior operator leaves, they take with them the knowledge of how each client wants documents prepared, the actual deadlines at each terminal, and how to handle the exceptions that come up every week. Key person dependency is the operational risk that most freight forwarding owners recognize, feel, and postpone addressing.
There is a reason for the postponement. As long as the operator is at the desk, the operation works. The client receives documents in the format they expect, free time is tracked from memory, the B/L draft comes out right because the person filling it in has known the consignee for three years. The problem surfaces the day that person calls in sick, goes on vacation, or resigns. That is when the owner discovers how much of the process lived in someone’s head and how much lived in the system.
The knowledge that lives outside every system
Every mid-size freight forwarder has at least two or three operators who hold knowledge that no manual captures. One of them knows that Client X wants the draft with the trade name rather than the legal entity name in the consignee field. Another knows that Terminal Y in Santos charges storage from the third business day after discharge, and that Facility Z in Navegantes only accepts pickup scheduling by email before 2 p.m. A third knows that the overseas agent on the Asia route needs the packing list as a separate PDF per container, because their system cannot read a consolidated file.
This knowledge accumulates over months and years of operations. It grows out of errors that caused rework, complaints that taught the operator to anticipate a requirement, agreements made over the phone that were never formalized. It lives in WhatsApp notes, personal spreadsheet tabs, sticky notes on the monitor. The company’s system records the shipment: reference number, dates, amounts, attached documents. The rules that keep the shipment running without friction stay outside it.
In our experience with freight forwarders in Brazil, the most revealing exercise an owner can do is to ask each operator to list five things they know about their clients that nobody else in the company knows. The list tends to be long, and the silence that follows is the moment the risk becomes visible.
At 50% turnover, knowledge loss is routine
Brazil’s logistics sector created 173,000 jobs between January and April 2026, according to Transporte Moderno. The market is hot, and experienced trade operations staff know they have options. Pay for the freight agent role ranges from BRL 2,676 to BRL 3,691 per month, according to CAGED, a modest figure for the technical responsibility involved: running an ocean import shipment requires knowledge of CE Mercante (Brazil’s cargo manifest registry), DUIMP or DI (import declarations filed through the Siscomex trade portal), free time, billing rules, shipping documentation, and the procedures of each terminal. The gap between what the role demands and what it pays feeds the turnover.
With turnover above 50%, losing an experienced operator is no longer a rare event. The question for the freight forwarding owner is when the next key operator will leave, not whether. Each departure repeats the same cycle: the replacement arrives, receives a verbal explanation from whoever is left on the team, gradually discovers each client’s exceptions, and makes the same mistakes the predecessor had already learned to avoid. The ramp-up time for a new operator at forwarders that run without documented processes often exceeds 60 days, a period during which service quality drops and the risk of errors in documents like CE Mercante filings and B/L drafts rises.
We covered the related metric in an earlier post about processes per operator. Processes per person reveals the volume. Key person dependency reveals what happens when that volume changes hands.
Three signs your operation depends on people, not processes
One sign is that the owner knows who “handles” each client but cannot transfer a client from one operator to another without a drop in quality. The transfer works for the first few days, while the shipments are straightforward. At the first exception, the new operator gets it wrong because they do not know the unwritten rule the previous one had mastered. The client complains, the owner steps in, and the client ends up going back to the original operator, who becomes even more irreplaceable.
A second sign shows up during vacations. If the operator who handles the five largest clients takes two weeks off and the shipments in that period fall behind, accumulate open items, or trigger complaints, the cause is clear: the workflow for those clients lived in one person’s head. Whoever covered did the basics, and the basics produced rework.
The third sign is the length of training. At a forwarder with standardized, system-recorded processes, a new operator can handle simple shipments within one to two weeks, because the system guides the steps, the required fields, and the milestones. At a forwarder where the process lives in the heads of veterans, training stretches to months, because the new operator must absorb, through observation and error, everything the system should contain. Thirty days to reach basic autonomy is already a sign that knowledge is distributed among people, and sixty days is a sign that the process depends on whoever is teaching, and that whoever is teaching is too busy to teach well.
What changes when the process lives in the system
Transferring knowledge from people to the system means recording, in configurable fields and rules, everything the senior operator carries by heart. In the day-to-day of a freight forwarder, this comes down to a few concrete decisions.
One is to define, for each shipment type, which steps are mandatory and in what order. An ocean FCL import follows a different sequence than an air export. A system that records this sequence shows the operator what is missing, without requiring them to remember or ask a colleague.
Another is to configure required fields by client. If Client X requires the B/L draft to show the trade name in the consignee field, that rule gets recorded in the client profile inside the system. The operator who opens a shipment for that client sees the instruction before filling in the draft, whether they are the regular operator or a first-time substitute.
A third decision is to tie deadlines and operational milestones to the shipment. The CE Mercante filing deadline, the VGM cutoff, the cargo delivery deadline at the terminal: these milestones exist in every shipment. A system that records and enforces them reduces the chance of a deadline slipping by when the person at the desk is not the one who usually handles that client.
The fourth is to keep history accessible. When an operator takes over a client from someone else, they need to see prior shipments, the rules applied, the exceptions that occurred, and how they were resolved. If the history is in the system, the transition is a lookup. If the history is in the predecessor’s head, the transition is guesswork.
When these things are in place, ramp-up time for new operators drops, quality holds during vacations and leaves, and the departure of a senior operator stops being a crisis. The operation loses the person but keeps the process.
How Tier2 Cargo records the shipment from quote to settlement
Tier2 Cargo organizes each shipment as a process with a defined type (ocean FCL import, air export, customs clearance, and others), configurable steps, required fields by client, and 13 operational milestones with deadlines. The full history of each shipment stays accessible, with documents, billing rules, and the parties involved (shipper, consignee, carrier, overseas agent, customs broker).
When an operator leaves or moves to a different portfolio, the next person finds in the system the client’s standards, the exact stage of each open shipment, and the rules applied in previous ones. The knowledge that used to depend on the memory of whoever operated the shipment now belongs to the company.
Learn about Tier2 Cargo or get in touch.
For any owner who recognizes key person dependency in their own operation, a useful first step is to pick one client and record, in a system, everything the responsible operator knows by heart: draft rules, documentation preferences, terminal deadlines, overseas contacts. That exercise shows the size of the risk and gives the next operator a starting point better than zero.
Ready to transform your operations?
Discover how Tier2 Systems can help your company with intelligent ERP, AI agents, and automation built from real-world experience.
Learn How We Can Help