Before You Publish Next Season’s Prices, Build a Fee Catalog Your Staff Can Explain

A board can approve a price sheet in ten minutes and leave staff with months of unanswered questions. Does the guest fee apply to every visit? Is the early-renewal discount based on payment date or application date? Can a midseason family move between packages? What happens when a credit already exists?

The useful answer is a fee catalog: one controlled list that connects each member-facing charge to its operating trigger, accounting treatment, exception rule, and plain-language explanation. It is not a marketing price grid. It is the bridge between what the board approved and what the billing team must run.

Build the catalog before renewal messages are written or invoices are scheduled. That order forces unresolved policy questions into the open while there is still time to decide them.

1Build the decision around the club’s real work

The strongest plan starts with one ordinary transaction, the people who touch it, the rules they apply, and the record that should remain when the work is done. Use the sections below as a working session with the employees and volunteers who run the process. Write down assumptions, unresolved questions, and owners as you go.

21. Give every charge one member-facing name

Similar labels create avoidable confusion. “Family membership,” “family dues,” and “annual family fee” may refer to the same charge or to three different things. Decide which name members will see and which internal code finance will use.

Keep the public name short and descriptive. Store the internal accounting category separately so staff do not expose ledger shorthand on a statement. Document any old label that may still appear in historical records.

Questions to answer:

• What will members see?
• What code will finance use?
• Does an old name remain?
• Is the name unique?
• Can staff say it aloud clearly?

Staff can search, explain, and report on the same charge without guessing whether two labels mean one rule.

32. Define the person or household that owes it

A price means little without eligibility. State whether the charge belongs to a household, an individual, a membership package, a guest, a program registration, or a transaction. Clarify age, relationship, residency, and other board-approved conditions.

Use rules the club can administer consistently. If proof is required, name the acceptable record and the person responsible for review. Avoid a vague “staff discretion” line when the decision actually belongs to a manager or committee.

Questions to answer:

• Who is eligible?
• Who is excluded?
• Is the unit a person or household?
• What evidence is needed?
• Who decides close cases?

The billing rule and the enrollment rule point to the same population, reducing corrections after invoices are sent.

43. Name the event that creates the charge

Some fees arise when a membership starts; others appear at renewal, reservation, guest entry, program enrollment, or purchase. The trigger should be an observable event rather than a general intention to bill later.

Write the trigger as a sentence: “Create this charge when…” Then test cancellations, date changes, partial completion, and duplicated actions. Decide whether the system should prevent a second charge or allow a reviewed adjustment.

Questions to answer:

• What event creates it?
• Can it happen twice?
• Can it be reversed?
• What if the event changes?
• Who reviews duplicates?

The team knows when a charge belongs on the account and can distinguish a missing charge from one that is not yet due.

54. Set due dates and installment behavior

“Due with renewal” may hide several dates: application submission, approval, first payment, final installment, and access start. Put each date in the catalog and explain which one affects eligibility or service.

For installments, state the schedule, rounding approach, failed-payment response, and whether a remaining balance accelerates after a change. Review the language with the people who answer member questions, not only with the person building invoices.

Questions to answer:

• When is the first amount due?
• Are installments offered?
• What happens after failure?
• Does access depend on payment?
• How are partial amounts handled?

Members receive a schedule the front desk and finance team can both interpret.

65. Write credits, refunds, and changes beside the price

A catalog that lists only what the club charges is incomplete. Identify approved credits, cancellation remedies, transfer rules, proration choices, and refund authority. Keep these rules aligned with the published membership terms.

Use realistic examples: a family withdraws before opening, a program date changes, or an approved credit remains from last season. Walk each example through the ledger, member message, and staff response before renewal opens.

Questions to answer:

• When can a credit apply?
• Who approves a refund?
• Is proration allowed?
• Can a fee transfer?
• How is the member told?

The club handles exceptions from an approved path instead of negotiating a new answer at the counter.

76. Connect each fee to reporting

The treasurer needs to know what the charge represents after hundreds of transactions occur. Map each catalog item to the reporting category, location, program, or season leadership actually reviews.

Test a sample invoice, payment, credit, and refund. Confirm how each appears on the household account and in the reports used for reconciliation. PoolPulse keeps recurring and one-time charges, credits, late fees, payment collection, and household-linked records together; test your specific catalog in a walkthrough.

Questions to answer:

• Which report receives it?
• How does a credit appear?
• Can location be separated?
• Can finance trace the account?
• What will the board review?

A clean member statement and a usable finance report come from the same rule set.

87. Publish an owner and version date

Fees change. Keep one effective date, one approved version, and one owner responsible for updates. Archive the prior catalog so staff can explain historical charges without quietly applying old rules to new accounts.

Distribute the current member-facing summary and the internal operating detail from the same approved version. When a rule changes, update training notes, templates, and system configuration together.

Questions to answer:

• What date does it start?
• Who owns the catalog?
• Where is the prior version?
• Which materials must change?
• How will staff be notified?

The club can answer which rule applied, when it applied, and who approved the change.

9Follow one realistic club example

