Board Update Narrative and Metrics Brief

Public field comparison

Board Update Narrative and Metrics Brief

Board Update Narrative and Metrics Brief

Turn operating metrics and leadership notes into a board-ready narrative with evidence, risks, asks, and follow-up questions.

Convert supplied operating evidence and leadership notes into a candid board-update draft with reconciled metrics, traceable claims, risks, decision-ready asks, and explicit human review gates.

Use this for preparing board update narratives that connect metrics, risks, decisions, asks, and operating priorities.

Use this prompt to prepare evidence-controlled board meeting updates, founder briefs, operating-risk narratives, and strategic decision requests without implying that metrics were independently verified or that the brief was approved or distributed.

Board Meeting Update Preparation
Investor Narrative Drafting
Executive Metrics Synthesis
Operating Risk Communication
Strategic Asks and Decision Framing
Founder Board Prep

Board Meeting Update Preparation
Founder Board Prep
Executive Metrics Synthesis
Operating Risk Communication
Strategic Asks and Decision Framing
Investor Narrative Drafting with Separate Audience Review

Reporting period
Company goals
Key metrics
Metric definitions
Wins
Risks
Misses
Strategic priorities
Board asks
Sensitive topics

Reporting period
Company goals and strategic priorities
Metrics evidence
Operating outcomes
Risks and sensitive topics
Board asks and decision context
Review and distribution constraints

Paste the reporting period, company goals, metric results, definitions, wins, misses, risks, strategic priorities, sensitive topics, and board asks. Use the output as a board update draft, then have leadership, finance, legal, or relevant executives review it before distribution.

Use this prompt in a Claude account or workspace approved for the sensitivity of the board materials. Replace every bracketed variable with the applicable reporting-period information.

Provide only materials your organization authorizes Claude to process, such as metric exports, definitions, leadership notes, risk records, prior-period comparisons, decision papers, review evidence, and distribution constraints. Redact unnecessary personal data, credentials, customer secrets, privileged advice, security details, and other restricted information.

Confirm that every referenced file or attachment is actually visible in the Claude conversation before running the prompt. Resolve blocking metric, definition, arithmetic, risk, or decision discrepancies with finance or the accountable owner.

Before distribution, obtain the applicable leadership, finance, legal, governance, HR, compliance, security, or investor-relations review. Claude prepares a draft and reconciliation record; it does not approve, distribute, or independently verify the board package.

A founder preparing a monthly board update needs to explain slowing growth, rising churn risk, improving product usage, and a hiring request without hiding caveats or overclaiming progress.

A founder uses Claude to draft a monthly board brief from supplied KPI tables and leadership notes showing slower growth, possible churn pressure, improved product usage, and a proposed hiring decision. Claude must preserve conflicting figures, distinguish management explanations from evidence, make the hiring ask decision-ready, and report which finance and leadership checks remain pending; it must not imply that the board package was verified, approved, or sent.

Expert

Expert

Claude

Claude

strategy

strategy

board-update
executive-brief
metrics
strategy
investor-communication
operating-review
risk-management
board-meeting
decision-making
leadership

board-update
executive-brief
metrics
strategy
operating-review
risk-management
decision-making

Board Update Narrative and Metrics Brief Prompt

Board Update Narrative and Metrics Brief Prompt

Create board update narratives from metrics, risks, wins, misses, strategic priorities, board asks, and executive review notes.

Draft evidence-controlled board updates in Claude with reconciled metrics, traceable risks, decision-ready asks, and human approval gates.

Prompt-body line comparison

Removed Added Unchanged context

−You are a senior operator and board communications strategist preparing a board-ready metrics narrative and executive brief.
+Prepare a board-update narrative and metrics brief using only the information and source materials available in this Claude conversation.
 
−Your task is to turn operating metrics, leadership notes, wins, misses, risks, strategic priorities, and board asks into a clear board update that connects performance evidence to operating reality, management action, and decisions needed.
+## Inputs
 
−## Context Placeholders
−Use the context below. If a required placeholder is missing, ask for it before drafting sensitive or decision-heavy sections. If a non-critical placeholder is missing, name the gap, make a conservative assumption, and continue.
−- [Reporting period]
−- [Company goals]
−- [Key metrics]
−- [Metric definitions]
−- [Wins]
−- [Risks]
−- [Misses]
−- [Strategic priorities]
−- [Board asks]
−- [Sensitive topics]
+- Reporting scope: [Reporting period]
+- Goals and priorities: [Company goals and strategic priorities]
+- Metric records, definitions, units, periods, targets, prior results, segments, owners, and source references: [Metrics evidence]
+- Wins, misses, explanations, management actions, dependencies, and accountable owners: [Operating outcomes]
+- Known risks, incidents, uncertainty, and matters requiring restricted treatment or specialist review: [Risks and sensitive topics]
+- Decisions requested, deadlines, options, tradeoffs, and management recommendations: [Board asks and decision context]
+- Required reviewers, confidentiality limits, audience, format, and distribution conditions: [Review and distribution constraints]
 
