Agency Tracking Checklist for Documentation and Agency Coordination Teams
A detailed agency tracking checklist for managing external certificate submissions, agency queries, payment proof, issue timelines, corrections, and escalation records.
Set up the agency record before submission
Agency tracking should begin before documents are submitted. Create the agency record with certificate type, shipment reference, issuing agency, agency contact, portal link if any, application owner, supporting documents, fee requirement, expected submission date, and expected issue date.
This prevents the common situation where a certificate is submitted by one person and everyone else has to ask for updates later.
Submission evidence checks
After submission, capture application ID, acknowledgement email or portal receipt, document list submitted, payment proof, submission timestamp, and any agency reference. If the agency does not provide an ID, record the email subject, contact person, and timestamp clearly.
The submitted document pack should be saved. If the agency later raises a query, the team needs to know exactly what was submitted originally.
Daily status and query checks
For time-sensitive certificates, status should be reviewed daily. The review should distinguish between submitted, payment pending, under review, query raised, correction requested, approved, issued, collected, dispatched, or rejected. A single word such as pending is not enough.
When a query is received, record the query, owner, response document, response date, and expected next step. Queries are valuable learning signals; repeated queries usually mean the application pack or source data needs improvement.
Escalation and final hand-off checks
Escalation should be based on deadline risk, not emotion. If the expected issue date threatens vessel cut-off, buyer dispatch, bank presentation, or customs filing, the escalation path should be triggered with evidence.
After issue, record certificate number, issue date, collection method, digital verification link, correction status, and final version location. Close the agency record only when the certificate is validated and attached to the correct shipment file.
| Checklist Step | What to Capture | Why It Helps |
|---|---|---|
| Agency setup | Agency name, contact, portal, owner, due date, certificate type. | Creates ownership before the application disappears into a queue. |
| Submission proof | Application ID, submitted documents, receipt, payment proof. | Provides evidence for follow-up and disputes. |
| Status detail | Exact status instead of generic pending. | Makes planning and escalation realistic. |
| Closure proof | Certificate number, issue date, final version and validation result. | Ensures the agency task closes only after document readiness is real. |
Agency checklist swimlane
Swipe ↔