Extract meeting actions without inventing owners

Autor: AILesson5 min de configuraçãoTestado com:ChatGPTRevisado em: 2026-08-28

Resposta rápida

Separate explicit commitments from suggestions and keep missing ownership visible. Forneça: Meeting record, Action scope and cutoff, Commitment and field rules. Resultado esperado: A traceable action register with owners, dates, dependencies, evidence, and gaps.

1

Adicione seu contexto

Seu texto permanece neste navegador. O AILesson Prompts não o envia para um modelo ou servidor.

2

Seu prompt

Campos não preenchidos permanecem visíveis como marcadores de posição, para que você ainda possa copiar e editar o prompt

Extract action items from the meeting record.

Record:
[record]

Scope and cutoff:
[scope]

Commitment, date, status, and evidence rules:
[rules]

Distinguish explicit commitments, assigned actions, proposed actions, recurring responsibilities, and open needs. Do not assign an action to the person who mentioned it unless the record says they own or accept it. Preserve conditional language. Return a table with ID, action phrased as a verifiable deliverable, classification, explicit owner or Unassigned, due date or Not set, trigger, dependency, status, evidence locator, and confidence. Separate proposed items from the committed action list. Flag conflicting owners or dates, vague verbs, duplicate actions, and actions whose completion cannot be checked. Finish with questions needed to make the register executable.
Experimente no Playground
Privado por padrãoA montagem do prompt acontece localmente no seu navegador. Evite colocar informações confidenciais em qualquer serviço de IA, a menos que sua organização permita.

Da entrada ao resultado

Um exemplo prático

Veja como um contexto concreto transforma esta receita em um resultado útil

Entrada real

Meeting record
12:04 Mia: We need the privacy review before beta. Could Omar take that? Omar: I can submit the review request by Friday, but Legal owns completion. 12:08 Jules: I will send Omar the data-flow diagram tomorrow. Mia: Maybe Priya should draft customer wording. Priya: I can help after Legal identifies required changes; no date yet. 12:12 Omar: If Legal flags high risk, we will pause invitations. Mia: Let's also consider a support briefing. No one responds.
Action scope and cutoff
Beta-readiness actions through 12:12. Include conditional commitments but keep suggestions separate.
Commitment and field rules
Commitment requires first-person acceptance or explicit assignment accepted in the record. Keep relative dates as written because meeting date is missing. Evidence uses timestamp and speaker.

Exemplo de saída

Committed actions A1 | Submit privacy review request | explicit commitment | Omar | Friday | none | needs data-flow diagram | Not started | 12:04 Omar | high. A2 | Send data-flow diagram to Omar | explicit commitment | Jules | tomorrow | none | supports A1 | Not started | 12:08 Jules | high. A3 | Assist with customer wording | conditional commitment | Priya | Not set | after Legal identifies required changes | Legal findings | Waiting | 12:08 Priya | high. A4 | Pause beta invitations | conditional team action | Unassigned | Not set | if Legal flags high risk | Legal risk result | Waiting | 12:12 Omar | medium; “we” does not identify an owner.

Not an action owned by Omar: Legal completes the review; the record identifies Legal's responsibility but no person or due date. Proposed only: Priya drafting the wording; support briefing. Questions: what calendar dates do Friday/tomorrow mean, who tracks Legal completion, who owns the pause decision, what deliverable constitutes customer wording, and should anyone own the support briefing?

Por que isso funciona

  1. 1

    Commitment classification prevents a facilitator's suggestion from silently becoming somebody else's task.

  2. 2

    Verifiable deliverables make action completion observable instead of subjective.

Verifique o resultado

  • Does every named owner explicitly accept or receive the action in the record?

  • Are proposed and conditional actions labeled separately from commitments?

  • Can completion of each action be verified from its wording?

Use com confiança

Perguntas frequentes

Respostas práticas sobre quando usar esta receita, o que fornecer e onde a revisão humana ainda é importante

What should I prepare before using “Extract meeting actions without inventing owners”?

For “Extract meeting actions without inventing owners,” prepare Meeting record, Action scope and cutoff, and Commitment and field rules. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Extract meeting actions without inventing owners” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—A traceable action register with owners, dates, dependencies, evidence, and gaps—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Extract meeting actions without inventing owners”?

The published test record for “Extract meeting actions without inventing owners” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

Mais maneiras de explorar

Onde esta receita se encaixa

Mantenha o trabalho em andamento