Trade Evidence Gap Checklist

1. Case identity

• The canonical trade case reference is present and consistent across materials.
• Relevant parties, roles, goods or receivables, currency, value, and dates are identified.
• Duplicate or competing case identifiers have been linked or explained.
• The current lifecycle state is stated without implying approval or execution.

2. Source and provenance

• Each material claim points to a source artifact or responsible participant.
• The producing party or system is known.
• Source date, upload date, and any superseding version are recorded.
• Extracted values remain distinguishable from human-confirmed facts.
• Weakly attributed or manually asserted evidence is clearly marked.

3. Completeness

• Required contract, invoice, transport, warehouse, inspection, insurance, customs, and identity records have been checked for applicability.
• Each review requirement has sufficient supporting evidence or an explicit gap.
• Partial evidence is not presented as full coverage.
• Missing confirmations and unanswered review questions are listed.

4. Freshness and validity

• Time-sensitive records are current enough for the review purpose.
• Expired insurance, identity, inspection, or authorization records are marked stale.
• Validity periods and review dates are visible.
• Later amendments or cancellations have been checked.

5. Conflicts and uncertainty

• Conflicting quantities, values, dates, parties, and shipment references remain visible.
• No conflicting value has been silently overwritten.
• Each material difference has a review question and expected respondent.
• Known, claimed, confirmed, conflicting, missing, and not-applicable states are distinguished.

6. Gap record and next action

• The affected claim or requirement is identified.
• The reason current evidence is insufficient is stated.
• Sources already checked are recorded.
• The participant expected to respond is named by role.
• The next action is review-only and does not trigger external execution.
• The gap's effect on handoff readiness is explicit.

Working notes