Document follow-up
How should an import team follow up on missing shipment documents?
Follow up on a missing shipment document by naming the required record, revision, shipment context, accountable responder, due decision, and acceptance check. Tyllus keeps the request, response, file, and next review connected to the shipment rather than treating a sent email as completion.
By Ayhan Karaca, Co-Founder · Updated: August 19, 2026
A document request needs more than a filename
A request such as “please send the invoice” is hard to close reliably. The recipient may send an older revision, a file for a different shipment, or a document that still needs a broker, operations, or finance review. A better request says what record is needed, which shipment or purchase order it relates to, what version or fact must be checked, and who will accept the response.
CBP importer guidance makes clear that import responsibilities and recordkeeping cannot be reduced to a file exchange. Operational teams need enough context to route evidence to the responsible reviewer and preserve what was actually used for the shipment.
| Request element | Control question | Completion evidence |
|---|---|---|
| Required document | Which record or fact is missing? | Correct file or confirmed exception |
| Shipment context | Which shipment or purchase order does it support? | Reference matches the operating record |
| Responder and reviewer | Who supplies it and who accepts it? | Response is reviewed by the right owner |
| Next decision | What remains after receipt? | Decision, handoff, or escalation is recorded |
Close the request with a reviewed outcome
A sent message is an activity, not proof of completion. Keep the request open until the expected evidence is received and the responsible team accepts it or records a reviewed exception. If the response changes a shipment fact, make the changed fact visible to the next owner rather than leaving it inside the attachment or a reply thread.
- Separate a missing file from an unreviewed file.
- Keep the latest version and its shipment reference together.
- Record whether a professional review, partner answer, or decision is still pending.
- Escalate based on the shipment dependency, not simply the number of reminder emails.
- Retain the final response and reason when the request closes.
Where Tyllus fits
Tyllus brings document collection, shipment context, partner follow-up, ownership, and exception visibility into one operational view. Teams can see what was requested, what arrived, what still needs review, and which person owns the next decision without manually reconstructing the thread across mailboxes and folders.
Tyllus does not determine whether a document is legally sufficient, file customs entries, replace a broker, or guarantee a clearance outcome. The accountable professional and shipment-specific process remain essential.
Use your own records to quantify the problem
Measure aged document requests, repeat requests for the same evidence, time from request to accepted review, and instances where a missing or unclear record delayed a documented decision. Do not convert a generic count of emails into claimed savings. The useful baseline is the one your closed shipments can support.
Make document follow-up visible work.
See how Tyllus ties requests, files, ownership, and review context to the shipment that needs the decision.