There is a widespread misconception about what a vote is. When a governance professional says "we took a vote," what they typically mean is: someone asked for a show of hands, hands were raised, the chair announced the outcome, and the secretary noted it. That sequence describes an event. It does not describe a vote in the legal sense — a documented, individually attributable, verifiable expression of preference that can withstand scrutiny after the fact.
A legally binding vote is not a moment. It is a chain of eight distinct procedural steps, each with specific legal requirements, each with specific failure modes, and each with consequences that compound if the step is skipped or executed informally. The chain is only as strong as its weakest link. A failure at step two — quorum — can invalidate everything that follows, regardless of how correctly steps three through eight were executed.
This article walks through all eight stages in the order they occur. For each one, it sets out what must happen, what commonly goes wrong, and what a system that takes governance seriously does to prevent the failure. The interactive diagram at the end allows you to explore each stage in depth.
Stage one: Assembly notice issued
The governance process begins before the meeting. It begins with the notice — the formal communication to every eligible voter that an assembly is being convened, specifying what will be decided. The notice is not administrative formality. It is the mechanism by which voters are informed of their right to participate, and it sets the legal parameters for everything that follows.
Under the Danish Companies Act and equivalent legislation across European jurisdictions, notice periods are specified in law and typically supplemented by the organisation's own articles of association. For an A/S general meeting, the minimum notice period is typically two weeks, though articles often specify longer periods. The notice must include the complete and exact text of any resolutions to be voted on — not a summary, not an indication, but the precise text.
The practical implication is that the resolutions must be drafted and approved before the notice is sent. Changes to the agenda after the notice is dispatched — additions, amendments, textual revisions — require re-notification, which means restarting the notice period. This is frequently treated as an inconvenience to be avoided, but the alternative — proceeding with informal changes to the agenda — creates a vulnerability in every vote taken on those items.
Stage two: Quorum confirmed
Quorum is a threshold condition. It is not a formality, an estimate, or a courtesy check. It is the legal prerequisite for the assembly having authority to act. An assembly that proceeds without confirmed quorum has no authority to take binding decisions — and decisions taken in the absence of quorum are void regardless of how the vote went.
The specific threshold depends on the type of organisation, the type of resolution being voted on, and the articles of association. Some resolutions — ordinary resolutions in most Danish companies — require no minimum quorum, meaning any level of attendance is sufficient. Others — particularly resolutions that amend the articles, dissolve the company, or involve qualified majority requirements — specify minimum attendance thresholds. Whatever the threshold, the calculation must be conducted on the basis of verified attendance, not estimated attendance, and the result must be recorded before voting opens.
Proxy votes count toward quorum in most jurisdictions — but only valid proxy votes. An unverified proxy, received informally and not checked against the requirements, cannot properly be counted toward quorum. The implications are significant: if the margin between quorum and non-quorum is narrow, the validity of proxy documentation matters not just for the vote count but for the legal authority of the entire assembly.
Stages three through six: Identity, motion, window, and ballot
These four stages form the core of the voting process and are where the greatest variety of practice — and the greatest variety of failure — is found in European assemblies.
Identity verification is simultaneously the most important and the most commonly skipped step. The assumption in most in-person assemblies is that the people in the room are who they say they are — an assumption that breaks down the moment any of them is challenged. For digital and hybrid assemblies, identity verification is not optional: it must be engineered into the voting mechanism, not assumed.
The formal statement of the motion before voting opens is a procedural discipline that is routinely collapsed in practice. Chairs summarise, paraphrase, or shorten the resolution text for the sake of efficiency. This creates a divergence between what was in the notice, what was stated on the floor, and what appears in the minutes — three versions of the same resolution, none of which can be definitively reconciled after the fact.
The voting window is the period during which votes may be cast. Its legal significance is that votes cast outside the window — before it opens, or after it closes — do not count. This seems obvious, but in practice it is frequently managed informally: voting continues after the chair has moved on, proxy votes are added to the count after the window closed, or the window is never formally defined and the count is taken at an arbitrary moment.
The individual ballot record — the record of each specific vote as cast — is the foundation of the audit trail. Without it, everything else is circumstantial. A result that cannot be broken down into individual attributed votes cannot be verified. The entire edifice of governance documentation rests on this one fact: that the vote record links each decision to a specific person with specific authority, with a timestamp, and that the record cannot be altered.
Stages seven and eight: Result and record
The result announcement is the moment of legal crystallisation. Before this moment, a vote exists as a set of individual acts. After this moment, it exists as a collective decision — a fact about the world that has legal consequences. The precision of the announcement matters. "The motion was carried" is insufficient. "The motion was carried by 142 votes in favour, 38 against, and 11 abstentions, representing 68.3% of votes cast" is a record. The difference between these two statements is the difference between a declaration and an evidence base.
The minutes are not a summary. They are the legal record of what was decided.
The minutes of an assembly are, in most European jurisdictions, the primary legal instrument that establishes what was decided and when. Court cases, regulatory filings, and contractual disputes are resolved by reference to the minutes. The meeting itself is, in legal terms, ephemeral — it happened, it is over, and its content survives only in the documentary record.
This makes the quality and timeliness of the minutes the single most important factor in the legal defensibility of assembly decisions. Minutes drafted weeks after the meeting, from incomplete notes, by someone who was not the primary recorder — and unsigned because the process of obtaining signatures was not managed — are a documentary liability, not an asset. They represent an organisation's best guess at what happened, not a contemporaneous record of what actually occurred.
For Danish companies, signed minutes are required before any actions taken under a resolution can be formalised — including registration with the Business Authority. For associations and other organisations, the articles typically specify a signing deadline. In both cases, the practical discipline of having a draft ready immediately after the assembly, reviewed and signed within days, is the difference between an organisation with a clean governance record and one that is perpetually playing catch-up.
The interactive diagram below allows you to explore all eight stages in depth. For each stage, click to see the specific legal requirements, the most common failure modes, and how those failures manifest in practice.
Interactive diagram
The eight stages of a legally binding vote
Click any stage to see what must happen, what commonly goes wrong, and how Assembley addresses it.
What must happen
The notice must be dispatched to every eligible voter within the period required by law and the organisation's articles of association. For Danish A/S companies, the Companies Act (Selskabsloven) requires a minimum notice period for ordinary general meetings, typically two to four weeks. The notice must specify the date, time, location, and the complete agenda — including the full text of any resolutions to be voted on. A notice that omits an agenda item, or that is dispatched late, creates a procedural defect that can invalidate any vote taken on that item.
What commonly goes wrong
The most common failure is an incomplete agenda: a resolution is added after the notice is sent, or its wording is changed between notice and meeting. This gives any interested party grounds to challenge any vote on that item. The second most common failure is dispatch to an outdated shareholder or member register — notices sent to the wrong address, or not sent at all, are grounds for exclusion and potential challenge.
What Assembley does
Assembley generates and dispatches personalised digital notices with timestamped delivery confirmation for each recipient. The agenda is locked at dispatch — no modifications can be made to agenda items after invitations are sent without triggering a re-notification process.
What must happen
Before the chair opens the first agenda item, quorum must be established. This means counting the number of shareholders, members, or voting units present or validly represented, and comparing it against the threshold set by the articles of association and applicable law. The count must be exact — proxies must be checked, late arrivals must be factored in — and the result must be recorded in the minutes before voting opens. Quorum confirmed at 11:04 is a substantive legal fact. Quorum "probably met" is not.
What commonly goes wrong
Quorum is the most frequently challenged procedural step. The typical failures are: not confirming quorum explicitly (the chair opens the meeting and begins without a formal count); confirming quorum from an estimate rather than an actual count; counting unverified proxies toward quorum before checking their validity; and failing to record the quorum confirmation in the minutes. Any of these creates grounds to challenge the validity of the entire session.
What Assembley does
Assembley tracks confirmed attendance and proxy registrations in real time. The platform prevents voting from opening on any agenda item until quorum is confirmed by the administrator. Quorum confirmation is logged with a timestamp and stored as part of the immutable assembly record.
What must happen
Each voter must be verified as the person they claim to be — or as the holder of valid authority to represent someone else. In an in-person assembly, this has traditionally been done by checking the attendee register against an identity document. In a virtual or hybrid assembly, identity must be established through a mechanism that creates a verifiable record: a personalised access link, an authenticated login, or a verified identity assertion. The verification must happen before any vote is cast, and the method and result must be documented.
What commonly goes wrong
In practice, most in-person assemblies rely on a sign-in sheet at the door, with no document check. Attendees sign their own name, and their identity is taken on trust. This creates multiple points of vulnerability: a person can sign in under a name they are not entitled to use; a proxy holder can sign in without producing a written proxy; a person can attend for a member who has not authorised them to do so. Each of these is a potential ground for challenge.
What Assembley does
Assembley issues a unique, cryptographically signed, single-use ballot link to each registered voter. The link is time-limited and tied to the specific assembly. It cannot be forwarded and retain its validity. Identity is verified at two levels: email ownership (the link was received and clicked) and session binding (subsequent actions are tied to the authenticated session). Both levels are logged.
What must happen
Before a vote is opened, the resolution must be read aloud or clearly displayed in its exact form — the same wording that appeared in the notice. Shareholders are not voting on a paraphrase or a summary. They are voting on a specific legal text. The text that is voted on must match the text in the notice, and the text that appears in the minutes must match both. Deviation between any of these three versions — notice, floor, minutes — is a source of challenge.
What commonly goes wrong
The chair summarises the resolution informally instead of reading the precise text. A resolution is amended from the floor — which may be permissible under some circumstances — but the amendment is not documented. The minutes record the resolution in slightly different language than the notice. These are minor-seeming variations with significant consequences: they create ambiguity about what was actually decided and whether the vote taken corresponded to the decision being recorded.
What Assembley does
Agenda items in Assembley carry a fixed text set at the time of notice dispatch. The text displayed to voters during the assembly is the same text, retrieved directly from the database. The minutes automatically include the exact resolution text as it appeared on the ballot. There is no opportunity for informal paraphrasing between notice and record.
What must happen
The chair (or designated administrator) opens voting for the specific agenda item. From this moment, entitled voters may cast their vote. The voting window must be clearly announced — voters must know when it opens and when it closes. Votes cast before the window opens, or after it closes, must not be counted. Proxy votes must already be registered and attributed to the proxy holder. The window must remain open for a period sufficient to allow all entitled voters to participate.
What commonly goes wrong
Votes are accepted informally before the window is officially open. The voting window is closed prematurely, before all voters who wished to participate have done so. Proxy votes submitted during the window are attributed to the grantor rather than the proxy holder, creating a double-count. The administrator opens voting for the wrong agenda item. These are operational failures with legal consequences — each one can affect the vote count and, if the margin is narrow, change the outcome.
What Assembley does
Voting windows in Assembley are opened and closed explicitly by the administrator. The system enforces window boundaries — votes submitted outside an open window are rejected at the server level, not just in application logic. Each vote carries a server-side timestamp. Proxy registrations are pre-processed before the window opens and attributed correctly to the proxy holder's ballot.
What must happen
Each entitled voter submits their vote. The vote must be recorded individually — linked to the specific voter, the specific agenda item, and the specific choice made. Where voting is weighted by share value or membership units, the weighting must be applied at this stage and documented. Abstentions must be recorded as a distinct category, not ignored. Where a voter does not cast a vote, their absence from the record must be distinguishable from an abstention — these are legally different states.
What commonly goes wrong
This is where informal voting methods fail most fundamentally. A show of hands produces no individual record. A paper ballot without chain of custody cannot be audited. A digital system that records only aggregate totals — not individual votes — cannot be used to verify that specific voters cast votes, or that the count was correctly tallied. The failure to distinguish non-voters from abstainers can also affect the calculation of required majorities, particularly where a qualified majority is measured against all entitled voters rather than those present.
What Assembley does
Every vote in Assembley is written as an immutable, individually attributed event: voter identity, agenda item, choice, share weight, timestamp, and IP address. Votes are write-once at the database level — no administrator can modify or delete a submitted vote. Abstentions are explicitly recorded. Non-voters are tracked separately. Weighted results are calculated from the individual vote record, not from an aggregate.
What must happen
The chair announces the result: the specific vote count (for, against, abstain), the weighted total where applicable, whether the required threshold has been reached, and the outcome (carried or not carried). This announcement must be documented in the minutes contemporaneously — not reconstructed from memory after the meeting. If the result is disputed from the floor, the dispute and its resolution must also be documented. The outcome of the vote is only as legally secure as the record that documents it.
What commonly goes wrong
The chair announces the verdict — "carried" — without the underlying count. The minutes record only the verdict, not the figures. A challenge is raised from the floor and dismissed without documentation. The result is announced before all votes have been tallied (common in hybrid assemblies where remote votes arrive asynchronously). These failures strip the declared result of evidentiary support: a "carried" notation in the minutes, unaccompanied by figures, is nearly impossible to defend against a challenge that disputes the count.
What Assembley does
Assembley computes and displays results in real time as votes are submitted, with the full breakdown (for, against, abstain — both by count and weighted value) visible to the administrator. When the administrator closes voting, the result is finalised and locked. The result, including the full breakdown, is automatically included in the generated minutes.
What must happen
The minutes must be completed, reviewed, and signed — typically by the chair and at least one other designated signatory — within the timeframe specified by the articles of association, and in any case before any action is taken on the resolutions they record. For Danish companies, best practice (and often a requirement under the articles) is to have draft minutes distributed to signatories within a matter of days, and signed minutes available within two weeks. The minutes must be stored securely and in a manner that demonstrates they have not been altered since signing. For resolutions that require registration with Erhvervsstyrelsen, the signed minutes or a certified extract must accompany the filing.
What commonly goes wrong
Minutes are drafted weeks after the meeting, from notes that may have been compiled informally. They are not signed because the signatories are unavailable, or because the signing process is not systematised. They are stored in a format (a shared folder, an email attachment) that provides no protection against modification. An important resolution — a capital increase, a change of board composition — is filed with the Business Authority before the minutes are signed, meaning the registration is based on an unverified record. Each of these failures undermines the legal standing of every decision recorded in the minutes.
What Assembley does
Assembley generates a complete draft minutes document immediately on assembly close, including all agenda items, vote counts, attendance, quorum confirmation, and proxy registrations. The document is time-stamped and hash-sealed at the moment of generation. It is stored in the Assembley platform alongside the complete audit trail, accessible to the organisation for the duration of required retention. Signing workflows are outside Assembley's current scope; users typically export the document for execution in their existing signing process.
The chain is only as strong as its weakest link
The eight stages described above are not independent. They form a chain, and a defect at any point in the chain propagates forward. An invalid notice means that voter identification in stage three cannot be verified against the correct register. Unconfirmed quorum in stage two means that the authority of the entire assembly is in question regardless of the legitimacy of the vote count. An inadequate ballot record in stage six means that the result announced in stage seven cannot be verified.
The organisations that run legally defensible assemblies are not those with the most complex governance structures. They are the ones that execute all eight stages correctly, consistently, and with the documentation to prove it. They do this not because they expect every assembly to be challenged, but because governance that cannot withstand scrutiny is not governance — it is the appearance of governance, and the two are not equivalent when it matters.
A company secretary who can walk a lawyer through all eight stages of their last AGM — notice, quorum, identity, motion, window, ballot, result, minutes — and produce the documentary record at each stage is in a fundamentally different legal position from one who cannot. The difference is not in what happened at the meeting. The difference is in what can be proven about what happened.
Is your next assembly ready?
Assembley's AGM Readiness Assessment walks through each of the eight stages and identifies where your current process creates procedural risk.
Take the assessment →