HHow to Write a Community Constitution

Communities do not die because they ran out of people. They die because two members had a falling out, no one knew who decided what, and the room split. The constitution is the document you write before that fight happens, not after. Most Indian professional communities skip this step because it feels overweight for a group that just wants to have dinner together. Twenty-four months in, when the first real conflict lands, they wish they had spent the weekend writing it.

¶What a constitution actually does

A community constitution is not a legal document. It is a written answer to a small number of questions that you will be asked eventually: who decides who gets in, who decides who gets out, what counts as a violation, what is the appeal process, and what happens when the founder steps back. If you can answer these five questions in writing before the community is twelve months old, you have done ninety percent of what governance ever does.

The constitution should be short. Two to three pages, plain language, no legalese. Anything longer will not be read. Anything shorter will leave too much ambiguous. We have seen good constitutions in Indian communities run between eight hundred and fifteen hundred words.

¶The five sections that matter

Section one is purpose and scope. One paragraph, no more. Who is this community for, what does it do, what does it explicitly not do. The explicitly-not-do is the part most founders skip. If your community is for AI-native operators in India, say it. Then say what it is not: not a job board, not a deal flow network, not a thought leadership platform. The negatives are what keep the community from drifting into something its members did not sign up for.

Section two is membership: how people get in, how they stay in, how they leave. Cover the application process, the vouching requirements, the annual renewal or contribution expectations, and the conditions under which a member is asked to leave. The leaving clause is the most important. A community that cannot remove a member it should not have admitted is a community that decays.

Section three is decision rights. List the decisions the community makes and name who makes them. Who decides on new member admissions, who decides on chapter expansion, who decides on theme curation, who decides on conflict resolution, who decides on financial questions if any. The default failure is to leave this implicit and have everything decided by the founder. That works for the first eighteen months and then breaks. Better to write it down and revise it than to leave it in someone's head.

¶Section four: conflict resolution

This is the section nobody enjoys writing and everybody is grateful for later. Specify the steps in order. Step one, direct conversation between the parties, mediated only if requested. Step two, escalation to a named council member or trustee. Step three, a council review with both parties present. Step four, a binding decision by the council. Specify the council's composition: typically three to five long-tenure members, with at least one outside the founder's immediate circle. Specify the timeline: most disputes should be resolved within twenty-one days from the moment they are raised. Specify what the council can decide: warning, time-bound suspension, permanent removal, or a no-action finding.

The detail matters because the alternative is improvisation under pressure, which is when bias and favouritism creep in. The Bharath.CLUB Bengaluru chapter ran into a tricky case in March 2025 where a member shared confidential information from a table on a public podcast. The chapter's written conflict process let the council resolve it in nine days with a one-year suspension. Without the written process, that decision would have either dragged out or felt arbitrary.

¶Section five: succession and amendment

The founder will eventually step back or step away. Write down what happens then. Who picks the next steward, by what process, with what input from the membership. The most common pattern in Indian communities is a two-step succession: the founder nominates a successor, the council ratifies. This keeps continuity while preventing capture. Specify also the amendment process: how does the constitution itself change? A typical rule is that amendments need a two-thirds vote of the council plus a thirty-day comment period from the membership.

¶How to actually write it

Do not write the constitution alone. Write the first draft in two sittings, ideally with a co-founder or a long-tenure member. Run the draft past three trusted members for comment. Incorporate the feedback. Publish the document somewhere persistent and accessible, like a Notion page or a Google Doc, and link to it from the community's main welcome message. Re-read it once a year. Amend it when you find a gap, not before.

A useful test for a draft constitution: imagine the worst-case scenario for your community, the one that keeps you up at night. Maybe a senior member behaving badly. Maybe a chapter going rogue. Maybe a co-founder leaving on bad terms. Read your draft and ask, does this document tell us what to do? If the answer is no, the draft is not done yet.

This weekend, block three hours. Open a new document. Write down the five questions and force yourself to answer them in writing. Share the draft with two people you trust. By month twelve, you will be glad you did, even if the document never has to be used.