Every transporter on a shipment has to be named on the manifest before the first signature happens. On an electronic manifest, that's not just good practice — it's enforced by RCRAInfo itself. The moment the manifest moves past "Scheduled" status (which happens once the first transporter takes custody), the transporter data locks. No API call, correction, or amendment can add or change a transporter after that point — not even RCRAInfo's own post-completion "Correct" tool, which only becomes available once the manifest is fully signed, by which time the same lock is still in effect.
That raises an obvious question: what happens when reality doesn't cooperate?
Two real scenarios, one regulation
40 CFR 263.21 is the rule that actually governs this — and it covers both of the practical situations that come up:
- A transporter genuinely can't complete the leg (breakdown, an emergency, anything that isn't simply the facility rejecting the waste) — the transporter has to contact the generator and get authorization to revise the transporter designation.
- One company picks up, a different company delivers — this is normal, planned relay transport, not an emergency. It's handled through a transfer facility: a loading dock, parking area, or similar transportation-related location where a shipment can sit briefly between transporters.
Transfer facilities and the 10-day rule
Under 40 CFR 263.12, a transporter can hold manifested waste at a transfer facility for 10 days or less without triggering the permitting requirements that apply to actual storage facilities. One detail that's easy to get wrong: the 10-day clock only counts time the waste sits still — EPA guidance is explicit that it "does not apply to the period of time that such waste is actually in transit between the pick-up and delivery points." There's no separate federal rule capping how long a shipment can be on the road overall — only this holding-time limit at a transfer point, and the unrelated 90-day accumulation clock generators face before waste ever ships in the first place.
Agency authority — skipping the phone call
Calling the generator every time a substitution is needed doesn't scale well for a transporter that regularly relays shipments to a second carrier. 40 CFR 263.21(b)(3) has an answer: if the generator's contract with the initial transporter explicitly grants that transporter authority to add or substitute later transporters on the generator's behalf, the initial transporter can make that call without asking each time. The catch is that this authority has to be declared on the manifest itself — specifically, in Item 14 (Special Handling Instructions), using this exact certifying sentence:
"Contract retained by generator confers agency authority on initial transporter to add or substitute additional transporters on generator's behalf."
This only applies to the initial transporter (Transporter 1) — it's not something later transporters in the chain can claim for themselves.
Since Item 14 is only reliably editable before anyone has signed, ManifestMate captures this at manifest creation — a checkbox under the first transporter's details writes the certifying sentence into Item 14 automatically, so it's part of the manifest from the start rather than something added after the fact.
What this doesn't solve
None of this reopens a manifest that's already moving. Agency authority and transfer facilities are both about handling substitutions within the rules as written — they don't create a way to edit a live electronic manifest's transporter list. And regardless of who's doing the driving at any given moment, the underlying regulation is clear that none of this reduces the generator's liability for the waste.