Translating Documents
The Translation home screen is where a run is assembled. It has no composer and nothing to type: you choose documents, set a target language and a page range on each one, and confirm an estimate. This page covers every control on that screen, region by region, and the modal that ends it.
The setup screen
The step trail, the file band, the language control and the run button are all on this one screen. The hero sits above them.
The hero
The heading reads "What would you like to translate today?" with the subtitle "100+ languages, with the original formatting kept intact." Three controls sit on the same row.
| Control | Where | What it does |
|---|---|---|
| Watch demo | Top right, beside the subtitle | Opens a player showing the whole Translation walkthrough as a loop |
| Take tour | Between the other two | Highlights the screen's parts in place, starting at the file band |
| View guide | End of the row | Opens this documentation in a new tab |
Take tour appears only while the product tour is available to you. The other two are always there.
The step trail
Directly under the hero is a three-step trail. It is a read-only indicator, not a set of buttons, and Translation's is different from every other feature's because a translation needs no brief and no authored items.
| Step | Label before files are chosen | Label after |
|---|---|---|
| 1 | Pick documents, marked as the current step | Documents added, marked as done |
| 2 | Choose a language, upcoming | Choose a language, now the current step |
| 3 | Review and run, upcoming | Review and run, upcoming |
Step one is the current step from the first frame, with no "Optional" tag, because documents are required.
Flush right on the same row is a jurisdiction chip: a flag and a country name. It echoes the setting in the top bar and cannot be changed here. A translation run is not scoped to a jurisdiction, but that setting decides which languages are promoted to the top of the language lists below.
The file band
The file band is the only place this screen asks for documents. It never opens a picker of its own: both of its verbs reveal the shared Files panel, which is where documents are actually chosen. You cannot browse or search your library from the Translation page.
Before you choose anything
The band is a dashed box reading "Choose the documents to translate", with the note "You pick the target language next."
| Control | Where | What it does |
|---|---|---|
| Choose files | Left button in the band | Opens the Files panel on its Files tab, so you can tick documents already in the project |
| Upload | Right button in the band | Opens the Files panel with its upload surface ready for new documents |
Once files are in
The band becomes solid and summarises the run: the number of files, and the total pages once every file has reported a page count.
| Control | Where | What it does |
|---|---|---|
| Add more | Left button in the band | Reopens the Files panel so you can tick more documents |
| Clear all | Right button in the band | Empties the run and clears the file selection behind it |
| Remove on a chip | The small cross on each file chip | Drops that one file from the run |
| +2 more | Below the chips | Reopens the Files panel when more files are selected than the band paints chips for |
The band paints six chips at most. The selection itself is never trimmed: the summary line above keeps counting every file, and Clear all still clears all of them.
The file cap
Translation accepts up to 10 files in a single run. That is a lower cap than Timeline, Document Review, Review Matrix, and Case Strategy, which each take 50.
Because the allowance is small, the band starts warning early. From the eighth file onward it shows a readout beside the page total, "8 of 10", so you can see the ceiling approaching. Go past it and the readout changes to name the problem and the fix, for example "11 selected · limit 10. Remove 1 to continue.", and the run cannot be started until you do.
The configuration card
The configuration card appears as soon as one file is selected, below the band. Its heading counts the documents in the run, and under it sits the instruction "Set a language and a page range on each. Change one at the top to apply to all."
The target-language control
| Control | Where | What it does |
|---|---|---|
| Target language | Top right of the card, beside the caption "apply to all" | Sets the target language on every file in the run at once |
This dropdown is a shortcut, not a batch setting. Picking a language here writes that language onto each file's own control. It shows a value only while every file agrees; set one file to something different and this box goes back to its placeholder, "Select a language", because there is no longer a single answer to show.
Both this control and the per-file one open the same list. It is searchable, with the placeholder "Search languages", and it is grouped: your jurisdiction's languages come first under their own heading, then a heading reading "All languages · 116" and the rest of the catalogue. In India the promoted block is the 19 scheduled languages that Judicio supports. Group headings are labels, not choices.
The per-file card
Each selected document gets its own card inside the configuration card.
| Control | Where | What it does |
|---|---|---|
| File name and source badge | Top of the file card | Shows the document and, in a blue badge, the source language Judicio detected. You never set the source language |
| Page count | Under the name | Reads "9 pages", or "Loading…" until the count arrives |
| Translate into | Middle of the file card | Sets the target language for this file alone |
| All pages | Under "Translate pages" | Translates the whole document. This is the default |
| Custom range | Beside it | Reveals the page-range picker for this file |
| Remove file | The cross on the right edge of the card | Drops this file from the run and deselects it |
Because each file carries its own Translate into value, one run can target several languages at once. Set two contracts to English and one to Hindi and all three are translated in the same run, each into the language on its own card. There is no need to split them into separate runs.
The page-range picker
Choosing Custom range on a file reveals a picker for that file. Everything in it describes the same range, so the slider, the boxes, and the summary can never disagree.
The page-range picker
The picker belongs to one file. A second file keeps its own range, and its own target language.
| Control | Where | What it does |
|---|---|---|
| Summary line | Top of the picker | Reads the current range and its size, for example "Pages 1–9 of 9 · 9 pages" |
| Range slider | Under the summary | Two handles set the first and last page. Shown only when the document has more than one page |
| Start page | Left number box | Sets the first page to translate |
| End page | Right number box | Sets the last page to translate |
| "max 88" | Right of the boxes | States the document's last page |
Selecting Custom range pre-fills the full document, so the first thing you see is a valid range you can narrow. Both edges are clamped between page one and the last page, and the start can never pass the end, so an impossible range cannot be built. While a document's page count is still loading, the picker shows "Loading page count…" and the run is blocked with a message naming the file rather than failing later.
The footer
| Control | Where | What it does |
|---|---|---|
| Selection summary | Left of the footer row | Reads the pages selected across the documents in the run, for example "24 pages selected across 3 documents" |
| Clear selection | Middle | Empties the run and clears the file selection behind it |
| Primary button | Right | Opens the confirmation modal |
The primary button names the page count, never the language. With 12 pages selected it reads "Translate 12 pages". Its number is the total after every page range has been applied, so narrowing a range changes the button.
Pressing it does not start anything. It fetches the credit estimate and opens the confirmation modal.
The Confirm translation modal
This modal is the last thing before a run starts, and the only place the cost is quoted.
| Region | What it shows |
|---|---|
| Title | Confirm translation |
| Subtitle | "Review the documents and credit estimate before starting." |
| Selected documents | One row per file, each with the page count the estimate returned |
| Target language | The language of the run. When files target different languages, every language in the run is listed here |
| Estimated time | How long the run should take, with the note "Runs in the background. You can continue working." |
| Estimated cost | The credits the run will consume, with your remaining balance beside it |
| Footer button | What it does |
|---|---|
| Cancel | Closes the modal and returns you to the setup card with the selection intact |
| Start translation | Starts the run |
There is no Deep Mode toggle in this modal, and no template card: Translation has neither.
Credits
If your balance will not cover the run, the modal replaces the cost row with "Insufficient credits to start this translation. Please upgrade your plan." and Start translation stays disabled. See Credits Explained.
What happens when the run starts
Files are grouped by target language and each group is sent as its own job, which is how a mixed-language run works. Every group is independent.
- Everything started. A "Translation started" message appears, the selection is cleared, and you land in the history view on In progress.
- Only part started. The message names the split, for example "Started 2 of 3 files", the files that did start leave your selection so a second press cannot submit them twice, and the ones that failed stay selected and ready to retry.
Recent activity
Below the configuration card, the home screen keeps a Recent activity strip: your five most recent translations, grouped under Today, Yesterday, and Earlier. Each row carries the document name, its page count, its status, and, while a run is live, a progress bar with the current stage. Click a row to open it. View all opens the full history.
If the strip cannot load it says "Couldn't load recent activity." and offers Try again, rather than implying you have no runs.
Next steps
- Reviewing Translations - the result screen, page navigation, search, and the source pane.
- Downloading Results - the export modal and Save to Judicio.
- FAQ - answers and troubleshooting.