L1Law firmsCourt deadlines from acts and PEC
Work out court deadlines from the served act or the PEC
Reads the notified act or the PEC as it arrived and computes every procedural deadline by written rules: appeal, long term, opposition, statement of defence, the 171-ter briefs.
The problem
A judgment served by PEC on 10 July: the appeal falls due on 9 September, not 9 August, because August is suspended. A wrong deadline cannot be recovered, and every date has to be worked out and checked.
Who it is for, and when
- Who it is for
- The lawyer of a one-to-five-lawyer studio, the trainee who opens the PEC and the assistant who keeps the diary; the in-house legal office that receives acts for the group's companies.
- When
- Every time a notification arrives: the judgment a colleague serves by PEC, the payment order the client forwards, the writ the bailiff delivers, the court office's notice — several times a week, and in August too.
What you give it, what you get
You give it
The PEC saved as .eml, exactly as it arrived — or the act as PDF, signed .p7m or scanned with its relata — and the matter (ordinary civil, labour, interim…), which decides the August suspension.
You get
The nearest deadline first, with its rule; every deadline with its step-by-step computation, marked to be confirmed; the warnings (a PEC after 9 pm, the patron saint's day, a matter to check); the .ics calendar and the e-mail ready for the office.
How it works, in three steps
- Upload the PEC or the act and pick the matter
- Check each deadline against its computation and confirm it
- Import the calendar and forward the e-mail to the office
On its own, in a flow. Connect it to the webhook or the folder where the PECs are saved: every notification is read, the deadlines go to the lawyer for approval and, once confirmed, the calendar and the e-mail go to the office.
The rules it applies
In the agent's own words: what it checks and what it never does.
- Appeal by 9 September, not 9 August: August suspended
- Every date with its rule and computation, to confirm
- The PEC read as it arrived: relata, .p7m, delivery time
- Read-and-recommend only. The agent never moves money.
A real example
A case from the demo catalogue, with anonymised documents.
The judgment served by PEC on 10 July: appeal by 9 September, not 9 August
On Friday 10 July at 11:42 the notification from colleague Galletti reaches the PEC box of Laura Ferri, Acme Impianti's lawyer: «Notificazione ai sensi della legge n. 53 del 1994», with judgment no. 1234/2026 of the Tribunale di Bologna — Acme ordered to pay €38,460 for the defects of a residential complex's electrical system — and the digitally signed relata (.p7m). The trainee saves the PEC as it is and uploads it. Thirty days from today would be 9 August: but August does not count.
The recorded result
Sentenza n. 1234/2026 Trib. BOLOGNA notificata il 10/07/2026 → appello entro mercoledì 9 settembre 2026 (30 gg art. 325, sospesi 1–31 agosto) · termine lungo art. 327: lunedì 1° febbraio 2027 — da confermare
real time 1 min 50 s28 credits
Frequently asked questions
Can I rely on the date it works out?
Every deadline comes with the rule and the calculation, to confirm: the lawyer checks and confirms before anything reaches the calendar. The PEC is read as it is — proof of service, .p7m, delivery time.
What does it cost, and how long does it take?
Usually 21–43 credits a notification (≈ €0.87–1.77) and 1–3 minutes. It depends on the act: more pages cost more; computing the terms is code and costs nothing. The recorded example cost 28 credits in about 2 minutes.
Can it run on its own, in a flow?
Connect it to the webhook or the folder where the PECs are saved: every notification is read, the deadlines go to the lawyer for approval and, once confirmed, the calendar and the e-mail go to the office.
Who checks what the agent did?
You do — and it takes a minute, not an afternoon. Every run is a trace: the live timeline, each tool call, each document read, the cost per step, the confidence and sources. Actions that leave the building wait for your approval. The platform never sends, never touches a live store, never moves money.
Where does my data live, and how do you handle GDPR?
Your data is stored in the EU, on one server in Germany. The EU/US data-region setting limits which models an agent can be saved with, not where your data is stored. A no-retention mode and a local runner on your own machine are available. Your plan sets how many days your data is kept — you can change it — and when they run out it is deleted automatically. You download each run's results and delete files, agents and connections in the console; an owner deletes the whole workspace and each person their own account from Settings. The “Your data” page names the services that handle your data.
Guides on this job
Related agents
- L2Contract review against your playbookReads the counterparty's contract, even 60 pages long, and checks it clause by clause against your playbook: red, amber or green by written rules — the double signature of art. 1341, art. 1229, the 60 days of D.Lgs. 231/2002, the art. 28 GDPR processor agreement — with the change to ask for.
- L3Contract and deadline registerReads contracts, policies, permits and certificates and computes every deadline: tacit renewals, notices, policies, DURC.
- L4Debt recovery dossierBuilds the dossier the lawyer files for a payment order: each invoice against its signed delivery note and the bank, the interest to the day, the evidence the court asks for and what is missing, the court, the formal notice as a PEC draft.
Try it on your own documents
The demo shows the recorded cases without an account; with your own workspace you run it on your files.