# The membership roster is the record to get right first

> Why one accurate roster beats a dozen spreadsheets, what a roster actually needs to track, and how to clean yours up without a big migration project.

Canonical page: https://priv-life.com/blog/membership-roster

Every membership organization already has a roster. Usually it has four — the secretary's spreadsheet, the email list, the dues ledger, and whatever the last officer left behind. None of them agree, and every job that touches people inherits the disagreement.

## Why the roster comes first

Almost everything an organization does starts with a question about people. Who can vote at the meeting? Who is covered by the insurance policy? Who gets the announcement? Who hasn't paid? Who is still certified?

Each of those questions is answered from whatever list is closest at hand, and the lists drift apart quietly. Someone joins and makes it into the email list but not the dues ledger. Someone resigns and gets removed from one spreadsheet out of four. Nobody notices until an election, an audit, or a renewal forces the lists into the same room.

The fix isn't a better spreadsheet. It's deciding that one roster is the roster — the single record other lists are generated from, never edited alongside.

## What a roster actually needs to track

Less than you'd think, and a few things people forget:

- **Identity and contact** — name, email, phone. The email matters doubly if members will ever sign in to anything: it's how a person proves a roster entry is theirs.
- **Membership type** — full, associate, junior, life. Types carry the rules: who votes, who pays, who counts toward quorum.
- **Status and dates** — active, lapsed, resigned, and *when*. Most disputes about a member's standing are really disputes about dates nobody wrote down.
- **The requirements attached to membership** — dues owed, certifications held and their expirations, hours served if your bylaws require them. These are what "in good standing" actually means, and if the roster doesn't hold them, standing gets decided by memory.
- **History** — when they joined, offices held, type changes. The roster is the organization's institutional memory about its people; a row that only shows today's state loses the story.

What a roster should *not* be is a place where every field is visible to every member. Contact details, dues balances, and certification records deserve narrower visibility than "the whole roster can see everything" — decide who sees what on purpose.

## Cleaning up without a migration project

If your lists disagree today, resist the urge to reconcile everything before you start. A workable sequence:

1. **Pick the most trusted list** — usually the dues ledger, because money gets attention — and make it the seed.
2. **Import it once**, then treat every other list as a source of corrections, not a second import. When two lists disagree about a person, the roster's version wins after someone decides; nobody edits both.
3. **Let members verify themselves.** The fastest way to find stale entries is to ask people to claim their own record — a bounced email or an unclaimed entry is a lead worth following.
4. **Retire the old lists visibly.** Announce that the spreadsheet is frozen, link to the replacement, and generate any list anyone needs — mailing labels, sign-in sheets, the audit copy — from the roster instead.

---

<div class="tryIt"><p><strong>Priv Life Members</strong> is a roster built this way: one record per person, membership types with their own rules, good standing computed from dues, hours, and certifications rather than remembered, and field-level visibility you control. It's free for your first 100 members. <a href="/apps/members">Explore Members →</a></p></div>
