User Journey

Detailed journey with brief-backed rationale

Each stage maps user intent, product behavior, screen coverage, and the exact briefing text that supports the design decision.

Brief Flow Backbone

Directly quoted from the End-to-End Experience Flow.

01

Upload documents

"Upload documents"
02

Extract structured data

"Extract structured data"
03

Generate missing checklist

"Generate missing document checklist"
04

Complete checklist

"User completes checklist"
05

Verify with data sources

"System performs verification"
06

Generate legal opinion

"Legal opinion generated"
07

Optional lawyer validation

"Optional lawyer validation"

General User Journey

General User: 'I understand this property and what I should do next.'

10 stages

Stage 01

Choose role and enter the product

01-04, 30
"General Users: Buyers, sellers, investors seeking clarity, safety, and simple outputs."

§4 User Roles

User Goal

Understand that this product is for property decisions, not generic document storage.

User Action

Starts from the index/prototype, selects Buyer / Investor, and enters the dashboard.

System Behavior

Stores the selected persona locally, adjusts the bottom menu, and presents buyer-focused KPIs and actions.

Outcome

The user sees a simple buyer path: properties, documents, opinion, lawyers, and services.

Stage 02

Upload imperfect property documents

07
"Users can upload multiple documents. System auto-categorizes them into structured groups such as sale deeds, EC, RTC, and khata."

§6 Document Upload & Organization

User Goal

Add all available files without needing to know the exact document taxonomy.

User Action

Uses the drag-and-drop area or browse button, uploads multiple documents, and watches progress.

System Behavior

Shows upload states and starts grouping uploaded files into sale deed, EC, RTC, khata, and other categories.

Outcome

The user feels the system can handle messy real-world due diligence inputs.

Stage 03

Extract and organize document intelligence

08-09b
"It reads documents, validates them against government data, identifies risks, and produces a traceable legal opinion."

§2 Product Vision

User Goal

See what the platform understood from the uploaded files.

User Action

Reviews extracted fields, corrected categories, grouped folders, document metadata, and document detail.

System Behavior

Displays extracted structured fields, confidence/status indicators, and document organization by type or opinion section.

Outcome

Raw paperwork becomes navigable evidence for verification and legal opinion generation.

Stage 04

Resolve missing documents

10-12
"Each item explains why it is needed and the risk if missing."

§7 Missing Document Checklist

User Goal

Know exactly what is missing and why it matters before proceeding.

User Action

Reviews critical, high-priority, and recommended items, expands why/risk explanations, and requests help when needed.

System Behavior

Presents missing document rationale, risk if missing, source offices, portal links, pricing, and Realtee procurement.

Outcome

The buyer can complete the diligence packet without legal guesswork.

Stage 05

Select diligence depth

15
"Users can choose Light, Moderate, or Strong diligence levels, affecting depth of analysis."

§12 Diligence Depth Levels

User Goal

Control the depth, speed, and confidence level of due diligence.

User Action

Chooses Light, Moderate, or Strong diligence based on risk appetite and transaction urgency.

System Behavior

Frames the expected behavior: basic verification, full verification plus checklist, or deep legal/compliance/risk analysis.

Outcome

The user understands what level of checking they are buying into.

Stage 06

Verify claims against external records

13-14
"Verification Over Assumption - All outputs must be backed by verified data."

§3 Core Design Philosophy

User Goal

Move from document claims to verified facts.

User Action

Checks overall verification, opens agency-level detail, and compares document data with government records.

System Behavior

Shows BBMP, RTC, Sub-Registrar, and BDA/CDP verification status with discrepancy severity and source references.

Outcome

Trust comes from visible comparison, not a black-box score.

Stage 07

Understand risk and property intelligence

16-18
"Displays key metrics such as verification status, risk scores, zoning overlays, road widening, and water bodies."

§11 KPI & Intelligence Layer

User Goal

See whether zoning, compliance, title chain, disputes, or location factors threaten the deal.

User Action

Reviews KPI cards, risk meter, compliance list, overlay map, and chronological title chain.

System Behavior

Surfaces risk score, compliance indicators, CDP zoning, water bodies, buffer zones, road widening, gaps, disputes, and court references.

Outcome

The buyer sees risk as a decision-making layer, not buried legal detail.

Stage 08

Read the legal opinion

19-24
"Decision-Centric - Help users decide whether to proceed, renegotiate, or walk away."

§3 Core Design Philosophy

User Goal

Understand whether to proceed, renegotiate, or walk away.

User Action

Reads executive summary, title genesis, ownership timeline, legal risks, supporting documents, and final recommendation.

System Behavior

