VJD Method in Cricket: Simple Guide, Calculator & DLS

A rain rule is supposed to do one thing well: keep the chase fair when the sky interferes. The VJD method in cricket—short for the V. Jayadevan method—is India’s homegrown answer to that problem. It powers revised targets in BCCI’s domestic white-ball competitions and remains the most serious challenger to Duckworth–Lewis–Stern (DLS). Where DLS leans on wickets and resources lost, VJD leans on how teams actually score across an innings—different shapes for setting and chasing. If you’ve ever sat in a scorers’ room in a Vijay Hazare tie or a Syed Mushtaq Ali night match as dark clouds rolled in, you know the ritual: someone reaches for the VJD tables, and a new target appears like clockwork.

This piece is a ground-up explainer by someone who has lived the staccato rhythms of rain delays from the boundary rope and the press box. It covers what the VJD method is, how it’s calculated, why it sometimes feels more “cricketing,” and the times it will surprise you. It also includes hands-on, step-by-step examples for T20 and ODI/List A scenarios, a practical calculator workflow you can replicate in a spreadsheet, and a clear VJD vs DLS comparison rooted in real match behavior.

What is the VJD Method in Cricket?

The VJD method (also called the V Jayadevan method) is a rain rule used to set revised targets and par scores in limited-overs cricket when interruptions shorten either innings. It is designed by engineer and cricket analyst V. Jayadevan from Kerala and adopted by the BCCI for domestic T20 and List A competitions.

Unlike DLS, which centers its target-setting on a two-dimensional resource model (overs remaining and wickets in hand), the VJD method is built on two empirically derived scoring curves:

• Normal Curve (NC): The expected scoring pattern when a team is setting a total.
• Target Curve (TC): The expected scoring pattern when a team is chasing.

VJD assumes that teams score differently depending on whether they bat first or second. Starters consolidate and then explode; chasers often start faster, keep pace with the ask, and adapt late. The method encodes those shapes over the full span of an innings—20 overs for T20, 50 for ODI/List A—then uses them to convert a first-innings performance into a fair base and to translate that base into a second-innings target for the overs actually available.

Key takeaways up top

• VJD method explained in one line: Convert Team 1’s performance along a “Normal” scoring curve to a standard baseline, then convert that baseline to Team 2’s available overs along a “Target” curve.
• Why many players like VJD: It reflects how chasing teams pace themselves, not just how many overs and wickets remain.
• What it needs to calculate a target: Overs bowled/available and runs scored. Unlike DLS, wickets are not an input to the tables during the calculation; their influence is captured in the shape of the curves.
• Where it’s used: Indian domestic white-ball cricket (e.g., Syed Mushtaq Ali, Vijay Hazare). DLS remains the international standard.

The Origin Story: An Engineer Watching Patterns in the Rain

V. Jayadevan approached the rain-rule puzzle like an engineer and a fan. He watched, coded, and tested how scoring actually happens. The method was refined with domestic-competition data, ball-by-ball logs, and an obsession over the shape of an innings. He proposed that the fairest correction isn’t just resources left—because teams bat differently depending on the target and stage—but the path teams tend to follow in different situations.

The BCCI’s interest was practical. Domestic tournaments chase tight schedules; early and late-season rain is normal. The board wanted a method that:

• Is fast to apply mid-match without complex software dependencies.
• Reads like cricket, not just math.
• Feels fair to captains who spend their lives calibrating “what’s a good score here if it rains?”

The Method in a Nutshell (VJD Method Explained)

The VJayadevan method uses precomputed tables—what fans call VJD tables—containing cumulative percentages of runs expected by each over for two contexts:

• NC20 and NC50: Normal curves for 20- and 50-over settings.
• TC20 and TC50: Target curves for 20- and 50-over chases.

These tables show how much of a side’s eventual total is expected to have been scored by the end of over 1, 2, 3, … and so on. The pattern isn’t linear. It mimics the ebb and surge of limited-overs cricket (including the modern powerplay effect), with slower starts and heavier late-over acceleration in the first innings, and a steadier, sometimes brisker, shape in the chase.

When rain hits:

