Board Meeting Packet Template
Five documents and three sheets, including a contributor tracker whose deadlines are each derived backwards from the date the packet has to reach directors.
Free download · No account needed
How a Contributor Deadline Is Derived
Twelve contributors, four deadlines
Halberd Instruments, Q4 FY27. Board meeting Thursday 12 November 2026. Seven calendar days' notice under the bylaws puts distribution on Thursday 5 November, and every date below is counted backwards from that one.
| Route | What still has to happen after the section arrives | Working days downstream | Required by | Float against one deadline |
|---|---|---|---|---|
| Financial statements | Ledger tie-out, CEO note, legal review, deck, chair sign-off | 8 | Mon 26 Oct | -3 |
| Feeds the CEO note | CEO note, legal review, deck, chair sign-off | 6 | Wed 28 Oct | -1 |
| Needs legal review | Legal review, deck, chair sign-off | 4 | Fri 30 Oct | +1 |
| Straight into the deck | Deck, chair sign-off | 2 | Tue 3 Nov | +3 |
The old convention put all twelve sections on Thursday 29 October, five working days before distribution. Two of the four routes need their sections earlier than that, so the deadline was already too late for four of the twelve on the day it was set. The other eight had one to three working days of room nobody had told them about.
What skipping the derivation cost
Seven contributors were chased last quarter, being everyone who delivered after 29 October. Four of those seven were never late against their own required-by date. Two contributors who were late got no chase at all, because they hit the date they had been given. One of the two was Finance, three working days past 26 October, and distribution landed on Tuesday 10 November: two calendar days with the book instead of seven.
A board packet runs on one date. Sections are due some fixed number of working days before distribution, every contributor gets the same date, and the week before the meeting goes on chasing whoever missed it. That date cannot be right for more than one contributor, because a submitted section is not finished work. It still has to pass whatever comes after it, and what comes after it differs by section.
Halberd Instruments, a fictional instrumentation manufacturer, distributes on Thursday 5 November 2026 for a Thursday 12 November meeting. Its financial statements sit eight working days upstream of distribution, through a ledger tie-out, the CEO note, legal review, deck assembly and chair sign-off. A committee report sits two working days upstream. Four routes, four required-by dates, spanning seven working days. The old convention put all twelve sections on Thursday 29 October, which was already too late for four of them.
So the chase went to the wrong people. Seven contributors were chased and four of them were never late. Two who were genuinely late got no message, because they hit the date they were given, and one was Finance at three working days past its real deadline. Directors got two calendar days with the book instead of seven. The register leaving the meeting gets the same treatment, filled from commitments attributed to whoever spoke them and then reconciled arithmetically. The standing meetings behind all of it are worth pricing off the calendar export first.
What is in the pack
Contributor Tracker
One row per section owner carrying its own derivation: the assembly steps still downstream, the working days they take, the required-by date that falls out, and the float. Sorted by float, which is chase order. The same problem on a wider list is a review cycle.
Action Item Register
Items carried in plus opened equals closed plus carried out, printed on every meeting. Aged in meetings rather than days, with the closure rate by time of asking on the same sheet.
Attendance and Governance Log
Board rate and aggregate rate side by side for every director, with the reason each denominator is what it is. Collapsing those two columns is what hides the mechanism.
How a Contributor Deadline Is Derived
Three pages to read before the tracker. The derivation itself, what negative float means, and why a required-by date in the past belongs with whoever owns the calendar rather than with the contributor.
Board Book
The assembled packet with front matter, a nine-item agenda marked decision, review or consent, and two reconciliations shown on the page. Every decision item carries the motion, the cost and the rejected alternative. The one-to-one with each director beforehand runs off a briefing sized to the gap in front of it.
Section Templates
One per owner, each opening with kind, ask, data cutoff and what changed since last quarter, and each stamped with the derived deadline for its own route rather than a shared one. The compensation committee's report is written against a band structure rather than a market summary.
CEO Note
Two pages written after the sections it draws on, so it can name a contradiction between two of them and put a number on it. Includes the paragraph on what the last note got wrong.
Minutes Draft
Drafted from the agenda before the meeting, with a resolution stub under every decision item. Records abstentions with their reasons, and dropped action items with who dropped them. The version written after the meeting, classified from the transcript into what the record actually needs, is a separate pack built around that judgment call.
How it works
- 1
Send the meeting date and your notice period
From the bylaws, the information rights clause, or a written board agreement. Subtracting it gives the distribution date, which is where every other date is measured from.
- 2
Name the assembly steps and their real durations
Ledger tie-out, executive note, legal review, deck, sign-off, in working days. Then say which steps each section actually passes through, because that is what makes the deadlines differ.
- 3
Deadlines come back derived, with float on every row
The first thing reported is how many sections your current single deadline is already too late for. A required-by date in the past goes to whoever owns the calendar, not to the contributor.
- 4
Chase by float, then carry the register forward
Smallest float first, and nothing to anyone who is not actually late. After the meeting the register reconciles and the minutes get drafted from the agenda you already built.
Frequently asked questions
Why would two contributors have different deadlines for the same packet?
Because a submitted section still has to pass through whatever comes after it. Halberd's financial statements sit eight working days upstream of distribution, through a ledger tie-out, the CEO note, legal review, the deck and sign-off. A committee report sits two. Same packet, six working days apart.
What does a negative float actually mean?
That the deadline was impossible before anybody started. Four of Halberd's twelve sections were being asked for by a date three or one working days after they were needed. That is a scheduling problem for whoever owns the notice period or the accounting close, and handing it to Finance as a deadline is how it survives four quarters.
How does the action register stop resetting every quarter?
One identity, printed on every register: carried in plus opened equals closed plus carried out. Halberd's Q2 FY27 register was circulated showing 13 out when its own figures gave 17, so four items had vanished. An item leaves closed, or dropped with a named person and a reason. Extracting commitments from the transcript is what fills it in the first place.
Why report the closure rate by time of asking?
Because it changes what you do with an old item. At Halberd an item closes 51 percent of the time at the first asking and 21 percent from the third onwards. So the four items past their second asking go to the board to be renegotiated: new owner, smaller scope, an agenda item in its own right, or dropped.
Why compute attendance per director rather than one board figure?
Because the threshold is an aggregate of board meetings held while a director plus committee meetings held while serving, so the denominator differs per person. Four Halberd directors each attended four of five board meetings and their aggregate rates are 80.0, 77.8, 75.0 and 72.7 percent. Only the last is named.
How quickly do the minutes have to go out?
Within five working days here, for two reasons. The register in them is the input to the next book's derivation. And an organisation filing Form 990 is asked whether every meeting was contemporaneously documented, meaning by the later of the next meeting or 60 days, which is comfortable until a meeting slips.
What format are the downloaded files, and is it free?
Five Word documents and three CSV sheets in one zip, free and with no account. The documents open in Word, Pages and Google Docs, the sheets in Excel, Numbers and Google Sheets. Edit with AI installs the same pack as a private Space and derives the deadlines against your own assembly chain.
Find out which of your deadlines were impossible
Send the meeting date, the notice period your bylaws require, and the real duration of each assembly step between a submitted section and a distributed packet. The first thing back is how many of your sections the current single deadline is already too late for, before any list of dates.
Edit with AI