−## Important Constraints
−- Do not invent facts, metrics, revenue, runway, customer status, contracts, hiring plans, investor commitments, approvals, screenshots, citations, or stakeholder positions.
−- Separate metric facts from interpretation, assumptions, narrative framing, and recommendations.
−- Include definitions and caveats before interpreting any metric.
−- Flag sensitive topics such as cash runway, churn, legal exposure, customer concentration, layoffs, security incidents, regulatory issues, financing, founder disputes, or board-level governance concerns.
−- Label confidence level for major conclusions: High, Medium, or Low.
−- Include a human review gate for legal, finance, compliance, security, HR, investor relations, customer-facing, or board-governance decisions.
−- Keep the narrative candid, concise, and board-appropriate. Do not hide risks, but do not dramatize them.
−- Make every recommendation specific to the supplied company context, metrics, operating constraints, and decision timeline.
−- Do not present the output as legal, financial, regulatory, or investment advice.
+## Claude and confidentiality boundaries
 
−## Step-by-Step Instructions
−1. Restate the reporting period, company goals, strategic priorities, available metrics, missing inputs, and sensitive topics.
−2. Build a metric evidence table that includes metric name, definition, current result, prior period or target if available, interpretation, caveat, confidence level, and owner.
−3. Identify the central board narrative: what changed, why it matters, what management is doing, and what the board needs to understand.
−4. Separate wins, misses, risks, and open decisions. For each, explain evidence, impact, management response, owner, urgency, and next action.
−5. Draft board-ready language that is candid, specific, and suitable for inclusion in a board package.
−6. Prepare likely board questions and concise management responses.
−7. Create a final executive prep checklist for review before the update is shared.
+Use Claude only to inspect, organize, compare, calculate from, and draft against material actually visible in this conversation.
 
−## Output Format
+Do not imply access to:
 
−### Board Narrative Snapshot
−Provide:
−- One-sentence headline for the reporting period
−- 3-5 board-level takeaways
−- What is improving
−- What is under pressure
−- What management is doing next
−- What the board should focus on
+- company systems;
+- board portals;
+- email;
+- live dashboards;
+- financial systems;
+- customer records;
+- external sources;
+- files or prior discussions whose contents are not available here.
 
−### Metrics Evidence Table
−Create a table with:
−- Metric
−- Definition
−- Current result
−- Target or prior period
−- Direction of travel
−- Interpretation
−- Caveat or data limitation
−- Confidence level
−- Owner or accountable function
+Do not claim that Claude:
 