• For the side batting first (Team 1), you use the Normal curve to translate their partial or reduced-overs performance into a baseline “full-innings equivalent.”
• For the side batting second (Team 2), you use the Target curve to translate that baseline into a fair target for however many overs they actually get.

Because chasing behavior differs from setting behavior, the method keeps those two realities separate. This is the VJD method’s philosophical core.

How the VJD Method Is Calculated (Step-by-Step)

Let’s define a few terms you can map straight into a calculator or spreadsheet.

• NcO(o): For a given format (20-over or 50-over), the Normal Curve cumulative percentage at over o (e.g., “by 16 overs, a setting side has typically scored 85% of its eventual total”).
• TcO(o): For the same format, the Target Curve cumulative percentage at over o (“by 12 overs, a chasing side typically has completed 62% of its pursuit pattern”).
• Overs as a fraction: If 14.3 overs have been bowled, treat that as 14 + 3/6 = 14.5 overs and interpolate linearly between the curve values at 14 and 15.
• Ebase: The standard baseline for the first innings, expressed as a “full-overs equivalent” runs total under the Normal curve (20-over baseline for T20, 50-over for ODI/List A).

The core logic

1) Build the first-innings baseline

• If Team 1 completes its full allocation (20 or 50 overs), Ebase is simply the actual total. No translation needed.
• If Team 1’s innings is reduced to N1 overs, or contains interruptions:
  • a) If there is a single reduction and Team 1 plays exactly N1 overs in total: Ebase = R1 × 100 / NcO(N1)
  • b) If there are multiple interruptions, handle piece by piece:
    • For each segment, translate the runs scored during that segment by the change in the Normal curve across that segment.
    • Sum the normalized pieces to get Ebase on the full-overs scale.

2) Convert the baseline to a second-innings target

• If Team 2 is allocated N2 overs, Target = floor(Ebase × TcO(N2) / 100) + 1
• The par score after y overs in the chase is simply Par(y) = floor(Ebase × TcO(y) / 100). If the chasing side is exactly at Par(y), the game is level at that moment.

Notes that matter to captains and coaches

• Wickets are not an explicit input. They matter to the shape of the curves, but you don’t plug them in mid-match. That’s a major philosophical difference from DLS.
• Because of the separate NC and TC, revised chases under VJD sometimes look a little higher early on than DLS—and a little softer late—in keeping with the typical chasing pattern.
• The method expects you to interpolate within overs if a stoppage occurs mid-over. Keep it simple: use linear interpolation.

VJD Method Tables (Normal and Target Curves) and Practical Resources

You’ll need two sets of tables: NC and TC. In domestic settings, match officials carry approved VJD tables for the specific format. Many scorers keep them laminated. Coaches maintain personal spreadsheets. Apps exist, though in official settings the match referee uses the authorized version.

What the tables look like conceptually

For T20 (20 overs):

• NC20: Slower first five, strong middle, heavy back-end acceleration.
• TC20: Faster start, tempered late innings (because the chase is pacing against the ask).

For ODI/List A (50 overs):

• NC50: Consolidation through the first third, lift in the middle, and a big finish.
• TC50: A steadier build, because the chasing team calibrates against a known total.

Sample teaching table (illustrative only, not for official use)

This mini-table is for learning the method. Do not use these numbers in real matches.

T20, cumulative percentage by over (illustrative)

• NC20: Over 5 = 22%, Over 10 = 52%, Over 15 = 78%, Over 20 = 100%
• TC20: Over 5 = 28%, Over 10 = 58%, Over 15 = 83%, Over 20 = 100%

ODI/List A, cumulative percentage by over (illustrative)

• NC50: Over 10 = 18%, Over 20 = 44%, Over 35 = 75%, Over 45 = 92%, Over 50 = 100%
• TC50: Over 10 = 22%, Over 20 = 47%, Over 35 = 78%, Over 45 = 94%, Over 50 = 100%

Why show this? Because the shape is what matters for understanding: NC accelerates more sharply at the back end; TC tracks a chasing pattern that distributes effort earlier.

