Training a new customs entry writer: a 30-day plan

You have hired an entry writer. Perhaps they have a trade degree and no customs experience, or they come from freight and have never keyed an entry. Either way, you need them working independently long before they understand everything, and somebody on your desk has to train them while still clearing today's arrivals.

This is a plan for how to train a new customs entry writer, written for the owner, operations manager or licensed broker doing the training. It covers four weeks, what to leave out of them, and how to tell whether it is working. It assumes your office already has its own system, clients and procedures; adapt the order to those rather than the other way round.

What the job actually is

When a new hire asked on r/CustomsBroker what the role involves, the practitioners who answered broadly agreed on three things.

• Most of the day is reading documents and keying them. Invoices, packing lists and transport documents arrive from clients, forwarders and carriers, and their contents go into the brokerage system. Several described it as data entry, often measured against a quota of entries or lines.
• The mechanics are quick to learn; the judgement is not. One writer said that a year in they still barely understood what was going on, while feeling confident with the accounts they managed. Another said the steps are easy but the work needs an understanding of the tariff schedule, commercial invoice requirements, other agencies' rules and Incoterms.
• The deadlines are physical. A shipment is on a vessel or aircraft, and the clock runs whether or not the documents agree with each other.

A 30-day plan cannot teach a year of judgement. What it can do is make the hire reliable on the mechanics quickly, and teach them to recognise when a question is above their pay grade. That is what the four weeks below are for.

Week 1: the packet

Goal: the hire can take a closed entry file and explain where every value on the entry came from.

Pull 20 closed, clean entry files from your own book, across your main clients and modes. For each one, have the hire lay the source documents next to the filed entry and trace each value back to the page it came from: parties, value, quantities, weights, origin, classification. They are not keying anything yet. They are learning what a correct packet looks like at your office before they see an incorrect one.

Spend one short session on the two forms the whole job revolves around, because new hires routinely confuse them:

• CBP Form 3461 (Entry/Immediate Delivery) is the entry documentation used to get the goods released (19 CFR 142.3).
• CBP Form 7501 (Entry Summary) is the entry summary (19 CFR 142.11), which completes the entry with the declared value, classification and rate of duty (19 USC 1484). When the entry summary is filed at the time of entry, the 7501 can serve as both, and a separate 3461 isn't required (19 CFR 142.3).

In practice both are electronic transmissions from your system, but the distinction between release and summary is one the hire will use every day.

The rest of the week is your system: screens, client profiles, where documents are filed, how an entry moves from draft to transmitted. For background reading, one of the practitioners in that thread recommended the opening of CBP's ACE Entry Summary Business Rules and Process Document as a description of the entry writer's scope. It is a reasonable first read; the later chapters can wait.

Week 2: consistency

Goal: the hire finds disagreements between documents before they reach an entry.

Go back to historical packets, this time including ones that caused trouble. Ask the hire to find every place the invoice, packing list and bill of lading or air waybill disagree, and to say what they would have done about each. Our guide to invoice and packing list mismatches covers the triage itself; use it as the reference rather than improvising a policy on the spot.

Teach the manufacturer identification code this week too, because it is built from the invoice and new hires get it wrong in predictable ways. The MID walkthrough covers it step by step.

By the end of the week the hire should be pre-keying with shadow review: they key a live entry in draft, a senior writer keys or reviews the same entry independently, and the two are compared before anything is transmitted. Nothing the new hire keys goes to CBP this week.

Week 3: prerequisites and deadlines

Goal: the hire knows what has to be true before anything is transmitted, and which clocks are running.

The expensive early mistakes are rarely typos. Practitioners in the thread listed transmitting without an in-bond (IT) on file, without an ISF on file, or to the wrong port, each of which is worse if it is noticed after duty has been paid. Cover:

• ISF. For most ocean cargo, the Importer Security Filing is due no later than 24 hours before the cargo is laden at the foreign port (19 CFR 149.2). The ISF mistakes post covers what goes wrong and what it costs.
• In-bond movements. Where the goods are moving under bond, and what the entry needs from that movement (19 CFR Part 18).
• The 15-day clock. Merchandise must generally be entered within 15 calendar days after landing, or after arrival at the port of destination for goods moved in bond (19 CFR 142.2).
• The 10-day clock. Where the entry summary is not filed at the time of entry, it is due with estimated duties within 10 working days after the time of entry (19 CFR 142.12).

