13d • Templates & Workflows
Calm Capacity Brief | Issue 002
Practical AI. Stronger systems. Room for the mission.
The Calm Infrastructure Lab | LUR Growth
Issue 002 | September 18, 2026
This week: build a board packet someone else can assemble
A board packet can look like a document, but it is really a chain of decisions.
Someone has to know which reports belong in it, where the approved numbers live, what changed since the last meeting, who can see sensitive information, and who decides that the packet is ready.
When those decisions live in one person's head, the packet becomes heavier every month. AI may help gather approved material or create a first draft, but it can't fix unclear ownership or decide what belongs in front of the board.
This week, the goal is simple: make one section of your next board packet clear enough for another person to assemble safely.
Three updates worth understanding
1. ChatGPT can work with more connected business data:
On September 10, OpenAI added a Data plugin to ChatGPT Business. It can help eligible teams analyze connected business data and create reports or dashboards. OpenAI notes that workspace administrators control installation and that connected-account permissions still apply.
Read the ChatGPT Business release notes: https://help.openai.com/en/articles/11391654-chatgpt-team-release-notes
My practical take: access is not the same as approval. Before connecting a source, name which board questions it supports, which fields are needed, and who is allowed to see the result. A faster report is not useful if it draws from the wrong source or exposes information the reader should not receive.
2. Microsoft is treating AI governance as an ongoing operating practice:
Microsoft's September 1 Responsible AI update describes governance that follows the full lifecycle of an AI system. It highlights tool permissions, action monitoring, practical controls, and the people responsible for implementing policy.
Read Microsoft's Responsible AI update: https://blogs.microsoft.com/on-the-issues/2026/09/01/responsible-ai-in-2026-how-we-are-adapting-for-whats-ahead/
My practical take: a written AI policy is a beginning, not a complete operating system. For a board packet workflow, record who gathers information, who checks each section, who approves the final packet, and what happens when the sources disagree. Review that process after each cycle.
3. Google is adding more specific access controls for Gemini Enterprise:
Google announced context-aware access controls for Gemini Enterprise on September 8, with a gradual rollout expected through September 15 for eligible plans. Administrators can apply access conditions such as device security and location. The feature is limited to the plans listed in Google's announcement and should not be assumed to exist in every Google Workspace account.
Read the Google Workspace update: https://workspaceupdates.googleblog.com/2026/09/context-aware-access-controls-are-available-for-Gemini-Enterprise-in-the-Admin-console.html
My practical take: vendor controls can support your rules, but they do not define them. Your organization still needs to decide whether board, personnel, client, donor, legal, or financial information may enter an AI tool at all. If the team cannot answer that question, keep the material out of the tool while you establish the boundary.
The signal underneath the updates
AI tools are becoming better at connecting to organizational data and taking action across systems. That increases what they can do, but it also increases the importance of source quality, access, ownership, and review.
You do not need an enterprise platform to practice those disciplines. You can start with the board packet your team already prepares.
Your 20-minute capacity practice
Choose one section of the next board packet, not the entire packet. A program update, financial summary, executive director report, or committee report is enough.
Write down:
1. Purpose: What question should this section help the board understand or decide?
2. Source: Where does each approved number, date, or claim originate?
3. Owner: Who gathers the information, and who is the backup?
4. Access: What information should not enter an AI tool or appear in the board version?
5. Review: Who checks facts, context, confidentiality, and final readiness?
6. Finish line: What evidence shows the section is complete and approved?
Then hand the map to a colleague and ask them to explain the process back to you. If they can't say where to begin, which source controls, or who approves the result, the workflow isn't ready for AI yet.
A safe practice instruction
Use fictional information or material your organization has explicitly approved for the selected tool.
Using only the approved source notes below, create a draft board-packet section with three parts: what happened, what the board should understand, and any decision or follow-up required. Cite the source label after every factual claim. Do not invent outcomes, explanations, dates, or numbers. Mark missing or conflicting information as NEEDS REVIEW. Do not include names or sensitive records. Do not send, share, or publish the draft.
Review the output against the source notes. Count the time spent gathering information, drafting, and correcting the result. The whole workflow matters, not only how quickly the first draft appeared.
Resource you can use this week
The Board Packet Handoff Map attached to this post helps you document one packet section, its sources, access boundary, reviewer, backup owner, and finish line. It includes a rehearsal so you can test whether someone else can assemble the section without relying on your memory.
From Systems That Hold
Grant Portfolio Reporting Should Not Require Another Spreadsheet Every Month
This field note offers five questions for turning scattered grant information into a reporting workflow leadership can trust.
Read the field note: https://lurgrowth.substack.com/p/grant-portfolio-reporting-should
The purpose is not to remove leadership judgment. It is to stop making one leader carry every step needed to reach that judgment.
Which section of your board packet would be hardest for someone else to assemble today?
Latoya
Latoya U. Robinson, M.S.
The Nonprofit Thrive Architect™
LUR Growth
Source notes
• OpenAI, ChatGPT Business release notes, September 10, 2026.
• Microsoft, Responsible AI in 2026, September 1, 2026.
• Google Workspace Updates, Context-aware access controls for Gemini Enterprise, September 8, 2026.
0
0 comments
Calm Capacity Brief | Issue 002
powered by
skool.com/the-calm-infrastructure-lab-3421
Calm capacity systems for nonprofit leaders: build ethical AI workflows, board-ready reporting, and sustainable operations—without the hype.
Suggested communities
Powered by