Workflow (from case to deliverable)
This is the recommended route if you want to use the Prudai Platform (LEO, VERA, or ZIA) as a real working environment rather than a demo chat.
Step 0 — Choose product and workspace
Section titled “Step 0 — Choose product and workspace”Two choices directly affect answer quality:
| Choice | Use it when |
|---|---|
| LEO | you need broad legal sources or research jobs |
| VERA | the task is about Omgevingswet, IPLO, or official publications |
| ZIA | the work should stay centered on internal knowledge and project documents |
| Personal context | for your own files outside a matter |
| Project context | for matter work, collaboration, tasks, and project chat |
Step 1 — Build the document layer first
Section titled “Step 1 — Build the document layer first”- Create a project.
- Upload only the core files.
- Wait for Processed status.
- Add metadata where it helps:
- title,
- tags,
- dates,
- comments.
Why this matters:
- chat, timeline, tasks, and exports all improve when the document layer is clean;
- audio such as
.mp3is only useful after transcription/processing finishes; - ZIP contents only become available after archive extraction finishes.
Step 2 — Reduce the knowledge set to what you need
Section titled “Step 2 — Reduce the knowledge set to what you need”Do not turn everything on by default.
Practical per-product guidance:
- LEO: enable only the legal source families that matter for this case.
- VERA: keep Omgevingswet/IPLO/official publications and, if applicable, BIM tools (IFC/DWG) on, and disable irrelevant extras.
- ZIA: work mainly from project, organizational, and personal documents; there are no public legal source families. The Nedap ONS connector is available here for care-sector matters.
You fill in your Vakgebied (legal areas, role, industries) once on first login via the stepper. That profile influences which sources and suggestions surface first.
More: Knowledge.
Step 3 — Use chat as the control surface
Section titled “Step 3 — Use chat as the control surface”Strong prompts always include:
- goal,
- audience,
- desired format,
- constraints.
Use context deliberately:
@documentfor specific files,#taskin project chat,- attachments only after they finish processing.
Useful behavior:
- outside a project, chat uploads can be stored in personal Files, an existing project, or a new project;
- inline workspaces and slash commands keep you in the same conversation flow;
- DeepThink is there for heavier, more careful work;
- you can branch a conversation, regenerate a reply, or stop a generation (button or Escape) without leaving the project;
- voice in/out is available in every chat; the microphone stops automatically after a few seconds of silence.
More: Chat.
Step 4 — Turn findings into actions
Section titled “Step 4 — Turn findings into actions”Use Tasks (formerly “kanban”) for:
- missing facts,
- research points,
- deadlines,
- review work.
Use Notifications for:
- collaboration actions,
- document processing outcomes,
- research/job status,
- second-opinion flows.
More: Tasks and Notifications.
Step 5 — Finish the deliverables
Section titled “Step 5 — Finish the deliverables”Use:
- Export for Word/PDF,
- Translate for supported file types,
- Word add-in if the output should land in Word directly.
More: Export, Translate, and Word add-in.
Step 6 — Use research only where the product supports it
Section titled “Step 6 — Use research only where the product supports it”- LEO: use research jobs for deep, multi-step research.
- VERA and ZIA: work directly through chat, project documents, and the available knowledge tools.
More: Research jobs.