Which Version of a Board Pack Did Directors Actually Receive?

A director opens the board pack on Friday. Finance replaces a forecast on Monday morning, and the portal now shows only the new file. The secretary needs to reconstruct the Friday release, explain Monday's change, and identify which material supported the meeting's decisions.

Start with the exact released package, its approval, intended recipients, and release time. Then examine the available delivery, access, or acknowledgment evidence. A record that a pack was made available establishes something different from proof that a director downloaded, acknowledged, or read it.

Follow each pack through preparation, release, and retention

1. 1 · Prepare

   Select the exact papers

   Connect agenda items, document versions, approvers, and the proposed audience.

2. 2 · Release

   Preserve the issued set

   Record the approved package, recipients, release time, and subsequent supplements.

3. 3 · Retain

   Connect the meeting record

   Link minutes, resolutions, attendance, and action follow-up to the material considered.

Give the meeting and each release their own identity

Create a meeting record with the board or committee, meeting date, agenda, responsible secretary, participant group, deadlines, and confidentiality rules. Give each released pack or supplement a distinct reference within that meeting. Links to current working papers can remain useful during preparation.

For release, preserve a protected manifest listing the exact document IDs, versions, titles, order, and recipient set, with checksums where used. FormKiQ's document model provides stable document identities and version context. The application must associate the approved selection with the release it represents.

If members receive a combined PDF, retain that exact output with its manifest and approval. Changes in templates, conversion, or ordering can produce a different file later. Keep the issued rendition as well as the source papers.

Keep four record states distinct

Handle Monday's forecast as a new release

In the example, Friday's pack contains forecast version 3. Finance submits version 4 on Monday with a correction. Keep Friday's pack intact, review the replacement, and issue an approved supplement or replacement pack with its own release reference.

Identify the affected agenda item and explain which earlier material the change supersedes. Record recipients, notification attempts, failures, and any required acknowledgment. During the meeting, the secretary can identify which forecast the discussion and decision relied on.

Check the audience before assembling and releasing the pack

Committee membership and item-specific restrictions can differ. Where a recusal or confidentiality rule excludes a director from an agenda item, check the paper, attachments, generated pack, search results, and exports. Restricting a source document is ineffective if its contents remain inside a broadly shared PDF.

Create the appropriate audience-specific selection and output before release. Recheck membership if it changes after approval. OWASP recommends validating permissions on every request; apply that principle to later access as well. Revoking portal access cannot remove a copy already downloaded.

Describe what each distribution event establishes

Keep the intended recipient list and release record separate from sending attempts, provider delivery results, download activity, and explicit acknowledgments. Define what the selected channel records and what remains unknown. A generated access link alone does not establish that a file reached the director's device.

Where acknowledgment is required, collect an authenticated response tied to the release reference and version. Record its scope, such as receipt of the pack, without treating it as proof that the director understood every paper. Assign unresolved delivery or acknowledgment work to an owner.

Connect decisions to the material considered

Link minutes, resolutions, attendance, declarations, and action items to the relevant agenda item and release. Preserve corrections to approved minutes with their review history. Give action owners and due dates their own tracking so approval of the minutes does not imply every action is complete.

Retain the required meeting records, releases, restricted source papers, and available distribution evidence under the organisation's record policies and applicable holds. Keep enough identity and historical membership context to explain earlier releases without granting former participants continued access.

Test one meeting from release through follow-up

• Reconstruct Friday's exact pack and its approved recipient set.
• Release Monday's forecast correction while preserving the earlier pack and notification history.
• Change committee membership between approval and release and verify the resulting selection.
• Exclude a restricted agenda item from the relevant recipient's pack, attachments, and exports.
• Distinguish release, delivery results, access activity, and explicit acknowledgment.
• Trace a resolution and its open actions to the papers considered and approved meeting record.

Preserve the pack, its audience, and its outcome

A reliable board-pack record identifies the exact released material, the intended audience, subsequent changes, and the evidence available about distribution. Connect that record to the meeting's decisions and follow-up so a later review can explain the sequence without relying on the current portal view.