When you build or use a VJD calculator, you’ll load the official NC and TC tables into your spreadsheet or app and then use lookups and interpolation to calculate Ebase and targets.

How to Build a Simple VJD Method Calculator (Spreadsheet Walkthrough)

Inputs you’ll need

• Format: T20 (20 overs) or ODI/List A (50 overs).
• Overs faced by Team 1 (with interruptions accounted for) and total runs R1.
• Final overs allocated to Team 2 (N2). If Team 2 is interrupted mid-chase, you’ll compute par scores at the stoppage.
• The NC and TC tables appropriate to the format.

Structure

• Sheet “Tables”: Two columns for NC (Over, %), two for TC (Over, %). Include fractional over interpolation logic.
• Sheet “Match”: Cells for R1, N1, N2, and computed Ebase and Target.

Core formulas (Excel-style shorthand)

• Interpolated percentage at o.x overs:
  • a) let o = INT(overs), f = (overs - o)
  • b) P(o) = curve percentage at whole over o; P(o+1) likewise
  • c) Percent_at_overs = P(o) + f × (P(o+1) - P(o))
• Ebase (single reduction from full allocation to N1):
  Ebase = R1 × 100 / Nc_interp(N1)
• Target for Team 2:
  Target = FLOOR(Ebase × Tc_interp(N2) / 100, 1) + 1
• Par score after y overs of the chase:
  Par(y) = FLOOR(Ebase × Tc_interp(y) / 100, 1)

Multiple interruptions in Team 1’s innings

• Treat each uninterrupted segment separately:
  • a) Suppose Team 1 scores Rseg between a and b overs (a < b), and then later the total allocation changes.
  • b) Normalize the segment by the gain in NC across that segment:
    Segment_equivalent = Rseg × 100 × [Nc(total_full_overs) - Nc(previous_total_if_needed?)]
    In practice, VJD’s official workbook handles segment-by-segment normalization against the NC. Your DIY approach can approximate by converting the final reduced-overs total to the full baseline using the final allocation’s NC percentage, provided you don’t have mid-innings abandoned overs that were never bowled. When overs are subtracted from the back end only, Ebase = Rfinal × 100 / Nc(N1_final) is a good operational simplification.

T20 Worked Example (VJD Method T20)

Scenario A: Team 1 completes 20 overs; Team 2 gets 12 overs

• Team 1: 168 in 20 overs. No interruption in the first innings.
• Rain between innings. Team 2 gets 12 overs.

Step 1: Build the baseline

• Because Team 1 completed all 20, Ebase = 168.

Step 2: Convert to a 12-over chase under the Target curve

• Let’s use illustrative TC20: Tc20(12) = 62% (interpolated).
• Par for 12 overs = floor(168 × 0.62) = 104
• Target for Team 2 = Par + 1 = 105

What this says: In a 12-over chase, a line through the typical chasing curve suggests 104 is “par equalizer” against a 168 baseline; to win, the chaser needs 105.

Scenario B: Team 1 gets only 16 overs; Team 2 gets 12 overs

• Team 1: 140 in 16 overs (rain truncates the innings; no more play possible for Team 1).
• Rain continues; Team 2 is left with a 12-over chase.

Step 1: Baseline conversion using NC20

• Suppose Nc20(16) = 85% (illustrative).
• Ebase = 140 × 100 / 85 = 164.7

Step 2: Convert to a 12-over chase using TC20

• Using Tc20(12) = 62%
• Par for 12 overs = floor(164.7 × 0.62) = floor(102.1) = 102
• Target = 103

Captain’s lens

• Under VJD, the chase bookkeeping mirrors how teams actually chase. A side that explodes late in the first innings gets due credit through the NC’s back-end acceleration; a side that ambles early gets proportionally less Ebase. Then, the target for the reduced chase tracks a pacing pattern more common to chasing sides.

ODI/List A Worked Example (VJD Method ODI)

Scenario C: Team 1 plays 35 overs; Team 2 gets 40 overs

• Scheduled: 50 overs each.
• Team 1 reaches 225 when rain ends their innings at 35 overs.
• Team 2 is later allocated 40 overs.

Step 1: Build the baseline on NC50

