We are an eMembership publication and naturally know our own platform best. This guide is written to be useful to any union leader evaluating union organizing software, regardless of which vendor they choose. It draws on how organizing, ratification, and contract work actually run inside a union, and on public product documentation.

What union organizing software does

Union organizing software is the set of tools a local or international uses to run new member campaigns, track member support, sign up members, and carry that work through to a ratified contract. In practice it spans four jobs that unions often buy separately: campaign and turf management, member sign-up with electronic signatures, online voting for ratification and officer elections, and the collective bargaining agreement records that hold it together.

Those four jobs belong in one guide because they are one continuous process. A campaign that signs up members should feed the same database that later sends those members a ratification ballot. When the tools are separate, the data drifts, and by the time you need a clean voter list you are rebuilding it by hand.

Good organizing software does four things well. It builds working lists from live member data, so field lists stay current instead of going stale the moment they are exported. It records where each member stands, with assessment history that follows the person across campaigns. It converts a signature into a member record the instant a card is signed. And it carries that membership through to a vote whose roll is drawn from the same records.

The organizing-to-ratification lifecycle: a buyer's framework

Most organizing tools are sold as point solutions: a turf cutter, an e-signature service, a voting platform. That framing hides the real risk, which is what happens between the tools. To make the handoffs visible, it helps to see organizing as a single lifecycle with five stages, each of which either preserves the member record or breaks it. Score any tool you are considering against each stage. For the wider purchase process this sits inside, from needs assessment through reference checks, see our union management software buyers guide.

Stage 1: Target

You define who you are organizing, building lists from live data. Those are either current members you want to activate for a contract campaign or potential members you have not signed yet. The test of this stage is whether targets and members live in the same system. When potential members sit in a spreadsheet and members sit in a database, the two never reconcile.

Stage 2: Assess

Field reps make contact and record where each person stands. Support scoring, worksite conversations, and visit notes accumulate on the person over time. The test here is whether an assessment recorded in one campaign is still attached to that member in the next one, or whether it disappears when the campaign ends.

Stage 3: Sign

A target becomes a member. With electronic signatures, this is the moment a card becomes a full member record. The test is immediacy: does the new member exist in the system the instant they sign, or do they wait in a stack of cards for someone to key in later?

Stage 4: Ratify

The membership votes, most often to ratify a contract, sometimes to elect officers or authorize a strike. The test is whether the voter roll is drawn from the same live membership data, and whether the vote itself meets the legal standard for a binding union election.

Stage 5: Record

The ratified agreement becomes the contract of record, setting dues rates, wage schedules, expiration alerts, and coverage. The test is whether that contract connects back to the members it covers and the dues they owe, or whether it is a document nobody can act on.

Organizing challenges: new member campaigns and tracking

The recurring failure in union organizing is not effort. It is that most unions keep two sets of lists. The dues database holds current members, while organizing targets live in spreadsheets or a separate campaign tool, and the two drift apart within weeks. Reps knock doors with stale lists, new signups get re-keyed by hand, and nobody can say how a campaign actually changed the membership.

That gap has real costs. Assessments recorded during a card-check drive vanish when the drive ends. A member who moves between employers shows up as two records. Leadership cannot answer a basic question, which is whether the last campaign grew the membership or just generated activity.

Running organizing inside the membership system rather than beside it closes the gap. In eMembership's organizing module, turfs are built from live member data by employer, region, chapter, or any field in the system. Internal organizing, meaning the members you already have, and external organizing, meaning the members you have not signed yet, run on the same records. Assessments and contact history stay with the person across every campaign rather than resetting each time.

How organizing software works: turf, outreach, and sign-up

Organizing software has three working parts: dividing the population into workable segments, managing the contact that happens in each segment, and signing up the people who say yes.

Turf cutting is the practice of dividing a membership population into geographic or employer-based segments and assigning each segment to a specific field rep. A turf is a saved set of member criteria that generates a working list. Good turf tools let you define segments by employer, region, chapter, zip code, or any combination, and cut them into visit groups on a map by clicking members individually or selecting a geographic cluster. Because the lists build from live member data, they stay current as payroll and roster imports come in rather than going stale.

