01
Define the rollout scope
Do not start by migrating every historical document. Start with the next meeting and the records required to run it well.
A focused rollout gives directors a concrete workflow to learn and gives administrators a controlled way to test permissions, board packs, minutes, and actions.
- Choose the first board or committee
- Pick one upcoming meeting as the pilot
- Decide which historical records are needed immediately
- Name an administrator and backup owner
- Set success criteria for the first cycle
| Phase | Owner | Outcome |
|---|---|---|
| First 30 days | Board admin and CEO office | Pilot meeting selected, roles mapped, next board pack built in the portal |
| Days 31-60 | Board admin, chair, directors | First live meeting completed, minutes approved, actions assigned |
| Days 61-90 | Governance owner and IT/security | Committees added, historical records prioritized, security review closed |
02
Set roles and permissions
Access rules should be set before files move into the portal. That avoids accidental exposure and makes the first director experience cleaner.
Map real board roles instead of copying folder permissions from a shared drive. Directors, executives, committee members, observers, and assistants usually need different access.
- Board members
- Board chair or meeting owner
- Executives and presenters
- Committee members
- Observers and guests
- Administrative assistants
Where BoardKite helps
BoardKite lets teams model organization and meeting roles directly, so access follows the board workflow instead of inherited folder membership.
03
Prepare the first board cycle
The first board cycle should prove the system: agenda planning, board book assembly, circulation, live meeting use, minutes, approvals, and action follow-up.
Keep the process simple. A polished first meeting is more useful than a broad but incomplete migration.
- Create the agenda
- Attach supporting materials to agenda items
- Circulate the board pack
- Capture decisions during or after the meeting
- Draft and approve minutes
- Assign follow-up actions
Where BoardKite helps
BoardKite keeps these steps connected so the board pack, decisions, minutes, and action items stay part of the same record.
04
Worked example: scaleup 90-day rollout
A scaleup with a monthly board and two committees chooses the next full board meeting as the pilot. The chief of staff owns the rollout, the CFO owns finance papers, the chair reviews the agenda, and IT reviews SSO, access, and data processing.
The team does not migrate five years of folders first. It loads the next meeting, tests director access, circulates the pack, captures two decisions, approves minutes, and then uses the first cycle to decide what history is worth moving.
| Metric | Baseline | Pilot target |
|---|---|---|
| Board pack prep time | Two days of PDF assembly and link checking | Same-day pack assembly from agenda items |
| Director support tickets | Several access or version questions before each meeting | One or fewer access questions per meeting |
| Minutes cycle time | Two weeks from draft to approval | Draft within 48 hours, approval before next meeting |
| Action visibility | Spreadsheet updated after the meeting | Owners and due dates visible from the meeting record |
05
Train directors around jobs to be done
Training should be practical. Directors do not need a feature tour; they need to know how to find the current pack, prepare for the meeting, approve minutes, and review actions.
The best onboarding is short and role-specific. Administrators need configuration depth, while directors need confidence that the portal is easier than email.
- How to sign in and find the next meeting
- How to review the board pack
- How to find changed materials
- How to approve minutes or decisions
- How to search historical records
06
Cutover checklist for meeting day
Cutover should be boring. The board should know where to sign in, which pack is final, how late updates will appear, and who to contact if access fails.
Keep the legacy folder read-only during the pilot if needed, but make the portal the source of truth for the circulated board pack. Otherwise directors will split between tools and the test will not prove anything.
- Confirm every director can sign in before circulation
- Freeze or label the old file-sharing folder as not current
- Circulate the final pack from the portal
- Document who can approve late paper changes
- Assign one admin to monitor access issues during the meeting
- Capture decisions and actions in the portal before closing the meeting
07
What not to migrate yet
The fastest way to slow a board portal rollout is to treat it like a full archive project. Most teams do not need every old draft, duplicate PDF, source spreadsheet, and committee file in the portal on day one.
Move the records that directors and administrators actually need: recent minutes, active decisions, current committee charters, the next board pack, and the last few approved packs. Leave raw working files and deep historical archives in the existing system until there is a clear retrieval or compliance reason to move them.
| Migrate early | Leave for later |
|---|---|
| Next meeting agenda and final pack | Draft source files used to build the pack |
| Recent approved minutes and open actions | Old duplicate PDFs and obsolete pack versions |
| Committee records directors actively use | Large archives nobody has searched in years |
| Policies needed for current governance work | General company files that are not board records |
08
Review after the first meeting
After the first meeting, review what worked before expanding. Look for friction in access, document changes, director preparation, minutes approval, and action follow-up.
Then decide what to migrate next: past minutes, committee records, board book archives, recurring templates, or security policies.
- Were directors able to access materials without support?
- Were late document changes clear?
- Were decisions captured consistently?
- Did minutes approval happen faster?
- Were follow-up actions assigned and visible?