Write how your clan runs
A clan's policy is how it runs, written down by its leader and co-leaders. Nothing in Clan judges anyone until there is one, and every save is a new version.
Every clan runs differently, so Clan has no rules of its own. The clan's policy says what it counts, how Elder works, how long a quiet member has, and which actions to raise. Until a leader saves one, nothing is judged: no standing, no actions, no awards.
Who writes it
The leader and co-leaders, under Run, once their player is verified. Leaders can prepare and save a policy at any clan size; the small-clan page offers leaders Prepare the policy alongside Open Recruit. Operational reviews, Actions, standing and awards remain paused below 10 members and resume at 10. Saving below ten creates no announcement Action. Policy is Elixir's agreement for the clan, not a game setting. Every member reads an active policy on Standing, under How it works here, and on the clan's Policy tab, one card a rule.
On the Policy tab, each rule ends with a quiet line on who sees what about you under it:
- About this clan: nothing about you; every member reads it, and so does the clan directory.
- What this clan counts: every member sees your war decks, donations and battles each week, on the week.
- Minimums and Becoming an Elder: when Elder is earned by participation and Members see where everyone stands is on, every member sees on Standing who's rising and who's slipping. Otherwise only you and the leader and co-leaders see where you stand. Only the leader and co-leaders see a promotion or demotion before it's done, and it never goes to the clan's Discord; it's shared with the clan once it is.
- When you go quiet: only you and the leader and co-leaders see your days without a battle, whether you're at risk, and your away. A removal action never goes to the clan's Discord, and a removal is shared with the clan once it's done.
- Newcomers: Elders and the leader and co-leaders get an Action naming each newcomer.
Under the rules: Elders read the Elders' notes about a member, and the leader and co-leaders read every note. Closed Actions and the policy's past versions are for the leader and co-leaders.
Starting points
The About section starts from what the clan is for. Pick one and every section is filled from it, yours to change before you save:
| Starting point | Counts | How strict |
|---|---|---|
| A war clan | Clan Wars and donations | strict |
| A climbing clan | ranked play and trophy road | standard |
| A donation clan | donations | standard |
| A social clan | nothing; Elders by hand | relaxed |
| A bit of everything | all four | standard |
How strict (relaxed, standard or strict) sets where the minimums and clocks start. Playing together can be said but is never measured: the game does not say who plays with whom. On a saved policy, a starting point replaces the whole draft. Every preset turns on the inactivity clock, welcomes, departure questions and announcements; review those tabs before saving. Changing How strict alone does not retune fields already in the draft.
Clan War participation comes first on About and in the Draft agreement summary, and the Clan Wars section links back to it. It records the leaders' intent: participating, not participating, or not specified, which is where a policy starts. It is separate from Count Clan Wars, which controls scoring and minimums; starting points and category switches never set or change it.
The Discord agent's scheduled war-deck check uses this saved intent (Clan directory). Participating permits the check only in the appropriate war phase after a fresh policy read succeeds. Not participating suppresses the check; not specified, unavailable or stale context defers it. The agent refreshes before planning and immediately before firing, and the final read must be no more than 60 seconds old. This gate applies to the scheduled war-deck check; other agent content keeps its own rules.
What this policy can do today
Once a policy is saved, the top of the page lists each judgment it asks for, with one of:
| Status | Means |
|---|---|
| Live | Clan acts on it now |
| Needs more evidence | it will act once the record has what is named: 10 members, a saved policy, or one finished review week |
| Off | the policy does not ask for it |
The judgments listed are promoting and demoting Elders, removing inactive members, asking quiet members if they are away, asking how a member left, and welcoming newcomers.
Preview before you save
Preview the last reviews reads the clan's record and shows what the last four reviews would have said under the draft, beside the current policy: the Elder band before and after, and each member who would read differently. No policy, Action, award or decision is saved or raised by a preview, and no model is called. The member-count reading and normal recorded-read audit are updated; the Preview result itself is not saved. Holds and decision cooldowns are not applied in this comparison, so it is not an exact forecast of pending Actions. Editing any setting clears it.
Saving
Saving makes a new version; the first is version 1. Add a line on why, if you like; the versions list, for the leader and co-leaders only, keeps who saved each and when. A setting out of range is refused, with the section that holds it opened and the field marked. The clan is read afresh under the new version, which can raise or withdraw pending Actions at the next evaluation, including reviews of recorded weeks. Completed decisions and saved award grants stay as recorded; awards have a separate setup. A stale browser version is refused instead of overwriting a newer policy, and unsaved edits survive a refetch. No policy save changes game settings, kicks a member or sends a message. A saved policy lists the clan in the clan directory, with the policy's public part.
Saving does not restart review streaks or the activity clock. Recorded review boundaries are replayed under the new values; the current Trophy Road figure is used when that category counts. A pending recommendation that still qualifies retains the evidence and policy version saved when it was raised. Current thresholds, grace and waiting periods apply at reevaluation without rewriting previous decisions.
When Tell the clan when the rules change is on, a save raises Tell the clan how it runs for the leaders: chat copy with an explicit durable Inbox alternative, saying how the clan runs the first time, and what changed after.