Skip to main content
OpenCommunity logo

OpenCommunity

Log in
Members & participants

Published June 10, 2026

· Updated September 4, 2026

What Participant Information Should You Collect?

Collect only what serves a clear purpose, not what might be useful someday. Here is a purpose-first guide to participant information for community programs.

Key takeaways

Collect information only when you can name the purpose it serves, not in case it is useful later.

Basic contact details suit most programs; sensitive details need a clear reason and extra care.

Explaining why you ask, and protecting what you keep, is part of collecting well.

Start with why you are asking

The best guide to what you should collect is a simple question: why do we need this? If you can name the purpose, whether it is contacting a participant, planning a program, or meeting a specific funder requirement, the field probably earns its place. If the honest answer is that it might be useful someday, it usually should not be collected.

This purpose-first habit keeps forms short, respects participants, and aligns with your privacy basics.

The usual basics

Most programs run well on a small set of basics.

  • A name, and how the person prefers to be addressed.

  • One reliable way to reach them, if you need to.

  • The program or programs they are joining.

  • Anything essential for safety, such as an emergency contact where appropriate.

Notice how little that is. Many organizations collect far more than they use.

Collect sensitive details with care

Some programs genuinely need more sensitive information, such as age ranges, languages, newcomer status, or accessibility needs. These can help you serve people better and may be required for certain funding. When you collect them, do so with care.

  • Ask only for what a real purpose requires.

  • Make sensitive fields optional wherever you can.

  • Offer inclusive, respectful response options.

  • Explain why you are asking, briefly and plainly.

When the participant is a child, there is a further question: who is actually agreeing to any of this. Consent for a child usually comes from a parent or guardian, and BC decides that by capacity rather than by a fixed age.

What not to collect

Some information is better left uncollected unless a specific, current purpose demands it. Gathering sensitive details just in case creates risk without benefit, and can make cautious participants, including newcomers, less willing to take part. When in doubt, leave it out, and revisit only if a genuine need appears. This matters most for children's records, where collecting less is the main safeguard.

Explain it and protect it

Collecting well is not only about which fields you include. It is also about being open and careful. Tell people what you collect and why, keep it only as long as you need it, and limit who can see it. The companion guide, explaining data collection to participants, covers how to say this simply.

Note: This article is general information only and is not legal, financial, or professional advice. For questions about your organization's obligations, consult a qualified professional or the relevant government resource (for example, the CRA for registered charity matters, or your provincial or territorial registry for nonprofit governance).

Frequently asked questions

What information should a community organization collect?
Collect what serves a clear purpose: usually a name, one way to reach the person, and the programs they join. Add sensitive details only when a real need, such as a specific funder requirement, justifies them.
Should we collect demographic information?
Only when you have a genuine purpose, such as serving people better or meeting a funding requirement. Make such fields optional where possible, explain why you ask, and avoid collecting sensitive details just in case.
Is it better to collect more information to be safe?
No. Collecting more than you use creates risk and can make participants, especially newcomers, less willing to take part. A short, purposeful form is usually both safer and more welcoming.
How long should we keep participant information?
Keep it only as long as it serves the purpose you collected it for, unless a rule requires longer. Retention is a topic on its own, and worth setting a simple schedule for.

Trying to make your centre run more smoothly?

OpenCommunity helps neighbourhood houses and family centres manage sign-in, programs, and attendance in one place.

Note: This article is general information only, not legal or professional advice.

Members & participants

Protecting Children's Personal Information in BC Programs

Community programs collect a lot about children. Here is what counts as their personal information and what BC's privacy law expects you to do with it.

9 min read

Read
Members & participants

How to Explain Data Collection to Community Members

People share more willingly when they understand what you collect and why. A plain-language guide to explaining data collection with respect.

5 min read

Read

Ready to simplify your centre's admin?

OpenCommunity helps neighbourhood houses and family centres manage sign-in, programs, and attendance in one place.

OpenCommunity logo

OpenCommunity

Simplicity, purpose-built for local communities.

Product

FeaturesWho it's forHow it worksFAQBlogCustomer stories

© 2026 OpenCommunity

Built with love in Vancouver, BC