# Board Reporting Module - TheAICommand skill file

Name: Board Reporting Module
Version: 1.0
Date: 2026-08-15
Source: https://theaicommand.com/library/skills
Article: https://theaicommand.com/grc/skill-files-as-controlled-documents
Platforms: ChatGPT (Skills or a project), Claude (skills or project instructions), Microsoft 365 Copilot (Agent Builder)
Tested against: Claude Fable 5 (Anthropic), 15 August 2026 - pass. All other platforms: not yet tested.
Changelog:
- v1.0 (2026-08-15): Initial library release. Extracted from the published article.
Licence: Free to use and adapt internally. Attribution appreciated. No warranty. Educational purposes only.
Disclaimer: General information and education only. Not legal, compliance, financial, or professional advice.

---

# Skill: Board Reporting Module

Version: 1.0
Owner: [ROLE_OR_NAME]
Approver: [ROLE_OR_NAME]
Approved on: [DATE]
Review trigger: quarterly, or on any change to the obligations, committees or
source systems this file assumes

## Change log
v1.0 [DATE]. Initial version approved for use in board and committee reporting.

## Purpose
Turns working material from the risk and compliance team into a draft board-pack
module for a named committee. The output is a decision-ready draft for the
module owner to verify, never a finished paper.

## When to use
Use when a board or committee pack module is due and the input documents are
assembled. Do not use for ad hoc queries, for matters under legal privilege, or
where inputs contain personal information that has not been removed.

## Inputs required
- Committee and reporting period: [COMMITTEE], [PERIOD]
- The prior period's module: [PRIOR_MODULE]
- Input documents, each with a date: [INPUT_DOCUMENTS]
- Decisions the paper seeks: [DECISIONS_SOUGHT, or none]

## Method
1. Read every input document before drafting anything.
2. Open with a BLUF: the one paragraph the committee must absorb.
3. Draft the movement section: what changed since the prior module, citing the
   input document each change comes from.
4. Describe the metrics table: which metrics, which period, and which source
   document holds each number. Never invent or recalculate a number.
5. State each decision sought as a single clear sentence.
6. Build the evidence trail: list every input document with its date.
7. Flag every statement the prior module made that these inputs no longer
   support, rather than carrying it forward.

## Output format
BLUF / Movement since last report / Metrics table description / Decisions
sought / Evidence trail (every input document and its date) / Gaps flagged.

## Guardrails
- No number appears in the draft unless it appears in an input document.
- The evidence trail section is mandatory and is never trimmed for length.
- Every draft is headed DRAFT: UNAPPROVED until the owner signs off.
- If an input appears to contain personal information, stop and ask.
- The skill drafts the module. The owner verifies every line against source
  documents and remains accountable for what the committee reads.