A club approves a new family package and a discounted early-renewal price. During catalog review, the team discovers that “early” has never been defined, the discount cannot be combined consistently with a sibling adjustment, and an old credit rule conflicts with the draft email. The team resolves those decisions before configuration. When renewal opens, staff can explain the charge, finance can reconcile it, and families receive the same answer across the portal, invoice, and front desk.

Use the example as a rehearsal, not as a promised result. Replace its assumptions with your club’s approved rules, actual volumes, responsible people, and operating calendar. The goal is to make the next decision observable: another staff member should be able to tell what happened, why it happened, and what must happen next.

10A practical readiness checklist

• Use one public name and one internal code for every fee.
• Define eligibility and the unit being charged.
• Name the event that creates the charge.
• Document due dates and installment rules.
• Explain failed-payment handling.
• Place credits, refunds, proration, and transfers beside the price.
• Map the fee to the report finance reviews.
• Test an invoice, payment, credit, and refund.
• Add an effective date and approval record.
• Give staff a plain-language explanation.

11Keep a decision ledger beside the working plan

A checklist shows whether a task is complete; a decision ledger shows why the club chose the rule behind it. For each material choice, record the question, the approved answer, the approving role, the effective date, the source document or meeting, and any condition that would require another review. Keep the language brief enough that the people operating the process can use it.

The ledger is especially useful when reasonable people remember the discussion differently. It prevents a draft suggestion, an old exception, or a vendor demonstration from quietly becoming policy. If no authorized decision exists, mark the item open and name the person responsible for bringing it to the correct group. “Open” is a useful status; it is better than a confident answer nobody actually approved.

Include the decisions that feel obvious today. Staff changes, board turnover, and the pressure of a busy season can make an unwritten assumption expensive to reconstruct. A new employee should be able to see which rule applies, when it began, and where to ask for a change. Archive superseded versions instead of deleting them so the club can explain historical records under the policy that existed at the time.

Review the ledger from the perspective of club finance administrators and membership managers. The operational owner should confirm that the answer can be carried out. Finance should confirm how money or reporting is affected when relevant. The member-facing owner should confirm that the explanation is understandable. A short cross-role review often exposes a gap that a longer single-department meeting misses.

12Rehearse the handoff, not just the happy path

Choose one ordinary case and one difficult case, then let the people who will run the process complete it from beginning to end. Give them the approved rule and sample information, but do not coach every click or conversation. Watch where they pause, switch tools, ask for permission, or create a side note. Those pauses reveal where the operating design still depends on memory.

For the difficult case, change one condition that matters: a deadline has passed, a balance conflicts, an eligible person becomes ineligible, a staff member lacks access, or the expected record cannot be found. The purpose is not to surprise employees. It is to confirm that the process provides a safe next step when the routine path stops. Staff should know what they may decide, what they must escalate, and how to leave a useful record for the next person.

Ask another employee to pick up the saved result without hearing the rehearsal conversation. Can they identify the current state, the last decision, the responsible owner, and the next date? If they must call the original employee to understand the record, improve the labels, notes, ownership, or workflow before launch. A handoff is successful when context survives the shift change.

Repeat the rehearsal after a material correction. Testing the edited version matters because a fix in one place can create inconsistency somewhere else. Re-read the member message, account or work record, report, and staff instruction together. The club is ready when the same approved answer remains visible across the complete journey.

13Measure the first cycle without inventing a success story

Decide in advance what the club will observe during the first cycle. Useful measures may include incomplete cases, unresolved exceptions, repeat contacts, manual corrections, processing time, or the number of records waiting for an owner. Choose only measures that the club can define and collect consistently. A small trustworthy set is more useful than a dashboard filled with ambiguous counts.

Pair counts with a review of the underlying cases. A rise in questions may mean the message is unclear, the policy is new, or members are paying closer attention; the number alone does not identify the cause. Read representative records, talk with the employees doing the work, and separate a policy gap from a training need, a data problem, and a product defect before choosing a response.

Set a review date and an owner for each measure. During the review, keep completed changes separate from recommendations. Record what evidence supports the conclusion, what remains uncertain, and whether the next step requires management or board approval. Do not claim saved money, retained members, or better performance unless the club has a sound baseline and a method that supports that conclusion.

The most useful outcome of the first cycle may be a narrower rule, a clearer message, or a better exception route. Treat those corrections as part of operating the process, not as evidence the plan failed. A practical system makes learning visible and controlled while preserving the decisions that still apply.

14Connect the decision to one operating record

PoolPulse’s billing and payments workflow keeps dues, guest fees, snack bar charges, credits, payments, and household account context connected. Explore the relevant PoolPulse workflow .

A connected platform does not remove the need for policy, ownership, or judgment. It should make the approved rule easier to execute, keep the result beside the member or operating record, and give the next authorized person enough context to act. Ask to see the complete journey—including an exception—using sample information that matches the club’s real process.

For a related operating exercise, review every household credit before renewal .

15Choose the next step

Assign one person to complete the checklist, one person to review it from another role, and one date for the next decision. Keep unknowns visible. If a material question remains unanswered, make resolving it the next gate instead of treating silence as approval.

Bring your draft fee catalog to a PoolPulse walkthrough and test how each rule would appear from invoice to report. Schedule a personalized PoolPulse walkthrough . You can also review current PoolPulse pricing before the conversation.