A deadline-control policy becomes most important when something goes wrong. Companies and their UPC representatives need a record showing which deadline applied, how it was entered and checked, and what happened after an error was discovered. The practical objective is reliable prevention and a factual response, not confidence that a missed deadline will be excused.
The decision of 28 April 2026
In Optopol v Topcon, UPC_CoA_56/2026, the standing judge rejected discretionary review of a retrospective extension under Rule 9.3(a). Evidence about the existing control system and an individual recording error supported the assessment. The order also stressed prompt action when seeking retrospective extension. This was an assessment of the particular procedural order, not a general entitlement to forgiveness.
Audit the whole deadline chain
Our recommendation is to trace a sample deadline from the originating event through calculation, entry, verification and completion. Identify whether the trigger is service, a specific court direction or another procedural event. Record the document relied upon and the person who calculated the date. Different tasks arising from the same submission may need separate entries and responsible people. A shared calendar alone does not demonstrate that every legal consequence was identified.
The company should agree with external counsel who supplies technical material, who gives instructions and which internal milestones precede the court deadline. Internal dates must be realistic enough to allow review, translation and correction. A late engineering report can jeopardise preparation even when the formal deadline remains several days away. Escalation should begin when an internal milestone slips, rather than only when the court period has expired.
Preserve the incident record
After discovery, secure the original calendar entries, relevant instructions, confirmation messages and filing receipts. Record corrections transparently without overwriting the history. The procedural application should follow counsel’s assessment of the applicable route and the circumstances. Waiting for a complete internal investigation may itself create additional difficulty; essential facts can be identified while the broader review continues. Also assess the other party’s response time and whether the proposed correction would disrupt the timetable.
Four hypothetical practical examples
These examples are independent illustrations, not findings about the parties in Optopol.
1. A period entered from the wrong trigger
An assistant records a deadline from the date an email was read rather than the legally relevant event. A second reviewer checks the underlying notification and corrects the entry before expiry. The file retains the source document and the calculation, making the control understandable to someone outside the original team.
2. One pleading creates several tasks
A response requires work on infringement, a revocation counterclaim and proposed claim amendments. The team assigns a responsible lawyer and technical contact to each stream. Separate internal milestones reveal a missing validity contribution before the final document is assembled, rather than allowing one calendar entry to hide incomplete preparation.
3. Absence during a critical week
The usual in-house contact becomes unavailable while an expert report is being finalised. A named substitute can approve urgent instructions and access the necessary records. The external team does not have to guess whether silence means approval, and the escalation route is documented in advance.
4. Discovery after expiry
A discrepancy is found after a filing period has ended. Counsel receives the original records immediately and assesses the procedural options. The team documents when it learned of the problem and what it did next. It does not postpone action merely to produce a polished account of the incident.
Review without losing the litigation focus
An internal review should produce specific improvements: clearer triggers, independent calculation, reliable substitutes and completion checks. Preserve existing controls as evidence of what actually operated at the relevant time. A newly written policy is not proof of an earlier system. Keep business continuity and the substantive case moving while the procedural question is addressed; neither a pending application nor internal remediation changes the deadline automatically.