Simplifying Member Rules and Checking Understanding
For ordinary chat, upload packs/simplify-member-rules.md, which includes the shared rules, this method, and required references
Organize the existing system into a verifiable rule table, then rewrite the customer explanation. Preserve eligibility, benefit value, deadlines, fees, and exceptions so customers can determine what they can do. See Sources and adopted scope for method sources
Required inputs
Upload existing membership terms, customer explanations, and the scope to organize, with the applicable version, date, and product type. Include customer-service misunderstanding records or interview responses if available, removing unnecessary personal information such as names and contact details
General teaching questions may use examples with explicit assumptions; actual rewriting must follow the supplied system. When the same condition conflicts across documents, list original locations and points to confirm while organizing the remaining confirmed material first
1. Organize the original rules
Number every rule, retain its source location, and complete the table below. Mark fields absent from the source as “Not provided,” distinguishing a nonexistent benefit from missing information
| Rule ID / source | Trigger action | Applicable products and eligibility | What is received | When usable | Scope and expiry | Stacking and exclusions | Refund / cancellation / expiry handling |
|---|
Separate qualification progress from spendable points; distinguish physical goods, paid subscriptions, permanently purchased digital content, and gifted benefits. Record fees, minimum spend, redemption caps, partial refunds, and negative-point handling according to the original terms
2. Simplify the expression
Find synonymous items with different names, repeated explanations, different multipliers for the same action, hidden exceptions, and conditions requiring calculations across pages. For each, choose to standardize names, merge identical explanations, move information to where it is used, or retain differences, recording the before-and-after mapping
Different points and product benefits may be listed separately on one page. Preserve scope and conditions when merging text; retain separate rules when balances, redemption ratios, or refund mechanisms differ. Treat requests to remove exceptions, raise thresholds, shorten expiry periods, or merge balances as system-change proposals separate from wording simplification
3. Verify benefits using the same scenarios
List applicable scenarios such as purchases, recurring charges, partial refunds, skipping one period, subscription cancellation, and expiry of paid digital benefits. Test only scenarios actually included in the system; for permanently purchased content, check access after cancellation of other services
| Scenario and conditions | Original rule IDs | Benefits / fees under original wording | Benefits / fees after rewriting | Same or different | Points to confirm |
|---|
Check boundaries for thresholds, expiry, availability timing, and redemption caps, such as below, exactly at, and above a threshold. When amounts are provided, retain formulas and rounding methods
Results for the same scenario must match before and after rewriting. If they differ, correct the wording; if the original terms contradict themselves, leave the location pending confirmation rather than choosing the interpretation that favors the brand or customer
When points are reclaimed, separately list the original balance, points due for reclamation, actual deduction, outstanding reclamation, and available balance, calculated under the original terms. The overview, full rules, and answer table within the same customer explanation must agree. List only missing items that affect this question's judgment; directly retain conditions already provided clearly. Count equivalent scenarios using actual table rows and separately mark rows whose outcomes remain unconfirmed
4. Write the customer explanation
Start with a short overview explaining “what to do next, what you get, and when and where you can use it,” followed by the complete rule table. Place deadlines, fees, exclusions, and refund / cancellation effects next to the relevant benefit so customers can decide at that moment
Every statement must trace to a rule ID. Keep offers, exceptions, benefits, and customer-service promises absent from the source pending confirmation
5. Prepare comprehension tests
Design open questions using the same scenarios and ask customers to find answers themselves and explain their reasoning, such as “After returning one item in this order, which points can you still use?” or “After canceling the subscription, what content can you access next month?” Do not reveal correct answers in the questions
Deliver questions and answers separately. The moderator's answer sheet lists original rules, expected judgment, acceptable expressions, and points to confirm; do not show answers before customers respond. Mark questions with conflicting rules as pending confirmation and fix them before including them in accuracy calculations
Record actual verbatim answers, correctness, the answer-finding process, and locations of misunderstandings. When comparing two wordings, keep benefits and scenarios identical and record which version each participant saw and in what order. Label AI reasoning as simulation; the user supplies human responses after testing. Report correct counts and denominators for each question from actual valid responses, separating preference ratings from understanding results
Delivery
Deliver the original rule table, rewrite comparison and equivalent scenarios, customer explanation, participant questions, and moderator answer sheet. If human responses already exist, also organize actual misunderstandings and revision locations; after completion, wait for the user's next data batch
