L3Law firmsContract and deadline register
Contract deadline register: tacit renewals, notices, policies and DURC
Reads contracts, policies, permits and certificates and computes every deadline: tacit renewals, notices, policies, DURC.
The problem
A tacitly renewing contract must be cancelled by a date nobody wrote down; a policy expires in the middle of a job. The dates sit in the clauses of dozens of documents, in different formats.
Who it is for, and when
- Who it is for
- The law firm that keeps its clients' contracts, and the legal or admin office of a 20–200 person company with subcontracts, rentals, software and insurance policies.
- When
- Once a month, or whenever a new contract comes in: before a cancellation window closes without anyone noticing.
What you give it, what you get
You give it
The folder of contracts, policies, permits and DURC — PDF, Word or scans — or the register exported as CSV.
You get
On top, what has expired and which notices are due; the register with every date computed in code and the rule beside it, the .ics calendar to import and the termination letter in Word to approve.
How it works, in three steps
- Upload the folder or the contracts export
- Read what has expired and which notices are due on top
- Import the calendar and approve the termination letters
On its own, in a flow. Connect it to a webhook: the folder arrives, you get the register and the calendar; if something has expired or a notice must go out within 60 days, it asks for your OK first and then sends you the letters to sign.
The rules it applies
In the agent's own words: what it checks and what it never does.
- Tacit renewal: the notice deadline and the renewal it stops
- Dates computed by code, rule cited, “to confirm” if unsure
- Calendar (.ics) and a notice draft, never sent by the agent
- Read-and-recommend only. The agent never moves money.
A real example
A case from the demo catalogue, with anonymised documents.
The site folder: the expired policy and the subcontract that renews
Five documents scanned one after another: the subcontract with its art. 9 “tacit renewal unless notice is given 60 days ahead”, an invoice at 30 days, the liability policy stamped “expired — renewal not received”, the public-land permit and the accountant's notice with the tax deadlines. On the first of April the policy has been expired for seventeen days.
The recorded result
10 scadenze · 1 scaduta: polizza RCP-2025-118402 Assicurazioni Emiliane S.p.A. scaduta da 17 giorni, tolleranza art. 1901 c.c. finita il 30/03/2026 — sei scoperto · 1 entro 15 giorni (Pagamento fattura 2026/FT-0184 Rossi Componenti Industriali S.r.l., 11.143,48 €) · 4 entro 60 giorni · il subappalto SUB-2025-07 Bianchi Costruzioni S.r.l. si rinnova per 12 mesi il 30/09/2026 se la disdetta non arriva entro il 31/07/2026
real time 1 min 31 s18 credits
Frequently asked questions
How does it handle a tacitly renewing contract?
With two rows: the last day to give notice and the renewal it avoids. Dates are worked out by code with the rule cited and «to confirm» where needed; the .ics calendar and the draft notice are never sent by the agent.
What does it cost, and how long does it take?
Usually 13–27 credits a folder (≈ €0.54–1.11) and 1–3 minutes. It depends on the folder: each extra document is one more reading; a CSV export costs less. The recorded example cost 18 credits in about 2 minutes.
Can it run on its own, in a flow?
Connect it to a webhook: the folder arrives, you get the register and the calendar; if something has expired or a notice must go out within 60 days, it asks for your OK first and then sends you the letters to sign.
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.
Related agents
- L1Court deadlines from acts and PECReads 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.
- 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.
- 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.