Uploading a document before midnight is not enough if it is the wrong submission. For companies involved in several UPC cases, electronic filing needs a substantive verification step as well as a technical receipt. A 2026 procedural order illustrates why an incident must be classified correctly before selecting the remedy.
The decision of 10 March 2026
In Angelalign v Align Technology, UPC_CoA_37/2026, the standing judge refused discretionary review of a retrospective extension after the wrong reply had been filed. The order distinguished extensions for written submissions in pending proceedings under Rule 9.3(a) from re-establishment under Rule 320. It did not give parties permission to disregard deadlines: the court retained control of the procedural timetable.
Treat filing as a controlled handover
Our recommendation is to identify the proceeding, document type, version, signatory and attachments before upload. An electronic receipt should be reconciled with the actual submitted document. Save both the receipt and the final file in the matter record. Where the same parties litigate several patents, use the patent number and action reference prominently in internal approval messages. Party names alone may not distinguish the files reliably.
The internal task should end only when someone has checked the submitted package, not when the upload button has been pressed. A second check should be sufficiently independent to detect a wrong document rather than repeat the same assumption. Agree who monitors registry messages, including during absence or handover between offices. These measures reduce error without assuming that technology or a second person guarantees perfection.
Respond to an incident with facts
If an error is discovered, preserve the original record and tell the responsible legal team promptly. Establish what was intended, what was actually filed, when the mistake became known and which corrective steps are possible. Counsel should assess the relevant procedural route and any non-extendable period separately. A generic statement about human error is less useful than a short chronology supported by documents. Consider the other party’s opportunity to respond and the existing hearing schedule.
Four hypothetical practical examples
These examples illustrate internal controls and are not additional facts from the judgment.
1. Two disputes between the same companies
A team prepares replies in two patent cases with identical party names. Its final check compares the patent number, action reference and requested relief, revealing that the wrong document was selected. Correcting the package before submission prevents a technical upload success from concealing a substantive filing failure.
2. An annex replaced after approval
An engineer supplies a corrected test report shortly before filing. The team records the approved version and updates the exhibit index. After upload it verifies the report actually attached. This avoids assuming that an updated filename necessarily contains the approved measurements or that every system copied the latest version.
3. An error found the next morning
Counsel discovers that a signed reply relates to a parallel case. The original receipt and file are preserved, the correct document is identified and procedural advice is sought immediately. The team does not overwrite the local evidence or quietly substitute a document without addressing its procedural status.
4. A delayed response from an overseas office
The European filing team receives a late approval from colleagues abroad. Its checklist distinguishes internal approval times from the court deadline and records who is authorised to decide. This prevents a commercial escalation process from being mistaken for a procedural extension granted by the Court.
What businesses should implement
A useful filing protocol can be short: clear matter identification, final-content verification, receipt reconciliation and an incident escalation route. Test it on a real bundle rather than relying solely on a written policy. Management should also know who can authorise urgent instructions when the usual contact is unavailable. Procedural recovery remains case-specific; prevention should be the normal operating model.