Executive Assistant Scheduling Software for Confidential Board Committee Meetings

Schedule a confidential committee meeting in eight controlled steps

Use this runbook for one compensation or audit committee session involving a chair, outside directors, outside counsel, the corporate secretary, the executive’s EA, and director EAs across Google Workspace and Microsoft 365. The board, legal, privacy, and security owners must set the organization’s rules. The workflow does not create confidentiality, legal privilege, or compliance by itself.

1. 1

   Open a restricted control brief before outreach

   Create one meeting ID and one restricted source of truth. Record the neutral purpose class, committee, duration, bounded date range, deadline, required roles, optional roles, organizer calendar, IANA zones, notice and buffer rules, relationship owner, disclosure owner, approval owner, materials owner, outreach channels, invitation policy, and terminal proof. Put the sensitive subject, personnel names, legal analysis, and draft agenda only where their designated owners allow them.
   • The control brief names who may know the committee, the subject, the attendee list, and the materials.
   • The EA keeps relationship judgment, disclosure, approvals, exceptions, agenda, and pre-read work.
   • A hold, poll result, draft, or open calendar cell is not booked.
2. 2

   Build a disclosure-and-role roster

   Separate meeting participants from scheduling contacts. For each outside director and counsel participant, record the verified identity, role, required or optional status, approved assistant, calendar source, local zone, contact channel, and the minimum wording that contact may receive. Name who may add, remove, or substitute a participant. Never infer committee membership or copy a director’s assistant onto meeting content just because that assistant supplied availability.
   • Scheduling contact does not automatically mean meeting attendee or materials recipient.
   • Counsel or the corporate secretary owns any privilege and governance decisions; the calendar system does not.
   • Distribution lists and autocomplete recipients are expanded and reviewed before sending.
3. 3

   Set calendar authority and privacy boundaries

   Document who may read free/busy, see private-event details, send as organizer, place a neutral hold, contact each assistant, approve wording, write the invitation, and cancel or repair it. Request only the provider access the workflow needs. Google and Microsoft expose different sharing, private-item, and delegate controls; a calendar permission proves technical access, not business authority.
   • Private-event detail is not collected when busy intervals will do.
   • Every connected account, delegate, and service identity has a named owner and revocation path.
   • A private label is treated as one provider control, not a promise that every privileged viewer is blocked.
4. 4

   Collect availability on the minimum-disclosure track

   Read approved Google or Microsoft free/busy for connected calendars. Contact unconnected directors, EAs, and counsel through approved channels with a neutral meeting label, duration, bounded window, local times, response deadline, correction path, and reminder cap. Record source, actor, IANA zone, reply time, freshness, expiry, and consent for that coordination use. Do not put the sensitive subject, another director’s response, or board material into a poll or broad thread.
   • External participants can reply without connecting a calendar.
   • Silence, failed access, and an expired window remain unknown rather than free.
   • The disclosure owner approves any wording change that reveals more than the neutral label.
5. 5

   Compute slots against attendance and handling rules

   Intersect every required participant, then apply the approved committee attendance rule, working hours, notice, buffers, travel constraints, protected preparation time, conferencing policy, and proposal expiry. Rank preferences only after hard rules pass. Treat any quorum, independence, recusal, substitute, or adviser rule as supplied policy from the designated governance owner, never as a scheduling model’s legal conclusion.
   • An optional observer cannot displace a required outside director.
   • Each candidate is rendered in every participant’s named local zone.
   • No-overlap produces one bounded exception instead of a wider disclosure blast.
6. 6

   Return one decision when policy cannot finish

   Show the EA or named owner only the choice that remains: widen the date range, release protected time, shorten duration, change format, approve an already-authorized substitute, contact another assistant, or stop. Include current candidate times, role coverage, evidence freshness, disclosure effect, deadline, and expiry. Keep unrelated event titles, director responses, compensation detail, audit issues, and legal notes out of the decision card.
   • The person deciding can see the consequence without seeing unrelated calendar content.
   • Only a named owner can change attendance, disclosure, or protected-time policy.
   • The EA can pause, revise, or reclaim the meeting at any point.
7. 7

   Separate the calendar invitation from board materials

   Re-check required availability and current approval, then write one invitation under the approved organizer. Review every field: neutral title, start and end, zone, attendee list, organizer identity, free/busy status, privacy setting, location, conferencing, description, reminders, attachments, guest permissions, and forwarding behavior. Put agenda and pre-read documents in the organization’s approved restricted repository or board portal and add only the approved access reference to the invitation.
   • The title does not expose a compensation subject, investigation, transaction, person, or legal theory.
   • No board document is attached or linked unless the materials owner approved the audience and access path.
   • Conferencing and room details reach the intended participants without broadening the recipient list.
8. 8

   Read back, test, and close one meeting state

   Read the provider state after the write. Verify organizer, exact time and zone, required attendees, optional decisions, title, privacy, conferencing, description, attachments, and invitation delivery state. Reconcile an uncertain write before retrying. When a participant, time, or disclosure rule changes, revoke affected proposals and approvals, update material access through its owner, issue one traceable repair, and verify again.
   • A repeated approval or provider retry cannot create a duplicate event.
   • Removing an attendee from the calendar does not pretend to revoke a document already shared elsewhere.
   • Completion means one verified invitation set or one bounded exception with an owner and deadline.

Compare confidential board meeting scheduling by completion and exposure

The best fit is not the tool with the most calendar access. It is the operating path that completes routine coordination with the least necessary disclosure while preserving EA and governance-owner control.