Route dangerous-goods documentation to qualified air-cargo reviewers

A matching document set can still need a qualified decision

A booking and a declaration show different package counts. The document system can identify the difference, but it cannot safely decide whether it reflects an error, different counting scope or a permitted representation.

The useful automation is to preserve both sources, identify the apparent discrepancy and route it to someone qualified and authorised to interpret it. The reviewer then follows the applicable requirements and records the decision. The queue should organise work around that decision, not replace it with a generic “documents complete” flag.

This article concerns document coordination. It does not provide instructions for classifying, packing, marking or accepting dangerous goods.

Establish which requirements apply to the shipment

As of this draft's review date, 15 October 2026, the IATA — DGR 67th edition, significant changes effective 1 January 2026 identifies the 67th edition changes effective from 1 January 2026. The IATA — Dangerous Goods documentation and updates also advertises forthcoming 2027 material and provides access to updates and related documentation. A page promoting a future edition should not be treated as the requirements already in force.

The responsible specialist must identify the rules applicable to the actual shipment date and movement, including relevant regulatory requirements, current amendments and state or operator variations. The change summary is not the complete rule set.

Record the source and edition or effective date used for the review, together with any applicable update. If a shipment is rebooked or its details change, the reviewer determines whether the earlier review remains valid. The workflow should make that question visible rather than silently carrying approval forward.

Avoid hard-coding a generic checklist from an old document into an application. The controlled checklist needs an owner, a review process and a way to distinguish historical decisions from the current requirements.

Define the queue's authority boundary

The queue can capture the shipment reference, booking version, declaration version, document availability, apparent inconsistencies and assigned reviewer. It can alert the responsible team when a required review is outstanding.

It should not infer a dangerous-goods classification from a product description, authorise a packaging method or determine acceptance from extracted text. Those decisions belong to the qualified parties under the applicable process.

These are proposed workflow controls. Their implementation should follow the organisation's approved operating and training arrangements.

Worked example: a count difference becomes a review case

The following example is illustrative. A booking states twelve packages and declaration version D1 states ten. The initial comparison identifies a difference of two, but the system does not assume that both fields describe the same counting level.

The qualified reviewer examines the source context and confirms, for this case, that the two fields are intended to describe the same package scope. The difference is therefore unresolved evidence requiring action. The reviewer asks the responsible origin party to establish the correct record through the applicable process.

When a revised declaration D2 arrives, the system preserves D1, links D2 to the same case and returns the affected review to the authorised person. Receipt of D2 does not automatically prove that the discrepancy is resolved or that the cargo is accepted.

Now consider a wider test sample of twenty document sets. Sixteen pass the configured administrative completeness screen and four are flagged for review.

All twenty cases remain subject to the reviews and physical acceptance steps that apply. The sixteen unflagged sets must not bypass required scrutiny because software found no mismatch.

These figures are not a detection-performance claim. To measure detection quality, the team would need independently reviewed reference outcomes, including problems missed by the screen.

Design the review record for a later handover

For each case, retain the documents actually reviewed, their versions, the requirement reference, the reviewer identity and the scope of the decision. A reviewer may resolve an administrative discrepancy without having authority to make every downstream acceptance decision.

Use a qualification and authorisation record appropriate to the organisation's process. Confirm currency and scope through the responsible training or compliance owner. Access to a review button should follow that approved role, rather than serve as proof of qualification.

A shift handover should show unresolved issues, the last decision, the next responsible person and any time-sensitive dependency. Avoid sending the next shift a list of filenames without explaining which version is current and what remains unanswered.

Restrict access to the business need. Documents may contain customer and commercial information; a shared exception queue should not become an unrestricted document library.

Compare a controlled register with embedded workflow

A controlled register can support a small, stable operation when qualified reviewers already use a reliable document process. It needs disciplined versioning, assignment and evidence of decisions.

An embedded workflow may help where bookings change frequently or several teams handle the same case. Test whether a revised source document reopens the affected review and whether administrative clearance stays separate from operational acceptance.

Automated document comparison can reduce the effort of locating differences. Evaluate it using poor scans, changed layouts and fields whose meaning depends on context. Measure both unnecessary flags and missed discrepancies against qualified reference review.

The comparison should focus on whether the tool makes the required review more reliable and manageable. A lower queue count can mean improved preparation, but it can also mean that the system stopped detecting problems.

Test the paths that could produce an unsupported accepted status

Use authorised test data to attempt acceptance with an unresolved discrepancy, a superseded declaration, an unavailable qualified reviewer and a changed booking. Inspect both the visible screen and any downstream message.

The expected result is a clearly identified pending condition under the approved process. A generic administrator role should not clear specialist decisions simply because it can edit ordinary booking fields.

After an interruption, reconcile changed document versions and decisions before resuming the workflow. Preserve the prior accepted record where appropriate, but do not assume it applies to a materially changed shipment. The qualified authority determines the required re-review.

Track unassigned cases, reviews waiting on external evidence and decisions whose supporting version is missing. Those measures reveal coordination weaknesses without pretending to measure regulatory compliance through queue statistics alone.

Make the qualified review easier to perform and reconstruct

The strongest digital support reduces searching, version confusion and missed handovers while keeping specialist decisions accountable. It should leave a clear record of what was reviewed, by whom, under which applicable requirements and with what unresolved conditions.

Next actions

1. Ask the responsible compliance lead to define the current review boundary and authorised roles.
2. Select a controlled sample containing a count discrepancy, a revised declaration and a changed booking.
3. Test administrative checks and version routing against qualified reference decisions.
4. Confirm that no document-screen result can bypass the applicable acceptance process.

A workflow assessment should begin with the approved procedures and an anonymised case history. It should not attempt to derive dangerous-goods rules from an OCR model or a generic checklist.