Use ChatGPT Canvas to Review a Memo Against a Decision Checklist

A memo can sound finished while leaving the decision itself unclear. A short review in ChatGPT Canvas can expose missing evidence, open questions, and unsupported recommendations before the memo reaches a manager.

This is a documentation-based workflow. It uses a fictional memo, so the output below is illustrative rather than a report of a personal test.

The fictional input

Imagine that Maya, an operations manager, has a memo called Q4-support-hours.md:

Q4 support coverage proposal

The support team should move to extended weekday coverage in November. Customer demand is increasing, and the change will improve response times. The team can cover the extra hours with the current rota. We should announce the change next week.

Decision requested: approve the new coverage pattern.

Maya also has this checklist:

Decision checklist

1. The memo states the requested decision.
2. It identifies the evidence for the demand claim.
3. It shows the staffing assumption behind the rota claim.
4. It names the implementation owner and date.
5. It lists an unresolved risk or question.

The checklist is the review contract. It tells ChatGPT what to check and gives Maya something concrete to inspect afterward.

Three steps

1. Open Canvas in ChatGPT and paste the memo. OpenAI describes Canvas as an interactive workspace for co-writing and editing, with inline suggestions and file support. Availability can depend on the current model and account.

2. Paste the checklist below after the memo. Ask for a review table first. Tell ChatGPT to quote the relevant memo passage, mark each item as supported, missing, or unclear, and explain the reason in one sentence. Tell it to preserve unknowns instead of filling them in.

3. Review the table against the memo. Select any passage that needs work and ask for a suggested edit in Canvas. Keep a copy of the original until a manager approves the revised wording.

Copy this prompt

Review the memo below against the checklist. Work in a review-first way.

Rules:
- Use only the memo and checklist as evidence.
- Do not invent numbers, owners, dates, causes, or customer results.
- Quote the smallest memo passage that supports each finding.
- Mark every checklist item as supported, missing, or unclear.
- For missing or unclear items, write a question for the decision owner.
- Do not rewrite the memo yet.

Return this table:
1. Checklist item
2. Status
3. Evidence quote or "No supporting passage"
4. Owner question

After the table, write a short list called "Safe revision requests". Each request must say what to clarify without supplying the missing fact.

Memo:
[PASTE MEMO]

Checklist:
[PASTE CHECKLIST]

Illustrative output

Review table

| Checklist item | Status | Evidence quote or No supporting passage | Owner question |
| --- | --- | --- | --- |
| The memo states the requested decision. | supported | "Decision requested: approve the new coverage pattern." | None from this memo. |
| It identifies the evidence for the demand claim. | missing | No supporting passage. | Which demand record supports the claim that customer demand is increasing? |
| It shows the staffing assumption behind the rota claim. | missing | No supporting passage. | Who confirmed that the current rota can cover the extra hours? |
| It names the implementation owner and date. | missing | No supporting passage. | Who owns the change, and what date is approved for the first shift? |
| It lists an unresolved risk or question. | unclear | "The team can cover the extra hours with the current rota." | What could prevent the rota from covering the new hours? |

Safe revision requests

- Add the source for the demand statement.
- Ask the rota owner to confirm the staffing assumption.
- Add an owner and an approved implementation date.
- Name the main risk that still needs a decision.

The table is useful because it leaves gaps visible. It does not prove that the proposal is right, and it does not turn a missing source into a fact.

Acceptance checks

Before sharing the revised memo, check that:

• Every checklist item has a status and an evidence quote or an explicit missing-evidence note.
• Every quoted passage exists in the source memo.
• New owners, dates, numbers, and outcomes came from a decision owner or another approved source.
• The decision request is still easy to find.
• The original and revised versions can be compared in Canvas.

Troubleshooting

Canvas does not open. Ask for use Canvas to review this memo, or paste the text and use the Canvas shortcut in the composer. If Canvas is unavailable for the current model or account, run the same prompt in a normal chat and keep the review table as the artifact.

The review invents an answer. Repeat the evidence rules and ask for missing or unclear instead of a completion. Replace the output with the last version that kept the gap visible.

The document is too long to review clearly. Split it by decision section, keep the same checklist, and label each section. Merge the tables yourself only after checking that no finding was lost.

• A suggested edit changes the meaning. Compare it with your original copy and ask for a smaller edit that changes only the selected sentence.

Verdict

TRY this for a low-risk memo whose decision criteria are already written down. SKIP it when nobody can define what a good decision memo must contain. USE the review table as an editing aid, not as approval or evidence that the proposal is sound.

If you want one practical AI workflow each week, join The Weekly Verdict.

Sources

• ChatGPT capabilities overview describes Canvas as an interactive workspace with inline suggestions and file support.
• Uploading files and audio to ChatGPT documents supported text and document uploads.