Your first project
The fastest way to understand Judicio is to run one thing all the way through. This is that run: a project, a document, and a review that comes back with findings you can trace to the page they came from.
It takes about ten minutes, most of which is Judicio reading. You need one document, ideally a contract of a few pages.
If your account still has Judicio's sample files, skip step 2. Open the Review a contract for risks chip on the home screen and press the button on its sample card, Review the sample. It stages the sample contract for you and lands you where step 4 begins.
Make a project
A project keeps one matter's files, runs and people together. Working outside one is possible, but a first run is easier to find again if it has a home.
On the home screen, press New project. The form has two fields, Project name and Description, both required. Name it after the matter, not after the exercise.
Press Create project. On an organisation plan the form has a second step for sharing it, so the button reads Save and continue and Create project comes after.
The new project becomes the one named in the project selector at the top left. Everything you do next is filed under it. See Creating projects.
Add your document
Press Upload files on the home screen. That opens the File Library ready to take documents; drag them in or pick them from your machine.
Judicio does not just store the file. It reads it, runs text recognition over anything scanned, and pulls out the parties, dates and amounts it can find. That takes a moment, and it has to finish before the document can be reviewed. The file shows its progress while it works.
Accepted formats, cloud imports and everything else about the library are in Uploading files.
Point Document Review at it
Go back to Home and press the Review a contract for risks chip.
The panel that opens says what it wants: a contract, PDF or DOCX, and that the review checks generate themselves from the document. Press Choose from library, tick the file you just uploaded, and confirm.
Your document now appears as a chip in the panel, and the buttons change. Press Start review.
This does not start anything yet. It carries your document into Document Review and lands you on its home, headed What would you like to review today?, with the file already selected.
Say what you want checked
Document Review does not have a fixed checklist. You describe what matters and it writes the checks.
Type into the composer under the file band. Its placeholder reads Describe the review checks you want. For a first run, plain language works: something like a request to flag unusual liability, indemnity and termination terms, and anything that looks one-sided.
Two chips sit on the composer rail. Deep Mode runs a more thorough pass and costs more. Leave it off for a first run. Settings holds the response language for this run.
Press Generate review checks.
Approve the checks, then run it
Judicio replaces the composer with the checks it wrote. Each is a title, a description, and a chip saying how strictly it should be treated. Untick anything you do not want, edit a row that is close but not right, and add one of your own if something is missing.
Press Start review. A confirmation opens before anything is spent: it lists your document and its page count, the checks you approved, how long the run should take, and what it will cost against your remaining balance. Nothing is charged until you confirm.
Press Start review again to begin.
Nothing is billed until you confirm
Every AI run in Judicio quotes its cost before it starts, and the quote is against your actual balance. Reading, filtering and exporting the results afterwards are free. See Credits explained.
Leave it running
Judicio moves you to its jobs view and puts your run on In progress, with a live progress cell and a stop control.
You do not have to watch. The banner under the table says so: the run continues in the background and you will be told when it is done. Go and do something else. The notification bell will light up. See Notifications.
Read what came back
Open the completed row.
Your document fills the middle of the screen, with the findings listed in a rail beside it. Each finding names the clause it was raised against and says why it matters, and every one of them can be opened at the exact passage in the document that produced it.
Check one. Open a finding, jump to the clause it points at, and read the clause yourself. That habit is the whole point of the product: an answer you cannot trace is an answer you cannot use.
Then work the finding: fix it with the AI, edit it yourself, accept it, or flag it for someone else. Resolving findings covers each.
Take it with you
Press Export in the header once you have reviewed at least one finding.
Judicio recommends one format based on what you actually did, and offers the rest below it. Pick one, name the file, and download it. Exporting results covers all four.
What you have now
- A project holding one matter, which you can share with a colleague.
- A document Judicio has read, indexed and can now answer questions about.
- A review whose every finding points at the passage that produced it.
- An export you can send to someone who has never heard of Judicio.
Where to go from here
You have run one tool. The other six take the same shape: pick documents, say what you want, confirm the estimate, read a cited result.
| If you want to | Read |
|---|---|
| Ask a legal question and get a cited answer | Research |
| Produce a document, then revise it with the AI | Drafting |
| Map the grounds for and against your side | Case Strategy |
| Ask the same questions of many documents at once | Review Matrix |
| Pull every date and deadline into one chronology | Timeline |
| Translate a document and keep its layout | Translation |
| Save this set of checks and reuse it | Templates |
| Bring a colleague into the matter | Collaboration |
Next steps
- Document Review, screen by screen - the same run, in full detail.
- The home screen - the seven chips and what each one opens.
- Credits explained - what that run cost, and why.