Auto-submit, off by default - why we shipped DEFRA auto-submission as opt-in

The most-requested feature on our roadmap was automatic DEFRA submission: log a load, and we file it for you, no button press. We built it. Then we shipped it switched off. Here's why.

Submission is a commitment, not a save

When you submit a waste movement to DEFRA, you're making a regulatory declaration. Getting it wrong isn't like a typo in a draft - it's a record an auditor can pull. We didn't want the first time a customer thought hard about that to be after a month of loads had already gone out automatically.

Opt-in builds trust faster than opt-out

There's a version of this where we default auto-submit on and let people turn it off. It would have looked better in a demo. But the operators who trust software least are exactly the ones the mandate hits hardest - and an opt-out default would have confirmed every fear about 'computers doing things behind my back'.

• Week one, you review every submission and press the button yourself
• You see the AI get the classification right, load after load
• When you're ready, you flip auto-submit on - and now it's your decision, not our default

“The toggle being off is the feature. Turning it on is the moment you've decided to trust us - and that has to be yours.”

- The LoadSnap team

What auto-submit actually does once it's on

With it enabled, an approved load submits to the DEFRA API automatically, you get a confirmation reference back, and the movement is marked filed. If a submission fails validation, it drops back into a review queue rather than failing silently.

You can scope it, too - auto-submit non-hazardous movements but hold hazardous ones for manual review, for instance. Most operators land there within a month.

LoadSnap team

UK waste compliance

Written by the team building LoadSnap, the UK waste compliance platform for carriers and receivers.