01 / REVIEW

Preserve the old value

Record the original statement and document version before adding a correction. Keep the conflicting source visible so a later reviewer can understand why the question arose.

02 / REVIEW

Record the resolution

Attach the explanation, issuer, date and relevant corrected document. Distinguish a supplier correction from an internal transcription fix. Neither should be silently represented as an independent verification.

03 / REVIEW

Propagate carefully

Identify downstream records affected by the change. Update them with a reference to the correction while preserving prior versions where needed for the archive.

Correct the record without concealing the original

Errors happen in labels, units, quantities and descriptions. The useful question is whether another person can understand the correction. Preserve the original value, the replacement, the reason, the date and the supporting record. A silently edited spreadsheet loses that explanation.

Separate a transcription correction from a change in evidence. Fixing a mistyped bundle number to match a photographed label is different from receiving a new supplier statement that changes the claimed origin. The second may require revisiting decisions that used the earlier claim.

Keep a short change log

Keep a short change log
Change fieldFictional example
Record affectedReceiving lot REC-18
Original entry24 pieces
Corrected entry42 pieces
BasisDated recount and photograph references
Follow-upReconcile transfers made using the earlier total

The example is a recordkeeping exercise, not an explanation of a real shipment. The corrected number should appear in the current view, while the earlier value remains available in the history. This keeps the working record readable without making it unauditable.

If a correction affects a shipment, send the corrected record through the established project process and identify what changed. Do not assume that updating your local copy also updates a contractor’s downloaded copy. Link the change to the affected quantity reconciliation.

Decide what kind of correction you are making

Start with the disputed field, not a replacement document for the whole lot. A local typing error, a revised supplier statement and two unresolved sources call for different actions. Record who supplied the information separately from who entered it or reviewed it. A person updating the register is not necessarily the issuer of the underlying claim.

Decide what kind of correction you are making
SituationCurrent recordHistory to retain
Local entry differs from its sourceCorrect the entry to match the identified sourceOld entry, source location, editor, date and reason
Issuer sends a revised statementLink the new statement and identify the field it supersedesBoth versions, issuer explanation and material covered
Two sources still disagreeKeep the field disputed; show both statementsQuestion sent, sources compared and response still needed
New statement covers only part of a lotApply it only to the identified partParent/child lot links and the unresolved remainder

A newer date alone does not resolve a conflict. Check whether the document addresses the same material, quantity and transaction, and whether its issuer actually explains the change. Keep unrelated fields as they were. Correcting a lot number does not also establish a species or origin claim.

Follow a correction through a split lot

Consider a fictional receiving lot REC-18 with 42 pieces. Twelve pieces went to project A, ten to project B and twenty remain in stock. A revised packing list corrects the supplier reference from BX-471 to BX-417. Before changing the record, confirm which delivery and labels the issuer means. The fact that the quantities add to 42 does not prove the reference is correct.

Once the reference correction is supported, retain REC-18 as the internal identity. Add the corrected supplier reference and link the issuer’s explanation. Then check the project A transfer, project B transfer and remaining-stock record. Each needs a link to the correction; none needs an invented new origin statement. Preserve the earlier exported records so a recipient can explain why their copy differs.

If the issuer can identify only one bundle, do not extend that answer across all 42 pieces. Identify the covered subset using the available physical and transaction records, and leave the rest unresolved. The split-lot guide explains how to keep those relationships visible.

Close the loop with the people holding earlier copies

Updating the master register does not replace copies already attached to a project file. Keep a distribution check with the correction: recipient or record owner, affected document/version, replacement supplied and acknowledgment status. Record “sent” when it was sent and “acknowledged” only when a response supports that status.

  • Name the exact field and lot affected in the correction notice.
  • Identify the earlier record and the new version without deleting the earlier reference.
  • State the basis for the correction and any questions that remain open.
  • List the transfers, stock records and handover packets reviewed.
  • Record who completed the review and when; retain unanswered recipient checks as open.

Keep internal working notes separate from the packet a recipient needs. The handover archive should let someone find the current record and follow its history without searching an entire mailbox. A correction trail supports traceability; it does not turn a supplier statement into independent verification.

Draft one traceable correction

Use references to documents, not confidential document contents. Keep the original file in your own archive. Export this draft before leaving; reloading clears it.

Draft incomplete: 12 fields not recorded.

Neither a completed draft nor a supplier revision independently verifies an origin claim.

Show fields not recorded
  • Correction kind
  • Correction reference
  • Internal lot reference
  • Original document and version
  • Field being corrected
  • Original statement or value
  • Proposed or corrected value
  • Reason and supporting record
  • Correction issuer / role and date
  • Corrected document reference
  • Affected transfers, stock and recipients’ copies
  • Open questions and next action

This export does not change a supplier document, update downstream records or notify recipients. Link it to the relevant records through your organization’s process.

A lot-record scenario

Fictional example: a transposed lot number is corrected by the issuer. The receiving record retains the original label photograph and links the written explanation and revised packing list.

Use the result

Keep the completed review with the relevant project record. Assign unresolved items before relying on a conclusion. If the material, condition or document changes, revisit the affected questions.

Evidence workspace
Technical references

General background for the subject. Project worksheets and fictional situations are original review aids, not official agency forms.

APHIS: Lacey declaration guidance

APHIS: Lacey declaration questions

APHIS: CITES plant trade guidance