---
name: meeting-preparation-brief
description: Meeting Preparation Brief converts meeting date, agenda item, owner, prior decision into agenda-linked context, action-status table, decision requests, KPI snapshot, risks, and source notes, with cited evidence, explicit rules, and unresolved exceptions. Use for meeting preparation brief, recurring review, and decision preparation.
license: Apache-2.0
metadata:
  adlass.categories: "executive-strategy/meetings-decisions"
  adlass.industries: ""
  adlass.tags: "process-review,evidence,exceptions,decision-support,source-traceability"
  adlass.adaptation: "mapping"
  adlass.source: "original"
  adlass.version: "1"
---

# Meeting Preparation Brief

## Purpose

Meeting Preparation Brief turns the supplied records into agenda-linked context, action-status table, decision requests, KPI snapshot, risks, and source notes. It keeps source facts, derived values, recommendations, and limitations separate so each conclusion can be checked.

## Scope

Cover meeting date, agenda item, owner, prior decision, action ID, due date, status, KPI value, exception, decision needed. Preserve source identifiers, dates, units, and wording needed to trace every result.

**Excluded for agenda decisions and meeting readiness:** changing source records, taking external actions, making a human approval or employment decision, and asserting facts absent from the corpus.

## Data basis

- Process documents and tables containing meeting date, agenda item, owner, prior decision, action ID, due date, status, KPI value, exception, decision needed.
- Company policy, rubric, schema, templates, and reference tables in scope.
- Run input for period, audience, entity, or threshold when it changes this run.

## Result

Produce agenda-linked context, action-status table, decision requests, KPI snapshot, risks, and source notes. Each material row and conclusion cites a document, section, page, row, field, or run input.

## Quality criteria

- Every action carry-forward and metric freshness record is included or has an exclusion reason.
- Calculations state fields, units, denominator, and rule.
- Missing, contradictory, stale, and ambiguous values stay labelled rather than guessed.
- Facts, interpretations, and proposed next actions use separate fields.
- Supplied terminology, thresholds, and status values are used consistently.
- The final limitations section states what the corpus could not establish.

## Instructions

Organize evidence by agenda item. Carry forward every open action with owner, due date, and status; distinguish recorded decisions from proposed decisions and show metric period and unit. Preserve original values beside normalized values, cite every material finding, and use “not assessed” when required evidence or a rule is absent. When sources disagree, show both citations and explain the conflict. Keep row-level evidence in the supporting sheet and summarize only supported conclusions in the document.

## Adapt before use

- Map the agenda, minutes, and action-ID mapping fields and row citation convention.
- Add the governing policy, rubric, schema, or reference tables to the scope.
- Define thresholds, status values, units, and exception severity.