Decision Review System

Back

Loading concept...

🏏 The Decision Review System (DRS)

Your Second Chance to Get It Right!


🎬 The Story of DRS

Imagine you’re playing a board game with your friends. Someone makes a move, and the referee says “That’s not allowed!” But wait—you’re sure the referee made a mistake. Wouldn’t it be great if you could say, “Hey, can we check that again?”

That’s exactly what the Decision Review System (DRS) does in cricket! It’s like having a super-smart helper with special cameras and computers that can look at plays again when someone thinks the umpire might have made a mistake.

Before DRS, if an umpire said “OUT!” or “NOT OUT!” that was final—even if they were wrong. Players had to accept it, even when they knew the decision wasn’t right. Now, with DRS, cricket became fairer for everyone!


📜 Player Review Rules

What Are Player Reviews?

Think of player reviews like having special coins in a video game. Each team starts with a limited number of these coins, and they can spend them to challenge the umpire’s decision.

How Many Reviews Do Teams Get?

Match Format Reviews Per Team When Do They Reset?
Test Match 2 reviews Every 80 overs
ODI 2 reviews Per innings
T20 2 reviews Per innings

The Rules for Using Your Review

1. Only the person involved can ask for a review:

  • If you’re the batter and you’re given OUT → Only YOU can review
  • If you’re the fielding team and batter is given NOT OUT → Only the captain can ask

2. You must be quick!

  • You have only 15 seconds after the umpire’s decision to ask for a review
  • It’s like a buzzer game—if you wait too long, you lose your chance!

3. You keep your review if you’re RIGHT:

  • If the original decision gets changed → You keep your review coin!
  • If the original decision stays the same → You lose that review coin

🎯 Real Example

The batter is hit on the pad. The umpire raises his finger—OUT! The batter thinks the ball was going over the stumps. He makes a “T” shape with his hands (the signal for review). The TV shows the ball WAS going over! Decision reversed to NOT OUT, and the batting team keeps their review!


👨‍⚖️ Umpire Review Rules

When Can Umpires Ask for Help?

The on-field umpires can also use special technology, but only for specific situations:

graph TD A["Umpire Unsure About Decision"] --> B{What Type of Decision?} B --> C["Caught Behind/Edges"] B --> D["Boundary Line Calls"] B --> E["Run Outs/Stumpings"] C --> F["Ask TV Umpire for Help"] D --> F E --> F F --> G["TV Umpire Reviews with Technology"] G --> H["TV Umpire Gives Final Decision"]

What Umpires Can Review

✅ Can Review ❌ Cannot Review
Close catches LBW decisions
Boundary calls (4 or 6?) Wide balls
Run outs No balls (except height)
Stumpings Overthrows

The Soft Signal

Here’s something interesting! When the on-field umpire asks the TV umpire for help on a catch, they first give a “soft signal”—their initial guess.

  • Soft Signal OUT → TV umpire needs clear evidence to change it to NOT OUT
  • Soft Signal NOT OUT → TV umpire needs clear evidence to change it to OUT

It’s like the umpire saying, “I think it’s this, but I’m not 100% sure. Can you help?”


🔬 DRS Technology Components

The Amazing Tools That Help Find the Truth!

Think of DRS like a detective kit with different gadgets. Each gadget solves a different mystery!

1. 🎥 Hawk-Eye (Ball Tracking)

What it does: Shows where the ball went and where it WOULD have gone

Imagine you throw a ball, and a magical camera can:

  • Show exactly where the ball bounced
  • Show where it hit the batter’s pad
  • Predict where it would have hit the stumps!

Used for: LBW decisions (Leg Before Wicket)