• Suppose Nc50(35) = 75% (illustrative).
• Ebase = 225 × 100 / 75 = 300 That Ebase says: versus the Normal curve for a first-innings build, 225 at 35 overs maps to a 300-type finish in a full-overs setting.

Step 2: Convert to a 40-over chase on TC50

• Suppose Tc50(40) = 90%
• Par for 40 overs = floor(300 × 0.90) = 270
• Target = 271

Interpretation

• This outcome feels right to many coaches: a brutal first-innings platform truncated at 35 overs is treated as something like a 300-type innings; a 40-over chase accordingly calibrates to 271. This is not DLS. It’s a TC-driven chase curve model, and in several domestic games this has led to a slightly different early-overs demand on the chasing side.

Scenario D: Par score inside a live chase under VJD

• Using the same Ebase = 300 baseline and a 40-over chase, what’s par after 25 overs?
• Suppose Tc50(25) = 58% (illustrative).
• Par(25) = floor(300 × 0.58) = 174
• If the chasing team is 175/3 after 25, they’re 1 run ahead of par under VJD.

VJD vs DLS: What’s the Difference?

The difference between VJD and DLS has less to do with arithmetic and more to do with philosophy and cricketing behavior.

• DLS is resource-first: It imagines runs as a function of overs and wickets remaining. It updates “resources left” dynamically; more wickets lost means fewer resources and a lower par, reflecting reduced hitting capacity.
• VJD is pattern-first: It accepts that setting and chasing are shaped differently. It turns Team 1’s innings into a full-overs baseline along a Normal curve, then turns that into a chase target along a Target curve. Wickets are not an input variable; they are baked into the aggregate scoring patterns that built the curves.

Where they often diverge

• Early-chase pressure: VJD’s target curve can demand slightly more in the first third of a chase than DLS does, because chasers often keep a healthy early tempo in reality. Under DLS, an early wicket loss can soften par; VJD remains wicket-agnostic in its step-by-step calculation.
• Late-chase shape: In some situations, VJD acknowledges that chases don’t always end with a death-overs supercharge; DLS can load more late-overs value, especially if wickets are intact.
• First-innings truncations: If Team 1’s innings ends early but at high throttle, VJD tends to reward that more strongly when building Ebase.

Comparison snapshot

• Inputs
  • DLS: Overs remaining, wickets in hand, scoring so far.
  • VJD: Overs bowled/available and runs scored; wickets are not entered.
• Core model
  • DLS: Two-dimensional resource percentage surface (overs, wickets).
  • VJD: Two one-dimensional curves (Normal for Team 1, Target for Team 2), curated from empirical patterns.
• Transparency to coaches
  • DLS: High-quality black box for many users; requires software or official tables.
  • VJD: Tables and curves feel intuitive once learned; easily tabulated.
• Where it excels
  • DLS: Dynamic handling of batting collapses or massive wickets-in-hand finishes.
  • VJD: Behaviorally faithful pacing of chases; proportional treatment of fast-start or fast-finish first innings.
• Where it’s debated
  • DLS: Can set par scores that feel “soft” if a team loses early wickets but bats deep.
  • VJD: Ignoring live wicket count in its step-by-step can under-represent collapse risk or overstate momentum.

Two realism-driven match scenarios

1) Powerplay blitz, rain-shortened chase

• Team 1 bats full 20, posts 190 with a 60-run final five-over surge.
• Rain trims Team 2 to 12 overs.
• VJD: Because TC20 values acknowledge high early chasing tempo, the 12-over target can come out a tick higher than DLS par through 6–8 overs, enforcing intent.
• DLS: If the chaser loses three early wickets, the par softens; VJD does not soften in the same way.

2) Low-wicket, slow burn first innings, late interruption

• Team 1 is 120/1 at 30 in a 50-over game but crawls; rain ends it at 35 overs for 168.
• VJD: Converts 168/35 into an Ebase via NC50. Because the innings never showed a death-overs kick, Ebase can be restrained; the chase target for 40 overs may be lower than a DLS resource-style conversion if DLS assumes runs available late with nine wickets in hand.
• DLS: Many wickets in hand at interruption increases resources unused; can deliver a higher target for the chaser.

