Start with the actual notes

Paste the relevant notes as text. QuickieTime does not open links or fetch documents from a URL. Remove unrelated chatter and sensitive information before submitting the source.

Incomplete notes produce incomplete summaries. If a deadline was discussed but never agreed, say that explicitly in the source.

Separate decisions from discussion

Use the focus field to ask for confirmed decisions, named owners and explicit deadlines. The summary should not fill gaps just because a tidy action list looks more useful.

EXAMPLE BRIEF OR WORDING

Focus on confirmed launch decisions and explicit deadlines. Mark unresolved questions as unresolved. Do not assign an owner unless the notes name one.

Pick a structure for the reader

A short paragraph works well for an update at the top of an email. Bullet points make several decisions easier to scan. Brief detail is useful for a quick recap; detailed summaries can retain supporting context.

The summary should stay shorter than the source. If you need a complete record, keep the notes alongside the summary rather than asking the summary to replace them.

Audit the result against the notes

Check each decision and deadline. Watch for certainty changes: “might launch Friday” is different from “launches Friday.” Ensure disagreements and unresolved items have not disappeared.

A summary is a reading aid. It does not establish that a meeting participant approved an action, and it should not be treated as a substitute for a formal record when one is required.

Before you use the output

  • Only source-supported claims
  • Owners actually named
  • Deadlines explicitly agreed
  • Unresolved items preserved
  • Original notes retained