graph TD A["Ball is Bowled"] --> B["Multiple Cameras Track Ball"] B --> C["Computer Creates 3D Path"] C --> D[Shows Ball's Journey] D --> E{Would Ball Hit Stumps?} E -->|Yes| F["Could be OUT"] E -->|No| G["NOT OUT"]

2. 📺 UltraEdge (Snicko)

What it does: Listens for tiny sounds when the ball touches something

Remember how a microphone can hear a tiny whisper? UltraEdge is like a SUPER microphone that can hear if the ball touched the bat—even the tiniest touch!

It shows a wavy line on screen:

  • Flat line = No touch
  • Spike in the line = Ball touched something!

Used for: Caught behind decisions, bat-pad catches

3. 🌡️ Hot Spot (Thermal Imaging)

What it does: Shows heat marks where ball touched bat or pad

When you rub your hands together, they get warm, right? When a cricket ball hits the bat or pad, it creates a tiny bit of heat. Hot Spot cameras can SEE this heat as a bright spot!

Used for: Edges, bat-pad catches

4. 📹 Super Slow Motion Cameras

What it does: Plays action at super-slow speed

These cameras can make everything look like it’s happening in slow-motion dreams! They record so many pictures per second that even the fastest ball can be seen clearly.

Used for: Run outs, stumpings, catches, no-balls

Technology Summary Table

Technology What It Finds How It Works
Hawk-Eye Ball path & predictions Multiple cameras + computer magic
UltraEdge Sound of ball touching Super-sensitive microphone
Hot Spot Heat from contact Special heat cameras
Slow-Mo Cameras Clear view of action Ultra-fast recording

🎯 The Umpire’s Call Concept

The Most Important Rule to Understand!

Here’s a really clever part of DRS. Sometimes, even with all this technology, we’re not 100% sure. That’s when “Umpire’s Call” comes in!

What Does Umpire’s Call Mean?

Imagine you’re coloring a picture and you need to stay inside the lines. But what if your crayon is RIGHT ON the line—half inside, half outside? Is it inside or outside?

In cricket, if the ball is predicted to hit the stumps but barely touches them (less than half the ball hitting the stumps), it’s called Umpire’s Call.

The Zone of Uncertainty

graph TD A["Ball Predicted Path"] --> B{How Much Hits Stumps?} B -->|More than half| C["Clear Decision - Can be Changed"] B -->|Half or less| D[Umpire's Call - Original Decision Stays]

Why Does This Rule Exist?

Here’s the smart reason: Even Hawk-Eye isn’t perfect! It has a tiny margin of error. So when the prediction is “just touching” the stumps, we can’t be 100% sure.

If original decision was OUT and it’s Umpire’s Call → Stays OUT If original decision was NOT OUT and it’s Umpire’s Call → Stays NOT OUT

🎯 Real Example

The umpire gives the batter NOT OUT for LBW. The bowling team reviews. Hawk-Eye shows the ball was JUST clipping the top of the stumps—less than half the ball. “That’s Umpire’s Call!” says the TV umpire. The original decision of NOT OUT stands, BUT the bowling team keeps their review because part of the ball WAS hitting!

The Three Impact Points

For LBW decisions, Hawk-Eye checks three things:

  1. Where did ball pitch? (Must be in line or outside off-stump)
  2. Where did ball hit the pad? (Important for “playing a shot”)
  3. Where would ball hit the stumps? (Umpire’s Call zone applies here!)

🧠 Tactical Review Usage

Using Reviews Wisely—Like a Chess Game!

Smart teams don’t just use reviews randomly. They think carefully, like playing chess!

When TO Review

✅ Strong reasons to review:

  • You’re 100% sure you hit the ball (caught behind)
  • You’re sure the ball was going over the stumps (LBW)
  • You’re sure the ball pitched outside leg stump
  • It’s a crucial wicket (star player or close game)
  • You still have reviews remaining with few overs left

When NOT TO Review

❌ Bad times to review:

  • You’re just hoping you might be right
  • It’s early in the match and you might need reviews later
  • The umpire looked very confident
  • Your partner at the other end says “don’t review!”

The Strategic Thinking

graph TD A["Decision Made Against Your Team"] --> B{How Sure Are You?} B -->|Very Sure - Wrong Decision| C{Check Situation} B -->|Not Sure| D[Don't Waste Review] C --> E{Important Moment?} E -->|Yes - Key Wicket| F["REVIEW!"] E -->|No - Easy Situation| G{Reviews Remaining?} G -->|Many Reviews Left| F G -->|Last Review| H["Think Carefully"]

Team Communication

Smart teams communicate:

  • Batters talk to each other before reviewing
  • Fielders share what they saw with the captain
  • The wicketkeeper’s opinion matters a lot (they see edges!)

🎯 Real Example

It’s the last over of a T20 match. The batting team needs 12 runs. Their best batter is given OUT LBW. They have 1 review left. The batter FELT the ball was going over the stumps. His partner says “I saw it hit high.” The batter reviews—Hawk-Eye shows it WAS going over! Decision reversed! They keep their review AND their best batter stays to win the match!

The Pressure Factor

Reviews are harder to use wisely when:

  • 🔥 The match is very tense
  • ⏰ You only have 15 seconds to decide
  • 😰 You’re frustrated about the decision
  • 🏆 The stakes are very high

Pro tip: The best teams stay calm and trust their judgment, not their emotions!


📝 Quick Summary

Topic Key Points
Player Reviews 2 per team, 15 seconds to decide, keep it if you’re right
Umpire Reviews For catches, run outs, boundaries—gives soft signal first
Technology Hawk-Eye, UltraEdge, Hot Spot, Slow-Mo cameras
Umpire’s Call When ball barely hits stumps, original decision stays
Tactical Usage Save reviews, communicate, stay calm, use wisely

🎉 Congratulations!

You now understand how the DRS works! Next time you watch cricket, you’ll know exactly what’s happening when a player makes that famous “T” signal. You’re not just watching—you’re understanding the game like a true cricket expert!

Remember: DRS isn’t about proving umpires wrong. It’s about making cricket fairer for everyone. Even the best umpires are human and can make mistakes. DRS is simply a helpful friend that gives everyone a second chance to get it right! 🏏

Loading story...

Story - Premium Content

Please sign in to view this story and start learning.

Upgrade to Premium to unlock full access to all stories.

Stay Tuned!

Story is coming soon.

Story Preview

Story - Premium Content

Please sign in to view this concept and start learning.

Upgrade to Premium to unlock full access to all content.