"Pre-lodged" is a word that has quietly taken over UK customs vocabulary since GVMS went live. If you ship through a RoRo port now, your declaration is almost certainly pre-lodged — meaning, submitted to HMRC before the goods physically arrive at the border. The theory is simple. The practice, as anyone who has ever watched a sailing slot disappear because a declaration went into query at the wrong moment will tell you, is less simple.
This guide unpacks the timing question: when is a declaration too late, when is it too early, and where does the sweet spot actually sit for a busy UK-EU lane?
What pre-lodged actually means
In pre-Brexit frontier work, declarations were often made at the point of crossing or immediately on arrival. The truck showed up, paperwork was presented, the goods were cleared, and the vehicle moved on. That model does not scale for RoRo volumes post-Brexit. There simply is not enough time, space or staff at Dover and similar ports to examine thousands of trailers in real time.
Pre-lodgement solves that by moving the declaration out of the port and onto the HMRC Customs Declaration Service hours (or days) before the ship sails. By the time the driver arrives, the declaration has already been risk-assessed, classified, and — ideally — cleared. The driver's job at the gate is no longer to present paperwork but simply to present a GMR, which acts as proof that pre-lodged paperwork exists and is good.
The real constraint: when GVMS actually wants the MRN
A GMR can only be built after each underlying declaration has a valid Movement Reference Number (MRN). The MRN is issued by CDS once the declaration has been accepted into the system. So the earliest your GMR can exist is the moment after the last component MRN is live.
That cascade is where timing lives or dies. If the declaration goes in and is immediately accepted, you can build the GMR within minutes. If the declaration goes into query, you have to answer HMRC before the MRN clears. That response takes however long it takes — in practice anywhere from 15 minutes to several hours.
If the sailing is in one hour and the declaration has just gone into query, you're in trouble. If it's in four hours, you have a lot more room.
The rule-of-thumb window
For a typical short-sea RoRo movement (Dover-Calais, Harwich-Hoek, Holyhead-Dublin) we work to these internal guidelines:
- Commercial documents in, latest: sailing minus 4 hours. Past this point, if a classification or valuation question comes up, we're running close to the sailing slot.
- Declaration submitted to CDS: sailing minus 3 hours. This gives the declaration time to clear in normal conditions, or to absorb a query in slow ones.
- ENS/EXS lodged: sailing minus 3 hours, same as the commercial declaration.
- GMR built: sailing minus 30 to 60 minutes. Not earlier, because the vehicle and trailer details should be confirmed against what's actually arriving.
- Driver present at gate with GMR: sailing minus 15 minutes (or whatever window the ferry operator requires).
These are guidelines, not laws. Some ferry operators and some port gates require more margin. For high-value or complex loads we push the timing earlier. For a known, clean, regular movement with standard commodity codes we can compress it — but we never compress below 2 hours between MRN issue and sailing as a rule.
The "too early" trap
Going too early has its own failure mode. Most commonly:
- An export declaration lodged 5 days before sailing will usually time out if the goods haven't physically moved by then.
- ENS / S&S data has an expected arrival time that's audited — if the real arrival is wildly different, the declaration may need re-lodging.
- Vehicle and trailer details that were accurate a week ago often aren't accurate tomorrow.
Pre-lodging far in advance is fine for the commercial paperwork side (invoice, packing list) but risky for the formal CDS submission. Our internal practice is usually: collect documents as early as you want, but submit to CDS only when you have confirmed a sailing slot.
When it's going wrong, what to do
Three signals you should treat as "stop what you're doing":
- The MRN has not returned within 30 minutes of submission during UK office hours. Something is wrong — stuck in a queue, a query not yet flagged, a data error.
- The declaration returned a query and you haven't heard back from your broker within 20 minutes.
- The sailing is less than 90 minutes away and the GMR has not yet been built.
Any of these mean you need to escalate. In our setup, all three trigger an automatic phone call to the fleet contact. Your setup should too, whether that happens through a broker, an internal team, or a combination.
The one-sentence summary
Pre-lodged doesn't mean "as early as possible". It means "early enough that a problem is fixable, late enough that the data is still true". Three hours before sailing is a good default for both ends of that sentence.