Genealogy society member upload guidelines for digitized records

Your county genealogical society runs on volunteer hours. Members mail thumb drives, email ZIP files, and post phone photos in the Facebook group. Each upload carries a different filename, a different resolution, and a different story about who owns the paper. Without member upload guidelines, the web chair spends weekends renaming IMG_4821.jpg and guessing whether Aunt Ruth gave permission to publish Uncle Henry’s baptism record. A short society policy fixes intake before anyone argues about privacy or quality. This article is for board members, records chairs, and web volunteers who set rules for contributed scans. It covers consent, file standards, review queues, and where genealogy OCR fits as a draft step. For family-level digitization how-tos, see the related guides linked at the end. For the product stack, see Genealogy and family archives.

Why member uploads stall local genealogy societies

A successful call for materials often creates a backlog faster than your transcription team can open files. One member sends fifty JPEGs from a reunion binder. Another forwards a PDF exported at screen resolution. A third uploads a marriage register page that includes a living granddaughter’s address in the margin. Volunteers burn out sorting instead of indexing.

Societies differ from solo family projects. You publish on a society site, a chapter newsletter, or a shared drive that outlives one researcher’s laptop. Members assume “the society has it” means permission to quote names in a meeting handout. Without written rules, officers inherit arguments about copyright, living people, and image quality.

The fix is policy before promotion. Tell members what to scan, how to name files, who reviews uploads, and what never goes online. Policy does not kill enthusiasm. It channels energy into records the society can actually use and cite.

Boards that skip this step often reopen the same debate every election cycle. New web volunteers inherit mystery folders. A one-page guideline plus a simple intake form costs less than one evening of cleanup.

What belongs in a society member upload policy

Treat the policy as an operations sheet, not a legal treatise. One or two pages in plain English. Post it on the society website and link it from every “contribute records” call.

Cover six blocks: who may contribute, what document types you accept, technical standards for files, consent and privacy, the review path, and how long you keep submissions. Name a contact role (records chair or web volunteer) so members know where to send questions.

State what the society does with uploads. Many chapters keep a master archive on a society-owned drive and publish only approved extracts on the public site. Say that clearly. Members who think every emailed photo will appear on the homepage will hesitate less when expectations match reality.

Link your policy to meeting minutes when the board adopts it. A dated PDF in the members-only area beats a blog post that disappears after a platform change.

Minimum fields on the intake form

Require these fields on every submission, even informal ones:

• Contributor name and membership status (member, guest, institutional partner)
• Relationship to the material (owner, descendant, custodian with written permission)
• Description of each item (document type, approximate date, place, family surnames)
• Source of the physical item (private collection, courthouse copy, funeral program, etc.)
• Permission checkbox: publish on society site, members-only archive, or research use only
• Living people named in the document (yes/no; if yes, list for redaction review)

Optional but useful: GEDCOM match, cemetery name, parish, or project tag (Smith-bible-2026). Structured intake saves volunteers from opening every file to learn what it is.

Who may contribute and who holds copyright

Societies usually accept member contributions, non-member donations with documented permission, and copies of public records members photographed at a courthouse. They should refuse uploads where the contributor cannot explain custody or rights.

Copyright on old registers and published county histories often sits with the publisher or archive, not the person who photographed a page. Your policy should say the society indexes and shares under fair use or license terms the board defines with counsel when needed. It should also say the society removes material on valid takedown request.

Guest lecturers and cemetery walk participants are not automatic members. If they email photos after an event, route them through the same form as everyone else.

File formats, resolution, and naming members should follow

Standardize formats so volunteers batch-process instead of fighting odd exports. For page images, prefer lossless TIFF or high-quality JPEG at 300 dpi equivalent for typed or printed text. For handwritten letters and registry pages, 300–400 dpi at full page width is a practical target. PNG works when members export from a phone editor without recompressing to mush.

Accept PDF when the member already has a multi-page scan, but ask for one document per PDF when possible. Mixed shoebox PDFs with twelve unrelated families force manual splitting.

Naming convention example: YYYY-MM-DD_place_doctype_surname_page01.jpg. At minimum: surname_doctype_year.jpg. Ban bare scan001.jpg in the policy text even if you still receive some.

List maximum file size and total batch size so the web host and volunteer inboxes survive. If you use a form upload, test it on a slow phone connection before you announce the drive.

Phone photos versus society scanner

Many members will never visit the library scanner. Permit phone photos when they meet quality rules: full page in frame, even light, no finger shadow on names, camera parallel to the page. Link members to Phone camera tips for better OCR from your policy page.

Reserve society scanner sessions for bound volumes, oversize maps, and fragile items members should not flatten at home. For handling rules on brittle paper, point volunteers to Scan fragile papers without a flatbed without copying that walkthrough into your policy.

