What’s inside: audit trail · company memory
The question this file answersWhich of my people would I trust to file a DG declaration at the last minute before the cutoff — and why is it always the same one?
Fits: cross-border operators assembling customs files by hand.
Typical, from the logistics playbook — customs and compliance volume “varies”, so no count is claimed. For every hazardous shipment a clerk copies UN numbers, packing groups and emergency contacts into the declaration, then hunts for the SDS. It hurts before each vessel cutoff, and when the DG-literate clerk is away.
The morning before cutoff, the DG clerk opens declarations that are already filled and already carry the SDS, with a note on every field showing where the value came from — their work is the check and the signature, not the copying. When a new substance appears, it is on their desk as a question, not in a submitted form.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
of assembly time on regulatory paperwork — the low end of the customs playbook’s range, held on purpose; filing stays a signature
Before: a clerk copies UN numbers and hunts the SDS for every declaration. After: the playbook holds this to a conservative 30–50% of the assembly — a wrong UN number is expensive, so the check and the filing stay with a named person.
The logistics playbook uses 30–50% for customs and compliance documentation, dangerous-goods documents included; WCO (2023) reports 40–60% faster processing with automated pre-clearance — that figure is about customs clearance, not DG paperwork. A deliberately conservative range, not our measurement.
Your booking system and the filing channel stay — CargoWise, the carrier’s DG portal or the forms you use now. This is the same form-assembly build as our customs-declaration file, restricted to the DG part:
Nothing is filed without them.
Classification arguments. New substances. Correspondence with the authority. A wrong UN number is expensive, and it is signed by a person.
If the product master holds no UN data, or holds it in free text, the first weeks are spent building that table — the declarations cannot be filled from nothing. A new substance or a borderline classification is exactly what a model gets wrong, which is why classification is never automatic here. The playbook’s 30–50% is deliberately the low end for regulatory paperwork, and the WCO (2023) speed figure is about customs pre-clearance, not DG.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Logistics.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.