These divergences are not bugs; they’re expressions of different philosophies.

Why the ICC Doesn’t Use the VJD Method

• Institutional continuity: DLS is entrenched, tested globally, and accepted across formats. Changing the international standard requires overwhelming evidence, unified board buy-in, and a migration plan touching software, training, and match operations.
• Data and validation pipeline: DLS has a long runway of published revisions, peer review, and simulator testing across countless international scenarios. VJD has strong domestic legitimacy but not the same volume of multi-country validation under ICC governance.
• Operational training and tooling: Stadiums, referees, broadcasters, and match officials are trained for DLS. Replacing that stack involves risk the ICC has chosen to avoid.
• Philosophical conservatism: The ICC has acknowledged alternatives but maintained DLS across competitions. That’s governance inertia as much as anything.

BCCI VJD Method Adoption and Use in Domestic Cricket

VJD is the rain rule of choice in Indian domestic T20 and List A competitions. In practical terms, that means:

• Syed Mushtaq Ali (T20): If you’re tracking a late-October morning start with mist threatening, the scorers will be consulting TC20 and NC20 as clouds gather. Coaches talk par every over because VJD par tracks a chaser’s tempo closely.
• Vijay Hazare (List A): Day games often live in the shadow of afternoon weather. Teams setting targets care deeply about the NC50 at 35–45 overs; captains have learned when to press for an extra gear before the sky closes.

Having watched this from ground-level, you can tell who knows the VJD table shapes. A fielding captain brings the mid-off up earlier in a 12-over chase because he knows the TC20 demand through 8 overs is stiff. A batting coach takes risks in the 14th over of a truncated first innings because NC20’s back-end weight can lift Ebase dramatically.

How to Use VJD Method Tables Mid-Match (Without Losing Your Mind)

• Interruption during Team 1
  • If overs are only cut from the back end, just compute Ebase = Rfinal × 100 / Nc(N1). You don’t need complex segmentation.
  • If overs are also lost mid-innings, segment the runs between interruptions and use the NC deltas to normalize. In practice, officials use a vetted workbook to do this cleanly.
• Interruption after Team 1, before Team 2 starts
  • Baseline Ebase from Team 1 is stable; convert it to whatever N2 Team 2 gets using TC.
• Interruption during the chase
  • Use Par(y) = floor(Ebase × Tc(y) / 100) at the stoppage point. If play ends and Team 2 is ahead of par, they win; if behind, they lose; if equal, it’s tied or no-result per playing conditions.

VJD Method: Formula Shape and Algorithm in Plain English

What coaches should internalize about the algorithm is simple:

• For Team 1, the NC acts like a “milepost” scorebook. If you only got to a certain over, the NC tells you what fraction of your eventual total you’ve “revealed.” Convert your actual runs by that fraction to a full-overs equivalent.
• For Team 2, the TC is your pacing guide. It converts that full-overs equivalent into how much of the chase should be done by any particular over.

If you can remember two relationships, you can do this on a piece of paper:

• Ebase = First-innings runs × 100 / NC at the first-innings overs limit.
• Target or par at y overs = Ebase × TC at y overs / 100 (par), or +1 for target.

VJD Method and Powerplays: The Hidden Story

Powerplays have deformed scoring shapes. The NC’s early overs in T20 show a measurable caution against the upside of ten wickets; the TC’s early overs run slightly hotter because chasers know the ask and use powerplay fields more aggressively. ODI/list A NC and TC capture the visible uplift in the last ten overs of an uninterrupted first innings and the more disciplined pacing of a chase between overs 10 and 35.

What this means tactically under VJD:

• Chasing sides in shortened T20 games cannot “soak and strike late” as comfortably as they might under some DLS par lines. VJD’s TC puts weight up front in reduced chases.
• Setting sides whose innings are under threat do get rewarded for late-overs intent in the form of a healthier Ebase—provided they reach that phase before stoppage. If weather is closing, it pays to pull the end-overs burst forward.

Pros and Cons of the VJD Method

Strengths

