Skip to content
Engagement & operations21 October 20263 min

Manual surveys and feedback collection in Skool

Before asking whether people like something, decide what the answers could change and how you will protect privacy.

Manual surveys and feedback collection in Skool

You can collect feedback about your Skool community through comment replies, voluntary messages, or an external form. First define the decision you need to make, then use a few neutral questions. This manual process does not depend on native polling or imply anonymity in channels that do not provide it.

Ask to decide, not to confirm

Write down the pending decision before preparing the questionnaire: keeping a format, changing a time, or simplifying a resource. Then ask about a recent experience and the obstacle encountered. Avoid “do you love our new session?” and do not combine quality, duration, and timing in one answer. Include “I have not used it” where appropriate. If you request a numeric rating, add an optional explanation and keep the scale consistent across reviews. Do not collect personal information that is unnecessary for the decision.

Choose the channel according to sensitivity

For low-sensitivity preferences, publish a question and count replies manually. For personal criticism, offer a private message or an external form with clear terms. Skool's official overview describes comments and chat; it does not make those exchanges anonymous. 1 If you use a form, check what information it actually records and explain who can access it and when it will be deleted. Do not promise anonymity if you collect emails, identifiers, or details that make a member easy to recognize.

Example: review an office-hours session

Imagine you need to decide whether to keep an office-hours session. Invite attendees and people who could not attend, but separate those experiences during analysis. The following questions provide a template. In a hypothetical calculation, if twelve of forty invited people respond, report “twelve responses from forty invitations,” not “the community thinks.” Respondents may not represent everyone else. Do not automatically treat the most frequent preference as binding if it conflicts with team availability or systematically excludes other members from the activity.

  • Did you attend the last session or read its summary?
  • What were you trying to resolve, and which part helped, if any?
  • What made attending or using it difficult?
  • If we could change one thing, what would you choose and why?

Close the loop with a visible decision

Group themes manually, preserve disagreements, and publish what will change, what will not, and why. Track invitations, responses, and agreed actions completed. Avoid repeating the same survey without acting or quoting identifiable criticism without permission. In the next review, ask about the specific change rather than general satisfaction that cannot be connected to the decision.

Explore PowerUpSkool features to support your community operations.

Continue

Sources and documentation

Frequently asked questions

Can I call a private message anonymous?

No. Private means it is not public, not that the sender's identity is unknown to you. Explain that difference before requesting sensitive feedback.

Turn this guide into work done in your community

PowerUpSkool reads your Skool community and shows you daily who is going quiet, which threads need replies and what message to send. Free to start; Pro with a 15-day trial.

Keep reading

Start free, no card

15 days of Pro whenever you want

Sign up