Skip to content

The Tatkal clock · From uncertainty to clarity

IRCTC — Bringing Clarity to Interrupted Tatkal Bookings

Designing a clearer post-transaction experience so Tatkal users can understand their ticket, payment and refund status when a booking is interrupted.

PROJECT TYPE
UX redesign / Hackathon project
TEAM
Madhura and Likhitha
MY ROLE
UX Designer
DESIGN DIRECTION
Clarity after interruption
My responsibilities
  • UX audit.
  • Secondary research.
  • Primary research.
  • User interviews.
  • Problem identification.
  • Ideation and How Might We questions.
  • User flows and journey mapping.
  • Wireframing.
  • UI design.
  • Prototyping.
  • Final solution.
Open the hackathon board
FROM UNCERTAINTY TO CLARITY
Proposed refund details screen with payment received, booking failed, refund initiated and refund credited timelineProposed Rebook This Journey screen with journey and traveller details and Search Trains Again actionProposed booking unsuccessful screen separating ticket not booked, payment received and refund initiated

02The problem

When a booking has no clear answer.

01

Was my ticket booked?

The user is uncertain about the actual booking outcome.

02

Was my payment deducted?

The user needs to understand what happened to the transaction.

03

What should I do next?

The user must decide whether to wait, retry booking or track a refund.

ONE BOOKING. MULTIPLE SOURCES. NO CLEAR ANSWER.

IRCTC users booking Tatkal tickets may not know whether their ticket was booked or whether their payment went through when the booking is interrupted. Because booking, payment, and refund details are shown separately across different platforms or incompletely, users must check different sources and decide whether to wait, retry, or request a refund. This can cause stress, fear of duplicate charges, and the risk of losing the ticket opportunity.

03Research

Following the evidence, not the error.

Secondary research informed the research and discovery stage.

Research, UX audit & affinity mapping

Users are very conscious of the limited booking time.

Before / During Booking

01Users prepare everything before Tatkal opens.

02Users are very conscious of the limited booking time.

03Users want to complete the booking as quickly as possible.

04Users experience slow loading during Tatkal.

05The app/website sometimes hangs.

06Some users get logged out.

07Some users have to restart the booking process.

08Seats can disappear while users are trying to complete booking.

09Users become worried when the system takes too long.

After an Error / Payment

IRCTC / My BookingsBank / UPISMSEmail

Users don't immediately know whether the ticket was booked.

Users check "My Bookings."

Users check their bank/UPI.

Users check SMS/email.

Users wait to see what happens.

Users try booking again.

Some users ask someone else what to do.

Users worry that retrying might result in duplicate payment.

Users worry that they will lose the available seat if they wait.

Users feel frustrated when there is no clear answer.

04Insights

Six insights. One need for certainty.

01

Time pressure increases the impact

Users can tolerate small delays during normal booking, but during Tatkal even a few minutes can mean losing the available ticket.

02

Users need certainty

After making a payment, users want to immediately know whether their ticket is actually booked.

03

Unclear failures create risky decisions

When the booking result is unclear, users don't know whether to wait or try booking again.

04

Users look in multiple places

Users may check IRCTC, their bank/UPI app, SMS and email to understand what happened to one booking.

05

The problem is bigger than payment

Login, authentication, system errors, payment and booking confirmation can all interrupt the Tatkal journey.

06

The user's biggest need is knowing what to do next

When something goes wrong, users need a clear explanation and a clear next step instead of simply seeing an error message.

05Ideation

How might we make the next step clear?

01

How might we make sure that the failed payment status, ticket status and refund status are shown in a clear and understandable manner?

02

How might we make sure that the users are able to make a clear decision about re-booking the ticket based on the information of the previous booking outcome?

03

How might we give users enough certainty about their failed booking and refund status that they feel safe to re-book immediately?

Ticket status Payment status Refund status Rebooking decision

MAKE THE NEXT STEP CLEAR.

06Before → After

From scattered answers to one connected result.

01

Ticket status

02

Payment status

03

Refund initiation

04

Refund tracking

05

New booking

CURRENT EXPERIENCE

After a failed Tatkal booking, users may see no clear explanation that payment was deducted while the ticket was not booked. They must manually check Booked Ticket History, track the refund separately and restart the booking process.

PROPOSED REDESIGN

A clear transaction-result screen separates payment status from ticket status, confirms that the refund has been initiated, provides refund tracking information and gives the user a direct path to start a new booking for the same journey.

07Final solution

The interface becomes the answer.

Proposed design screens from the hackathon. The amounts, dates and refund estimates shown belong to the original design artefacts; they are not live transactions or refund guarantees.

01 — A clear transaction result

Ticket and payment status are shown separately. The refund summary and Rebook This Journey action appear in the same result.

01 — A clear transaction result

02 — Refund details in one view

The refund-details view connects payment, booking failure and refund status along one timeline.

02 — Refund details in one view

03 — A direct path to the same journey

The rebooking screen brings forward the previous journey and traveller details, with a direct Search Trains Again action.

03 — A direct path to the same journey

08Reflection

A booking interruption is also a moment of uncertainty.

A booking interruption is not just a technical failure. It creates uncertainty at a moment when users have very little time to make decisions.

The design direction focuses on making the transaction outcome understandable by bringing ticket status, payment status and refund information into a clearer experience.

WHEN A BOOKING IS INTERRUPTED, USERS SHOULDN'T HAVE TO GUESS WHAT HAPPENED NEXT.