Outreach management is where contact gets recorded. Reps reach members through text, email, phone, or in-person visits and log assessments, scores, and follow-up notes regardless of how the contact happened. The messaging runs through the same integrated email and text tools the union uses everywhere else, so the turf list and the message sent to it draw on one set of records. The design detail that matters is that assessment forms are the union's own: custom questions and scoring scales, with responses tracked over time, by member, so support can be measured across multiple visits and campaigns. This is engagement measurement built on union signals, worksite conversations and organizer visits, rather than association metrics like committee seats or event attendance.

Sign-up is the payoff. Field reps capture membership applications and digital signatures from any device, and the new member record is written directly into the system on submission. No paper, no follow-up scanning, no gap between the win and the dues cycle.

Contract ratification: online voting, e-signatures, and verification

Contract ratification is where organizing software meets election law. Running a ratification vote online is not the same as sending a survey. Officer and delegate elections at covered unions are governed by Title IV of the Labor-Management Reporting and Disclosure Act of 1959, and the Department of Labor's OLMS guidance on remote electronic voting describes what the agency weighs, case by case, when an internet officer election is challenged: ballot secrecy, adequate safeguards for a fair election including observer rights, preservation of records for one year, and preservation of the right to vote. That last item carries the clearest obligation, which is that a member without internet access has to be offered another way to vote on request. Two scope points matter before you measure any voting tool against that standard. Title IV does not reach unions made up entirely of state, county, or municipal employees, though a mixed local with both public and private sector members is covered. And contract ratification and strike authorization votes are not Title IV elections at all. They are governed by a union's own constitution and bylaws, which courts treat as binding. The LMRDA is not absent from them either. Title I gives every member an equal right to vote in the union's elections and referendums, enforceable directly in federal court, and a separate provision requires a secret ballot to raise dues or levy an assessment. Most unions hold ratification to the officer-election bar anyway, because a vote that can be challenged internally creates the same problem as one challenged federally.

In eMembership, ratification voting runs through the Surveys and Votes module. Any survey can be configured as anonymous so individual responses cannot be linked to specific members, which is the required mode for formal votes. The module's electronic voting is built to comply with the LMRDA and the Department of Labor's OLMS compliance guidance on electing union officers using remote electronic voting systems, upholding ballot secrecy, observer rights, and record preservation. Two caveats belong with that claim. The OLMS guidance addresses officer and delegate elections, not ratification votes, and OLMS assesses each challenged election on the totality of its facts rather than certifying any vendor or system. How a union administers the election matters as much as the platform it runs on, so confirm any specific compliance question about your union's situation with your legal counsel. Ballots go out by email from within the system, with open tracking so administrators can follow up with members who have not yet voted. For unions that add the optional Member App, ballots can also arrive as push notifications.

The verification piece matters as much as the ballot. Because the voter roll is drawn from live membership data, the people eligible to vote are the people who are actually members in good standing at the moment the vote opens, rather than a list exported and edited by hand. That connection between the roll and the record is what keeps the eligibility question clean.

Electronic signatures sit alongside voting in the ratification stage. When a contract is ratified, membership cards, dues deduction authorizations, and other documents can be sent for legally binding electronic signature, with known fields pre-filled from member records and the signed document saved straight back to the member's profile. On a labor timeline, that speed is the point.

Collective bargaining agreement management

A ratified contract is only useful if the union can act on it. Collective bargaining agreement management, sometimes searched as union CBA management software, is the practice of storing agreements so their terms drive the rest of the system rather than sitting in a drawer.

The Contract Management module tracks each agreement's terms, wage scales, expiration dates, employer coverage, and dues rates in one searchable place. Contracts approaching expiration are flagged automatically, so negotiators get advance notice instead of discovering a lapse after the fact. Stepped wage schedules are built once, with a start and end date per step, and the rate updates on the right date without manual intervention. Dues rates are set at the contract level by classification or craft, and a single click assesses the entire bargaining unit.