−### Wins, Misses, and Operating Reality
+- independently verified a metric;
+- approved a recommendation;
+- obtained board consent;
+- sent or distributed the brief;
+- completed a management action;
+- contacted a stakeholder;
+- implemented a decision.
+
+Minimize the reproduction of:
+
+- personal data;
+- credentials;
+- customer secrets;
+- privileged legal advice;
+- confidential contract terms;
+- detailed security information;
+- unnecessary commercially sensitive material.
+
+When restricted information is necessary to explain a board issue, summarize it at the minimum level needed for the authorized audience and identify the required specialist review.
+
+## Evidence states
+
+Apply these evidence states consistently:
+
+- **Supplied fact** — directly stated in an identified source supplied in the conversation.
+- **Supplied management assertion** — reported by management but not independently established by the supplied evidence.
+- **Calculated result** — derived from supplied values using a displayed formula and rounding convention.
+- **Interpretation** — a reasoned explanation based on supplied evidence.
+- **Assumption** — a necessary proposition not established by the available evidence.
+- **Unknown** — information required for a conclusion but not provided.
+- **Conflict** — supplied sources disagree and the discrepancy remains unresolved.
+- **Unverified** — material exists or is asserted, but the available evidence is insufficient to rely on it.
+
+Confidence does not change an assumption, assertion, conflict, or unverified claim into a fact.
+
+## Management-action states
+
+Keep management actions separate from evidence states:
+
+- **Completed** — supplied evidence supports that the action occurred and identifies its result or current status.
+- **Underway** — supplied evidence supports that work has begun but is not complete.
+- **Proposed** — recommended or planned but not yet approved or executed.
+- **Pending review** — awaiting an identified human or specialist review.
+- **Blocked** — cannot proceed because a required input, authority, dependency, or decision is missing.
+- **Unknown** — the action status was not supplied.
+
+Do not label an action Completed merely because it appears in a plan, note, presentation, or prior commitment.
+
+## Input controls
+
+First determine whether the following are sufficiently clear:
+
+- reporting period;
+- company goals and priorities;
+- metric definitions;
+- current metric values;
+- units;
+- comparison periods or targets;
+- material wins and misses;
+- material risks;
+- the status of each board ask;
+- audience and distribution restrictions.
+
+Treat these as substantive gaps:
+
+- blank values;
+- ambiguous units;
+- mixed reporting periods;
+- incompatible metric definitions;
+- unexplained methodology changes;
+- conflicting figures;
+- totals that do not reconcile;
+- unsupported causal explanations;
+- unclear decision ownership;
+- asks without deadlines, options, or consequences of delay.
+
+When a blocking input is missing, ask one concise consolidated set of questions before drafting the affected conclusion or decision request.
+
+If follow-up is unavailable, complete only the unaffected sections and include a blocking-input register. Do not fill material gaps with invented data.
+
+For non-blocking omissions, use Unknown and explain the limitation.
+
+When sources conflict:
+
+1. Preserve both values or statements.
+2. Cite their source identifiers.
+3. Describe the nature of the discrepancy.
+4. Identify the accountable owner or evidence needed for reconciliation.
+5. Do not silently select a preferred figure.
+
+If no board ask, risk, miss, sensitive topic, or material exception exists, require an explicit supplied statement to that effect rather than inferring that none exists.
+
+## Metric and evidence rules
+
+Create source identifiers only for materials actually supplied. Use the source title or user-provided label where available.
+
+Do not invent:
+
+- document names;
+- quotations;
+- citations;
+- owners;
+- dates;
+- approvals;
+- targets;
+- benchmarks;
+- financial results;
+- customer commitments;
+- board positions.
+
+Tie every material metric, causal statement, risk assertion, management action, and board ask to one or more source identifiers or label it as an assumption, unknown, conflict, or unverified claim.
+
+Before interpreting a metric, state:
+
+- definition;
+- unit;
+- reporting period;
+- scope or segment;
+- comparison basis;
+- known caveat.
+
+Do not compare figures with incompatible definitions, periods, currencies, populations, or scopes.
+
+Recalculate percentages, changes, totals, ratios, and runway only when the required components are supplied. Show:
+
+- formula;
+- source values;
+- rounding convention;
+- resulting value.
+
+If components do not reconcile to a stated total, retain and quantify the discrepancy.
+
+Do not present a management explanation as an established cause unless the supplied evidence supports the causal relationship. Otherwise label it as:
+
+- management interpretation;
+- plausible explanation;
+- alternative explanation;
+- unresolved cause.
+
+## Confidence rules
+
+Use qualitative confidence only:
+
+- **High** — the definition, period, value, comparison basis, scope, and supporting sources align without a material unresolved conflict.
+- **Medium** — the evidence is relevant but incomplete, partially reconciled, or dependent on limited interpretation.
+- **Low** — the conclusion depends materially on assumptions, indirect observations, stale information, or unresolved conflicts.
+
+Explain every confidence rating briefly.
+
+Do not use numerical confidence percentages.
+
+## Risk rules
+
+Apply the organization’s supplied risk method when one is provided.
+
+Otherwise use:
+
+- High
+- Medium
+- Low
+- Unknown
+
+Base impact and likelihood on supplied evidence concerning:
+
+- affected objective;
+- financial or operational exposure;
+- customers or stakeholders affected;
+- timing;
+- existing controls;
+- mitigation progress;
+- incident or trend evidence.
+
+If the available evidence does not support a defensible impact or likelihood assessment, use Unknown.
+
+Do not infer likelihood solely from generic business experience or from the theoretical existence of a risk.
+
+## Authority, audience, and review limits
+
+Produce a draft for management review. This is not:
+
+- legal advice;
+- financial advice;
+- regulatory advice;
+- governance advice;
+- employment advice;
+- security advice;
+- investment advice;
+- evidence of board approval.
+
+Do not infer:
+
+- board consent;
+- investor support;
+- financing availability;
+- customer commitments;
+- contract status;
+- management authorization;
+- approval of a proposed action.
+
+Mark recommendations as Proposed.
+
+Mark legal, finance, HR, compliance, security, investor-relations, and governance review as Pending review unless supplied evidence establishes that the review occurred and defines its scope.
+
+Even when review evidence is supplied, state exactly what that evidence supports rather than declaring unrestricted or final approval.
+
+Keep board and investor audiences separate. Do not repurpose the board draft for investors, employees, customers, lenders, or the public without audience-specific review and authorization.
+
+## Focused workflow
+
+1. Build an intake and source register covering every input, source identifier, reporting scope, missing item, conflict, sensitivity restriction, and drafting blocker.
+
+2. Build a metric reconciliation ledger. Retain original values, normalize only where the conversion basis is supplied, show calculations, and identify definition, period, segment, currency, scope, or arithmetic mismatches.
+
+3. Determine the central reporting-period narrative from traceable evidence:
+
+   - what changed;
+   - why it matters;
+   - what remains uncertain;
+   - what management has completed, is doing, or proposes next;
+   - what the board needs to decide or monitor.
+
+4. Analyze wins and misses without treating activity as an outcome. Separate:
+
+   - evidenced result;
+   - management interpretation;
+   - plausible alternative explanation;
+   - dependency or constraint;
+   - next evidence checkpoint.
+
+5. Build the risk and response register. Preserve Unknown impact or likelihood where evidence is insufficient.
+
+6. Convert every board ask into a decision record containing:
+
+   - exact decision requested;
+   - decision owner;
+   - deadline;
+   - reason for timing;
+   - available options;
+   - tradeoffs;
+   - management recommendation marked Proposed;
+   - supporting evidence;
+   - assumptions;
+   - dependencies;
+   - consequences of delay;
+   - required specialist review;
+   - unresolved information.
+
+7. Draft likely board questions and concise management-response notes. Do not script unsupported certainty. State when management should return with evidence.
+
+8. Run the draft-acceptance and distribution checks. Revise only from supplied evidence; do not conceal or rewrite a failed check into a pass.
+
+## Required deliverable
+
+Keep the brief concise and proportional to the reporting period, evidence volume, material risks, and number of decisions.
+
+Use source identifiers to avoid repeating the same evidence across several sections.
+
+Where a section is genuinely not applicable, retain the heading, state Not applicable, and explain why.
+
+Never omit:
+
+- evidence and source coverage;
+- metric reconciliation;
+- material risks;
+- board decision records;
+- acceptance and distribution checks;
+- required human reviews.
+
+### A. Intake, source, and blocker register
+
 Provide:
−- Key wins and why they matter
−- Misses or underperformance areas
−- Root-cause interpretation
−- Management response
−- Dependencies or constraints
−- Follow-up actions
 
−### Risks and Management Actions
−Create a table with:
−- Risk
−- Evidence
−- Business impact
−- Severity
−- Management action
−- Owner
−- Timeline
−- Board visibility required
+- reporting scope;
+- source identifiers;
+- available evidence;
+- missing information;
+- conflicts;
+- sensitivity restrictions;
+- affected sections;
+- accountable reconciliation owner where supplied;
+- blocker status.
 
−### Board Asks and Decisions Needed
+### B. Board-period headline and narrative
+
 Provide:
−- Clear asks for the board
−- Why each ask matters now
−- Decision deadline
−- Options or tradeoffs
−- Recommended management position
−- Information still needed before final decision
 
−### Likely Board Questions
−List likely questions the board may ask, with concise suggested responses. Include questions about metrics, misses, risk, runway, hiring, customer health, growth, execution capacity, and strategic priorities where relevant.
+- one evidence-supported headline;
+- three to five board-level takeaways;
+- what improved and the supporting evidence;
+- what is under pressure;
+- what remains uncertain;
+- management actions by status;
+- matters requiring board attention;
+- source identifiers and confidence for each major conclusion.
 
−### Executive Prep Checklist
−Create a checklist covering:
−- Metrics verified
−- Definitions confirmed
−- Sensitive topics reviewed
−- Finance/legal/compliance review completed where needed
−- Owners aligned
−- Board asks clarified
−- Follow-up commitments documented
−- Narrative checked for overclaiming or missing caveats
+### C. Metric reconciliation ledger
 
−## Verification
−- Confirm every metric includes a definition or caveat before interpretation.
−- Confirm every major claim is tied to supplied evidence or clearly labeled as an assumption.
−- Confirm sensitive topics are flagged for executive review.
−- Confirm board asks are specific, time-bound, and decision-ready.
−- Confirm all relevant context placeholders were used.
−- List missing inputs, blocked assumptions, and human checks required before distribution.
+For every decision-relevant metric, provide:
 
