If you run dispatch for cross-border trucks, you already know the "paper" part of a border crossing never fully went away. Even with ACE eManifest, FAST lanes, and automated status messages, your driver still needs something readable, consistent, and easy for a booth officer to match against what's in the system. That's what the ACE manifest lead sheet is really for: a standardized, driver-friendly summary that ties the trip in the real world to the trip in ACE — especially when the yard is loud, the clock is tight, and one missing number can mean a secondary pull.
I've spent enough years around dispatch desks to know that the difference between a clean crossing and a 40-minute headache usually isn't some exotic compliance failure. It's a mismatch — a swapped trailer, a typo'd SCAC, a driver swap that nobody reprinted for. The lead sheet is the cheapest, most boring tool you have to prevent all of that, and it's worth treating as part of the filing workflow rather than an afterthought.
What ACE eManifest is (and what the lead sheet does)
ACE — the Automated Commercial Environment — is CBP's primary trade platform. For highway shipments, the ACE eManifest is the electronic "pre-arrival" trip record that includes your conveyance and driver details along with the cargo-level information attached to that trip. It's the U.S. equivalent of the data you'd transmit through ACI on the Canadian side, and it's been the backbone of commercial truck processing at the northern border for years.
Here's the operational point that matters: ACE is digital, but border operations are physical. A lead sheet bridges that gap by giving the driver a single, consistent document that identifies the trip and the carrier in a way that aligns with ACE records, lists the primary cargo identifiers like bill numbers and references, and acts as an easy handoff when an officer asks "what are you moving and under what trip?" It's not a substitute for the electronic filing — it's the human-readable face of it.
CBP keeps refining ACE for truck manifests. As recently as this spring, CBP deployed an ACE truck manifest enhancement enabling ATA Carnet information to be included as part of an electronic truck manifest filing — announced in CSMS #67960213 and live as of March 24, 2026, per the CBP CSMS bulletin. None of these updates change the day-to-day reality for carriers: the process rewards clean, consistent data and punishes last-minute improvisation. The lead sheet is the simplest thing you can standardize that has an outsized impact on what your driver actually experiences at the port.
What a lead sheet is not
A lead sheet isn't a commercial invoice, a packing list, or a broker's entry package, and it's definitely not a "magic pass" to skip inspection. It's a fast, readable summary of the trip identifiers that lets CBP reconcile the physical truck in front of them with the electronic trip that exists inside ACE. Done well, it reduces questions. Done poorly — or printed too early — it creates them, and questions create time.
What info must match: SCAC, trip, conveyance, driver
Most "day-of" delays don't come from complicated compliance problems. They come from mismatches: the thing the officer sees doesn't match the thing ACE expects. The lead sheet is your chance to make those matches obvious before the truck ever reaches the booth.
Carrier identity: your SCAC can't be "close enough"
Your SCAC (Standard Carrier Alpha Code) is your carrier identifier in CBP systems. In ACE eManifest it isn't just a label — it's the key that ties your company to your filings and trip history. If dispatch types it wrong, or an old code gets used out of habit, you can trigger rejections and last-minute scrambles. A practical fix: write your SCAC in one "blessed" format inside your TMS templates — capitalization, spacing, placement — and make it hard to override. If a field can be changed, someone will change it during a rush.
Trip references: keep the human ID and the system ID aligned
Most operations end up with two identifiers for the same trip: a dispatcher-friendly internal trip number, and a system-generated ACE reference that comes back after transmission and acceptance. The lead sheet should show both, clearly labeled, so the driver and the office are talking about the same crossing when someone calls from the line.
Conveyance details: truck and trailer go out of sync fastest
Swapped trailers are the classic example. You transmitted one trailer number, the yard swapped it, and the driver is rolling with a different unit. The fix is not "send the driver anyway and hope." The fix is a standard process: when equipment changes, the filing changes, and the lead sheet gets reissued. At minimum, your driver packet should make it easy to confirm:
- truck number and plate (and country),
- trailer number and plate,
- driver name and license details,
- port and estimated arrival window,
- trip and cargo references the officer can reconcile quickly.
Driver record hygiene: make "who is driving" a locked step
In many fleets, driver changes happen right up until the last minute — someone runs late, hours-of-service gets tight, a relay changes. If your workflow lets the driver name change without triggering a reprint and recheck, you'll eventually have a truck at the booth with a valid trip in ACE but the wrong driver in the data. Build a "driver swap" mini-checklist: if the driver changes, dispatch confirms the driver profile fields, re-runs the transmit/accept loop, and re-issues the driver packet. No exceptions.
A dispatch workflow that prevents rejections
Here's a simple, repeatable workflow that works well for highway carriers running Canada–U.S. lanes. The goal isn't to be fancy — it's to be consistent.
Step 1 — Confirm the trip data is final before printing anything
Before you generate the driver packet, verify the basics: driver assigned, truck and trailer confirmed, and the trip references are the ones you'll actually transmit. Print early and you almost always create version-control problems — two sheets for the same trip, or a sheet that doesn't match the final transmission.
Step 2 — Transmit, then wait for acceptance before you "bless" the packet
The best time to print is after you've received the acceptance response. That's the moment the system agrees your trip exists and the core identifiers are valid. Print before acceptance and you hand the driver a packet that implies the trip is ready when it might not be — and that gap turns into phone calls, stress, and last-minute edits while the driver is already rolling toward the bridge.
Step 3 — Print a clean lead sheet that puts identifiers first
Put the identifiers a booth officer cares about at the top: carrier identity, trip reference(s), and cargo references. Bury them and you slow the interaction down every single time.
Step 4 — Pair the lead sheet with the right supporting documents
Depending on the shipment, your driver packet may also include PAPS label references for inbound-to-U.S. moves, and high-security seal info when applicable. One caution: don't overload the packet with redundant pages. Drivers need clarity, not volume — hand them ten lookalike sheets and you raise the chance the wrong one gets presented.
Step 5 — Build a "rejection checklist" for dispatch
When a filing gets rejected, don't just fix it — capture the reason. Over time you'll see patterns. Common categories include truck/trailer number mismatch (transmitted vs actual), driver record mismatch, cargo reference mismatch (BOL, shipment, or broker references), and seal numbers missing or inconsistent when a sealed trailer is expected. After a few weeks you'll usually find three to five repeat offenders. Turn those into a pre-flight check and your rejection rate drops.
Timing, FAST lanes, and the "don't print too early" rule
Every carrier has heard "file at least an hour before arrival." In the real world, the more useful takeaway is this: your workflow should be built to prevent last-minute transmissions. Last-minute transmissions are where mistakes hide — you're rushing, the driver is already moving, and there's no time to calmly reconcile details. Even if the filing goes through, your packet might not reflect the final data.
What changes when a load is FAST vs non-FAST?
Operationally, FAST compresses the timeline and increases the cost of errors. When your drivers expect the FAST-lane experience, anything that pushes a truck into secondary feels like a major disruption. That makes lead-sheet clarity even more important — it supports a quick match-and-move interaction at the primary booth.
The "two-print" rule that saves dispatch teams
If you often have equipment or driver changes, consider a rule like this:
- First print (internal): a draft sheet for the dispatch desk while you're building the trip.
- Second print (driver): the official lead sheet, only after acceptance and final equipment confirmation.
This keeps drivers from walking away with a packet that's already out of date, and it reduces the "we printed it, so it must be right" bias that creeps in when everyone's tired.
Where brokers fit in
On many lanes your broker handles entry work while you handle the carrier-side filings. That split is fine, but it creates a risk: you assume the broker's reference will match yours, and they assume you'll flag equipment changes. A lead sheet that clearly lists the cargo identifiers and references keeps both sides aligned.
Where seals, ACI, and NCAP fit together
For many fleets, the border-paperwork stack includes several programs depending on direction, customer, and freight type — ACE for U.S.-side pre-arrival information, ACI eManifest for the Canada side, and NCAP FAST-lane paperwork in specific workflows. Even though those systems are separate, your driver experience should feel unified: one lead-sheet format, consistent placement of references, and a predictable "where do I find it?" layout.
Seals: when physical security meets digital records
Seals aren't required on every load, but when you use them, treat the seal number like a data element — not a side note. A seal number that's on the trailer but missing from the packet creates confusion at the booth, especially on high-value freight. If you need them, BorderPrint carries all three common types: bolt seals for high-security applications, cable seals for closures a bolt can't reach, and plastic security seals for pallet and internal closures.
And while we're talking about physical things in a digital process: yes, once in a while a driver will say the only thing that made the trip tolerable was the tiny die-cast semi on the dispatcher's desk. It doesn't clear customs, but it does keep morale up.
BorderPrint options (physical + digital)
If you're standardizing your driver packets for U.S. entries, our ACE lead sheets are built for fast, legible handoffs at the port — available as physical sheets and as a digital download for printing on demand.
Browse the full ACE manifest lead sheet collection for physical and digital formats.
The ACE sheet is also available as a digital download for on-demand printing. If you're keeping the whole cross-border kit consistent, you may also want PAPS labels in rolls, sheets, or digital PDF; the matching ACI eManifest lead sheets for the Canadian side (physical and digital); and NCAP FAST sheets (physical and digital).
Frequently asked questions
Do I need an ACE lead sheet if everything is filed electronically?
In practice, yes — because the driver still needs a simple way to present the trip identifiers at the port. A lead sheet makes it easier to match the physical trip to the electronic record quickly, which keeps the primary-booth interaction short.
What's the most common cause of avoidable border delays for highway eManifests?
Mismatch. The driver's truck, trailer, or driver details — or the cargo references on paper — don't line up with what was transmitted to ACE. Standardized driver packets and a print-after-acceptance rule reduce that risk dramatically.
Should I include seal numbers on the lead sheet?
If the trailer is sealed, treat the seal number like a key identifier. Include it consistently on the packet and make sure the physical seal matches the printed number before the truck leaves the yard.