← back to other articles

How to Choose a Board Portal

Boards
Meeting Management
July 16, 2026
July 16, 2026
Author
Dr. Boris Häfele
Managing Director & Co-Founder
Boris has extensive experience in management consulting and SaaS development. At Boardwise, he drives strategic direction and product innovation.
Table of contents

When choosing a board portal, what matters is less the range of features than four things that only reveal themselves in operation: reliable human support on meeting day, usability for occasional users, a clean data export on exit, and integration into the existing working environment. The feature lists of established providers barely differ. The differences show up later.

Usually when a member cannot get in shortly before the meeting, when a document was distributed in the wrong version, or when after two years no one knows where the resolutions from back then are stored. A selection process worth its name tries to anticipate these moments. This article describes what matters when doing so, and when a portal is not worth it.

When is a board portal worth it, and when not?

A board portal is not worth it for every body. For a small board of four people that meets four times a year and whose documents rarely exceed thirty pages, a well configured filing structure in the existing working environment may suffice.

The effort of introduction, training and upkeep of a dedicated system then bears no relation to the gain, and a tool that is not worth it will not be used either.

A portal begins to pay off when several conditions come together. When documents regularly reach a volume at which versioning errors become likely. When several bodies exist in parallel, for instance an executive board, a supervisory board and committees. When external members or advisers are involved whose access must end in a controlled way. And when regulatory documentation obligations exist for which an email history does not suffice.

Which selection criteria really matter?

The decisive criteria are four that are frequently missing from tenders, because security, usability and range of functions appear on every list yet barely distinguish one provider from another. Every serious provider meets them.

Human support on meeting day. Support promises sound similar in contracts, yet differ considerably in practice. What matters is whether, when it counts, a human being is reachable who knows the body and its routines, rather than a ticketing system with an anonymous queue. A dedicated contact who speaks the language of the body and knows its particular configuration is worth more, in the moment something goes wrong shortly before the meeting, than any guaranteed response time.

Usability for occasional users. Board portals are used by two very different groups. The board office works with the system daily and becomes practised. The board members open it rarely and start almost from scratch each time. An interface optimised for daily use can be unusable for occasional use. The relevant test question is therefore not whether the software seems intuitive, but whether it still is after a three-month pause.

Data export on exit. No one asks this question at the start, and it is the most expensive. Anyone wanting to switch after five years must be able to take the holdings with them, in a format that remains readable without the provider. A provider that answers this question vaguely sells not just a product, but a dependency.

Configuration effort until going live. Some systems are productive after two weeks, others need half a year of project work and external consulting. Both can be appropriate, but the difference belongs in the cost calculation, not in a footnote.

What does a board portal really cost?

Licence costs are only the visible part. For smaller organisations, solutions in the low three-figure monthly range are available, usually with a limited number of users or a reduced range of functions. A meaningful comparison, however, covers more than the licence.

Added to this are setup, migration of existing documents, training, ongoing administration and, depending on the model, costs per additional body or user. A low base price with expensive add-on modules can be more costly over three years than a higher flat rate.

The second hidden block of costs is internal time. If a system is so cumbersome that the board office spends additional hours on every meeting, the saving on the licence is quickly used up.

How important is integration into Microsoft 365?

Integration decides whether a portal is used in daily practice or bypassed. A portal that stands beside the familiar working environment gets bypassed as soon as it becomes inconvenient. Documents then get sent by email after all, because it is quicker, and the control the portal was acquired for is lost.

It is therefore worth asking whether a solution fits into the existing environment, for instance into Microsoft 365, so that permissions and identities are managed where they are maintained anyway. A departing member then loses their access through the same routine as everywhere else, rather than through a separate process someone has to remember.

At the same time, a caveat applies. Board documents need a stricter purpose limitation than project documents. An integration that levels this difference creates a new risk. The question is therefore not whether to integrate, but how.

What matters with mobile use and offline access?

With mobile use, what matters is less the offline capability itself than what happens to the locally stored data. For board members who prepare on the train or the plane, offline access is legitimate. Technically, however, it means that confidential documents reside locally on a device.

This is manageable when encryption, remote deletion and expiry periods take effect. It is a risk when these mechanisms are absent. The useful question is therefore not whether a solution works offline, but what happens to the locally stored data when the device is lost or the mandate ends.

How can a board portal be tested reliably?

A reliable test consists of playing through three concrete situations with real documents and real participants, rather than ticking off functions in a matrix.

First, a full meeting preparation, from the agenda to distribution, carried out by the board office itself and not by the provider. Second, the access of a member opening the software for the first time, without instructions. Third, the reconstruction of a resolution from the previous year, together with the documents on which it was based.

Anyone who completes these three runs knows more about a system than after five presentations.

The question behind the question

In the end, the choice of a board portal decides less about the digitalisation of a process, and more about how robust the working basis of a body will be in future. A good system makes visible what decisions were based on. A poor one shifts that visibility into a structure that, when it matters, no one can penetrate any more.

The decisive question is therefore not which portal can do the most, but which one presupposes least that everything goes well.

How Boardwise addresses these criteria

Boardwise has been developed along exactly these questions. The platform builds on the existing Microsoft 365 environment, so that identities and permissions are managed where organisations maintain them anyway. Board members work in a familiar interface, which lowers the hurdle for occasional users, and the board office retains central control over versions, access and deadlines.

At the same time, board documents keep their own purpose limitation, rather than merging with operational project data. Where AI is used, for instance to summarise extensive documents, it remains traceable what a summary is based on, so that the decision stays with the body and not with the machine.

Whether Boardwise is the right solution depends on the conditions this article describes. The three test runs with real documents are the best way to examine that for one's own organisation.

Frequently asked questions about choosing a board portal

What is a board portal?

A board portal is a protected digital platform through which executive boards, supervisory boards and other bodies prepare meetings, exchange documents securely, pass resolutions and document them. It replaces the scattered filing of email attachments, shared drives and printed meeting packs with a central, access-protected environment.

When is a board portal worth it?

A board portal becomes worth it as soon as documents regularly grow large, several bodies exist in parallel, external members need controlled access, or regulatory documentation obligations exist. For a small body with few meetings and lean documents, a well configured filing structure in the existing environment may suffice.

What does a board portal cost?

Solutions for smaller organisations start in the low three-figure monthly range, usually with a limited number of users. Beyond the licence come setup, migration, training, ongoing administration and, depending on the model, costs per body or user. A meaningful comparison considers the total cost over several years, not just the licence.

What should be considered regarding security?

Alongside end-to-end encryption, role-based rights and multi-factor authentication, a complete audit trail is decisive, documenting who accessed what and when. For mobile use, encryption, remote deletion and expiry periods for locally stored data are important.

Should a board portal be integrated into Microsoft 365?

Integration into the existing working environment lowers the hurdle to use and keeps permissions where they are managed anyway. What is decisive, however, is that board documents keep their stricter purpose limitation and do not fall into the same structure as project documents.

Similar articles