Surveyor Claim Tracker
Budget: ₹1,500 – ₹12,500 INR
Project Title: Motor Insurance Claim Management Dashboard (Full-Stack Development)
Introduction I am looking for a developer (or a final-year CS student) to build a functional Motor Insurance Claim Management Dashboard. I already have a design concept and a UI mockup. This is a logic-heavy project, not a design-heavy one.
1. Project Overview & Deliverables
Objective: Develop a fully functional web-based dashboard for an independent Motor Insurance Surveyor to track claims from start to finish.
Design Style: Professional Enterprise SaaS UI (Light background, clean typography, rounded cards, soft shadows).
Reference: https://sparkling-cajeta-3da285.netlify.app/dashboard
Handover Requirement: The developer must deliver the complete source code and a documented database schema. The developer is responsible for defining the storage location (via .env or config files) so that the client can easily launch and track the data on their own server.
2. Core Dashboard Layout (Home Page)
The landing page must provide a visual bird’s-eye view of the current workload.
A. Claim Summary (Center - Data Visualization) A Pie Chart displaying active claims by status (excluding Closed/Fee-Generated claims).
Survey Pending: Survey not yet conducted.
Documents Pending: Missing mandatory documents.
Approval Pending: Waiting for insurer approval.
Under Repair: Vehicle currently at the workshop.
FSR Pending: Final Survey Report submission pending.
Interaction: Clicking a pie segment must filter and show the list of claims in that category.
B. Global Sidebar Filters Filters affecting all dashboard widgets:
Insurance Company (Dropdown)
Workshop City (Dropdown)
Vehicle Model (Dropdown)
C. Management Widgets
Claim Bucket: List of newest claims with a search bar (Partial matching for Claim #, Insurer, or Vehicle #).
Document Management: List of claims with pending docs. High-priority missing documents highlighted with a red background.
Under Repair Tracking: A dedicated table/list to track vehicles currently in workshops, filtered by city for travel planning.
Today’s Work: A daily checklist for Pending Docs, Scheduled Visits, and FSRs due.
3. Detailed Claim Workflow (Step-by-Step)
Step 1: Intake & New Claim Entry
Form Fields: Insurer, Claim # (with duplicate warning), Policy #, Vehicle Registration (e.g., GJ-03-AA-1234), Make/Model, Accident Date, and Nature of Loss.
Logic: Auto-calculate "Delay Days" (Accident Date vs. Intimation Date).
Initial Status: Survey Pending.
Step 2: Survey & Documents
Survey Update: Input Survey Date, Workshop details, and Remarks. Status moves to "Survey Conducted."
Document Tracking: Three-way toggle for each document (Claim Form, RC, DL, etc.):
Received (Select Date)
Not Applicable
Pending
Step 3: Approvals & Repair
Status Toggles: Simple Yes/No toggles for "PSR Submitted," "Approval Received," and "Approval passed to repairer."
Repair Phase: Tracking "Vehicle Repaired," "Re-inspection Done," and "Pre-invoice Received."
FSR Phase: Status moves to "FSR Pending" once the pre-invoice is logged.
Step 4: Invoice & Closure
PDF Generation: Auto-fill claim and insurer data into a professional invoice template.
Closure: Once FSR is submitted, the "Fees Received" toggle appears.
Payment Log: Record UTR Number (payment reference) to mark the claim as "Closed."
4. Master Data & Settings
The system must include a Settings area to manage:
Insurers: Predefined list of 18+ companies (Acko, Bajaj, HDFC ERGO, ICICI Lombard, Tata AIG, etc.).
Workshops: Database of workshop names, cities, and contact persons.
Vehicles: Predefined list of Makes (Maruti, Hyundai, Tata, etc.) with modifiable models.
5. Technical Specifications & Features
Search Engine: Advanced partial matching (search for "1234" should find claim "CLM-1234-XYZ").
Automation: Auto-suggest/Auto-fill for Insurer and Workshop details based on past entries.
Notifications: Automatic alerts for delayed insurer approvals or pending FSRs.
Mobile Responsiveness: The dashboard must be fully usable on mobile devices for on-site workshop visits.
Security: Simple Login (ID/Password). No complex roles required.
Reporting: Monthly analytics showing "Pending vs. Closed" and "Average Approval Time."
6. Developer Instructions for Handover
Code Quality: Use modular code (React/Vue for frontend, Node/PHP/Python for backend).
Storage Definition: All database connection strings and storage paths must be stored in a .env file.
Documentation: Provide a brief "Deployment Guide" explaining:
How to connect the database.
Where the uploaded documents/PDFs are stored.
How to create new Login IDs manually in the database.
Introduction I am looking for a developer (or a final-year CS student) to build a functional Motor Insurance Claim Management Dashboard. I already have a design concept and a UI mockup. This is a logic-heavy project, not a design-heavy one.
1. Project Overview & Deliverables
Objective: Develop a fully functional web-based dashboard for an independent Motor Insurance Surveyor to track claims from start to finish.
Design Style: Professional Enterprise SaaS UI (Light background, clean typography, rounded cards, soft shadows).
Reference: https://sparkling-cajeta-3da285.netlify.app/dashboard
Handover Requirement: The developer must deliver the complete source code and a documented database schema. The developer is responsible for defining the storage location (via .env or config files) so that the client can easily launch and track the data on their own server.
2. Core Dashboard Layout (Home Page)
The landing page must provide a visual bird’s-eye view of the current workload.
A. Claim Summary (Center - Data Visualization) A Pie Chart displaying active claims by status (excluding Closed/Fee-Generated claims).
Survey Pending: Survey not yet conducted.
Documents Pending: Missing mandatory documents.
Approval Pending: Waiting for insurer approval.
Under Repair: Vehicle currently at the workshop.
FSR Pending: Final Survey Report submission pending.
Interaction: Clicking a pie segment must filter and show the list of claims in that category.
B. Global Sidebar Filters Filters affecting all dashboard widgets:
Insurance Company (Dropdown)
Workshop City (Dropdown)
Vehicle Model (Dropdown)
C. Management Widgets
Claim Bucket: List of newest claims with a search bar (Partial matching for Claim #, Insurer, or Vehicle #).
Document Management: List of claims with pending docs. High-priority missing documents highlighted with a red background.
Under Repair Tracking: A dedicated table/list to track vehicles currently in workshops, filtered by city for travel planning.
Today’s Work: A daily checklist for Pending Docs, Scheduled Visits, and FSRs due.
3. Detailed Claim Workflow (Step-by-Step)
Step 1: Intake & New Claim Entry
Form Fields: Insurer, Claim # (with duplicate warning), Policy #, Vehicle Registration (e.g., GJ-03-AA-1234), Make/Model, Accident Date, and Nature of Loss.
Logic: Auto-calculate "Delay Days" (Accident Date vs. Intimation Date).
Initial Status: Survey Pending.
Step 2: Survey & Documents
Survey Update: Input Survey Date, Workshop details, and Remarks. Status moves to "Survey Conducted."
Document Tracking: Three-way toggle for each document (Claim Form, RC, DL, etc.):
Received (Select Date)
Not Applicable
Pending
Step 3: Approvals & Repair
Status Toggles: Simple Yes/No toggles for "PSR Submitted," "Approval Received," and "Approval passed to repairer."
Repair Phase: Tracking "Vehicle Repaired," "Re-inspection Done," and "Pre-invoice Received."
FSR Phase: Status moves to "FSR Pending" once the pre-invoice is logged.
Step 4: Invoice & Closure
PDF Generation: Auto-fill claim and insurer data into a professional invoice template.
Closure: Once FSR is submitted, the "Fees Received" toggle appears.
Payment Log: Record UTR Number (payment reference) to mark the claim as "Closed."
4. Master Data & Settings
The system must include a Settings area to manage:
Insurers: Predefined list of 18+ companies (Acko, Bajaj, HDFC ERGO, ICICI Lombard, Tata AIG, etc.).
Workshops: Database of workshop names, cities, and contact persons.
Vehicles: Predefined list of Makes (Maruti, Hyundai, Tata, etc.) with modifiable models.
5. Technical Specifications & Features
Search Engine: Advanced partial matching (search for "1234" should find claim "CLM-1234-XYZ").
Automation: Auto-suggest/Auto-fill for Insurer and Workshop details based on past entries.
Notifications: Automatic alerts for delayed insurer approvals or pending FSRs.
Mobile Responsiveness: The dashboard must be fully usable on mobile devices for on-site workshop visits.
Security: Simple Login (ID/Password). No complex roles required.
Reporting: Monthly analytics showing "Pending vs. Closed" and "Average Approval Time."
6. Developer Instructions for Handover
Code Quality: Use modular code (React/Vue for frontend, Node/PHP/Python for backend).
Storage Definition: All database connection strings and storage paths must be stored in a .env file.
Documentation: Provide a brief "Deployment Guide" explaining:
How to connect the database.
Where the uploaded documents/PDFs are stored.
How to create new Login IDs manually in the database.