Board Meeting Preparation

The problem

A board meeting is where a company's leadership is held to what it said it would do. Preparing for one usually means a week of collecting slides from each function, reconciling numbers and trying to remember what was promised at the last meeting. The pack ends up describing each department's view of itself, and the cross-company story is assembled late, often the night before.

Picture an executive at a 120-person company six days before a quarterly board meeting. Finance is updating the numbers. The head of people is revising the hiring plan because two senior roles are still open. Operations has quietly moved the start of a new production line by a month after an equipment delay. Each change is known to its team. None of them has been written into one place, and the actions list from the last board meeting sits in a document nobody has opened since.

The risks are specific. A board member asks about an action agreed last quarter, and the room realises it was never assigned. A slip that was discussed in a management meeting is missing from the pack, so the board hears about it from a question. A decision the company needs, such as approving a credit line, arrives without the context the board needs to make it, and gets pushed to the next meeting.

None of this is about effort. It comes from preparation that depends on memory and on each team volunteering bad news.

What GeniOS is designed to surface

In pilot, GeniOS is designed to give the executive a prepared view before the board meets, drawn from email, calendar, chat, meeting notes and the business tools the company already uses.

• What slipped. Commitments and milestones that moved since the last board meeting, with when and where the change happened.
• What changed. Plans revised during the quarter, such as hiring, budgets or launch dates, with who changed them.
• Last meeting's actions. Each action agreed at the previous board meeting, with its owner and whether there is proof it was done.
• Decisions needed. Items that need a board decision, with the context and the date by which the company needs an answer.

Each item ends with Delegate, Done, Later or Not relevant. The executive can delegate a missing section to its owner, or a first draft of the cover note to a drafting agent, and approves everything before it is shared. For decisions waiting on leadership between meetings, see Executive Decision Monitoring; for the monthly investor version, see Investor Update Preparation.

A worked example

Example at a generic company. Names, dates and numbers are made up to explain the idea.

A 120-person industrial equipment company holds its quarterly board meeting next Thursday. Its chief operating officer owns the board pack. At the last meeting the board agreed four actions: start a second production line this quarter, hire a head of quality, review supplier contracts and come back with a financing proposal.

Here is how it would look in pilot: six days before the meeting, the chief operating officer receives one note. The new line start moved from this quarter to next, in an operations thread three weeks ago, after an equipment delivery slipped. The hiring plan changed: the head of quality role is still open, and the head of people has proposed using an interim lead. The supplier review was done, with the summary in a shared document. The financing proposal exists as a draft from the finance lead, and approving a credit line is the one decision the board needs to make this meeting.

The chief operating officer delegates a one-page explanation of the line delay to the operations head, asks the head of people for the interim proposal by Monday, and asks the finance lead to finish the credit line paper by Tuesday. Each request closes when the document arrives. The board pack goes out on Tuesday evening with the slip explained up front and the credit line decision framed with its context.

How teams use it day to day

Board Meeting Preparation is designed around the board calendar, with most of the work happening in the week before each meeting.

1. Capture actions at the meeting

   After each board meeting, agree the actions with owners and dates so they can be followed through the quarter.

2. Read the prepared view a week out

   About a week before the next meeting, read what slipped, what changed and which actions are still open.

3. Assign the missing pieces

   Delegate each gap in the pack to its owner with a date, early enough to finish it calmly.

4. Frame the decisions

   Make sure each decision the board needs has its context, options and the date the company needs an answer.

5. Approve and send

   Review and approve the pack and cover note before they go out. Nothing is sent without approval.

Where it applies

These are application areas where this use case can apply, not a list of current deployments. Our design partner work so far is in manufacturing, with Vaultex.

The use case applies to any company with a board or advisory board that meets on a regular calendar. That includes software companies, financial services firms, healthcare providers, manufacturers and energy businesses. The executive office would own the view, with investor relations, finance, and legal and compliance contributing the commitments and decisions their areas carry.

• Domains: Executive Office, Investor Relations, Finance, Legal & Compliance
• Industries: SaaS & Technology, Financial Services, Healthcare, Manufacturing, Energy & Utilities
• Roles: Executives

Status

Pilot We are shaping this use case with design partners now, and it is not yet a finished part of the product. If this is a problem you have, talk to us about shaping it with us. Design partners help us decide how far ahead of a board meeting the prepared view is most useful.