When a member brings a shoebox to a work day, scan to society standards on site and hand back a USB copy. That single step trains the format you want for the archive.

Batch uploads and folder structure

Ask contributors to zip one family or one project per archive, not one zip with every cousin’s wedding program since 1970. Inside the zip, use folders: Johnson-letters/, Johnson-census/.

If you run a shared Google Drive or similar, create an incoming/ folder with write-only access for members and a review/ folder volunteers move approved sets into. Never let the public site pull directly from incoming/.

Document who renames noncompliant files. Either the records chair fixes names or the upload returns with a polite template email citing the policy section.

Consent and privacy before anything goes public

Genealogy societies handle sensitive facts: adoptions named in obituaries, maiden names, church membership, military service, and addresses on twentieth-century forms. A member upload policy must separate collection from publication.

Collect broadly if your bylaws allow research use, but publish narrowly. Default new uploads to members-only or officer review until a named volunteer approves public display. Read Is it safe to upload documents online with your web team before you add a browser upload form. HTTPS and a reputable processor reduce risk; they do not replace consent rules.

Tell members you delete email attachments from officer inboxes after transfer to the society drive when possible. Personal Gmail is not an archive. If you use a third-party OCR tool for draft text, confirm retention matches your promise. Toolsy deletes uploads within about an hour after processing; that suits draft transcription, not long-term storage.

Living people and redaction rules

Adopt a living-person rule the board can defend: no publication of documents that name living individuals without written consent, or redact those lines before display. Obituaries after a stated embargo years (many societies use 25–50 years for address details) are a common compromise. Your mileage varies; write the number down.

Train reviewers to scan margins and reverse sides. Funeral programs and family sheets often list living nieces and nephews. Redact in the published copy; keep an unredacted preservation copy in the restricted archive if policy allows.

When in doubt, hold the upload. A delayed page beats a privacy complaint that reaches the county paper.

Where uploads land (email, drive, website form)

Email is easy and messy. Use it only with size limits and a single intake address forwarded to two officers. Drive folders scale better for batches. Website forms need spam protection and a confirmation email that repeats consent checkboxes.

Pick one primary channel per year and stick to it. Members ignore “you can send it anywhere” instructions.

If the society embeds an upload widget on its site, the society account pays for usage and sets allowed domains. See Embed an OCR widget on your site when you outgrow email. Until then, drive plus form fields is enough for most chapters.

Review workflow for volunteer transcribers

Upload guidelines fail without a review queue. Assign a small team: intake reviewer (format and completeness), transcription reviewer (names and dates), and publication approver (what touches the public site). One person may wear two hats in a small chapter; still write the hats down.

Intake reviewer checks filenames, form fields, and obvious privacy flags within a week of upload. They bounce incomplete packages with a template reply. Transcription reviewers work from approved images only.

Set a service standard members can expect: “We acknowledge within two weeks; publication may take several months.” Under-promise. Genealogy volunteers have day jobs.

Track status in a simple sheet: received, in review, transcribed, published, returned to contributor. A Trello board or spreadsheet column beats sticky notes on a library cart.

First pass versus publication sign-off

First pass confirms the scan is readable and metadata matches the image. Volunteers note language (English, German church book), script type (typed, cursive, Gothic), and damage (fold tear through a date).

Publication sign-off compares transcript to image line by line for anything on the public site. Indexes can be less strict than narrative quotes if your site separates “index fields” from “full text display.”

Never skip sign-off because OCR “looked fine.” Software confuses n and u in old hands. Society credibility rests on the volunteer who caught it.

Handling illegible lines and [?] markers

Policy should require transcripts to mark uncertain readings with [?] or [[illegible]], not silent guesses. Publish those markers in draft member areas; clean them for public indexes only when a second reviewer agrees on a reading.

When a line stays illegible, describe it (“signature line, unreadable”) instead of inventing a name. Future researchers may compare a sharper scan.

For Gothic or heavily abbreviated parish entries, pair a novice transcriber with an experienced script reader. OCR output can seed the draft; it does not replace expertise on reading old handwriting in English archives.

Genealogy OCR as a draft step on society projects

Genealogy OCR helps societies scale indexing when volunteers type the same register page three times because three members photographed it. Run OCR once on the best scan, distribute the draft transcript to indexers, and require verification against the image before the row goes live.

Toolsy’s Historical Manuscript tool targets old handwriting and family papers. It is a Pro desk tool (subscription required on the current site). Output is a searchable draft. Old script, bleed-through, and torn corners produce more [?] marks. The society’s publication standard still demands human review on originals.

Workflow for a church register project: society scans to TIFF on work days, officers upload the clearest page to Historical Manuscript, volunteers correct names and dates in a shared sheet, publication approver spot-checks every tenth line and all surnames on the public index.