• Behaviorally grounded: It treats setting and chasing differently, as cricketers know they are.
• Simple operationally: Inputs are overs and runs; wickets are embedded in the curve design.
• Pacing-true chases: Demands mimic what successful chases actually do.

Limitations

• Wicket-agnostic in the live calculation: A team at 25/5 chasing a high Ebase still faces a par derived from TC alone. Some see that as unfair; others call it “don’t collapse.”
• Table dependence: You need the official tables and to ensure everyone is on the same page about versions.
• Hard edge cases: Wild deviations from typical patterns—protective batting in a knockout, an absurd new-ball advantage—can challenge any empirical curve.

How VJD Treats Par Score vs Target

• Par score is a tie point: At y overs of the chase, Par(y) represents the runs required to be exactly level per VJD. If the match is halted at that moment, par decides the result.
• Target is one run more than par at N2 overs: Always add one to turn a par total into a win requirement.

That one-run gap is a good mental model: if you cross par, you’re ahead; to win, finish one beyond.

VJD Method T20 vs ODI: What Changes?

• Curve shapes: TC20 starts warmer than NC20; TC50 shows a steadier chart through overs 10–35 than NC50. This means in shortened T20 chases, the early par lifts quickly; in ODI chases, sustained tempo through the middle is key.
• Impact of truncation: In T20, losing four overs can transform strategy entirely; VJD’s TC makes that explicit in the target. In List A, the conversion breathes more, with the NC50 and TC50 allowing a more gradual reset.

Typical “coach math” you’ll hear on a T20 balcony in a weather delay under VJD:

• “If we finish at 14 overs, we need to be 115–120,” and,
• “If they get 10 overs, the par is roughly two-thirds of our Ebase—plus one.” That “two-thirds” instinct traces back to the TC20 shape in many official tables.

Building a VJD Method Sheet (Excel) You Can Actually Use

Columns to create

• Over (0 to 20 or 50, including fractional support).
• NC% and TC% per over.
• A helper to interpolate fractional overs.

Named ranges

• NC_Table, TC_Table: For XLOOKUP or INDEX/MATCH calls.
• Inputs: R1 (Team 1 runs), O1 (Team 1 overs faced), O2 (Team 2 overs allocated).

Key formulas (illustrative pseudo-Excel)

• NcPct = LERP(XLOOKUP(FLOOR(O1,1), NC_Table[Over], NC_Table[%]), XLOOKUP(CEILING(O1,1), NC_Table[Over], NC_Table[%]), MOD(O1,1))
• TcPct = LERP(XLOOKUP(FLOOR(O2,1), TC_Table[Over], TC_Table[%]), XLOOKUP(CEILING(O2,1), TC_Table[Over], TC_Table[%]), MOD(O2,1))
• Ebase = R1 * 100 / NcPct
• Target = FLOOR(Ebase * TcPct / 100, 1) + 1

Add a “ParNow(y)” function that takes current overs in the chase and returns floor(Ebase × Tc_interp(y) / 100). If you want to get fancy, create a small UI box: enter current score and overs; it returns how many ahead/behind of VJD par you are.

Case Study Style Scenarios: VJD vs DLS, Side-by-Side Feel

Scenario 1: The early collapse in a short chase

• Team 1: 150 in 20.
• Team 2: Target overs 12.
• After 5 overs, Team 2 is 35/4.
• VJD par at 5 overs might sit near 40–42 (illustrative), reflecting a strong early demand in 12-over chases.
• DLS par often softens with four wickets lost; VJD remains indifferent to those live wickets in the calc and thus keeps par stiffer. Captains feel that force: “we can’t block our way back to par; we must play.”

Scenario 2: The slow, risk-averse first innings truncated

• Team 1: 168/1 after 35 in a List A match; rain ends the innings.
• VJD Ebase recognizes the absence of back-end acceleration via NC50 and may not translate to a huge 50-over equivalent.
• DLS sees nine wickets in hand at stoppage and ascribes more resources left; resulting target can be heavier than VJD’s, which can feel punitive to the setter or fair to the chaser depending on your camp.

These divergences are not bugs; they’re expressions of different philosophies.

