ADR reference data only. Classification is the consignor's legal responsibility. Consult a DGSA for compliance decisions.
What the check answers, and what it needs from you
A load of dangerous goods by road raises several questions at once, and each is settled by a different part of ADR. This check takes the whole load — every line with its UN number, quantity and packages — and answers each of them in one go, the same way POST /api/adr/consignment-check does for a system or an agent: the small-load points of 1.1.3.6, limited and excepted quantities line by line (Chapters 3.4 and 3.5), the most restrictive tunnel code of the whole load against the tunnel categories on the route (8.6), the line each entry puts on the transport document (5.4.1), whether the lines may travel together (7.5.2), and the vehicle side: placards and orange plates (5.3), the equipment on board (8.1) and the driver’s training (8.2).
Every check comes back with its own state — pass, fail, conditional, insufficient data or not assessed — and the ADR section it rests on. A check is never passed for want of an input: where the load leaves something open, the answer lists that check first, open, with the input that would settle it under “What would settle it”; the checks that pass follow, one line each. A UN number with several Table A rows (diesel, UN 1202, has three) needs the row chosen; the form lists the rows after the first check and never chooses one for you.
The answer is computed on the ADR edition that applies on the date of carriage you give (today when you give none), from the same dataset as the UN number pages, the 1.1.3.6 calculator and the LQ / EQ checker. The load lives only in this page’s address, so a link to an answer re-opens it; nothing you enter is stored. The full contract is in the API reference.
The DG Document Check, which read a shipper’s declaration from a scan, is paused while it is rebuilt; this check needs the lines typed in.