Board support
Key takeaways
- provisional intake
- governance layer
- closure authority
Operating data
Playbook
A board register sits between governance and execution. Capture each provisional item with its agenda source and exact decision language, but activate it only after authorized minutes, written consent, or the designated owner confirms the instruction. A director’s question is not automatically an action.
Give every active row an immutable identifier, governing source, deliverable, accountable executive, due date, audience, confidentiality class, dependency, evidence date, and closure authority. Separate board oversight from internal production tasks, linking the layers without crowding the governance record.
The assistant-owned action-register guide can structure management work. Review exceptions weekly: missing acknowledgment, outside dependency, date at risk, scope change, or evidence awaiting approval. Never silently rewrite an original commitment when timing changes.
Report as of a stated cutoff and close only when named authority accepts evidence. BoardSource roles guidance reinforces governance-management boundaries; governing documents remain authoritative. Use briefing preparation support for controlled evidence assembly.
Quarterly, audit overdue items, ambiguous owners, altered dates, excess access, and entries activated without a valid source. Preserve cancellations and replacements as explicit dispositions so reviewers can reconstruct history.
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.
