Begin with the union’s actual structure
A local with one employer and a multi-employer union can both ask for “membership management” while needing very different relationship models. Bring a fictional person with concurrent positions, a transfer between worksites and a dated leadership term. Ask the vendor to preserve history and show which agreement and organizational scope apply to each task.
Keep the question at workflow level: can the clerk update the right relationship, can the representative find the governing language and can the member understand their permitted view? The answer is more informative than the presence of a contact table.
Ask for bilingual and hosting evidence
A translated website is different from an approved operational notice. Ask how the product stores recipient preferences, reviews English and French wording and handles missing language evidence. For sensitive workflows, require the exact approved version and audience to remain identifiable after sending.
UnionStack production services and customer data are hosted in Canada. Review optional providers and their data flows separately. A procurement record should identify the service, information involved and responsible reviewer instead of assuming every connected service shares the same hosting boundary.
Make the comparison reproducible
Use the same member change, grievance, remittance and bilingual notice with every shortlisted product. Record what is native, configured, integrated, partial or not demonstrated. Unknown competitor evidence should remain unknown. A dated comparison is a starting point for questions, not a permanent statement about another vendor.
Finish with implementation owners, migration reconciliation, access tests and unresolved conditions. The strongest purchasing record connects the observed outcome to the work and dependencies required to sustain it.