−## Final Instruction to Begin
−Begin now. If required context is missing, ask for it first. Otherwise produce the full board update brief in the requested markdown format.
+- metric;
+- definition;
+- unit;
+- period;
+- scope or segment;
+- current value;
+- target or comparison;
+- direction;
+- calculation or reconciliation;
+- source identifier;
+- owner if supplied;
+- caveat;
+- evidence state;
+- confidence;
+- discrepancy disposition.
+
+### D. Operating outcomes analysis
+
+For every material win or miss, provide:
+
+- claimed outcome;
+- evidence;
+- business significance;
+- management interpretation;
+- plausible alternative explanation;
+- dependency or constraint;
+- management-action state;
+- owner if supplied;
+- next evidence checkpoint;
+- confidence.
+
+### E. Risk and response register
+
+For every material risk, provide:
+
+- risk statement;
+- supporting evidence;
+- affected objective;
+- impact;
+- likelihood;
+- time horizon;
+- existing control or mitigation;
+- proposed action;
+- action state;
+- owner if supplied;
+- review requirement;
+- board visibility;
+- residual uncertainty;
+- source identifier.
+
+### F. Board decision records
+
+For every ask, provide:
+
+- exact decision requested;
+- decision owner;
+- deadline;
+- timing rationale;
+- options;
+- tradeoffs;
+- Proposed management recommendation;
+- supporting evidence;
+- assumptions;
+- dependencies;
+- consequences of delay;
+- specialist reviews required;
+- information still needed;
+- decision-readiness status.
+
+If an ask is not decision-ready, explain the blocker rather than polishing it into apparent readiness.
+
+### G. Likely board questions and response notes
+
+Cover only relevant areas, such as:
+
+- growth;
+- retention;
+- customer health;
+- runway;
+- hiring;
+- execution capacity;
+- product usage;
+- operating misses;
+- risk exposure;
+- strategic priorities.
+
+Each response must cite supplied evidence or explicitly acknowledge an unknown, conflict, assumption, or follow-up commitment.
+
+### H. Draft acceptance and distribution gate
+
+For each check, provide:
+
+- check;
+- method;
+- evidence reviewed;
+- expected observation;
+- observed result;
+- status: Pass, Fail, Blocked, or Not applicable;
+- remediation or clarification needed.
+
+Run these checks:
+
+1. **Period and scope alignment** — compared figures use compatible periods and scopes, or all mismatches are disclosed.
+
+2. **Definition coverage** — every interpreted metric has a definition, unit, period, scope, and comparison basis.
+
+3. **Arithmetic reconciliation** — reproducible calculations agree with supplied components within the stated rounding convention, or discrepancies are quantified.
+
+4. **Claim traceability** — every material claim has a source identifier or an explicit assumption, unknown, conflict, or unverified label.
+
+5. **Cross-section consistency** — metric values, owners, dates, actions, and risk descriptions agree across the narrative, ledgers, and decision records.
+
+6. **Risk-action linkage** — every material risk has evidence, action state, timing, residual uncertainty, review requirement, and owner where supplied.
+
+7. **Decision readiness** — every board ask states the decision, deadline, options, tradeoffs, recommendation, dependencies, consequences of delay, and missing information.
+
+8. **Sensitive-topic handling** — restricted details are minimized and all applicable specialist reviews are identified with evidence-supported status.
+
+9. **Overclaiming control** — completed, approved, verified, committed, or distributed language appears only where supplied evidence supports that exact status.
+
+10. **Audience and distribution control** — the intended audience, reviewers, confidentiality limits, and distribution authority are explicit.
+
+End with exactly one draft-readiness status:
+
+- **Blocked** — critical scope, metric, risk, decision, or review evidence is missing or conflicting.
+- **Ready for management reconciliation** — the draft is usable, but factual, arithmetic, ownership, or cross-functional checks remain.
+- **Ready for executive approval review** — all drafting checks pass and the brief is ready to be considered by authorized executives.
+- **Ready to request board-package distribution approval** — all checks pass and the required review evidence is present, but final distribution authorization has not yet been supplied.
+
+None of these statuses constitutes approval, verification, distribution, board consent, or acceptance of a management recommendation.
+
+Conclude with a concise human-review checklist naming:
+
+- required functions;
+- unresolved items;
+- decision owners;
+- confidentiality restrictions;
+- distribution restrictions;
+- final authorization still required.