irctc-ticket-status is a single-page, publicly reachable website that lets a rail passenger check the current status of an IRCTC ticket. The visitor supplies ticket details on the page, and the page returns that ticket's current status — confirmed, RAC, waitlisted, or cancelled — so the passenger can decide whether to travel or act on the booking.
The product intent is narrow and deliberate: one page, one job. There is no account, no booking, no payment, no cancellation, and no itinerary management. The audience is a traveler holding an IRCTC ticket who needs fast, legible certainty about that ticket's standing, frequently on a phone at a platform under time pressure. The page is therefore designed as a public information sheet — a ruled, colour-coded departure board — rather than a marketing landing page.
The system is a single public web page. It presents the ticket-status checker, accepts ticket details from the visitor, submits them to a backend that resolves the ticket's current status, and displays the returned status on the same page. No visitor identity is required, and no visitor-specific state is stored or resumed.
Actors
Accepted behavior
Ownership
Narrow exclusions
Delivery. The website is online and publicly hosted — not a local-only tool. It is reachable by any visitor with a browser and a network connection, with no installation and no sign-in.
Access ownership. The single page is publicly accessible with no access requirement. The visitor does not establish an identity, does not create an account, and does not resume prior state. This is a deliberate product boundary: the accepted journey is a one-shot check of a ticket the visitor already holds, and nothing in the accepted behavior requires the application to privately own or resume visitor-specific state. Because no durable actor-specific state, commitment, entitlement, or value transfer is bound to the visitor, no application-owned identity is introduced.
Current vs. future. Everything described in this document is current. No future-horizon requirements were accepted. Anything not listed here — additional pages, accounts, booking actions, saved history — is out of scope rather than deferred.
Provider boundary. The authoritative ticket status is owned by the external IRCTC / Indian Railways source. The application does not own, compute, or guarantee that status; it requests it and presents what is returned, including the case where the source cannot be reached.
Not applicable. No reference directive in the authoritative sources declares a content_source, so no source content inventory is produced.
The page contract is versioned and exact: one page, named Landing, with access requirement none, owned by the application, serving the Rail Passenger.
Information and state
IRCTC TICKET STATUS, flush left in all caps.Indian Railways · public status check.CHECK YOUR / TICKET / STATUS.Primary actions
Supporting actions
Domain entities
Component responsibilities
States
Each requirement is a distinct story point with its provenance, lifecycle facts, and observable acceptance.
FR-1 — Single-page public checker (explicit) As a Rail Passenger, I should reach one online page that checks IRCTC ticket status, so that I can get an answer without navigating a multi-page site or signing in.
FR-2 — Accept ticket details on the page (explicit) As a Rail Passenger, I should enter my ticket details on the page, so that the site can look up that specific ticket.
FR-3 — Choose between PNR and train-number lookup (explicit, from the accepted segmented PNR / Train toggle) As a Rail Passenger, I should choose whether I am checking by PNR or by train number, so that I can supply the kind of detail I actually have.
FR-4 — Submit the check (explicit) As a Rail Passenger, I should submit my ticket details, so that the site resolves the ticket's current status.
FR-5 — Return the ticket's current status (explicit) As a Rail Passenger, I should see the current status of my ticket returned on the same page, so that I know whether my booking stands.
FR-6 — Colour-code the returned status (explicit, from the accepted colour-code legend and status dot) As a Rail Passenger, I should be able to tell my status at a glance, so that I do not have to parse a paragraph to find the answer.
FR-7 — Explain the status codes (explicit, from the accepted legend strip) As a Rail Passenger, I should be able to learn what each status means, so that I can interpret a status I have not seen before.
FR-8 — Recover from a failed or empty lookup (required_inference) As a Rail Passenger, I should be told when my check could not be completed and be able to try again, so that a failed lookup does not leave me without an answer or force me to reload the page.
FR-9 — Resolve status through the external source (required_inference) As the system, I should query the authoritative IRCTC / Indian Railways status source with the submitted ticket details and normalize the response for the page, so that the status shown is the source's current status rather than a locally invented one.
Product context. The Rail Passenger holds an IRCTC ticket — a booking they have already made — and wants to know where that booking currently stands. They arrive at the page from a search, a bookmark, or a link, often on a phone, often at a station or on the way to one, and often with limited time. They are not shopping for a ticket and are not managing an account; they have one question and want it answered.
Primary goal. Learn the current status of their specific ticket — confirmed, RAC, waitlisted, or cancelled — quickly and without ambiguity, so they can decide whether to travel or act on the booking.
Distinct accepted responsibilities.
Relevant inputs and decisions. The passenger's input is a PNR or a train number, selected through the segmented toggle. Their decision is which mode to use, and then what to do about the answer — travel, wait, or act on the booking. The page does not make that decision for them; it gives them the status and the meaning of the status code.
Interactions with other accepted participants. The passenger interacts only with the page. The status itself originates from the external IRCTC / Indian Railways source, which the passenger never contacts directly and never sees; the page presents the source's answer as its own visible result. There is no other human participant in this product — no agent, no operator, no administrator — and no handoff to another person.
Observable success. The passenger sees the status word for their ticket on the same page where they entered the details, in the correct colour code, with the ticket attributes the source returned, and understands what that status means. Success is a single completed check with no sign-in, no navigation, and no ambiguity about which ticket the answer belongs to.
What makes this role distinct. The Rail Passenger is the only human actor in the product, and their work is a one-shot lookup rather than a session. They do not accumulate state, do not return to a saved record, and do not manage anything — they ask one question about a booking they already own and read the answer. Every design decision on the page serves that single, time-pressured act of reading.
IRCTC TICKET STATUS wordmark flush left, the Indian Railways · public status check label flush right, the three-line CHECK YOUR / TICKET / STATUS headline, the schematic route line, and the white check panel below the 2px red rule. No sign-in is requested.Failure and recovery. If the PNR is empty or malformed, the page states what is required, keeps the entered value, and lets the passenger correct it and submit again. If the external status source cannot be reached or returns no result for that PNR, the page states that the status could not be retrieved and offers a retry; the check panel remains fully usable and no reload is needed.
Failure and recovery. If the train number is empty or malformed, the page states what is required, keeps the entered value, and lets the passenger correct it. If the source cannot be reached or returns no result, the page states that the status could not be retrieved and offers a retry without a reload.
Failure and recovery. If the source returns a status outside the four known codes, the status word is shown in the neutral text colour with the dot in muted grey rather than being mis-coloured, so the passenger is never given a false colour signal.
The creative direction is authoritative for this section. It names Massimo Vignelli as the muse and frames the page as a public information and wayfinding problem: a ruled, colour-coded information sheet that reads like a departure board, not a SaaS landing page. The emotional register is trust, legibility, and fast certainty.
Colour tokens — light mode
| Role | Hex | Use |
|---|---|---|
| Background (paper ground) | #F4F1EA | Covers the whole page |
| Surface | #FFFFFF | Reserved for the status-result panel and the input fields |
| Text | #111111 | Type and rules only |
| Primary | #D22630 | Submit action, active toggle side, left rule of the result panel |
| Accent | #F2B705 | Waitlist/RAC states and the route-line position marker |
| Status — confirmed | #0B6E4F | CONFIRMED status text and its dot only |
| Muted | #6B6B6B | Labels, timestamps, helper copy |
Proportion: approximately 70% paper ground, 20% white panels, 10% colour codes. No colour is ever used decoratively. The warm off-white ground covers the whole page; pure white is reserved for the status-result panel and the input fields, so the returned answer physically sits on a brighter sheet. Black is type and rules only. IRCTC red is the primary code. Signal yellow is the second code. Deep green is used only for CONFIRMED status text and its dot. Muted grey carries labels, timestamps, and helper copy.
Typography
-0.01em, flush-left ragged-right, set very large.0.14em.Type scale — 1.333 modular on a 4px baseline:
| Token | Mobile | Desktop |
|---|---|---|
| Display | 40px | 88px — clamp(2.5rem, 7vw, 5.5rem) |
| H2 | 28px | 40px |
| Data value | 24px | 32px |
| Body | 16px | 17px |
| Label | 11px | 12px |
Line-height: 1.02 for display, 1.15 for headings, 1.55 for body.
Shape language. Hard edges only: 0px radius on inputs, buttons, panels, and rules. Structure comes from 1px black rules, 2px red rules on emphasis, and colour-filled rectangles. The one curved form is the circular status indicator — a filled dot with a 2px ring — used as the single pictogram on the page. No shadows, no gradients, no glass, no rounded cards.
Layout. A strict 12-column grid on a 1280px max-width sheet, with an always-visible 1px horizontal rule under the header and above the footer. Reading order top to bottom:
IRCTC TICKET STATUS flush left in caps, live Indian Railways · public status check label flush right, separated by a hairline.At 375px everything collapses to a single column, the headline drops to 40px and wraps, the route diagram moves below the headline as a horizontal strip, and label/value rows stack label-above-value.
Imagery. No photography, no 3D, no illustration for its own sake. The only graphics are diagrammatic: a horizontal route line with two station ticks and a moving position marker, and the circular status dot. Type and rules are the image. Any map-like element is a schematic line diagram in black on paper, with red and yellow used as line codes.
Readable-content rule. Headlines, wordmarks, labels, numbers, and controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling to fit, with no other element covering any part of them. Crops, bleeds, and off-edge placement are reserved for decoration only — shapes, textures, rules, and background art.
The public entry is composed as a ruled information poster, not a centred SaaS hero.
The dominant element is a three-line all-caps headline — CHECK YOUR / TICKET / STATUS — set flush left at clamp(2.5rem, 7vw, 5.5rem), spanning columns 1–9 and running close to the left edge of the sheet. To its right, in columns 10–12, sits a small black-and-red schematic route line with two station ticks and a yellow position marker, above a thin ruled caption. Directly beneath the headline, a full-width 2px red rule separates the hero from the white check panel and acts as the hero's baseline.
There is no subheadline paragraph, no gradient, and no button in the hero. The input field inside the panel below is the call to action, and the red submit button sits flush right inside that panel. The whole first screen reads as a printed departure board.
The signature moves that carry the concept:
clamp(2.5rem, 7vw, 5.5rem), flush left across columns 1–9, with the full-width 2px red rule beneath it.This concept only recomposes accepted content, states, and controls. It introduces no new behavior, page, or destination.
Interaction Model: Static Motion Tempo: still Hero Dimensionality: flat
The tempo is copied from the creative direction: instant and mechanical, matching Vignelli's no-decoration stance. There is no parallax, no scroll-triggered reveal, and no marquee.
Landing Hero Motion Brief
CHECK YOUR / TICKET / STATUS spanning columns 1–9, with the schematic route line and its yellow position marker in columns 10–12.prefers-reduced-motion, the result panel appears immediately with no translate, no stagger, and no dot pulse; the submit button's press state changes colour without a transition. All content remains whole and readable.No 3D or WebGL scene is required or requested; the hero dimensionality is flat.
NFR-1 — Single-page constraint (explicit) The product consists of exactly one page. No additional routes, pages, or destinations are built. Rationale: the authoritative requirement states "online 1 page IRCTC ticket status check website."
NFR-2 — Public online hosting (explicit) The website is publicly hosted and reachable over the network, not local-only. Rationale: the authoritative requirement states the site is online.
NFR-3 — No access barrier (explicit, from the page contract's access_requirement: none)
The page is reachable without sign-in, account creation, or any identity step. No authentication UI is built. Rationale: the accepted journey is a one-shot check of a ticket the visitor already holds, and no durable actor-specific state is bound to the visitor.
NFR-4 — Legibility under time pressure (source-backed, from the creative direction) Type, rules, and colour codes must let a status value be found at a glance on a phone at a platform. Data values use tabular numerals so columns align; the status word is colour-coded; the legend strip explains the codes. Rationale: the creative direction frames the page as a public information and wayfinding problem.
NFR-5 — Responsive integrity (source-backed, from the creative direction) At 375px, 768px, and 1280px, headlines, wordmarks, labels, numbers, and controls stay entirely inside the viewport and their container, wrapping or scaling to fit, with no other element covering any part of them. At 375px the layout collapses to a single column, the headline drops to 40px and wraps, the route diagram moves below the headline as a horizontal strip, and label/value rows stack label-above-value.
NFR-6 — Accessible colour coding (required_inference) Because status is conveyed by colour, each status word is also rendered as text and each legend square carries an uppercase text label, so the status is never conveyed by colour alone. Rationale: causally necessary for FR-6 and FR-7 to be usable by a visitor who cannot distinguish the colour codes.
NFR-7 — Reduced-motion support (source-backed, from the creative direction)
The page honours prefers-reduced-motion: the result panel appears immediately with no translate, no stagger, and no dot pulse, and all content remains whole and readable.
NFR-8 — External source dependency (required_inference) The application depends on the external IRCTC / Indian Railways status source for status data and must degrade to a stated, retryable error when that source is unreachable or returns no result. Rationale: causally necessary for FR-5 and FR-9 — the application does not own the status it presents.
No technology choices were specified by the user. The following are coherent defaults for a single-page public checker with a backend status lookup, labelled as defaults.
[Default — not specified by user][Default — not specified by user][Default — not specified by user][Default — not specified by user][Default — not specified by user]Constraints (binding)
Assumptions (narrow, labelled)
[Assumption] The external IRCTC / Indian Railways status source is reachable from the backend over the network and returns a status for a valid PNR or train number. The application does not own or guarantee this source.[Assumption] The status vocabulary presented to the visitor is the four accepted codes — CONFIRMED, RAC, WAITLIST, CANCELLED. A status outside this set is displayed in the neutral text colour with a muted dot rather than being mis-coloured.[Assumption] The ticket attributes shown in the result panel are those the external source returns for the submitted booking; the application does not invent or fill missing attributes.[Assumption] No visitor identity, session, or stored preference is required, because the accepted journey is a one-shot check with no durable actor-specific state.[Assumption] The segmented PNR / Train toggle is the accepted mechanism for choosing the lookup mode, as established by the creative direction's signature moves.Uncertainty retained
#0B6E4F) with a matching status dot.#F2B705) with a matching status dot.#F2B705) with a matching status dot.#D22630) with a matching status dot.
IRCTC TICKET STATUS
Indian Railways · public status check
Expected 10-digit passenger name record
Enter your ticket detail above and submit the check to see the returned status, coach, seat, and timestamp.
Status supplied by the external IRCTC / Indian Railways source — presented as returned.
Reference records available in this preview: 2
Status colour code

IRCTC TICKET STATUS
Indian Railways · public status check
Expected 10-digit passenger name record
Enter your ticket detail above and submit the check to see the returned status, coach, seat, and timestamp.
Status supplied by the external IRCTC / Indian Railways source — presented as returned.
Reference records available in this preview: 2
Status colour code
No comments yet. Be the first!