For API volume across a year-long digitization push, a club can share one API Starter key per the genealogy solution page hints. Forty free recognitions per month after sign-up lets you test on real society pages before you commit. Files are not kept as an archive; store images on the society drive.

OCR does not replace photography standards. Garbage focus in means garbage text out. Train members first; add OCR after intake quality stabilizes.

Do not OCR living-person records through public tools on personal accounts if your policy forbids it. Run restricted material on society-controlled machines and drives.

Documents and uploads your society should refuse

Clear refusals protect volunteers and members. Refuse uploads when the contributor lacks permission from the record custodian, when the item is a recent medical or school record with living subjects, or when the sole content is a paid database screenshot that violates terms of service.

Refuse bulk Ancestry or newspaper site exports you are not licensed to redistribute. Index facts you extracted by hand; do not republish paywalled page images.

Refuse original one-of-a-kind artifacts shipped by mail without a loan agreement. Societies are not conservation labs. Offer scan-on-site days instead.

Refuse “fix my tree” requests with no source images. Your society is not a research service unless bylaws define one.

When you must decline, use a short, kind template citing the policy section. Offer alternatives: bring the item to a scan day, fill a restricted research request, or donate a citation only.

Frequently asked questions

What should a genealogy society member upload policy include?

A usable policy names who may contribute, accepted document types, file format and naming rules, consent checkboxes, the review queue, and what happens to files after acceptance. It should name a contact role and distinguish members-only archives from public pages. Keep it to one or two pages so officers can link it from every recruitment email. Update the date when the board votes changes.

How is a genealogy society upload policy different from FamilySearch rules?

FamilySearch runs a global platform with its own contributor agreement, quality standards, and temple-related restrictions. Your local genealogical society sets rules for your site, newsletter, and chapter drive. You may accept the same scan FamilySearch would reject for naming reasons, or refuse publication FamilySearch would allow because a living cousin objected. Align spirit with major platforms when you can; do not assume one click uploads everywhere.

What file format should members use for genealogy society uploads?

Prefer 300 dpi equivalent JPEG or TIFF for page images, one logical document per file when possible, and PDF only when pages already belong together. Ban anonymous names like scan001.jpg in writing. List max file size so volunteer inboxes survive. Phone photos are fine when the page is flat, fully framed, and evenly lit.

Can genealogy societies use OCR on member-submitted scans?

Yes, as a draft step on images you have rights to process. Toolsy Historical Manuscript (Pro) turns photos of old handwriting into searchable text volunteers must verify. OCR speeds indexing; it does not certify accuracy for publication. Run OCR on society-owned copies after consent review, not on mystery email attachments you have not classified.

Is it safe for members to upload historical documents online?

Upload only through HTTPS forms or drives you control, with a clear privacy statement. Third-party OCR tools should delete files after processing if you do not want vendor retention. Read Is it safe to upload documents online before you add a public upload page. Train members not to post full register pages on open social media when margins list living relatives.

How do societies handle living people in contributed records?

Most chapters adopt a written rule: no public display of documents naming living people without consent, or redact those lines first. Reviewers check margins, reverse sides, and funeral programs for niece and nephew lists. When uncertain, hold publication. Restricted archives for members-only research are a common middle ground if the board approves access controls.

Who reviews member uploads before they go on the society website?

Split roles: intake reviewer (format and forms), transcription reviewer (names and dates), and publication approver (public display). Small societies may combine roles but should still document who signed off. Nothing goes from incoming/ to the public CMS without a second human comparing text to image for quoted material.

What uploads should a genealogy society refuse?

Refuse material the contributor cannot permission, paid database screenshots, recent records with living subjects you will not redact, and unique artifacts sent by mail without loan terms. Refuse bare Ancestry tree exports with no sources. Decline with a template that cites policy and offers scan-day alternatives.

Does genealogy OCR replace volunteer transcribers?

No. OCR replaces repetitive typing on clear scans of hard script. Volunteers still resolve ambiguous letters, archaic abbreviations, and damaged lines. Society indexes published under your chapter name need human sign-off. Treat OCR like a fast first draft, not a finished cemetery book transcription.

How long should a society keep member uploads?

Separate processing retention from archive retention. OCR tools like Toolsy delete uploads within about an hour after processing; your society drive holds the canonical scan per board policy. Say whether email copies are deleted after transfer. Tell members if you purge incoming/ after six months once items are cataloged. Long-term preservation belongs on society storage you backup, not a volunteer’s personal cloud.

For family-level letter digitization, see Digitize family letters for genealogy. For turning a household shoebox into a searchable archive, read Shoebox to searchable family archive. For fragile paper handling at scan days, use Scan fragile papers without a flatbed.