← Case Studies/Case #008/C8-021
C8-021DecidedPostureFoundational2026-04-25

Pre-Clarify Rules Before Play, Not After Results

Any question about rule interpretation — premium square reuse, theme standards, tile-count limits, valid word sets — must be raised before play begins, framed as clarification, not accusation. After results are announced, raising a challenge reads as sore-loser behavior regardless of its merit, triggers defensiveness, and has no resolution mechanism in an informal community event. Before play, the same questions are competent due diligence: 'Can you clarify how triple-word squares work when a later word passes through a square a prior word already used?' This is not suspicious — it is methodical. The failure to ask this question before the prior tournament is the specific gap that the 2nd place finish licenses fixing. Pre-clarification protects the game as well as the player: when everyone understands the rule before play, accidental scoring errors become less likely.

Freshness
Active

Active. Applies to every tournament iteration. The principle does not expire.

#pre-clarification#before-not-after#rule-questions#due-diligence#not-accusation#challenge-cost#governance-repair

Capture

At the prior tournament, the operator did not ask the organizer or judges to clarify the premium square rule before play began. Specifically: no one confirmed whether the rule that premium squares can only be used once was explicitly enforced, understood by all participants, and tracked in the self-scored format.

This omission is the specific correctable gap from the prior year. The gap is not "I should have scored more" — it is "I should have asked about the rules before play."

The correction: any question about rule interpretation — premium square usage, theme standards, legal word sets, tile-count limits — must be raised before play begins, framed as clarification questions.

Example question (premium squares): "Can you confirm how the triple-word squares work when a later word passes through a square already used by an earlier word? I want to make sure I'm tracking the scoring correctly."

Example question (theme standard): "What's the standard for theme connection? Are we looking for direct references or are broader connections acceptable?"

These are not accusatory. They are competent. A player who asks these questions before play is reading the rules, not challenging other players.


Why

After results are announced, raising a scoring concern requires contesting a result. Contesting a result in an informal community event is adversarial, has no resolution mechanism, and is universally perceived as sore-loser behavior regardless of its merit. Even a valid concern raised post-result faces these structural costs. The concern may be correct and still produce no corrective outcome while generating social friction.

Before play, the same concern is reframed as due diligence. No result has been announced. No one's result is being questioned. The question is simply: what are the rules? The organizer answers it, the answer is on record, and everyone plays with a shared understanding.

The pre-clarification principle serves the operator in two ways:

  1. If the rule is confirmed and everyone understands it: Premium square reuse is less likely to occur because the rule is freshly stated. Accidental errors of the type described in C8-004 are less probable when the rule is front-of-mind.

  2. If a scoring concern arises during play: The operator has a firm foundation for speaking up in the moment — "we confirmed this rule before play began, and I think this play may be using a square that was already scored." This is not retroactive complaint; it is in-the-moment application of a previously confirmed rule.


Why-Not

Why not ask these questions mid-round or at the end if they become relevant? Mid-round questions interrupt play, draw attention in an awkward context, and may be perceived as challenging a specific play already made. End-of-round questions are retroactive complaints with all the costs described above. Before play is the only window where questions are unambiguously neutral.

Why not avoid asking altogether to prevent appearing suspicious or adversarial? Asking is the competent behavior, not the suspicious behavior. A player who reads the rules carefully and asks clarifying questions is doing exactly what good players do. The suspicion concern comes from post-result challenges, not pre-play clarification. The social perception of "this player reads the rules" is positive or neutral, not negative.

Why not simply trust that the organizers will enforce the rules correctly? Trust that rules will be enforced is not a substitute for confirming what the rules are. Organizers of community events may not have expert knowledge of every rule interaction — they may not know the premium square exhaustion rule themselves. Pre-clarification confirms shared understanding. It does not assume bad faith on anyone's part.


Commit

Decision: Before play begins at every tournament: confirm premium square usage (exhaustion rule), confirm theme standard, and confirm any other rule creating uncertainty. Ask as clarification, not challenge. Record the answer. Apply it during play. Speak in the moment if a rule confirmed before play appears to be violated.

Post-event update: For the current year, the organizers proactively addressed the premium square gap via a scoring guide presented before play — an initiative the operator infers was prompted by the post-event email (C8-023). The specific gap this ADR targeted was resolved not by the operator's pre-play asking but by the organizers' proactive improvement. The principle remains valid for future iterations where such guidance may not be provided: if the organizers' scoring guide is absent or ambiguous, the operator asks. If it is present and clear, the operator acknowledges it and applies it. The pre-clarification posture now means verifying the existing guidance, not necessarily asking from scratch.

Confidence: High. The principle does not expire. Its form adapts to whether the organizers have already addressed it.


Timestamp

2026-04-25

C8-020C8-022