Turning a 22-month claim dispute into a navigable public resource
I transformed a dense personal evidence archive into a privacy-safe timeline, correspondence vault, and practical guide. The 96% claim recovery belongs to the personal dispute; the design outcome is the website that makes its evidence understandable.
- Role
- Author, designer & developer
- Duration
- Aug 2024–May 2026
- Team
- Independent
- Scope
- IA, redaction & front-end
Challenge
My personal reimbursement claim became a 22-month dispute spanning more than 500 pages of evidence, 33+ emails, and 60+ documents. It eventually reached the Insurance Ombudsman and closed with 96% of the claim recovered: ₹1,17,468.
That result did not automatically make the experience useful to someone else. The design problem was to turn a private, emotionally charged archive into a scannable public resource without exposing personally identifiable information or presenting one person’s experience as legal advice.
Evidence
The source material was the case itself: medical documents, insurer correspondence, grievance records, and escalation evidence. I inventoried the archive, ordered events chronologically, and separated primary records from explanation and personal interpretation.
Accessible timeline, no hidden interaction
The portfolio summary uses a semantic ordered list so chronology is understandable with a keyboard, screen reader, or without JavaScript. The live site adds deeper, redacted correspondence while preserving that order.
- Hospitalization and claim submission: the case begins with the treatment record and reimbursement request.
- Denial and document loops: insurer responses and repeated evidence requests are grouped without hiding their sequence.
- Formal grievances: internal escalation is separated from the original claim so visitors can see when the process changed.
- Ombudsman escalation: the external review becomes a distinct turning point in the narrative.
- Personal resolution: the dispute closes with a 96% recovery, clearly labeled as the case outcome—not a website outcome.
Decisions
Layer information by need
A short summary and key figures orient visitors before the full chronology and supporting material.
Keep source and commentary distinct
Correspondence, clinical evidence, and explanatory writing use clear labels so readers know what kind of information they are seeing.
Redact systematically
Names, policy identifiers, phone numbers, email addresses, and other personal details are removed before publication.
Design for small screens
Short sections, strong headings, and chronological structure keep the case usable for people researching on a phone.
The site also carries a clear limitation: it documents one personal experience and is not a substitute for professional legal or insurance advice.
Outcome
The claim dispute ended with ₹1,17,468 recovered—96% of the submitted amount—after Ombudsman escalation.
careinsurance.info launched as a live, privacy-safe resource with a structured timeline, redacted correspondence, evidence summaries, and consumer guidance.
No traffic, conversion, or advocacy-impact claim is inferred here. The verified website output is the information architecture and published resource; the recovery metric describes the underlying personal case.
Reflection
Designing from personal experience created both depth and bias. The most important discipline was preserving provenance—showing what came from a document, what happened in sequence, and what was my interpretation. A future iteration should add structured usability feedback from people currently navigating claims, while maintaining strict privacy review before any new material is published.