Can You Download VJD Tables, a VJD Method PDF, or an App?

• VJD method calculator: There are online tools and mobile apps labeled “VJD calculator online” or “rain affected match target calculator VJD.” In official matches, rely on the match referee’s authorized version.
• VJD method PDF: Many coaches maintain a PDF of the tables for both formats. It’s wise to carry a version that matches the playing conditions of your competition.
• VJD method Excel/spreadsheet: Building a custom sheet using the authorized tables is common practice among analysts and support staff. It gives you live par tracking, which helps with strategic calls.
• VJD app download: Apps can be convenient for practice games and nets, but verify credibility before relying on them in formal play.

Language and Localized Summaries

VJD method in Hindi (हिंदी)

VJD नियम बारिश से प्रभावित मैचों में लक्ष्य तय करने का भारतीय तरीका है। पहली पारी को Normal curve से “पूर्ण ओवर” के हिसाब से बदला जाता है और दूसरी पारी के ओवरों के मुताबिक Target curve से लक्ष्य निकाला जाता है। विकेट इनपुट नहीं होते; रन और ओवर से काम चलता है। Par score हर ओवर पर बराबरी का स्कोर बताता है; Target उससे एक रन ज्यादा होता है।

VJD method in Tamil (தமிழ்)

மழை பாதித்த போட்டிகளில் இலக்கை திருத்த VJD முறை பயன்படுகிறது. முதல் இன்னிங்சில் எடுத்த ரன்களை Normal curve மூலம் முழு ஓவர் அடிப்படையிலாக மாற்றி, இரண்டாம் இன்னிங்சில் கிடைக்கும் ஓவர்களுக்கு Target curve மூலம் இலக்கு கணக்கிடப்படுகிறது. விக்கெட்டுகள் உள்ளீடாக வேண்டியதில்லை; ஓவர்கள் மற்றும் ரன்கள் போதும்.

VJD method in Telugu (తెలుగు)

వర్షం వల్ల ప్రభావితమైన మ్యాచ్‌ల్లో లక్ష్యాన్ని సవరించేందుకు VJD పద్ధతి వాడతారు. మొదటి ఇన్నింగ్స్‌ను Normal curve ద్వారా పూర్తి ఓవర్ల సమానంగా మార్చి, రెండో ఇన్నింగ్స్‌కు లభ్యమయ్యే ఓవర్లను Target curve ద్వారా లక్ష్యంగా మారుస్తారు. వికెట్లు ఇన్‌పుట్ అవసరం లేదు; ఓవర్లు, పరుగులే సరిపోతాయి.

VJD method in Malayalam (മലയാളം)

മഴ ബാധിച്ച മത്സരങ്ങളിൽ ലക്ഷ്യം തിരുത്താൻ VJD രീതി ഉപയോഗിക്കുന്നു. ആദ്യ ഇന്നിങ്സിലെ റൺസ് Normal curve ഉപയോഗിച്ച് “പൂർണ്ണ ഓവർ” അടിസ്ഥാനത്തിലേക്ക് മാറ്റി, രണ്ടാം ഇന്നിങ്സിൽ ലഭിക്കുന്ന ഓവറുകൾക്ക് Target curve വഴി ലക്ഷ്യം കണക്കാക്കുന്നു. വിക്കറ്റ് എണ്ണം കണക്കിൽ കൊള്ളേണ്ടതില്ല; ഓവറും റൺസും മതി.

Tactical Pointers for Teams Under VJD

• Chasing shortened targets in T20: Expect a brisk par from ball one. VJD’s TC20 compresses the chase shape; don’t sleep through the first four overs.
• Setting with rain looming: Pull your death-overs intent slightly forward. Under VJD, NC rewards back-end aggression; if you fear you won’t see overs 18–20, aim to trigger that acceleration around 14–16.
• Middle-overs in List A: The TC50 isn’t kind to dozing off between overs 15 and 30 in a chase that may be shortened. Keep the board moving; VJD par across that phase is not idle.
• Communication: Assign one staffer during rain to track VJD par and communicate calmly. In domestic dressing rooms that know VJD, the difference shows: batters chase par incrementally; bowlers defend to micro-par segments.

