Prepare a Board Decision Pack Outline from Management Updates with ChatGPT

Management updates explain activity, progress, and concerns. A board decision pack must also make clear what the board is being asked to decide and which evidence supports that request. Simply combining updates into a long document can leave the decision buried among operational details.

This guide produces an original decision pack outline and a source-linked request register with ChatGPT. Examples are fictional. Current OpenAI documentation was checked on October 6, 2026. Adapt the outline to the organization's approved board process and pack structure; it does not define legal governance requirements or authorize any decision.

Confirm the meeting and pack requirements

Start with the meeting date, information cutoff, audience, approved agenda, and submission process. Identify the pack owner and the roles responsible for reviewing individual sections. Use the organization's actual requirements rather than a generic structure inferred from the word “board.”

Confirm which items are for decision, discussion, or information. An update containing a problem does not automatically constitute a request for approval. Ask the responsible manager what action is being requested and whether the board is the appropriate decision owner under the approved process.

Set the output boundary. The first deliverable should be a reviewable outline and request register, not a final pack containing invented recommendations, resolutions, or signatures. Establish the structure before drafting the narrative.

Build a source register for management updates

Collect the approved updates and supporting records with stable IDs, authors, dates, and versions. Note the reporting period for each update. A monthly report and a quarter-end report may describe the same metric over different intervals and should not be compared without that distinction.

OpenAI's projects documentation describes organizing related sources and chats. A pack workspace can use that organization, but the owner must confirm the source set and its cutoff. Do not assume a missing update is available merely because another document mentions it.

Preserve restrictions and audience requirements through the organization's process. Include only relevant approved material in the analysis packet. The pack outline should identify a necessary restricted appendix without reproducing unrelated confidential details in a general summary.

Extract requests separately from status reporting

Ask ChatGPT to identify explicit decision requests, candidate discussion items, and information-only updates. Require a source passage for each classification. A sentence such as “capacity remains constrained” reports a condition; it does not specify which change should be approved.

For every decision request, identify the proposed action, owner, timing, options supplied, supporting evidence, and unresolved conditions. If the source does not include an option comparison, mark that omission. Do not make the request look complete by generating unsupported alternatives.

Keep candidate requests awaiting manager confirmation distinct from confirmed requests. This prevents an analytical suggestion from entering the agenda as if it had already been authorized.

Ask for a source-linked outline

Provide the approved pack template, agenda, source register, and request schema. Require the model to preserve the template's required sections and flag gaps instead of replacing them with a generic presentation format.

Create a board decision pack outline from the supplied management updates.
Follow the approved agenda and pack structure.
Separate confirmed decision requests, discussion items, and information updates.
For each item cite source IDs and identify the sponsoring role.
Preserve reporting periods, units, qualifications, and unresolved conditions.
Do not invent approvals, resolutions, metrics, or recommended options.
Return the outline, request register, missing-information queue, and proposed appendix index.

Review the classifications with the pack owner. The model can find language suggesting a decision, but only the organization's process can establish that the item belongs before the board in that form.

Structure each decision paper

Use a consistent sequence: decision requested, context, supplied options, evidence, dependencies, unresolved questions, and proposed next step after approval. Keep the request near the start so readers understand why the paper is included.

Connect each material claim to its source. Distinguish reported facts from management estimates and commentary. A manager's expectation about next quarter is not an actual result, even if the update describes it confidently.

If a recommendation is part of the approved source material, retain its attribution and rationale. If no recommendation exists, identify the missing managerial decision. The pack outline should not silently create a position on behalf of management.

Work through a fictional item

Suppose a fictional update reports a delayed training rollout and asks for approval to run a smaller pilot. The source specifies the proposed pilot scope and its dependency on a reviewed lesson set. The pack outline can create a decision item with that request and link the supporting update.

It should also identify what remains missing, such as the approved pilot success criteria or a confirmed review owner. It should not promise that the pilot will eliminate the delay or state that the board has approved it.

A separate update about completed documentation revisions may be information-only. Include it in the appropriate section if the agenda requires it, rather than creating a redundant decision request simply because the topic relates to the pilot.

Reconcile metrics and repeated narratives

Compare repeated figures across updates, preserving units, time periods, definitions, and source versions. If two departments report different values for the same apparent measure, create a reconciliation question instead of selecting the more convenient number.

Group repeated project narratives while retaining their source references. The main pack can present one concise account with clearly attributed perspectives. Differences in interpretation should remain visible when they affect the requested decision.

Use a separate assumption register for conditions a proposal depends on but has not confirmed. Link material assumptions to the relevant decision item instead of distributing them vaguely across the pack.

Review the outline before drafting the full pack

Have the responsible owners confirm each request, classification, evidence trail, and missing-information item. Check that every agenda item has an appropriate supporting section and that the appendix index points to the intended document versions.

Remove unsupported commitments from future-tense wording. “If approved, the sponsoring team proposes this next step” preserves status more accurately than “The team will begin” when approval is still pending. Use the organization's approved phrasing for formal decision records.

After the outline is approved, draft the full pack within that structure and review the resulting facts and references again. Preserve the outline version, source cutoff, owner decisions, and final pack together. The process produces a traceable briefing structure without disguising incomplete requests as settled decisions.

Frequently asked questions