Document guide
Judicial order
Identify what each judicial order decides and which case it belongs to. Turn batches of decisions into traceable events within the case file.
Explore fields and examples ↓The information your team needs.
Subject of the order and case references. 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 references. | Enforcement 42/2026 |
| Court | Issuing court and location. | First Instance · Madrid |
| Decision date | Order date, separate from notification. | 24 Sep 2026 |
| Parties | Identities and procedural roles. | Enforcing party A · debtor B |
| Ruling | Content of the operative part. | Enforcement authorised |
| Amounts and actions | Amounts and actions stated in the order. | Principal: €3,000.00 |
Connect the data. Find what needs attention.
Compare case number and parties with the linked file.
Link the decision to available earlier applications and later notifications.
Classification uses the actual ruling, not just the “order” title.
Information ready for your workflow.
A case event linked to the decision. 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 →