Board Support Evidence Duties for Executive Assistants

Board Support Evidence Duties for Executive Assistants

by ExecutiveAssistantAgency Editorial Team · 6 min read

An analysis of board support evidence duties for executive assistants, covering record sets, version control, distribution proof, decisions, and cycle reconciliation.

In this article
  1. Board support is evidence work
  2. Define the board record set
  3. Track versions and approvals
  4. Prove distribution and access
  5. Evidence the meeting itself
  6. Capture decisions and follow-ups
  7. Protect confidentiality across the cycle
  8. Reconcile the record after the meeting
  9. Review the cycle with the board secretary

Board support is evidence work

Board support looks like scheduling and document collection, but its real product is a defensible record. Directors, auditors, and regulators may later ask what the board received, when it received it, and what it decided. The assistant is often the only person who can reconstruct that sequence. Treating the work as logistics misses the point. The board cycle is a series of evidence points that must line up.

The evidence does not need to be elaborate. A versioned pack, a distribution log, and a decision record cover most of the need. The problem is that these artifacts are usually produced in different tools by different people. An assistant who connects them creates a record that survives scrutiny. An assistant who treats each task separately creates a set of fragments.

Define the board record set

Start by naming the records the office must be able to produce after a board cycle. The set typically includes the notice and agenda, the final board pack, the attendance list, the minutes or decision log, and the follow-up action list. It may also include conflict disclosures, committee reports, and resolutions. Write the list down and assign an owner for each item.

The record set should distinguish between documents that are final and documents that are working drafts. A draft has value during preparation but should not be mistaken for the approved version later. Label each file with its status and its date. A simple status field prevents a draft from being cited as the board's decision, and include the approval date beside the status so the sequence is clear.

Track versions and approvals

Version drift is the most common board support failure. A director reads one version, the executive presents another, and the minutes reference a third. The cause is usually a filename that looks current but is not. A version log with a date, an approver, and a short change note fixes most of the problem. The board paper version control log describes a lightweight way to run it.

Approval should be recorded against the version that will be distributed. An email approval for an earlier draft does not cover a later edit. When a document changes after approval, route it again or record the approver's confirmation of the change. The assistant does not need to judge the substance, only to keep the approval aligned with the file. That alignment is the core of the control.

Prove distribution and access

A board pack that was uploaded is not necessarily a pack that was received. Record when the pack was distributed, through which channel, and to which list. Keep the distribution notice with the final pack. If a director reports a problem, the log shows whether the issue was access, timing, or format. Without the log, every dispute becomes a memory contest.

Access deserves its own check. Confirm that each director and invited guest can open the pack before the meeting. Remove access for anyone who has left the board or should not see the material. Review the permission list against the current roster rather than last cycle's roster. A stale permission is both a confidentiality risk and a source of confusion during the meeting.

Evidence the meeting itself

The meeting record should show who attended, what was presented, and what was decided. Attendance is more than a sign-in sheet; it supports quorum and voting. The presented materials should match the distributed pack, or the difference should be noted. Decisions should be recorded with the owner and the effective date. A recording can supplement the record but should not replace it.

An assistant can prepare the decision capture before the meeting by listing the items that require a vote. During the meeting, note the outcome and any condition attached to it. After the meeting, confirm the wording with the chair or the board secretary. A short confirmation prevents an ambiguous minute from becoming a disputed action, and store it with the decision log rather than in a personal notebook.

Capture decisions and follow-ups

The follow-up list is where board support becomes management work. Each action needs an owner, a due date, and a status. The list should be reviewed at the next meeting rather than left in a folder. A follow-up that nobody tracks is effectively a decision that was never implemented. The assistant's role is to keep the list visible and current.

Use the same identifier for an action across the minutes, the follow-up list, and any status report. Consistent identifiers make it easy to trace an item from the board room to the operating team. When an action slips, record the reason and the new date. A history of slippage is useful evidence for the next board discussion, especially when the same owner has slipped more than once.

Protect confidentiality across the cycle

Board material often contains sensitive commercial, legal, and personnel information. The assistant should know which parts are restricted and who may see them. Use a separate folder or a restricted section for the most sensitive items. Do not rely on a filename to signal confidentiality. A clear label and a controlled access list are stronger, and review that list whenever a director leaves the board.

The NIST access control guidance is a useful reference for limiting access to what a role requires. Apply the same idea to board portals, shared drives, and printed copies. Collect printed materials after the meeting or shred them according to policy. Confidentiality is a lifecycle property, not a setting applied once, so review the access list at the start and end of every cycle.

Reconcile the record after the meeting

After the meeting, reconcile the final pack, the minutes, and the follow-up list. Check that every decision in the minutes refers to a document in the pack. Check that every action has an owner and a date. Note any document that was replaced during the session and update the version log. This reconciliation is the step that turns a pile of files into a board record.

Resolve discrepancies with the board secretary rather than editing silently. A discrepancy may reveal a missing approval or an undocumented decision. Record how it was resolved and who confirmed the correction. The reconciliation note is short, but it demonstrates that the record was reviewed rather than assembled, and share it with the chair when the correction affects a decision or a disclosed conflict.

Review the cycle with the board secretary

At the end of each board cycle, hold a short review with the board secretary. Ask which documents arrived late, which access problems occurred, and which decisions needed clarification. Capture the answers as process fixes for the next cycle. A ten-minute review is enough to prevent the same friction from repeating, and assign an owner to each fix before the next cycle begins.

Once a year, review the full record set and the retention policy. Confirm that the office can still produce a complete packet for an older meeting. Check that departed directors no longer have access and that the archive is readable. The IRS recordkeeping guidance offers a general reference for retention discipline, though the board's own policy governs, so confirm the retention period with the board secretary each year.

Board support evidence is unglamorous work with a long tail. A clean record protects the executive, the board, and the assistant who assembled it. For help with board cycles and executive meeting coverage, contact us to discuss assistant support. The night-before board packet routine and the board portal permissions checklist put this analysis into practice, and a short cycle review keeps the evidence current, the access list accurate, the follow-up owners accountable, the retention dates visible, and the chair informed well before the next cycle begins.

★★★★★

“My EA handles everything from board prep to multi-city travel, and I finally have time to focus on the work that matters.”

Chief Executive Officer, Series B SaaS company