Document guide
LexNet notification
Classify notifications and attachments received through LexNet or legal representatives. Identify the case, decision and data the team needs to record and handle each incoming communication.
Explore fields and examples ↓The information your team needs.
Case references, dates and documents in the communication. Each value retains its document reference so the team can return to the source during review.
Illustrative fields · Fictional data. Fields and output are configured for the supplied documents and agreed workflow.
| Field | What it contains | Example |
|---|---|---|
| Proceedings | Number, type and case references. | Ordinary proceedings 142/2026 |
| Court | Stated court, location and jurisdiction. | Court of First Instance · Madrid |
| Decision type | Order, judgment, decree, procedural notice or request. | Procedural direction |
| Parties and recipients | Identities and roles stated in the communication. | Party A · recipient: legal representative |
| Dates | Issue, dispatch and receipt dates, each with its role. | Received: 30 Sep 2026 |
| Required action and stated period | What is requested, from whom and the period stated. | Correction requested · 5 days stated |
Connect the data. Find what needs attention.
Associate the message, receipt and attachments with the case; flag uncertain references.
Distinguish a copy or receipt from a new decision to avoid duplicating events.
The period stated in the document is retained with its source. The team reviews deadline calculation and the legal response.
Information ready for your workflow.
A classified entry with case reference, event and data for review. Receive an Excel or CSV file for review, or structured data in the format agreed for your system.
Use it in these solutions
Try it with a batch of your documents. We agree the sample, fields and confidentiality before starting.
Discuss my batch →