Structures the opinion into authoritative sections with status badges, recommendations, risks, and supporting document mapping.

Outcome

The buyer gets a clear decision and the reasons behind it.

Stage 09

Trace every important claim

20-25
"Every statement in the legal opinion must link back to supporting documents and verified data sources."

§10 Traceability

User Goal

Trust the opinion because each statement can be checked.

User Action

Taps source links from opinion sections and opens the supporting document and verified data point.

System Behavior

Shows statement, source document, highlighted clause, government record comparison, and chain of evidence.

Outcome

The buyer can audit the conclusion rather than simply accepting it.

Stage 10

Request expert validation or services

26-29
"Users can select from approved lawyers, view credibility indicators, and request validation of legal opinions."

§13 Lawyer Marketplace

User Goal

Bring in an approved expert when confidence or transaction stakes demand it.

User Action

Browses approved lawyers, opens a profile, requests legal opinion validation, and tracks services.

System Behavior

Shows credibility, experience, ratings, fees, service options, and procurement/validation tracking.

Outcome

The buyer can escalate from automated intelligence to human legal review.

Lawyer Journey

Lawyer: 'This mirrors my thinking and saves significant time.'

6 stages

Stage 01

Enter as a legal expert

02-04, 28, 30
"Lawyers & Legal Assistants: Experts requiring deep insights, verification logs, structured legal reasoning, and traceability."

§4 User Roles

User Goal

Start in a mode that respects expert workflows and higher information density.

User Action

Chooses Lawyer / Legal, signs in to the demo, and lands in Advanced Mode.

System Behavior

Switches navigation to Clients, Review, Opinion, and lawyer-specific More options.

Outcome

The lawyer sees the product as a review console, not a simplified consumer app.

Stage 02

Review raw extracted data

28, 08-09b
"Access to: Raw extracted data, Verification logs, Discrepancy detection, Editable inputs for lawyers"

§16 Advanced Lawyer Mode

User Goal

Check the system interpretation before relying on it.

User Action

Inspects extracted owner, survey number, area, document category, OCR status, and metadata.

System Behavior

Provides raw extracted data, grouped files, and discrepancy-ready structured fields.

Outcome

The expert can validate or challenge the machine-produced facts.

Stage 03

Audit verification evidence

13-14, 28
"All outputs must be backed by verified data."

§3 Core Design Philosophy

User Goal

Confirm exactly which claims match or diverge from public records.

User Action

Opens detailed verification, reviews document-vs-government comparisons, and checks logs.

System Behavior

Shows field-level matches, discrepancies, severity meters, API/log-like evidence, and source references.

Outcome

The lawyer saves time by starting from a pre-structured verification matrix.

Stage 04

Analyze title chain and risk logic

16-18, 21-22
"Chronological ownership history including family lineage and court cases must be displayed in a timeline format."

§15 Title Chain Visualization

User Goal

Find gaps, family lineage issues, court orders, encumbrances, and compliance concerns.

User Action

Moves through KPI intelligence, map overlays, title chain, ownership timeline, and legal risk screens.

System Behavior

Highlights chronological ownership, family clusters, disputes, risk categories, and compliance context.

Outcome

The lawyer can see how the product reached its legal reasoning.

Stage 05

Read and challenge the legal opinion

19-25
"Legal opinion must feel: Elegant, Structured, Authoritative"

§9 Legal Opinion Generation

User Goal

Evaluate whether the generated opinion mirrors legal thinking.

User Action

Reads the executive summary, genesis, ownership timeline, risks, supporting documents, final recommendation, and traceability path.

System Behavior

Presents structured legal sections with source evidence and summary/expert toggles where relevant.

Outcome

The expert can validate, refine, or dispute the generated opinion.

Stage 06

Deliver advice faster

24, 27-30
"Lawyer: 'This mirrors my thinking and saves significant time.'"

§19 Key UX Goals

User Goal

Turn verified reasoning into a client-facing decision or validation service.

User Action

Uses the final recommendation, service request flow, profile/persona settings, and advanced mode outputs.

System Behavior

Connects legal recommendation, validation requests, service tracking, and role-specific navigation.

Outcome

The lawyer uses Realtee as a time-saving expert workspace.

Screen Flow Diagram

01-03

Onboard

Role and account entry

04-06

Property Hub

Dashboard, list, detail

07-09b

Documents

Upload, extract, organize

10-12

Complete

Checklist and sourcing

13-17

Verify

Agencies, depth, KPIs, map

18

Title Chain

Timeline of ownership

19-25

Opinion

Opinion and evidence

26-30

Expert/Services

Marketplace, lawyer mode, profile