A worked example helps the two clocks stick. Example, with invented dates: a vessel lands on Thursday 15 October 2026, so entry is due by Friday 30 October. If the time of entry is Monday 19 October and the summary is filed separately, ten working days later is Monday 2 November. Have the hire compute both dates for five of this week's live arrivals and check them against your system.

Then introduce your office's own pre-transmission checklist, or build one with the hire using the pre-transmission checklist for entry writers as a starting point. From now on the checklist is run on every entry they touch.

Week 4: judgement with a safety net

Goal: the hire keys and transmits live entries, and every one of them is reviewed.

Two judgement calls deserve explicit teaching this week.

The importer's classification against the description. The importer of record is responsible for using reasonable care to file the declared value, classification and rate of duty (19 USC 1484), and many offices key the HTS number the client supplies. The hire's job is to notice when that number and the invoice description plainly don't fit, and to raise it rather than silently change it or silently file it. Classification decisions belong to the importer and your licensed broker, not the newest person on the desk.

Other agencies. Some goods need data for partner government agencies such as FDA, EPA or USDA as part of the entry (CBP's list of PGA requirements in ACE). Teach the hire to recognise when a shipment probably involves one, using your own clients' product lines, and to flag it rather than guess at the requirements.

Write down the escalation rule and put it where the hire can see it: which questions go to a senior writer, which go to the licensed broker, and which go back to the client. A new writer who escalates too much is a training cost. One who escalates too little is a compliance one.

Every live entry this week is reviewed by the licensed broker or a senior writer before or immediately after transmission, whichever your procedures require. That review is not only good training. Among the factors CBP weighs when judging whether a broker exercises responsible supervision and control are the training given to employees and how often a licensed broker reviews the customs transactions employees handle (19 CFR 111.28). The same section requires a broker to report a new employee's details to CBP within 30 calendar days of the start of employment, so put that on the week-one admin list as well. Our post on responsible supervision and control covers what that review looks like in a small office.

What not to teach in month one

Leave these out on purpose, and tell the hire you are doing so:

• Antidumping and countervailing duties. They need to know the phrase and that a case can apply. Working out whether it does is a later topic and, early on, an escalation.
• Drawback.
• Foreign-trade zones.
• The broker's licence exam. Some hires will ask about it. The exam is held in April and October (19 CFR 111.13), but whether and when to encourage a new writer to sit it is a conversation for your licensed broker once the basics are solid, not a month-one goal.

None of these are unimportant. They are simply easier to learn once the hire can read a packet without thinking about it.

How to know it's working

Track three numbers from your own office, week by week. Don't compare them with anyone else's; client mix and line counts vary too much for outside benchmarks to mean anything.

1. Corrections per reviewed entry. How many changes the reviewer makes.
2. Rejects and corrections after transmission. Entries CBP rejects, and corrections needed after filing.
3. Entries completed per day, at an acceptable correction rate.

Example, with invented numbers:

	Week 2 (shadow)	Week 4 (live, full review)	Week 8
Corrections per reviewed entry	3.1	1.4	0.5
Rejects after transmission	n/a	1	0
Entries per day	4	7	12

The direction matters more than the level. Corrections should fall while volume rises. If volume rises and corrections don't fall, slow down. If corrections fall but volume stays flat, the hire is probably over-checking, and more confidence, not more training, is what they need.

Keeping the person you trained

The role turns over, partly because so much of it is repetitive keying. Each departure resets this plan to week one and costs you the partial productivity of another ramp; the arithmetic is in what a customs entry writer costs.

The best retention lever most small offices have is progression: giving a capable writer more of the judgement work and less of the re-typing as soon as they are ready for it. The keying is the part a new hire learns fastest and resents most; tools like EntryWrite take the re-typing out of it, so review time goes on judgement instead.