The core operating system for a land acquisition and development company — every land parcel is a master file anchoring legal, revenue, survey, and document records.
What it is, who uses it, why it exists
The core operating system for a Karnataka-based land acquisition and development company — not a CRM or generic ERP, but a platform consolidating land intelligence, legal cases, revenue workflows, survey data, and a founder dashboard.
The Founder holds full system access with 24×7 oversight; in-house and external advocates manage litigation scoped to their assigned cases; revenue staff and surveyors track ground-reality data.
Land files, legal cases, and survey data lived across people's heads and disconnected spreadsheets. The founding principle — every land parcel is a Master File — keeps institutional memory intact even as staff change.
Who the platform serves, end to end
The full lifecycle, start to finish
Every module the platform is built from
Hover a module to see what it's responsible for.
Land Master
The anchor record every other module attaches to.
- District → Taluk → Hobli → Village hierarchy
- System-generated, non-editable Land ID
- Soft delete only
- Audit log on every field change
Legal Case Management
Court-grade tracking with an automatic compliance escalation path.
- Case, hearing, and document tracking per land file
- Plan of Action auto-escalation before every hearing
- All-cases calendar by advocate, court, or land file
- Case-scoped external advocate access
Document Vault
A version-controlled checklist for every required land document.
- RTC, EC, Phodi Sketch, Tippani, Grant Order, and more
- Full version history — nothing is ever hard-deleted
- Per-land-file completeness percentage
- Role-scoped visibility per document type
Task Management
Every operational activity is a task — nothing exists outside it.
- WhatsApp + SMS on assignment and overdue
- Daily 9 AM digest for pending tasks
- Hourly overdue detection via Celery beat
- Strict per-user visibility unless Founder or Management
Founder Dashboard
A single-screen command centre for 24×7 oversight.
- Land files by status
- Hearings today and next 7 days
- Advocate compliance status
- Travel Mode — critical alerts only
How the major features actually work
Legal Compliance Engine
The system auto-creates a compliance task 5 days before every hearing and escalates to a supervisor if the Plan of Action isn't uploaded in time — no manual step required.
Document Vault Versioning
Every document upload preserves prior versions with uploader and timestamp — nothing is ever hard-deleted, only archived.
Case-Scoped External Advocate Access
External advocate tokens are scoped to a specific list of case IDs — requesting a restricted case returns a 403, never a glimpse of the data.
From client to database, end to end
Select a node to see its purpose, technologies, and responsibilities.
Web interface for all 8 roles, from Founder to freelance surveyor.
- Not specified in PRD
- Role-scoped dashboards
- Document upload and case management UI
How information moves through the system
Problem, decision, reason
Institutional knowledge about a land parcel is scattered across people's heads and disconnected files.
Every entity — legal case, document, survey task, revenue workflow — carries a mandatory FK back to one Land Master record.
Preserves institutional memory independent of any one person.
Legal and compliance obligations mean land and case records can never quietly disappear.
No hard deletes exist anywhere — every removal is a soft delete or archive, and the audit log is append-only.
Every change to a land file must remain reconstructable, not just its current state.
A single audit table inside the primary database would eventually compete with operational queries.
Kafka streams every audit event to Cassandra for durable storage, separate from the OLTP database.
Lets log and event volume scale out without ever degrading the operational database.
Organized by category, with a reason for each choice
What makes this build hold up
Master-File Data Model
Every record anchors back to one Land Master file.
Append-Only Audit Trail
No hard deletes anywhere — every change is reconstructable.
Case-Scoped External Access
External advocates are scoped to their own cases at the API layer.
Kafka + Cassandra Scale-Out
Audit volume scales independently of the operational database.
Current, next, and future vision
Foundation
- Land records and master hierarchy
- Legal case management
- Document vault
- RBAC across 8 roles
- Task management and basic dashboard
Advanced Workflow
- Survey management module
- Revenue & government workflow tracking
- WhatsApp & SMS automation
- Valuation & market intelligence
Expansion
- Mobile application (iOS + Android)
- Post-commitment identity & KYC module
- Investor & capital intelligence
- Regulatory, policy & news intelligence
- Analytics & reporting
Interested in Land Intelligence Platform?
Let's discuss how this can work for you.