Making your kankotri list: a simple system that scales

The kankotri (કંકોત્રી) is the Gujarati wedding invitation card — and “making the kankotri list” is the months-long job of deciding who is invited, at what level, and who delivers each card.

It is the backbone of the whole wedding. Your headcount comes from it, and your headcount drives catering, seating, the size of the hall and a large share of the budget. Yet most families rebuild it three or four times across different WhatsApp messages, and names fall out each time.

Build one master list, and only one

The single rule that fixes most of the chaos: there is one list, and everything else is a view of it. Not the bride’s family’s list and the groom’s family’s list and Kaka’s list of his side, held separately and merged by hand at the end.

One list, with each entry carrying enough to be sorted later:

Household name, not just an individual — invitations go to households.
Relationship, in the words your family uses: Mama’s side, Kaka’s side, Papa’s office, Ba’s village.
Which side invited them.
How many people are expected to come.
Delivery method — hand-delivered, by post, or told in person.
Who is responsible for getting the card to them.

Get the headcount right, because everything depends on it

The most common and most expensive mistake is recording households rather than people. “Shah family” could be two people or nine. Caterers charge per plate.

Ask for a number per household, and record it. Where you genuinely do not know, record your estimate as an estimate so you can chase it later rather than quietly treating a guess as a fact.

Then track three separate numbers, because they are not the same:

Number	What it means
Invited	Households on the list
Expected	People, from the headcounts
Confirmed	People who have actually said yes

Caterers need the third one. Families usually only have the first.

Assign a deliverer to every card

Hand-delivering kankotris is itself a rivaj in many families — the card is taken in person, with sweets, to close relatives. This means the list is also a logistics plan.

Against each household, name the person responsible. Without that, the cards for one branch of the family sit in a bag for three weeks because everyone assumed someone else was taking them.

Track a simple status per card: not sent → sent → delivered. It takes seconds and it is the difference between knowing and hoping.

Handle the awkward parts explicitly

Duplicate households. The same family known to both sides. Decide who invites them, and mark it, or they get two cards and someone is offended by the implication.
Name variants. Harshadkumar, Harshadbhai and Harshad are one person. Deciding a convention early saves a deduplication job later.
Obligation invitations. Households you must invite because of vyavahar, whether or not you are close. Mark them so nobody “tidies” them off the list.

Import what you already have

Most families have something already — a spreadsheet, last wedding’s list, a contacts export. Start from it rather than typing hundreds of names again. What matters is mapping it into the one master list rather than keeping a second copy alongside.

What the list feeds

Done properly, the kankotri list is not a standalone document. It is the source for:

Catering numbers, per meal per day.
Seating and hall size.
The pahermani list, since many of the same households appear.
The Vyavahar Khata, since the people you invite are the people whose chandlo you will record.

That is the argument for entering a guest once, properly, rather than four times in four places.

How Taiyra handles it

One guest list per wedding, with relationship tags, per-household headcount, delivery method, delivery responsibility and confirmation status. It imports from a spreadsheet, so you are not retyping what you already have, and the same list feeds the readiness dashboard so you can see the confirmed count without counting.