LexNET notifications: how not to miss a deadline

Almost every deadline a firm misses is missed for reasons that have nothing to do with knowing the law. It is missed because the notification arrived on a Friday, whoever was on duty opened it, and by Monday nobody remembered it existed. This guide is about the circuit: what LexNET actually does, when a deadline starts running, and how to organise a firm so the response does not depend on somebody remembering.

This is not a guide on how to log into LexNET. It is a guide on what to do with what is inside it.

What LexNET is, and what it is not

LexNET is the Spanish Ministry of Justice system through which professionals — lawyers, procuradores, graduados sociales — receive notifications from the courts and file written submissions. Its use is compulsory for communication with the administration of justice under article 273 of the Civil Procedure Act and Law 18/2011.

It is worth being clear about what it is not, because that is where most of the trouble comes from:

• It is not a matter-management system. LexNET delivers an act of communication and its attachments. It does not know which of your matters it belongs to, who runs that matter, or what needs to happen next.
• It does not calculate deadlines. It gives you an access date. The computation is yours.
• It does not chase anybody. There is no reminder, no escalation, no “this has been sitting unopened for three days”.
• It is not universal. Several autonomous communities with devolved competences run their own systems — Avantius in Aragón, Navarra, Cantabria and La Rioja; eJusticia.cat in Catalonia; among others. If you litigate in those territories, LexNET does not cover everything.

Put differently: LexNET solves transport. Everything else — classifying, assigning, computing, reminding, responding — is still the firm’s work.

When the clock starts

This is the part that costs the most, and the part most often flattened in corridor conversation.

The general rule is that the act of communication is deemed effected the day after the date of access to the system, or the day after it is deemed effected if three working days pass without access. In other words: you do not need to open the notification for the deadline to run. Ignoring it does not stop it.

On top of that starting point, the ordinary computation rules apply:

• Procedural deadlines are counted in working days. Saturdays, Sundays and public holidays are excluded, as are 24 and 31 December.
• August is non-working for procedural purposes as a general rule (art. 183 LOPJ), with the familiar exceptions: urgent steps, criminal matters, and certain areas where the law or the court declares it working.
• Public holidays come in three layers: national, regional and local. A deadline before a court in Marbella does not count the same as one before a court in Bilbao, because local holidays differ. A calendar that only knows national holidays will compute wrongly several times a year.
• The final day runs to 15:00 on the following working day under article 135.5 LEC — the day of grace, which exists but should never be planned for as though it were an extra day.

A system that only works if somebody remembers is not a system. It is a habit that has been lucky.

The practical consequence: the deadline starts running on its own, with nobody’s involvement. A system that depends on someone opening an email and writing a date down by hand has a single human point of failure in the worst possible place.

The four failures that keep recurring

Having looked at a fair number of firm circuits, the same four problems come up again and again.

The notification with no owner. It arrives, somebody sees it, nobody takes it. In small firms this resolves itself through physical proximity; once the team passes five people or works across locations, it stops working. Every notification needs a named owner from the first minute, not a “we’ll look at it”.

The deadline that lives in two places. The date is in the head of the lawyer running the matter and, with luck, in their personal calendar. It is nowhere the partner, the colleague covering August or the procurador can see it. If that person falls ill, the deadline disappears with them.

The document left in the inbox. The notification is read, action is taken, and the PDF never reaches the matter. Months later, preparing the appeal, nobody can find the acknowledgement. The work was done properly and the trail was lost.

The local holiday nobody checked. The computation was done against the national calendar. The court sits in a town whose patron-saint holiday fell in the middle. The real deadline was a day shorter.

How to build the circuit

A circuit that works has five steps and none of them depends on anybody’s memory.

1. Receipt with controlled acknowledgement. Somebody — a person or a system — checks LexNET every working day, without exception. If that depends on the account holder being in the office, it is not a circuit; it is a habit.

2. Classification to the matter. Every notification is linked to its matter by proceeding number at the moment of receipt, not “when there’s a minute”. A notification without a matter is a notification already being lost.

3. Named assignment. One owner, by name, and a second pair of eyes where the deadline is peremptory. The useful rule is that no critical deadline should have a single owner over the holidays.

4. Computation written down, not remembered. The deadline is calculated against the right calendar — national, regional and local to the court — and recorded in the firm’s shared diary. With staged reminders: one on receipt, one at the halfway point, one the day before. A single reminder the day before is not a reminder; it is a fright.

5. Filing with the rest of the matter. The notification PDF, the acknowledgement and the response all live in the matter, not in a downloads folder.

None of this requires software. A three-person firm can sustain it with a shared spreadsheet and discipline. What happens is that discipline is expensive, and it degrades precisely when the workload is heaviest — which is when it matters most.

What Mandato automates, and what it does not

Mandato connects to LexNET to close steps 1 to 5 without manual transcription. The notification arrives, is assigned to the matter by proceeding number, the deadline is calculated over working days against the relevant court’s calendar, and it appears in the firm’s diary with an owner and reminders. The document is filed in the matter from the first moment, and submissions are filed from the matter itself.

What deserves saying just as plainly:

• The regional systems are not covered today. Avantius and eJusticia.cat are on the roadmap. If your practice lives in Aragón, Navarra or Catalonia, LexNET does not resolve the whole circuit for you, and no supplier should suggest otherwise.
• The computation is an aid, not a ruling. The procedural calendar automates the ordinary case. The specialities — substantive time limits, suspensions, terms the law counts differently — remain the lawyer’s judgement. The system saves you the arithmetic and the local holidays; it does not replace your judgement.
• Responsibility cannot be outsourced. No tool turns a missed deadline into the supplier’s problem.

The least this should leave you with

If this guide is good for one thing, let it be this question: if tomorrow the lawyer running your most urgent matter does not come to work, does anybody else know which deadline falls, and when?

If the answer is yes, and it is written down somewhere shared, your circuit works regardless of which tool you use. If the answer is no, that is the problem to solve first — before changing software, and more urgently than anything else on this list.