UK edition. This guide is written for volunteer-run clubs in the UK. Where rules differ — grants, tax, incorporation, safeguarding — follow the UK-specific pointers below or check with your national body.
A man arrives at the Tuesday help desk with a surname, a rough date and one immovable certainty — his great-grandfather was a sea captain. Ninety minutes later the certainty is gone, replaced by a shipping clerk, a second marriage nobody mentioned and a much better story. He goes home delighted, joins that week, and tells four people. That single interaction is worth more to the society than any amount of advertising, and it happened because a trained volunteer sat down with a stranger and knew which index to open first.
That is the thing a genealogy society has that the big subscription databases do not: people who know the local records, indexes that exist nowhere else because your members made them, and the judgement to tell someone gently that the family tree they found online is somebody's guess. It is also, awkwardly, an organisation whose day-to-day work involves other people's family data — including living people — which puts a privacy obligation on a volunteer committee that most community clubs never have to think about.
This guide is written for the committee of a family history or genealogical society. It covers running a help desk without burning out your researchers, building a paid research service with defined edges, indexing projects that survive the person who started them, publishing member-contributed data safely, and the consent and privacy questions that sit underneath all of it. Where the law is involved it is general information only — your national privacy regulator is the authority, not a guide.
What the society offers that a search box cannot
| Service | What it really is | What it costs the society | What it returns |
|---|---|---|---|
| Help desk | Trained volunteers giving an hour of guided searching | Roster hours, a room, a screen | New members, word of mouth |
| Local indexes | Records nobody has transcribed, made searchable by members | Years of volunteer hours | Distinctiveness, and enquiry income |
| Library and subscriptions | Shelf holdings plus paid database seats members share | The largest recurring budget line | Renewals — this is the retention hook |
| Education and mentoring | Beginner courses, special interest groups, one-to-one help | Preparation time, a venue | The next generation of volunteers |
Notice what is not on that list: raw record access. Trying to compete with commercial databases on volume is a losing proposition, and societies that frame themselves that way struggle to explain why anyone should subscribe. Frame it the other way — the society is where you go when the search box has stopped working — and every one of the four services above becomes an obvious reason to belong.
Running a help desk without burning out your researchers
The help desk is the society's front door and its most fragile resource, because it depends on a handful of experienced people whose time is finite. Structure protects them.
- Fixed sessions, fixed length. A published weekly or fortnightly slot with 45-minute appointments beats an open-door policy. Appointments mean the volunteer knows when the session ends, and the visitor takes it seriously.
- Take a booking with preparation questions. A short form before the session — who are you looking for, what dates and places, what do you already have, what have you already tried, what would a good outcome look like — halves the time wasted on ground the visitor has already covered, and lets you match the enquiry to a volunteer who knows that district.
- Publish the scope. State plainly what a help desk session is: guidance, orientation to the right records, and a plan. It is not a free research service and it does not build somebody's tree for them. Written down, that line is easy to hold. Improvised in the moment, it never is.
- Roster two people. One works with the visitor, one handles walk-ins, phones and the photocopier. A single volunteer alone with a queue is how you lose a volunteer.
- Record the outcome, not the conversation. A one-line note — enquiry type, district, records used, outcome, whether they joined — takes twenty seconds and gives the committee real numbers at the end of the year about what the society is actually doing.
- Have a graceful escalation. When an enquiry is genuinely a research job, say so on the spot and hand over the commissioned research form. Nobody is offended by being told their question is a big one.
Rotate new volunteers in as the second person on the desk for a season before they take enquiries alone. It is the fastest training there is, and it quietly builds the succession plan that most societies discover they need at the worst possible moment. Our guide on recruiting club volunteers has more on slicing roles small enough that working-age people can take one.
A paid research service with edges
Sooner or later the enquiries arrive from people who are never coming to the room — often from overseas, often with an ancestor who left your district a century ago. A commissioned research service turns those into income instead of guilt. It only works if it has hard edges.
Set it up with four decisions made in advance:
- What is free and what is paid. A common structure is a free short look-up — one name in one index, answered by email — and a paid commissioned search charged by the hour with a stated minimum and a cap the client agrees before work starts.
- You charge for the search, not the result. Say it plainly in the terms and repeat it in the acknowledgement: a thorough search that finds nothing is a real result and is billable. Societies that only charge on success end up doing free work on the hardest cases.
- What the report contains. Agree a standard shape — what was asked, what sources were searched (including the ones that produced nothing), what was found with a full citation for every item, images or transcripts as agreed, and a short "where to go next" section. The negative results are what stop a client paying twice for the same search.
- Who does the work and what they are paid. Whether researchers are volunteers, are paid a share, or donate their share back, write it down. The most common source of friction is a volunteer who also runs a private research business — publish a simple conflict-of-interest rule rather than discovering the problem after a complaint.
On fees, societies in the UK typically quote an hourly rate in pounds with a minimum of an hour or two, plus disbursements for certificates and record office copies. Publish the rate, the minimum, the cap and the disbursement policy, and note that overseas clients often prefer a fixed-fee first stage before committing to more.
Indexing projects that outlive the person who started them
Indexes are the most valuable thing a society builds, and the most commonly lost. The failure mode is always the same: one dedicated member transcribes a parish register onto their own computer for six years, and then moves, or dies, and the file is in a format nobody can open on a laptop nobody can unlock.
Run every indexing project with the same five disciplines:
- Get permission in writing from whoever holds the records. Custodians will usually agree, but they may attach conditions about publication, attribution or commercial use. Sort that out at the start, not when you are ready to publish.
- Transcribe what is written, not what you think it means. Record the spelling on the page. Put your interpretation in a separate field.
Smyth [Smith?]is useful; silently correcting it destroys the evidence and makes the index unsearchable for the people who need it most. - Agree a field schema before anyone types a row. Changing the columns halfway through a project is what turns two years of work into a merge problem.
- Verify, do not trust. Double-keying — two people transcribe the same page independently and a script compares them — is the gold standard. Where that is unaffordable, sample-check a fixed percentage of every volunteer's batches, and check every batch from a new volunteer for their first few sessions.
- Store it centrally from day one. The working file lives somewhere the committee controls, with versions and a backup, not on a member's desktop. Assign a project owner and a deputy on the day the project starts.
A workable minimum schema for most record types:
| Field | Example content | Why it is there |
|---|---|---|
| Source reference | Register 4, page 112, entry 3 | Lets anyone go back to the original |
| Record date | 1873-04-11 (or "1873, month unclear") | Searchable, with uncertainty preserved |
| Surname as written | Smyth | The evidence |
| Surname standardised | Smith | Makes the index findable |
| Given names | Mary Ann | As written, with variants noted |
| Event type | Baptism | Filters |
| Place | Parish and district | The society's core value |
| Other parties | Father, mother, spouse, witnesses | The links people are actually looking for |
| Notes | Marginal annotations, damage, illegibility | Where the real finds hide |
| Transcriber and date | Initials, 2026-05-03 | Accountability and query resolution |
Decide the publication model before the project finishes, because it changes how you build. Free and open builds goodwill and search traffic. Members-only makes the index a membership benefit. A middle path many societies use — a free searchable name index that returns a hit, with the full transcript available to members or for a small fee — gets you both the discoverability and the reason to belong.
Publishing member-contributed data
Member trees, submitted pedigree charts, family notes and DNA match lists are generous gifts and genuine hazards. Three rules keep them safe.
The living-person rule. Nothing identifying a living person gets published without that person's consent. In practice most societies apply a simple test — if the individual is known to be living, or cannot be shown to have died, their details are suppressed to name only, or omitted entirely. Apply it to the whole record, not just the name, because a birth date and a town is identifying on its own.
A contribution needs a licence, not just a file. When a member submits research, record what the society may do with it — publish online, include in an index, pass to another researcher, or nothing at all — and get it in writing. A one-line contribution statement on your submission form covers it.
Corrections are a process, not a favour. Publish how someone asks for something to be corrected or removed, who decides, and how long it takes. Two members will eventually contradict each other about the same ancestor, and the answer is never to pick a winner: publish both readings with their sources, note the conflict, and let the evidence speak.
DNA deserves its own line in your policy. Match lists, ethnicity estimates and shared-match screenshots identify living relatives, sometimes reveal misattributed parentage, and are not yours to republish. Support DNA questions at the help desk by all means, but keep results out of anything the society publishes.
Privacy and consent, in general terms
A genealogy society holds three separate pools of personal information: member records, enquiry and client records, and research data about third parties who never contacted you. All three deserve a written policy, and the club privacy policy template is a sensible starting point to adapt.
Practical habits that satisfy most frameworks without a solicitor: collect only what you need and say why on the form; store member and client records where only the committee roles that need them can look; set a retention period and actually delete; get explicit consent for photographs at meetings and for publishing a member's contact details in a journal; and know who in the committee is responsible if someone asks what you hold about them. Where you keep sensitive material — health information in a family record, anything about a child — treat it as a higher-care category and limit access further.
UK GDPR and the Data Protection Act are the framework, and the Information Commissioner's Office publishes small-organisation guidance, a self-assessment checklist and a registration process most societies handling this volume of data will need to consider. Lawful basis, retention and subject access requests are the three areas to get right first.
The names of the core records also differ, and getting the terminology right on your website matters more than it sounds — it is how people find you.
Civil registration of births, marriages and deaths runs through the General Register Office, with historical indexes searchable and certificates ordered from the registry. Parish registers, wills, estate papers and land records usually sit in county or diocesan record offices, and the national archives holds the major state series including census returns.
Meetings, courses and special interest groups
The society's program is what converts a one-off help desk visitor into a member who is still there in five years. Three formats do most of the work.
Monthly meetings with a speaker, a fixed date and a hard finish. Stream or record them where you can — the members who cannot drive at night, and the ones researching your district from the other side of the world, are a real and growing part of most societies.
A beginner course, run once or twice a year over four to six sessions: starting with what you already have, then civil registration, then census-type records, then parish and church records, then online sources and how to evaluate them, then citing and organising what you find. Charge for it, discount it for members, and finish with an offer of a mentor. This course is the single most reliable recruitment tool a genealogy society has.
Special interest groups — a district, a migration route, a surname, DNA, writing up your research — meeting less often and running themselves. Each one needs a convenor and a place to talk between meetings; a members-only chat space does that job better than a mailing list, and keeps the conversation searchable for the next person with the same question.
Turning the enquiry pile into a queue
Most of the administrative pain in a genealogy society comes down to intake and follow-through. Help desk bookings, commissioned research briefs, index transcription sign-ups, membership renewals and the volunteer roster all arrive by email, get answered by whoever sees them first, and live in one person's inbox. ClubHelix replaces that with forms that feed a shared inbox — a help desk booking form, a research commission form, a data contribution form with the consent wording built in — plus online membership and renewals, a members-only discussion space for your interest groups, and reports that tell the committee how many enquiries came in, from where, and what they turned into.
The free tier is enough for a small society to move its enquiry handling off email this month. It is built and hosted here, with the pricing published openly and no per-member surprises, and a volunteer can set your society up online between two committee meetings.
Frequently asked questions
What does a genealogy society do?
It helps people research their family history through help desks, meetings, courses and mentoring; it builds and publishes indexes to local records that are not available anywhere else; it maintains a library and shared subscription access; and it usually offers a paid research service for enquiries that arrive from a distance. The volunteers and the local knowledge are the product.
How do you run a family history help desk?
Book fixed-length appointments rather than running an open door, ask preparation questions when the booking is made, roster two volunteers so nobody is alone with a queue, and publish the scope so everyone understands it is guided searching rather than free research. Record a one-line outcome for every session so the committee can see what the desk is actually doing.
Should a genealogy society charge for research?
Yes, for commissioned work. Offer a free short look-up so nobody is turned away, then charge an hourly rate with a minimum and an agreed cap for anything larger, and make clear that the fee covers the search rather than a guaranteed result. Set the member rate below the public rate so membership pays for itself.
How should a society handle privacy for living people?
Publish nothing identifying a living person without consent, suppress or omit their details in indexes and published trees, get written permission covering how contributed research may be used, and keep DNA match information out of anything you publish. Write it into a privacy policy, set retention periods, and follow your national privacy regulator's guidance for small organisations.
How do you keep an indexing project going after the founder leaves?
Store the working file centrally where the committee controls it, agree the field schema before transcription starts, name a project owner and a deputy on day one, and keep versioned backups. Projects that live on one volunteer's personal computer are lost eventually — not because anyone intends it, but because life happens.
Keep reading — how to run a historical society if your collection is growing beyond paper, and how to run a member survey when you need to know what members actually want from the program.
