How to Check a Kundli Matching Report: Inputs, Scores and Exceptions

What should you check before reading the final score?

A report is easier to understand when you can follow its path from inputs to result. A high total does not repair a wrong birth time, and a low individual contribution does not explain itself. This checklist helps you identify the question to ask at each stage, including when two calculators disagree.

Keep the report open beside the Kundli matching calculator. The example below uses fictional people already documented in Astrogyana's worked method guide; it is not a client case or a relationship recommendation.

1. Read the birth details as carefully as the score

For each person, check the date, local clock time, place and timezone. Write a date unambiguously: “15 June 1992” avoids the uncertainty of a slash-separated date. Confirm AM or PM, and whether midnight belongs to the intended date. A city name should identify the actual birthplace, not the current residence.

Timezone conversion connects a local birth record to an astronomical instant. A historical birthplace may require the offset in force on that date, so a present-day device setting is not a substitute for the report's timezone information. Skyfield's time documentation explains the distinction between local clocks and astronomical time scales; it does not validate any astrological interpretation.

Record how certain the time is. “About 4:30 in the afternoon” and a documented 16:30:00 should not silently become equivalent claims of precision. If the time is unknown, say so. Entering noon simply to complete a required field can produce a precise-looking chart from an assumption. The unknown birth-time guide explains what information is missing.

Our fictional inputs are Example A, 1 January 1990 at 09:30 in New Delhi, and Example B, 15 June 1992 at 16:45 in Mumbai. Both use Asia/Kolkata. You do not need to copy these into your own report; they make this one example traceable.

2. Identify the calculation settings and rule profile

Separate the astronomical settings from the scoring rules. An ayanamsa belongs to the sidereal coordinate setup; a Koota lookup table belongs to the matching framework. Two reports can disagree because they differ at either layer. A label such as “Vedic calculation” is too broad to establish that both use the same choices.

For this stored example, the settings are true_chitra, whole-sign houses and true nodes. Its recorded engine version is de440s-natal-2026.4, and its matching rule version is north-india-basic-2026.2. These identify the reference calculation, not necessarily the version of a future live report.

The Swiss Ephemeris documentation is a useful independent reference for the existence of different sidereal modes. Citing it here does not mean Astrogyana's report was calculated with that library. For the implementation and supported profile, use Astrogyana's method guide. Do not assume that every chart setting changes every Koota: compare the actual factor inputs before attributing a score difference to a setting.

3. Add the eight contributions yourself

In the Ashtakoota framework illustrated here, the eight maxima add to 36. The traditional factor names identify parts of that framework; they should not be treated as rankings of a person's worth. Read the eight Kootas guide for the calculation roles.

The arithmetic is 0 + 2 + 1.5 + 1 + 3 + 6 + 7 + 8 = 28.5. That gives you a simple audit trail. If a copied report accidentally omitted the Yoni contribution of 1, its displayed rows would add to 27.5 while its headline could still say 28.5. That discrepancy calls for correcting or explaining the report before interpreting it.

Dividing 28.5 by 36 produces a proportion of available points. It does not create a tested probability of happiness, compatibility or marriage duration. A percentage badge may look scientific while adding no new evidence. Ask what the percentage's denominator is and how any predictive claim was established.

4. Keep raw scores, exceptions and other checks separate

This reference example records an unadjusted score of 28.5 and an adjusted score of 28.5. Their equality describes this example only. It is not a rule that the two values must always match.

If a report applies an exception, it should tell you which factor was affected, what condition triggered the exception and whether the number changed or only its interpretation changed. A vague sentence such as “dosha cancelled” leaves too much hidden. Traditional matching manuals discuss factors and exceptions, but implementations select particular rules; the existence of a rule in a book does not establish that a calculator implements it.

Also ask whether a separate check is included in the 36-point sum or shown alongside it. Do not add a second assessment's number to the total merely because both appear on the same screen. The score interpretation guide explains the limits of the headline total.

5. Compare two reports one difference at a time

1. Make the date, time, coordinates and timezone identical.
2. Check that the same person occupies the same A/B or bride/groom role. Some rule tables depend on direction; do not assume swapping roles is irrelevant.
3. Compare ayanamsa and the reported Moon sign and nakshatra.
4. Compare each Koota row rather than just the total.
5. Identify the rule profile and any named exceptions.
6. Keep both reports' version or calculation-date information with your notes.

Suppose the input records match and seven contributions agree, but Tara differs. The next useful question is how each report derives that Tara contribution. Re-entering both full charts repeatedly or debating the overall label will not isolate the discrepancy. This is a troubleshooting illustration, not a claim that Tara is usually responsible for disagreements.

If the recorded time has a real uncertainty range, compare that range and note which outputs change. Do not adjust the time until a preferred score appears. See what a ten-minute birth-time difference can change for the distinction between stable and sensitive outputs.

What to ask when reviewing the report with someone

• Which birth details are documented, and which are estimates?
• Can you show how each row contributes to the total?
• Which rule creates this warning or exception?
• Does the conclusion change within the known uncertainty of the birth time?
• Which statement is a traditional interpretation rather than a calculated value?

Use the answers to understand the report's assumptions. Decisions about a relationship also require the people's consent and direct conversations about expectations, communication and practical responsibilities. A traditional score cannot supply those conversations or decide on their behalf.

Frequently asked questions