Flow 1

Risk Report -> Editor -> AI Re-check

Upload a document, let BrieflyGo explain risks in plain English, open the same document in the editor, apply fixes, then ask AI to check the edited version.

Routes

Buttons

Screenshots

Watch-outs

Routes

/scan/report/[id]/editor-soft

ELI10

Upload a document, let BrieflyGo explain risks in plain English, open the same document in the editor, apply fixes, then ask AI to check the edited version.

Who: anyone reviewing a lease, contract, NDA, form, or PDF before signing.

What: risk scan, plain-English summary, issue list, clause locate, fix, and re-check.

When: before sending or signing.

Where: scan page, risk report, and Soft Editor.

Why: the AI must judge the latest edited document, not the old upload.

Flow graph

Screens and paths in this flow

Each step connects to its screen manual. Follow the nodes left-to-right to trace the document journey.

5nodes

Step 1ScanUpload document; AI extracts text and flags risk clauses.

Step 2Risk ReportPlain-English risk summary, issue list, and clause locator.

Risk Report -> Editor -> AI Re-check3 routes · 6 actions

Scan→Risk Report→Editor

Screen manualScan screenDetailed breakdown of every action on this screen.Screen manualRisk Report screenDetailed breakdown of every action on this screen.Screen manualSoft Editor screenDetailed breakdown of every action on this screen.

Important buttons

Upload PDF Open in Editor Show / Locate Fix Re-check Download TXT

Watch-outs

Locate must scroll to the exact clause, not just the page.

Re-check must include editor overlays, inserted text, redlines, and fillable fields.

If the original file is missing, the editor should show a recoverable state, not a dead end.

Risk Report -> Editor -> AI Re-check

Screens and paths in this flow

Never sign without understanding every clause.