Board meeting guest access checklist
A board guest checklist ensures that an approved participant receives only the access, materials, and attendance window needed for a defined agenda item. It also assigns responsibility for admitting the guest and removing temporary access afterward.
Begin with written confirmation from the meeting's governance owner. Record the guest's purpose, agenda segment, required materials, arrival point, departure point, and host.
Limit the material scope
Ask the document owner which pages or files the guest needs and whether any version must be redacted. Do not share the full packet simply because that is easier than creating a scoped view.
Use the approved board portal or controlled distribution channel. Avoid forwarding attachments from a personal inbox or creating public links that cannot be withdrawn.
Verify access beforehand
Confirm the guest identity, address, time zone, accessibility needs, and connection method before the meeting day. Test the invitation from the guest perspective without exposing other agenda items or participant information.
Apply the principle of least privilege described in NIST least privilege guidance. Internal governance rules remain the authority for what the guest may receive.
Manage the live window
Name the person who admits the guest, signals the start of the item, and confirms departure. Give the chair a quiet escalation route if the agenda changes or the guest joins early.
Track preparation through the office operating rhythm so access checks do not compete with final packet work. Never ask the guest to wait in a space where restricted discussion can be heard.
Remove and record
After participation ends, remove temporary portal, meeting, folder, and distribution-list access as planned. Confirm the action with the governance owner and retain only the evidence required by policy.
Use the speaking engagement intake for external appearances that resemble a presentation but are not board business. Keep guest access decisions distinct from event logistics.
Confirm governance approval and purpose
The meeting owner should identify why the guest is needed and which agenda outcome their presence supports. Record the approving authority, host, agenda item, attendance window, and whether the guest will present, answer questions, or observe. The assistant should not infer approval from a forwarded invitation or from the guest's seniority.
Board access follows the organization's governance process.
Ask whether counsel, the chair, the corporate secretary, or another owner must review the invitation. A guest may be appropriate for one discussion but not for minutes, executive session, voting, or unrelated material. Write these boundaries before access is provisioned.
Clear limits make the meeting easier to run and give the host a sound basis for asking the guest to join or leave.
Scope board materials precisely
Create a material list tied to the guest's agenda item. The list should name the approved file versions, access start, access end, download permissions, and document owner. If a redacted or excerpted packet is required, the substantive owner must approve it.
The assistant can verify that the distributed file matches the approved list without deciding which confidential facts may be removed.
Do not reuse a director distribution group for convenience. A guest folder, portal role, or controlled link should prevent visibility into prior meetings and unrelated current materials. Test the account with a sample view before publishing sensitive content.
When the platform cannot provide the required scope, escalate the limitation and choose an approved alternative instead of widening access silently.
Confirm the guest's full name, role, organization, email address, mobile contact if required, time zone, and executive assistant or coordinator. Use a known organizer or another approved verification route rather than trusting a reply from a new address. Similar names and auto-completed email fields can produce serious distribution mistakes.
Send joining instructions through the approved channel and explain any identity check, confidentiality acknowledgment, device requirement, or arrival procedure. Keep instructions concise and separate from restricted materials. If the guest delegates participation to another person, treat that as a new approval and access request.
Access should never transfer simply because the original guest forwarded a link.
Prepare the guest and host
Tell the guest the purpose, expected contribution, time allocation, participants they need to know, material to review, and decisions outside their scope. Identify the host who will meet them, introduce the item, manage questions, and close follow-up. This preparation reduces wasted board time and prevents the assistant from having to interpret the substance during the meeting.
Brief the chair and meeting producer on the join cue, waiting location, departure cue, and backup contact. If the agenda runs early or late, the host should decide whether to adjust the guest's window. The assistant can coordinate the message.
A guest should not be admitted to restricted discussion merely because the schedule changed and nobody wanted to send an update.
Control physical participation
For an in-person meeting, confirm building access, reception, escort, room, seating, name display, device rules, printed materials, and the place the guest will wait. Do not leave packets in an unsecured room or on a public reception desk. Collect temporary badges and printed material at departure when policy requires it.
Plan for a private transition into and out of the room. The guest may need a nearby workspace, but it should not expose conversations, screens, or documents from other agenda items. If the guest brings an unapproved colleague or recording device, pause admission and contact the governance owner.
Courtesy does not override the meeting's access rules.
Control remote participation
For remote attendance, use a unique invitation or approved guest identity rather than a reusable board link. Confirm display name, audio, camera expectations, dial-in backup, waiting-room behavior, screen-sharing authority, and support contact. Test the setup without opening the live board room.
Technical readiness should not require early access to confidential conversation.
The meeting producer should admit the guest only at the approved cue and remove them after the item. Watch for reconnect attempts, forwarded links, or a second device. If the platform cannot confirm removal, tell the chair and follow the contingency plan.
Record the incident factually without speculating about the guest's intent.
Close every temporary access path
Use a closure checklist covering the board portal, meeting platform, shared folders, distribution groups, physical badges, printed copies, recordings, and follow-up workspaces. The system owner should confirm removal at the planned time. Do not assume that removing the calendar invitation revokes the underlying file or portal permission.
Notify the governance owner that access has closed and record any exception, such as an approved follow-up file that remains available. Apply the retention schedule to evidence of approval and removal. Avoid retaining screenshots or access exports without a defined need, because the closure process should not create a new collection of sensitive board information.
Review the guest experience and control
After the meeting, ask the host whether the guest was prepared, joined at the correct time, received the right material, and left with clear follow-up. Also note access errors, agenda changes, support problems, or material that arrived late. This review should be brief and tied to changes the team can actually make.
Update the checklist when a repeated failure has a clear cause. A portal problem may need a longer setup window, while late agenda changes may need a stronger chair cue. Keep governance decisions with the proper owner.
The assistant's job is to make the approved participation work cleanly and leave reliable evidence that its boundaries were honored.