StrideGovernance OS

Meetings · Governance

Board meeting requirements (Nordics)

This guide summarizes practical legal checkpoints for board meeting workflows in Sweden, Norway, Iceland, Denmark, and Finland. It is designed for product configuration and process hygiene, not legal advice.

Meetings overviewAgenda workflow

Sweden

Aktiebolag (board-governed companies)
  • Board work must be organized with written rules of procedure, adopted at least annually.
  • The chair must ensure meetings are held when needed; meetings must also be called if a board member or the CEO requests it.
  • Minutes must be kept and signed/adjusted according to the Companies Act requirements.
  • Practical policy for Stride: assign and freeze board meeting numbers when minutes are approved.

Sources

Norway

Aksjeselskap / Allmennaksjeselskap
  • Board matters must be handled by the board; handling can be in meetings or other adequate methods if allowed.
  • The chair is responsible for board handling, and board members/CEO can require board consideration of specific matters.
  • Minutes are required for board handling and must be signed according to the statute.
  • Practical policy for Stride: keep chronological meeting numbers for non-final meetings and lock after signed minutes.

Sources

Iceland

Private/Public Limited Companies (board-managed companies)
  • Board is responsible for company affairs and organization of operations/control.
  • Chair calls meetings when necessary; meetings must be called when a board member or managing director asks.
  • Board decisions and discussions must be recorded in a minute book.
  • Practical policy for Stride: preserve numbering once minutes are formally approved.

Sources

Denmark

A/S board governance (Selskabsloven)
  • The board must adopt rules of procedure that govern board work.
  • Rules should cover meeting planning, decision process, and minute handling.
  • Governance setup should support traceability from meeting call through signed minutes.
  • Practical policy for Stride: use automatic chronological numbering and lock numbering after minutes approval.

Sources

Finland

Osakeyhtiö (Limited Liability Companies Act)
  • Board meeting practice is defined in Chapter 6, including convening and board decision-making.
  • Board minutes are required and must be kept reliably.
  • Numbered minute records support legal traceability and audit readiness.
  • Practical policy for Stride: keep sequential meeting numbers for board meetings and freeze after final minute approval.

Sources

Requirement to feature mapping in Stride

Use this as your implementation checklist when translating legal governance expectations into concrete process controls in Stride.

Formal board workflow with clear handoffs

Stride features

  • Unified board lifecycle statuses from DRAFT to MINUTES_APPROVED.
  • Planner flow with attendee finalization before circulation.
  • Presenter mode for live meeting execution and in-session documentation.

System anchors

  • Meeting statuses: DRAFT → FEEDBACK_REQUESTED → COMPLETED → CIRCULATED → IN_SESSION → HELD → MINUTES_SUBMITTED → MINUTES_APPROVED
  • Guide references: Agenda workflow + Invites & roles
Agenda workflowInvites & roles

Board composition, role clarity, and signer accountability

Stride features

  • Invite roles (Required, Optional, Observer) and meeting role assignments (Chair, Secretary, Minutes Adjuster, Presenter, Observer).
  • Finalize attendees step before circulation, with audit fields for who finalized and when.
  • Minutes approvals can be role-restricted (e.g., Secretary and Minutes Adjuster).

System anchors

  • Audit data: finalInvitesSentAt, invitesFinalizedById, roleAssignments
  • Approval logic: MINUTES signing permissions + quorum tracking
Invites & roles

Minutes must be kept, reviewed, signed, and preserved

Stride features

  • Minutes drafting in HELD status, then submission via MINUTES_SUBMITTED.
  • Approval workflow for board minutes with quorum progress and final approval state.
  • Signed minutes PDF generation and locked final state at MINUTES_APPROVED.

System anchors

  • Audit data: minutesSubmittedAt, minutesApprovedAt, minutesPdfAttachmentId
  • State lock: MINUTES_APPROVED is final; minutes changes require controlled reopen before final approval
Meetings overview

Traceability of agenda changes and decision trail

Stride features

  • Agenda versioning with reopen audit trail (who reopened and when).
  • Decision lifecycle from proposed to recorded/confirmed during live sessions.
  • Attachment release controls and persistent meeting workspace history.

System anchors

  • Audit data: agendaVersion, agendaReopenedAt, agendaReopenedById
  • Presenter mode support for live decision confirmation
Agenda workflow

Chronological, auditable board meeting numbering

Stride features

  • Automatic board meeting numbering by chronological order.
  • Renumbering of non-final meetings when new meetings are inserted between existing ones.
  • Number lock once minutes are approved, so signed records keep stable identifiers.

System anchors

  • Data model: meetingNumber (board meetings)
  • Protection rule: signed board meetings cannot be moved in date order
Meetings overview

Compliance note

Laws vary by company form and can change over time. Before adopting a governance policy, confirm details with local counsel for your exact entity type and sector-specific obligations.

Last reviewed: February 9, 2026.