How general meetings work in BoardKite

A General Meeting is a statutory wrapper around an ordinary BoardKite Meeting. Logistics stay on the meeting; legal rights stay on the general-meeting records.

• The linked Meeting owns calendar visibility, agenda, materials, minutes shell, signatures, and invites.
• The General Meeting owns record date, share-register snapshot, capacities, attendance, notice draft, and voting register.
• Access is organization-granted (GENERAL_MEETINGS, which depends on SHAREHOLDER_LEDGER). Without the grant, the nav and APIs stay hidden.
• Physical, hybrid, and digital modes are supported as participation modes — digital is not a separate legal event type.

Every general meeting must have exactly one linked BoardKite meeting so it appears on the existing meeting calendar.

• Create a new linked meeting, or attach an existing eligible meeting, when you create the general meeting.
• Do not look for a second “general meetings calendar” — calendar queries keep reading Meeting records.
• Calendar cards show a General meeting badge when a wrap exists; readiness detail lives in the general-meetings workspace.
• Participation mode maps onto the meeting location type (in person, hybrid, or virtual).

Voting candidates come from a locked, meeting-ready internal share-register snapshot selected under the company's legal eligibility basis.

• Use a reviewed internal company-maintained ledger snapshot for meeting capacity generation.
• A public Euroclear aktiebok PDF is informational and cannot establish voting entitlement or nominee mandates.
• Later share transfers do not rewrite the evidence used for this meeting once the snapshot is bound.
• You cannot approve a voting register without a locked snapshot.

Capacities are legal-rights candidates derived from the snapshot. They are not yet the voting register.

• Generate one expected capacity per internal shareholder.
• Nominee and custodian voting needs a future meeting-specific registration and mandate source; BoardKite does not invent beneficial owners.
• Expected and review-required statuses mean “candidate,” not “approved to vote.”
• RSVP on a meeting invite never creates voting rights.

Attendance is human-level: who is actually present. The röstlängd follows presence, not registration.

• Check people in (room, video, phone) and assign one or more capacities they will exercise.
• One person may represent themselves, a company, and proxies — each as a separate capacity.
• Mark absent when someone registered but did not show; that withdraws their approved capacities.
• Unrepresented shares are normal. Absentees should not be forced onto the locked register.

Approve the register from present/represented approved capacities, then lock an immutable version with a checksum.

• Draft summary shows eligible vs represented vs unrepresented shares and votes.
• Lock validation refuses capacities tied to absent attendees.
• Locked versions are never edited in place; corrections create a superseding version.
• Export CSV evidence for minutes; PDF export polish may follow.
• Live weighted ballots and postal voting are later phases — the locked register is the evidence base for those flows.

MVP includes a thin notice draft/lock and a minutes evidence handoff. Full statutory notice windows and bolagsstämma minutes templates come later.

• Capture location/URL, digital participation instructions, and proxy instructions as a draft.
• Treat notice-window and articles digital-clause checks as soft “needs review” until hardening ships.
• Attach locked snapshot and voting-register checksums as appendix references for minutes.
• Reuse the linked meeting for ordinary minutes authoring and signatures once the register is locked.