The connection back to members is what makes this more than document storage. A change in a contract rate flows through to dues assessment and billing without a second entry, which is where a contract stops being a document and starts driving money. For how that downstream cycle runs end to end, see our guide to how automated union dues billing works. A grievance links back to the relevant contract automatically, so when a case references a past agreement, the historical terms are still there. This is the recording stage of the lifecycle doing its job: the contract is the reference point every later process depends on. For the case-handling side of that connection, see our guide to how union grievance management software works.

Dispatch and skills matching

For building trades locals and any union running a hiring hall, dispatch is part of the same member-data question. Dispatch software matches qualified members to employer work orders based on the skills each job requires, most commonly ranking eligible members by days out of work for fair, rule-based prioritization. Every call, placement, and refusal is logged against the work order for a complete audit trail.

Dispatch belongs in this guide because it runs on the same records as organizing. Worth saying plainly: dispatch administration is a desktop application, and it is not part of every eMembership implementation. A union without a hiring hall simply does not turn it on. A member's skills, employment history, and standing all feed the matching process directly, and a member signed up in the field is immediately eligible for dispatch without re-entry. The skills list itself is configurable to the trade rather than imposed, so the match reflects how the local actually defines qualification.

What most unions get wrong

The most common mistake is buying organizing software and voting software separately, months apart, from different vendors. Each purchase looks reasonable on its own. The turf tool demos well. The voting platform is compliant. The problem only appears at ratification, when the voter roll has to be reconciled against a membership database the organizing tool was never connected to. Now someone is exporting, cleaning, and re-importing a list under deadline, which is precisely the moment a data error costs the most.

The second mistake is treating the contract as the finish line. A ratified agreement that is not connected to dues rates, wage schedules, and coverage is a document, not a system of record. The unions that get the most out of organizing software are the ones that close the loop, so the contract they just won configures the dues they are about to collect.

The third mistake is underinvesting in the field side of adoption. If signing a member up in the tool is slower than a paper card, reps fall back to paper, and the record fragments all over again. A system earns its place by being faster than what it replaces at the moment of the win.

How eMembership approaches organizing and ratification

This section is about our own platform. Everything above applies regardless of which vendor a union chooses.

eMembership runs organizing, electronic signatures, ratification voting, dispatch, and contract records on one member database rather than as separate tools. A turf built from live membership data, a card signed with eSign in the field, a ratification ballot sent through Surveys and Votes, and the contract that results all reference the same records, so a member does not have to be re-entered as they move from target to signed member to voter.

Measured against the lifecycle in this guide, the platform is built around the same five stages. On targeting, turfs build from live member data with internal and external organizing on the same records. On assessment, custom forms track support over time per member across campaigns. On signing, eSign in the field writes a full member record on submission. On ratification, the Surveys and Votes module runs anonymous electronic voting built to the LMRDA and OLMS standards described above with the roll drawn from live membership data, and members reach the ballot through the member portal. On recording, Contract Management ties the ratified agreement back to dues rates, wage schedules, and coverage.

eMembership is modular, built as a set of configurable union database modules. A union configures the modules its operations require through a paid Discovery Process, and the member portal and mobile app are separate add-ons rather than part of a base bundle. There is no claim here that everything comes in one package. The claim is narrower and more useful: the modules a union does turn on share one database, which is what makes the lifecycle continuous. Whether eMembership is the right fit depends on a union's size, structure, and how much it values that continuity. If you are weighing it against another organizing-focused platform, our eMembership versus Union Impact comparison lays out where each tends to fit, and our guide to how union member self-service portals work covers how members reach the ballot.

SEIU Local 500 represents roughly 20,000 workers across Maryland and Washington, DC. After the Supreme Court's June 2018 decision in Janus v. AFSCME ended fair-share fees for public employees nationwide, the local moved quickly to electronic signatures for membership cards and online voting for contract ratification. Its contract ratification votes across 20,000 members now close in days rather than the weeks the postal system required. The same platform handled the signatures and the vote, drawn from the same membership data, under real time pressure created by a change in the law.