Case files and portal.just.ro

A case file (dosar) is the litigation record Lex keeps for a client: court, section, panel, object, parties, your procedural capacity, the procedural stage, and the hearings. In an environment with a healthy configured connector, a linked file can be refreshed from portal.just.ro and its detected changes recorded.

You will find case files in the sidebar under Clients → Litigation, which holds two screens: Case files (the list of matters) and Hearing list (all upcoming terms across matters).

Create a case file and link it to the portal

Open Litigation → Case files → New Matter, or New Matter from a client’s page to have the client pre-selected.

Choose the Client.
Type the Număr dosar — the court case number.
Choose Search portal.just.ro underneath it. Three characters is the minimum.
Lex shows what the portal returned:
- one match — Case found on portal.just.ro;
- several — Multiple matches — select the correct case, so you can pick the right court;
- nothing, or Portal unavailable. Try again later.
Choose Use this data. Lex fills in Instanță, Secție, Complet, Obiect, Părți, Calitate procesuală, Stadiu procesual and Practică from the portal record, and shows a Portal data preview with the hearings (termene) and solutions it found.
Set the rest: Responsabil (defaults to you), Echipă, Status and Prioritate.
Choose Create Matter.

Two fields are easy to confuse, and the form says so inline:

Calitate procesuală is your client’s role in the case — Reclamant, Inculpat and so on. Lex infers it by matching the client’s name against the portal’s list of parties.
Stadiu procesual is the procedural stage — Fond, Cameră preliminară, and similar. It comes from the portal.

Practică follows the portal’s own case categories: Civil, Penal, Comercial, Contencios administrativ, Fiscal, Muncă, Insolvență, Familie. Categories that arrive from the portal outside that list are kept and appear in the list filter.

A case number can only exist once per firm, so two people cannot end up tracking the same dosar twice.

If the first sync fails

Lex attempts to sync the file when you create it in a provisioned portal environment. If that fails — the portal is unreachable, or the number matched several cases and none could be chosen — treat the file as unlinked and use Re-sync from portal only after confirming the number.

This matters more than it looks: a case file that never linked successfully has no portal reference, and the morning watch skips it. Its hearings will never update on their own. Lex guards against that in two ways:

The Case files list carries a Not portal-linked counter and marks the affected rows, with the explanation “hearing dates will not update automatically”.
Notification of an unlinked active file is preview behavior. The visible Not portal-linked status is the current reliable signal.

Status and what gets watched

Status	Meaning	Watched each morning?
Activ	Live, tracked in-house	Yes, when portal-linked
Monitorizat extern	Someone else — co-counsel, for instance — handles the portal side	Yes, when portal-linked; no nudge when it is not
Suspendat	Suspended	No
Închis	Closed	No

Because Monitorizat extern means “tracked elsewhere”, Lex does not nag you about a missing portal link on those files.

What scheduled refresh is designed to import

When scheduled refresh is enabled, the connector is healthy and the file is portal-linked, Lex can compare the latest portal record with its stored copy and record a change as one of:

Termen nou — a new hearing.
Termen modificat — a hearing whose date, time, panel, document or summary moved.
Soluție nouă — a solution recorded on a hearing.
Schimbare status — the procedural stage changed.
Actualizare date portal — the portal’s own last-modified timestamp moved.

Detected changes can be added to Portal change history on the matter page. Recipient notification and duplicate-delivery behavior are preview capabilities; do not rely on them until the firm’s environment has passed the delivery proof.

In a proved environment, new and changed hearings can also become entries on the calendar. Verify the imported term against the official portal before acting on it.

Re-syncing by hand

Re-sync from portal requests a current fetch. Its result depends on portal availability and the configured connector. Confirm the displayed sync status and verify the official record; do not infer notification delivery from a successful fetch.

The matter page shows Portal sync status and when the file was last synced.

Reading a case file

The matter page is organised as:

Object and Parties as they come from the portal.
Hearings (termene) — for each: the date, the estimated time, the panel, the solution and its summary, and the document type, number and date.
Portal change history — the audit trail described above.
Court details — client, court, section, panel, procedural stage, procedural capacity, and the portal’s last-modified time.
Ownership — responsabil, practice, priority and team.
View in portal — opens the search page of that specific court on portal.just.ro. Paste the case number, which is on the page in front of you, to reach the official record.
A Portal-linked or External monitoring marker at the top.

Working across all your files

Litigation → Case files gives you counters for total, active, suspended, closed, externally monitored and not-portal-linked, status tabs, and filters by client, responsabil and practică, plus a search across case number, court, object and client name.

Litigation → Hearing list is the cross-matter view of terms: date, estimated time, case file, court and responsible lawyer, filtered by client or responsible lawyer, searchable by case number, court, client or panel, and sortable by date or case number.

What Lex does and does not claim about the portal

Portal availability is outside anyone’s control. When the portal cannot be reached, treat the stored copy as stale and verify on the portal. Retry behavior depends on the environment’s scheduled connector configuration.

Terms and procedural deadlines, including the portal-versus-procedural confirmation step: Deadlines and calendar.
Asking the assistant what changed on your files, in plain language: Klu for legal work.
The court-data connectors and their sync schedule: Legislation and case-law research.