A lost voting link should trigger a documented replacement process, not an improvised email from a committee member. Before a remote union officer election opens, agree with your vendor on who may authorize replacement credentials, how observers can watch the process without seeing secret codes, and what evidence the union will retain.
This checklist is for election committees and buyers planning officer elections covered by Title IV of the Labor-Management Reporting and Disclosure Act (LMRDA). It concentrates on replacement access, rather than initial invitation delivery.
Start with the OLMS distinction: observe the process, not the code
The Department of Labor's Office of Labor-Management Standards (OLMS) addresses this issue directly in Electing Union Officers Using Remote Electronic Voting Systems. Its observer guidance includes the opportunity to observe preparation and distribution of credentials, including subsequent distributions to members who did not receive or lost them. It also says observers must be allowed to view the process but must not see the specific voting credentials sent to individual members.
That distinction should shape the help-desk workflow. An observer-facing screen should make the administrative action understandable without exposing a usable voting link, PIN, or other secret credential. Do not solve an observation request by forwarding the member's invitation to a candidate.
OLMS describes a non-exhaustive set of favorable safeguards and evaluates complaints case by case. The operational steps below are recommended controls to discuss with your vendor, not a claim that every step is a separate statutory mandate. A checklist does not provide a safe harbor or establish that a vendor is approved by the Department of Labor.
1. Agree on the replacement rules before voting opens
Put the replacement procedure in the committee's operating plan and the vendor's scope of work. Identify the person or role that approves requests, the support channels members can use, the verification method, and the escalation route for disputed eligibility or suspected misuse.
Separate a request for help from a decision about voting rights. Ask the vendor how support staff will refer an eligibility question to the authorized election official rather than deciding it informally. Also establish how requests received near the closing deadline will be handled under the election's governing rules; a help-desk ticket should not silently change the announced voting window.
When comparing election services for labor unions, ask for a demonstration of this exception workflow, not just a demonstration of casting an ordinary ballot.
2. Verify the request without collecting ballot choices
Choose a consistent identity-verification procedure before staff start handling replacement requests. Ask your vendor to show how it distinguishes a member requesting help from someone trying to redirect that member's access. Document how changes to a delivery address are checked and approved.
Support staff should not ask how a member voted, request a screenshot of a completed ballot, or place voting secrets in an ordinary support-ticket conversation. Keep any sensitive verification evidence in a restricted record rather than displaying it in an observer-facing queue.
These are recommended operating controls. For the legal secrecy context, the OLMS remote-electronic-voting guidance, section 1 explains that procedures must protect members from having their voting selections exposed while voting and afterward.
3. Demonstrate what happens to old access and an existing ballot
Require the vendor to explain what the system actually does when access is replaced. Does it resend an existing credential or generate a new one? If it generates a new one, how is the superseded credential disabled? What happens if the original invitation is later found or both links are opened?
Also ask what happens when a ballot has already been accepted. Do not assume that resetting access cancels a ballot, creates another voting entitlement, or permits a second submission. Have the committee confirm the intended treatment against the governing election rules and obtain the vendor's written explanation of how its configuration implements that treatment.
Before launch, request a practice demonstration covering an unused credential, a replacement request after an accepted ballot, a repeat replacement request, and use of the superseded access. Record the expected result for each scenario and compare it with the demonstration. Use test identities and practice ballots, not real member records or live votes.
4. Build an observer view that excludes usable credentials
Agree in advance how observers will receive a meaningful opportunity to watch replacement distributions. The procedure should account for individual support requests during voting, not only the initial batch of invitations.
Ask the vendor to demonstrate an observer-safe view of request receipt, authorization, and distribution status while hiding the credential itself. Keep observation records separate from the restricted credential archive. If screen sharing is used, check notification previews, email windows, and downloadable files as well as the main dashboard.
For example, a hypothetical union committee could demonstrate a replacement with practice records before voting begins. Observers could follow the approval and delivery steps while the secret credential remains hidden. This is an illustrative workflow, not a description of a client or a reported election result.
5. Preserve the replacement evidence without exposing secrets
The Fact Sheet: LMRDA Recordkeeping Requirements for Unions says all election records must be preserved for one year by the designated election official or, if none is designated, the union secretary. The OLMS electronic-voting guidance, section 3 expressly includes voting credentials and log files, alongside other paper and electronic election records.
As a practical closeout control, retain replacement requests, approval records, distribution outcomes, relevant system logs, and the procedure used. Assign responsibility for obtaining the records from the vendor and keeping them accessible throughout the retention period. Do not equate disabling an old credential with deleting its election record.
Preservation does not mean public disclosure. Arrange restricted storage for secret credential records and protect encrypted ballot files as OLMS describes. Before authorizing deletion, confirm the applicable retention schedule and whether any investigation, litigation, or other preservation obligation requires a longer hold.
Ask for a replacement-access walkthrough before signing
A useful vendor walkthrough should show who approves a replacement, how old access is handled, what observers can see, and which records the union receives. If any of those answers is unclear, resolve it before the election opens rather than leaving support staff to improvise.
If you are planning a remote union officer election, ask Votem to discuss your credential-replacement and observer procedures as part of your election planning.
This article provides general election-administration information, not legal advice. Review your union's governing documents and seek qualified advice about election-specific questions.