Test Mode First: Why Compliance Filings Deserve a Rehearsal
Most software mistakes cost you a click: undo, delete, try again. A government filing is not most software. It is worth understanding why that asymmetry exists, and what a rehearsal is actually worth.
The asymmetry
When a filing reaches a government system, it stops being a draft. It becomes a record: a legally meaningful statement, attached to your IEC, that someone may one day read back to you in an audit. If it is wrong, the cost is not a click. It is correspondence, correction, explanation, and time, all of it under someone else's clock.
That asymmetry deserves respect, and respect in software has a specific shape: a place to practise where nothing counts.
What a real rehearsal looks like
A rehearsal is only useful if it is honest. A demo with fake screens teaches you the demo. A real Test mode submits to a real sandbox: the same form, the same validations, the same feedback, with exactly one difference, which is that nothing that comes back is legally binding.
- Same form. The muscle memory you build is the muscle memory you will use.
- Same validations. The mistakes the sandbox catches are the same mistakes Live would have caught, discovered at zero cost.
- Same feedback. Row errors, statuses, certificates: the full loop, rehearsed end to end.
The switch should feel like a switch
The other half of a trustworthy rehearsal is a deliberate exit. Going live should never be something that happens by accident or by default. It should be an explicit choice with a confirmation in front of it, and the warning behind that confirmation should be blunt. The one we show reads, word for word:
A sentence like that is not friction. It is the product taking your filings as seriously as you do.
The receipt that settles arguments
One more property completes the design: every certificate should permanently record which environment produced it. With that stamp in place, a rehearsal can never be mistaken for a legal filing, in either direction. Six months later, nobody has to remember. The record remembers.
How to use a rehearsal well
- New to filing? Run your first certificate end to end in Test. Read everything that comes back before you consider Live.
- New workflow? Rehearse a small bulk file before the real batch. Twenty minutes of practice removes the ceremony from the real pass.
- New team member? Their first week happens in Test. Nothing they touch is binding, so nothing they touch is frightening.
- Then switch, deliberately, once, and file for real with the exact motions you practised.
The bottom line
Filings are asymmetric, so preparation should be too: generous where mistakes are free, deliberate where they are not. Practise on a real form before you file for real. Nothing is legally binding until you say so. When you are ready for the real pass, the eBRC playbook and the bulk workflow are the next reads.
Test mode is open to everyone: create a free account and rehearse today; nothing becomes legally binding until you switch to Live.
Frequently asked questions
Is a Test mode eBRC a real certificate?
No. A Test filing goes to a DGFT sandbox and is never legally binding. It exercises the same form, the same validations, and the same feedback as Live, so what you learn transfers exactly, without creating a real certificate.
Can a Test filing be mistaken for a real one later?
No. Every certificate permanently records the environment that produced it, so a rehearsal can never be confused with a legal filing, in either direction.
What happens when I switch to Live?
In Live mode, every eBRC you generate is submitted to DGFT as a real, legally binding certificate. Switching is an explicit choice with a confirmation in front of it, so it never happens by accident.
