RailMadad train complaints: prepare the incident record before choosing a file
Source text changed since your saved version. This does not establish a new factual review.
On this device
Saving a guide stores its ID and the source version for this language in this browser only. No account is needed. Clear your list at any time; clearing browser data also removes it.
Editorial standards and disclosures
Scope and limitations. Llandora publishes educational guides and illustrative tools. Reading a guide or using a calculator does not create a professional relationship. Examples and estimates omit individual circumstances and may be incomplete or outdated. Check dates, assumptions and the official authority for your jurisdiction. Do not use this site for medical, dental or health advice. No approval, savings, investment return or other outcome is promised. Nothing in this notice excludes consumer rights or liability that applicable law does not allow us to exclude.
On this page
Start here
Before using RailMadad's train grievance form, organise the incident details and supporting file separately. A clear attachment is useful only when the description identifies which journey and incident it relates to.
Read the actual form fields
The Indian Railways RailMadad train form shows mobile-number/OTP access, journey-information fields, coach and berth or seat details, a complaint description, type and subtype, incident date and an upload field. The displayed attachment instruction permits PDF, JPG, JPEG, PNG or MP4 up to 5 MB.
The form includes different journey identifiers; this article does not claim every field applies to every ticket type. Follow the actual choices and instructions for your journey. Do not invent a PNR, coach or seat number to fill a field.
Build a private incident note
Our suggested preparation is:
- Record the journey date and train or ticket identifier you actually have.
- Record where and when the incident occurred.
- Add the coach and seat only where known and relevant.
- Describe what happened in a short chronological account.
- Choose the supporting document, image or clip that corresponds to that account.
- Check the accepted file type and 5 MB limit before uploading through the official form.
For an illustrative cleanliness complaint, an image with no explanation may leave the train and incident unclear. A concise description linked to the actual journey gives the image context. This example is about organising evidence, not manufacturing a complaint or proving fault from a photograph alone.
Use the official process for private information
Keep OTPs, ticket identifiers, contact details and any personal documents out of public social posts. Include only relevant material and avoid unnecessary information about other passengers. Do not treat a travel discussion as the complaint-submission channel.
We inspected the public form without entering data, requesting an OTP or submitting anything. No response time, resolution, compensation or legal outcome is promised. This guide is not an emergency service and provides no health advice. Recheck the live form's requirements when you use it; a route-planning or ticket-booking app is a separate task.
Editorial note: Prepared with Codex AI assistance. This is original commentary and a planning checklist based on the linked source passages.
Scope: India, the named operator or venue only. Source passages checked October 25, 2026. This is a primary-source-led explainer, not a new-rule announcement or a claim of measured current popularity. No first-hand transaction or visit is claimed.
Disclaimer: General information only, not legal, immigration, tax, financial or other professional advice. Requirements can change; check the linked official sources for your situation.
Continue planning
Find more guides for this task · Explore all destinations.
This checkbox records your choice only on this device; it does not verify completion or notify anyone.
My reading