The Indian biodata: a complete guide to the format that has shaped matrimonial introductions for a century.

For at least three generations, the matrimonial introduction in Indian families has happened on paper.

The document is called a biodata. It is roughly one A4 page. It is forwarded over WhatsApp, printed for community elders, photocopied at temples, slipped into envelopes at weddings, and circulated through the wedding-planning network in ways that the Western dating app universe has no equivalent for. The biodata, more than any algorithm, has been the medium through which Indian arranged marriages actually happen.

This guide explains what every standard section of a biodata carries, why families read it the way they do, and how Bhava's Biodata PDF importer brings the same document into the app without losing fidelity.

What a biodata actually is

The biodata is a structured personal summary written specifically for matrimonial introduction. It is not a CV — though it shares format conventions. It is not a dating profile — though it serves the same first-introduction role. It is a Vedic-tradition document with a defined set of fields, expected in a defined order, that allows two families to evaluate compatibility before any in-person meeting.

Almost every biodata in circulation today follows the same skeleton, even though the specific wording varies:

1. Personal details — name, date of birth, time of birth, place of birth, height, complexion
2. Family background — father's name and occupation, mother's name and occupation, siblings, native place
3. Religion, community, gotra, manglik status
4. Education and profession
5. Languages spoken
6. Partner expectations
7. Contact information — usually the family contact, not the candidate's

The order matters. Personal details first. Family background second. Religion and community third. Career fourth. Partner expectations last. The order is the priority order a traditionally-structured family applies when reading the document.

Reading the document the way families read it

The first thirty seconds

When a family receives a biodata, the first thirty seconds are spent on three things:

• Date of birth and time of birth — these are the inputs to the Vedic chart used for compatibility scoring (Ashtakoota, see the previous article)
• Place of birth — required for accurate chart casting; longitude and latitude affect ascendant calculation
• Manglik status — declared at the top because mismatched manglik can be a structural deal-breaker

Almost nothing else matters in the first thirty seconds. A family reading the biodata will scan for these four data points first, set the compatibility analysis in motion mentally, and then read the rest.

The family background section

This is the section most outsiders to Indian matrimonial practice find unfamiliar. A biodata's family-background block lists the candidate's parents by name, their occupations, the candidate's siblings, and the family's native place (the ancestral village or town the family identifies with).

The reason this matters: in traditional Indian arranged marriage, the marriage is not just between two individuals; it is between two families. The biodata's family-background block lets the reading family construct a mental model of the family they would be marrying into — its rough socioeconomic register, its geographic roots, its likely community network. This is the same function a "where did you go to school / where did your parents grow up" series of questions performs in any modern relationship's first hours, compressed into three lines of formatted text.

The religion / community / gotra block

Field	What it carries
Religion	Hindu / Sikh / Muslim / Christian / Jain / Buddhist / Parsi / Jewish / spiritual-not-religious
Community	A more specific identification — Brahmin / Khatri / Reddy / Patel / Iyer / Iyengar / etc.
Sub-community	Further specificity where applicable — Bengali Kayastha, Tamil Iyer, etc.
Gotra	Patrilineal lineage, used to ensure marriage isn't within the same ancestral line
Manglik	Whether the candidate's chart is affected by Mars in certain houses

The gotra field exists for a practical reason: Vedic tradition prohibits marriage within the same gotra — meaning two people who trace patrilineal descent to the same rishi (sage) cannot marry. This is a genealogical-distance heuristic that predates modern genetics; it was the Vedic-era mechanism for preventing marriages within too-close family lines. It survives in the biodata because it survives in the practice.

Education and profession

This is the section that most resembles a CV. Degree, institution, current role, employer, sometimes salary range (less common in 2026 than 1996, but still seen). Read alongside the family background block, it gives the receiving family a sense of the candidate's individual trajectory layered on top of the family's general register.

Partner expectations

The closing block of a biodata is the candidate's (or candidate-family's) stated expectations of a partner. Age range. Education minimum. Profession preferences. Community preferences (or "no community preference"). Manglik tolerance. Diet preferences. Geographic preferences (city, country, willing-to-relocate).

This section is the most-evolved over time. Older biodatas treat partner expectations as the family's expectations expressed on behalf of the candidate; modern biodatas treat them as the candidate's own. The shift mirrors the broader cultural shift in who has the authority to make the marriage decision.

How Bhava reads it

When a Family curator on Bhava uploads a biodata PDF — their own Member's, or a candidate they want to introduce — the app parses the standard sections and pre-fills the matrimonial profile:

Biodata section	Maps to Bhava field
Date / time / place of birth	Vedic chart inputs (Lahiri ayanamsa)
Height	Profile height field
Religion / community / gotra	Cultural fields, used in compatibility filtering
Manglik status	Manglik flag, surfaced in compatibility view
Education + profession	Career fields
Languages	Language compatibility filter
Partner expectations	Pre-fills the partner preferences screens

The parser handles the standard layouts used by most biodata templates in circulation. Hand-typed biodatas with unusual section ordering may require manual confirmation of a few fields after import. The curator confirms the imported profile before Bhava saves it; nothing is auto-published.

The point is not just convenience. The point is cultural fidelity. The biodata is the document the Indian matrimonial tradition uses to introduce candidates. Bhava reads it directly because that is what the Indian matrimonial tradition expects a serious matrimonial product to do.

Practical notes for families using the importer

• PDFs work; image scans do not (yet). If your biodata is a photograph or a scan, convert it to a text-searchable PDF first — most modern scanning apps do this automatically.
• One-page biodatas import cleanest. Multi-page biodatas with appended horoscopes are supported but the parser ignores pages 2+.
• Hand-written sections are not parsed. If your biodata has the candidate's signature or any hand-written notes, those are skipped.
• You confirm everything before save. No imported field is committed to the profile until the curator confirms it on the next screen.

Why this matters more than it sounds

There is a recurring assumption in Western dating-app design that the cultural specifics of arranged marriage are inefficiencies waiting to be optimised away. The biodata, in that frame, looks like an outdated form to be replaced by a guided-onboarding flow.

This misreads what the biodata actually does. It is not an inefficient profile. It is an ordered profile — a document whose order reflects the priority order a traditionally-organised family applies when evaluating compatibility. The biodata does not need to be replaced. It needs to be read, preserved, and made native to the medium this generation actually carries.

That is what Bhava's Biodata PDF importer is for.

— Bhava Notes