JusAI User guide

END-USER GUIDE

How to use the workspace without overthinking it.

The product is meant to feel simple: choose the right assistant, attach the right material, ask one concrete question, and trust only what is cited.

Open the workspace

Your first 10 minutes

  1. Open the right assistant for the task.
  2. Upload or attach the source material.
  3. Use a starter prompt or ask a narrow question.
  4. Check every answer through its citations.
  5. Export the useful result to working papers.

Rule of thumb: if it is not cited, do not treat it as settled.

01

Start with the assistant, not the prompt.

The fastest way to get a useful result is to choose the assistant that already matches the workflow. Each one carries the right method, guardrails, and starter prompts.

Use legal assistants for

  • Contract review and clause extraction
  • Memo drafting with cited source material
  • Board and meeting minute review

Use audit assistants for

  • Journal and variance analysis
  • Interview walkthroughs and control mapping
  • Management statement reconciliation

Good first move

Pick the assistant first, then tap a starter message before free-typing.

02

Attach the exact source material you want the answer grounded in.

The system works best when the relevant contract, board minutes, journal export, statement package, or transcript is attached directly in the session.

For documents

Upload PDFs, DOCX files, and text-based material before asking extraction or review questions.

For spreadsheets

Upload the original XLSX or CSV file so the assistant can cite sheets, rows, and ranges properly.

For remote files

Use approved SharePoint or OneDrive attachments when the firm has that integration enabled.

What to avoid

Do not paste a summary of a source when the original file is available. The platform is strongest when it can quote the source directly.

03

Read the citations before you trust the answer.

The platform is designed for source-linked output. Treat it like an evidence assistant, not an oracle.

Green flag

The answer cites the page, clause, sheet, row, or transcript timestamp that supports the claim.

Yellow flag

The answer says "not supported" or "not belegbar." That is usually the correct behavior.

Red flag

The answer sounds precise but does not show evidence. Ask it to restate only what can be cited.

Useful follow-up

"Restate this as a table with one citation per row, and mark anything unclear as not belegbar."

04

Use the audit pack in repeatable patterns.

The audit assistants are designed to remove formatting and method friction. Keep the workflow narrow and evidence-led.

Contract extraction

Best for lease review, obligation capture, key dates, index clauses, and missing-field detection.

Prompt example

"Extract tenant, landlord, rent, term, notice period, and index clause from the attached lease. Use a table and cite each field."

Protocol or board-minute review

Best for checking whether risk, compliance, going-concern, or key contracts were actually discussed.

Prompt example

"Create a topic coverage matrix for risk, going-concern, compliance, and material decisions across the attached minutes."

Journal analysis

Best for manual versus automatic postings, weekend postings, round amounts, user patterns, and period-end flags.

Prompt example

"Analyze the attached BMD journal and list manual postings, weekend bookings, round amounts, and any after-hours entries with row citations."

Variance and anomaly review

Best for year-over-year differences, material movements, sign flips, and audit follow-up questions.

Prompt example

"Explain the material year-over-year deviations in this multi-year export and highlight sign-flip anomalies with supporting figures."

05

For interviews and walkthroughs, work from the transcript.

Record or upload the audio, let the system create the transcript, then use the transcript-oriented assistants for structure and evidence.

Step 1

Capture or upload the interview audio in the approved workflow.

Step 2

Wait for the transcript attachment to appear before asking process or control questions.

Step 3

Use assistants like "Prozessaufnahme" or "Pruefungseinstieg - Interne Kontrollen (IKS)" to structure the content.

Important

For audit work, retain the transcript if it needs to support the file. Treat the generated process summary as a draft, not as a replacement for professional judgment.

06

Export when the output becomes working product.

The best time to export is when the answer has become structured enough to reuse: a table, issue list, coverage matrix, or journal summary.

Export to Word

For client-facing drafts, review notes, and interview summaries.

Export to Excel

For journal exceptions, variance tables, and structured field reviews.

Export to PDF

For fixed evidence packs and working-paper snapshots.

07

Prompt patterns that work well.

Keep prompts concrete. Ask for one output shape. Tell the assistant what evidence standard to follow.

Good

"List the deviations from the standard agreement in a table with one citation from each document."

Good

"Analyze only the attached journal and show me manual postings on weekends or after 18:00."

Good

"Summarize this interview as process steps, roles, controls, and open risks, with transcript timestamps."

08

Common mistakes to avoid.

Most weak results come from weak scope, not from weak models.

Do

  • Use the assistant that fits the task.
  • Attach the exact source file.
  • Ask for a table, matrix, or list when possible.
  • Check the citations before forwarding.

Do not

  • Ask broad questions across missing source material.
  • Rely on unsupported narrative summaries.
  • Treat draft output as final professional advice.
  • Ignore a "not belegbar" warning just because the answer sounds plausible.