
Module 11
Member Lists & Data Privacy
17 min read
To equip Local Secretaries, Treasurers, and administrators with the technical skills and legal knowledge to clean, reconcile, and securely manage membership lists — distinguishing employer-provided dues data from card-carrying members in good standing while maintaining absolute data privacy under constitutional guardrails.
- Know: The strict terms of the **Membership List Directive**; the legal distinction between a dues payer under the **Rand Formula** and a card-carrying member in good standing with voting rights.
- Feel/Understand: Extremely protective of members' private contact details; aware that membership lists are a sacred union trust that must never be shared with outside political, commercial, or factional interests.
- Be Able To: Process and clean raw CSV reports from the employer; execute targeted sign-up outreach to convert dues payers into active voting members; store and edit local databases on encrypted, union-controlled systems with strong access controls.
Self-test at the end
This module includes a quiz after the reading. Use Jump to Quiz above when you are ready — a perfect score marks it complete.
Payroll rows are not voting members until cards are signed and stored off employer systems.
How to use this module
Allow 35–45 minutes. Read with your local bylaws, a recent employer dues report (CSV or spreadsheet), your signed-card roster, and access to your local's secure member database — not employer email. Sections move from Rand Formula vs. card-carrying members through the Membership List Directive, monthly reconciliation, and secure storage.
Pair with `/guide/membership-signup` for card-signing campaign craft — that guide teaches the floor pitch; this module teaches secretary reconciliation, constitutional privacy rules, and database hygiene. CLC membership administration materials and CUPE local secretary handbooks reinforce list custody; Unifor local officer training treats member data as a fiduciary trust.
💭 Reflection
Reflection: A dues payer who never signed a card pays for solidarity — but cannot vote until they join democratically. Your list work turns payroll rows into an organized membership.
To equip Local Secretaries, Treasurers, and administrators with the technical skills and legal knowledge to clean, reconcile, and securely manage membership lists — distinguishing employer-provided dues data from card-carrying members in good standing while maintaining absolute data privacy under constitutional guardrails.
- Know: The strict terms of the Membership List Directive; the legal distinction between a dues payer under the Rand Formula and a card-carrying member in good standing with voting rights.
- Feel/Understand: Extremely protective of members' private contact details; aware that membership lists are a sacred union trust that must never be shared with outside political, commercial, or factional interests.
- Be Able To: Process and clean raw CSV reports from the employer; execute targeted sign-up outreach to convert dues payers into active voting members; store and edit local databases on encrypted, union-controlled systems with strong access controls.
1. The Dues Report vs. the Signed-Up Membership List
One of the most common errors a new Local Secretary makes is assuming everyone on the employer's dues deduction report is a voting union member.
- The Rand Formula: Under Canadian labour law, because all employees in a bargaining unit benefit from the collective agreement, they must pay union dues — whether or not they have signed a membership card.
- The distinction: Paying dues does not make an employee a signed-up member in good standing. Under union bylaws, a worker must sign a physical or digital membership card to obtain the right to vote on contracts, attend general meetings, run for office, or vote in local elections.
- The Secretary's duty: Cross-reference the employer's monthly dues report against the local's database of signed cards. Anyone paying dues without a card belongs on a sign-up target list — not on the voting roll.
CLC organizing education and national union membership materials both stress: the payroll file is a dues file, not a democracy file. `/guide/membership-signup` walks card-signing campaigns; this module owns the reconciliation math behind those campaigns.
| Record type | Source | Grants voting rights? | Secretary action |
|---|---|---|---|
| Dues payer (Rand) | Employer payroll report | No — until card signed | Flag for sign-up outreach |
| Card-carrying member | Local signed-card database | Yes — if in good standing | Verify classification & contact |
| Member in arrears | Cross-check dues % vs. hours | Suspended per bylaws | Notify member; fix deduction |
| Terminated / transferred | Employer status column | No | Archive; update roster |
💡 Note
Note: A worker who signed a card ten years ago but whose dues stopped during a leave may show on payroll inconsistently — reconciliation catches both missing cards and missing deductions.
2. The Membership List Directive & Data Privacy
Union membership lists are highly sensitive constitutional documents. The Membership List Directive — adopted across many Canadian unions as a binding constitutional privacy practice — mandates strict security guardrails regardless of which national body your local affiliates with.
- Commercial use: Sharing, selling, or leasing a membership list with any commercial partner — even an affinity discount vendor — is a serious constitutional offense. Members join a union, not a marketing database.
- Political campaigns: Locals cannot release lists to municipal, provincial, or federal candidates or parties, even when the union formally endorses them. All outreach must be conducted internally by the local itself through union channels.
- Employer access: Never store, send, or edit membership lists on employer-controlled servers (Microsoft 365, Google Workspace at work, Slack, Teams, Outlook). Employers may legally monitor their networks — which destroys member privacy and union independence.
- Internal factions: Releasing selective contact lists to one slate in a local election without constitutional authority violates the same trust as releasing to outsiders.
❗ Warning
Warning: Password-protecting a folder on the employer's OneDrive is not secure storage — it is employer-accessible data with a cosmetic lock.
CUPE secretary guidance and OFL local administration workshops both repeat: if a third party asks for your list, the answer is almost always no — then design an internal communication plan instead.
📝 Practice
Practice: Draft a one-paragraph refusal script for a political campaign manager who requests member phone numbers. Name the internal alternative (union email, GMM announcement, steward handouts).
3. Database Cleansing & Reconciliation
Raw Excel or CSV sheets from employer payroll departments are notoriously messy. The Local Secretary should audit these files monthly — not once a year before an election.
Monthly reconciliation workflow
- Import the employer dues report into your union-controlled database (never the employer's cloud).
- Match employee ID or name + classification against signed-card records.
- Flag dues without card, card without dues, and classification mismatches.
- Export a sign-up target list for stewards (`/guide/membership-signup`).
- Log changes in a reconciliation journal — who imported, when, and what discrepancies were found.
Common data hygiene fixes
- Incorrect classifications: Employers often mislabel full-time workers as temporary or part-time to avoid benefit obligations. Cross-reference dues sheets with collective agreement classifications — errors become class-action grievance evidence.
- Arrears detection: Verify the correct percentage of dues is deducted for every hour worked. Modified duties, short-term leaves, and retroactive pay adjustments are frequent failure points.
- Address and contact drift: Home addresses on payroll may be outdated; steward site visits and sign-up drives need current phone numbers stored only on union systems.
- Duplicate rows: Mergers, name changes, and rehires create ghost records — deduplicate before any mail merge.
| Discrepancy | Likely cause | Floor action |
|---|---|---|
| Dues deducted, no card on file | Rand payer never signed | Steward sign-up visit |
| Card on file, no dues deducted | Payroll error or leave | Grievance payroll; member notice |
| Wrong classification | Employer coding | Document; group grievance if pattern |
| Missing from payroll, still employed | New hire lag | Confirm unit coverage; sign card Day 1 |
💡 Note
Note: Treasurers and Secretaries should reconcile together quarterly — dues rebated from the national body must match the cleaned local roster (see Module 5 trustee audit checklist).
❗ Warning
Warning: Never email unencrypted full membership lists — even to executive members. Use union secure drives with role-based access and multi-factor authentication.
Worked scenario
Worked scenario
Worked file timeline
- D0
Day 0 — dues dump
Receive employer CSV. Do not edit it on work OneDrive.
- D1
Day 1 — reconcile
Match dues rows to signed cards. Flag payers without cards.
- D3
Day 3 — signup list
Build internal outreach targets for /guide/membership-signup craft.
- D7
Day 7 — secure store
Update encrypted union database. Refuse any third-party list ask.
Reconcile monthly. Never store the cleaned list on employer cloud.
The ratification vote surprise. Contract ratification is Thursday. The Secretary pulls the employer dues report: 412 names. The signed-card database shows 318 active cards. Eighty-seven workers have paid dues for two or more years without signing. An executive member says, "They pay — let them vote."
Apply: Explain Rand vs. card distinction (Section 1). Run an emergency internal sign-up blitz using stewards and `/guide/membership-signup` tactics — cards at shift change, not employer email. For the ratification meeting, use only the signed-card roster cross-checked for good standing. Document the reconciliation gap for the next GMM membership report.
Don't apply: Do not add dues payers to the voting list without signed cards. Do not export the full payroll file to a campaign volunteer's personal Gmail to "get texts out faster."
Second beat — the political request. A city councillor endorsed by your local asks the Secretary for a CSV of member phone numbers for a GOTV text bank. The President says the candidate is "on our side."
Apply: Refuse list release under the Membership List Directive (Section 2). Propose an internal union communication — steward announcements, union email to members who opted in, GMM floor report — without handing contact data to the campaign.
Don't apply: Do not strip last names and call it anonymized — phone numbers are still identifiable PII. Do not store the requested export "just in case" on a personal laptop.
Practice drill
Round 1 — Reconcile a sample. Take a redacted employer CSV (20–30 rows). Import to a spreadsheet on a union device. Mark columns: dues payer only, card signed, classification mismatch, arrears risk. Write three steward assignments for sign-up targets.
Round 2 — Privacy tabletop. List five places officers might accidentally store lists (work email, shared steward locker USB, employer Teams channel, personal iCloud, printed stack on lunchroom table). For each, name the fix and who owns the migration.
💭 Reflection
Reflection: Where does your local's "master list" live right now — and who besides the Secretary can access it?
Floor checklist
Floor checklist
0 of 14 checked
Checks stay on this device so you can tick items during a real file.
Common pitfalls
- Payroll = membership — Treating every dues payer as a voter without a signed card.
- Employer cloud storage — Editing lists on work Microsoft 365 or Google accounts.
- Friendly political leaks — Releasing contacts to endorsed candidates "because we're aligned."
- Annual-only reconciliation — Discovering 100+ unsigned dues payers the week of an election.
- Unencrypted blasts — Emailing full CSV rosters to executive lists from personal accounts.
Further learning
- Canadian Labour Congress — membership administration and organizing fundamentals - CUPE local secretary / membership materials — list custody and reconciliation - Unifor local officer training — database hygiene and member privacy - Ontario Federation of Labour — local administration workshops - Your national union constitution — Membership List Directive and good-standing rules - UnionOps: `/guide/membership-signup` (campaign craft); Module 5 (dues rebate audit alignment)
Self-test
Module quiz
0 of 6 answered
Further reading from Canadian labour federations, multi-union steward handbooks, and public human rights guidance — not tied to one national. Confirm every rule against your own collective agreement and statute.
Sources & references
- CUPE Steward Handbook
Public CUPE steward handbook — grievance basics, human rights, and accommodation. Useful comparative education for any local; confirm against your own CA and national.
- Canadian Labour Congress — labour education catalogue
National CLC steward and leadership courses (Level 1/2 grievance handling). Cite for multi-union education; confirm live offerings with your labour council.
- Unifor education courses directory
Browse Unifor steward, human rights, and leadership courses. Delivery modes change — check the live directory.
- Ontario Federation of Labour
Provincial labour federation — solidarity and movement education; cite, do not mirror.
- Canadian Labour Congress
National labour congress — solidarity links on local sites; cite, do not mirror.