How to prepare a general assembly with amendments: a step-by-step guide

A general assembly with a heavy amendment agenda doesn't run itself. Yet in most associations, NGOs, and trade unions, the preparation still looks the same: a Word document sent by email, an inbox flooded with contradictory proposals, and a board spending the night before the meeting manually stitching everything together.

This guide outlines a structured four-step method that works regardless of the tools you use — and scales even better when you move to a dedicated platform.

Step 1 — Set the rules before opening submissions

Before members start submitting amendments, three rules must be clearly communicated:

Who can submit an amendment? All members? Only those with current dues paid? Designated delegates? Ambiguity here generates procedural disputes on the day of the meeting.

What is the reference text? Publish the official version of the document being amended — bylaws, internal regulations, a resolution — and freeze it. Every amendment must cite the exact article it modifies.

What is the submission deadline? A firm cutoff is non-negotiable. Without one, amendments keep arriving until the night before, making any consolidation impossible.

Step 2 — Collect amendments in a structured format

This is where most organisations lose hours. When every member submits their proposal in a different format — an Excel spreadsheet, a prose email, a scanned PDF — the consolidation effort multiplies.

The fix: use a single submission form that systematically captures:

— the article reference
— the current text (exact excerpt)
— the proposed replacement
— the justification (optional but useful for debate)

With a tool like Amendly, this form is built-in: the member selects the passage to change directly in the document, proposes their replacement, and the diff is computed automatically. No copy-paste errors, no lost references.

Step 3 — Review amendments before the assembly

Once the submission period closes, the review work begins. There are typically two layers:

Admissibility: does the amendment comply with formal rules (deadline, format, scope)? This is a quick check but an essential one. Authors of inadmissible amendments should be notified before the meeting.

Debate preparation: for admissible amendments, the board can prepare a position (in favour / against / referral) and group amendments that target the same article. This avoids debating the same paragraph twenty times.

In Amendly, administrators can add comments and reactions to each amendment, and group them by article. On the day of the assembly, everyone starts from the same shared dashboard.

Step 4 — Consolidate and export after the vote

The assembly votes. Amendments are accepted or rejected. Then comes the most tedious phase: incorporating accepted amendments into the final text and producing a clean document for signing and archiving.

Done manually, this means reopening the original document and copy-pasting each approved change — with the risk of missing one, or introducing a numbering error.

With a dedicated platform, consolidation is near-automatic: accepting an amendment injects it directly into the consolidated output. When you're done, a single click exports the final document as DOCX or PDF, ready to sign.

What structured preparation actually changes

A poorly prepared assembly leads to three recurring problems: debates that bog down on procedural points, votes on text nobody has read carefully, and a board leaving exhausted with a document to reconstruct under pressure.

Structured preparation shifts the work: instead of chasing information on the day, you invest time upfront in setting the framework. The assembly becomes what it should be — a moment of decision, not of data entry.

Amendly is built exactly for this: collect amendments in a structured way, review them as a team, consolidate in one click. Try it free before your next general assembly.