FNV Congress: Amendment & Validation Platform (work in progress)
A platform for FNV's union congress that turned 400+ amendments from 12 delegations into structured decision-making, with built-in validation and transparency.
The challenge
FNV Congress happens once every four years. 600+ union representatives gather to set policy direction by amending the congress document that shapes FNV's work for the next four years.
In previous years, this is what that looked like: A union member emails an amendment. The FNV team manually checks if that person is authorized. They add it to a spreadsheet. Three other people from the same delegation email similar amendments. Someone from a different delegation proposes the opposite. By week three, there are 400+ emails, overlapping proposals, conflicting changes, and no clear overview of what's actually being proposed for which paragraph.
The organizing team spent weeks compiling everything into a workable document. Delegations had no idea what they'd collectively proposed. Congress started with people still discovering amendments they hadn't seen before.
The problem wasn't participation. It was that democratic process became administrative chaos at scale.
The solution
Savvy built a platform that follows the flow of how an amendment actually moves through FNV's congress process.
Registration and validation
A union member wants to participate. They fill out a registration form styled to match FNV's website. The submission goes directly to the FNV team. No automatic approval. The team verifies: is this person a union member? Which delegation do they belong to? Are they authorized to submit amendments? Only after manual approval does the person get access.
This controlled validation matters because congress decisions are binding. Allowing unauthorized participants doesn't just create administrative problems—it creates legitimacy problems. If someone challenges a vote later, FNV needs to prove that only eligible members participated.
The member submits an amendment
They open the congress document in the platform. They select the specific lines they want to change. They write their proposed text and explain why. The system automatically tags which paragraph this affects. Within their delegation, other members see this proposal immediately.
This internal transparency serves two purposes: it prevents duplicate work (three people proposing the same change), and it allows delegations to align their positions before submission. Members can discuss, refine, and strengthen proposals together. But other delegations don't see it. This prevents reactive amendments—proposals made not on merit, but as a counter to what another group suggested. When delegations see each other's amendments early, the process becomes political positioning instead of policy development. Groups stop asking 'what's the right direction?' and start asking 'how do we block what they proposed?' By keeping amendments private between groups until review, the focus stays on content.
The FNV organizing team reviews everything
Every amendment is automatically grouped by paragraph. If five delegations proposed changes to section 3.2, those five proposals appear together. Conflicting amendments are immediately visible.
This bundled overview matters because conflicts need to be identified before congress starts. Without it, the organizing team discovers during the session that two popular proposals can't both be accepted—one wants to strengthen a clause, the other wants to delete it entirely. With this structure, those conflicts are resolved beforehand.
Congress day arrives
The document is already updated with accepted amendments. Delegations know what their group proposed and what made it through. Every proposal has a complete audit trail: who submitted it, when, which delegation they represented, and the reasoning behind it. The day focuses on discussion and voting, not on administrative catch-up or discovering what was submitted weeks earlier.
- Controlled registration and validation of participants
- Amendment submission with paragraph tagging
- Internal transparency within delegations
- Privacy between delegations until review
- Automatic grouping by paragraph
- Complete audit trail of all proposals
- Organiser dashboard with conflict detection
The results
Before Savvy: Weeks spent compiling amendments from emails. Delegations discovering each other's proposals during congress. Last-minute confusion about what was actually being voted on. No clear record of who proposed what and when.
With Savvy: 400+ amendments processed with full structure. 12 delegations worked independently with internal transparency. Zero unauthorized submissions reached the organizing team. Complete audit trail of every proposal, timestamp, and reasoning. Congress started with clarity instead of administrative cleanup.
- 400+ amendments processed with full structure
- 12 delegations worked independently with internal transparency
- Zero unauthorized submissions reached the organizing team
- Complete audit trail of every proposal, timestamp, and reasoning
- Congress started with clarity instead of administrative cleanup
- Delegations could focus on their priorities without distraction from other groups' proposals
Why it matters
Democratic governance at scale needs more than good intentions. It needs structure that respects how decisions actually get made. FNV's congress isn't a brainstorm session. It's binding policy formation. Amendments aren't suggestions—they're formal proposals that shape union strategy for four years.
That process can't rely on email and spreadsheets. It needs controlled access, transparency within groups, privacy between groups, and complete oversight for organizers. Savvy built that structure. Not as a collaboration tool, but as governance infrastructure. FNV's congress happened the way it was supposed to: democratic, transparent, and manageable.
Make democratic processes at scale manageable
Platforms that provide controlled participation, transparency and complete oversight for organisers in binding decision-making.