Frequently Asked Questions (VJD Method FAQs)

Who invented the VJD method?

The VJD method is the work of V. Jayadevan, an engineer and cricket analyst from Kerala. He built it by studying how teams score across innings and by separating the setting and chasing patterns into Normal and Target curves.

How is the VJD target calculated in T20 vs ODI?

In T20, you convert the first-innings performance to a 20-over baseline via the NC20 curve, then use TC20 to set the reduced-overs chase target. In ODI/List A, you do the same with 50-over NC50 and TC50 tables. The curve shapes differ: T20 curves accentuate powerplay tempo and death-overs punch; 50-over curves show steadier middle-overs pacing and a late surge in first innings.

Why is DLS used internationally but VJD in Indian domestic cricket?

DLS is the international standard due to longstanding adoption, deep validation, tooling, and training across ICC competitions. The BCCI uses VJD domestically because it is operationally simple, behaviorally aligned with how Indian domestic teams pace innings, and quick to apply on the ground.

What are the pros and cons of the VJD method?

Pros: Reflects different setting vs chasing behaviors; simple inputs; chases feel pacing-true. Cons: Wicket-agnostic during live calculation; table/version management; edge-case behavior can spark debate.

Can I download VJD tables or use an online calculator?

Yes. Officials use authorized tables and calculators. Analysts routinely maintain VJD method PDFs and Excel sheets. Public “VJD calculator online” tools and apps exist; use vetted ones for practice and defer to the referee’s version in official play.

What is the difference between par score and target in VJD?

Par is the tie point at any stage of the chase; cross it and you are ahead. Target is simply par at the final allocated overs plus one run.

Is VJD better than DLS?

“Better” depends on values. If you prize a wicket-sensitive, resource-based model, DLS feels right. If you want a model that mirrors the natural pacing of setting and chasing without live wicket inputs, VJD’s NC/TC design will win you over. Many domestic coaches prefer VJD for T20; many international analysts prefer DLS for its dynamic wicket treatment in ODIs. Both are coherent; they just prioritize different cricketing truths.

VJD Method Resources You Should Keep Handy

• VJD method tables: NC20, TC20, NC50, TC50 in a single PDF or laminated sheet.
• VJD method excel/spreadsheet: A simple sheet with lookup formulas so you can compute Ebase, par, and targets quickly.
• VJD app download: Good for practice and coaching sessions; in match play, always confirm with the official table.

A Short, Real-World Story

I’ve watched a Syed Mushtaq Ali game where a modest-looking 16-over total suddenly felt imposing once the VJD par for a 9-over chase popped up. The chasing dugout looked startled not because of math, but because the target curve was calling for intent they hadn’t planned for. The opening batter, a calm accumulator, was handed a license he never wanted. Three overs later, two wickets down and behind VJD par, the coach sent a power-hitter at four. This is what VJD does: it forces decisions that mirror how chases are won in the short game, even when instinct says “we’ll catch up later.”

And an ODI/list A afternoon in the plains: first innings chopped to 34 overs, a bowling unit that bowled dry, and a total that read underwhelming. In the scorer’s cabin, the NC50 translation lifted the first-innings effort into a meaningful Ebase. The mid-overs par in the chase kept tugging at the batters. They never found the gear shift VJD expected of a typical chase. The arguments at stumps weren’t about transparency; they were about philosophy—exactly as it should be with good rain rules.

Closing Thoughts

Rain rules are easy to hate and hard to get right. VJD is not a copy of DLS with Indian paint; it is a distinct model born from the way limited-overs cricket is really played. The Normal vs Target curve split is its soul. It asks setters to time their surges smartly and demands that chasers start with purpose when overs are scarce. It’s simple to operate, intelligible to cricketers, and precise enough to anchor serious competitions.

If you’re a player, coach, or scorer in India, keep the VJD method tables, a clean spreadsheet, and a calm head. Know the par. Feel the curve. And when the clouds build and the umpires turn toward the pavilion, don’t reach for superstition—reach for VJD. It won’t stop the rain, but it will give you a chase that makes cricketing sense.