Extract metrics, dates, and owners from a report

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

Resposta rápida

Create a structured register while preserving units, periods, targets, and attribution. Forneça: Source report, Extraction scope, Output and normalization rules. Resultado esperado: Traceable metric, date, and owner tables with relationships and missing fields.

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 metrics, dates, and owners from the report.

Report:
[report]

Scope:
[scope]

Output and normalization rules:
[schema]

Use only explicit report content. Return separate Metrics, Dates, and Owners tables plus a Relationships table linking them. Metrics must retain name, value, unit, reporting period, actual/target/forecast status, comparison baseline, scope, and evidence. Dates must distinguish reporting dates, deadlines, forecasts, and historical events. Owners must distinguish accountable owner, contributor, approver, and contact. Use Not specified rather than inferring missing fields. Preserve ranges, approximately signs, currencies, and percentage versus percentage-point differences. Flag duplicate labels, conflicting values, ambiguous pronouns, and dates without a year.
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

Source report
[Q2 review, p.2] June active customers were 12,480, up 8% year over year; the Q2 target was 13,000. Retention was 91.2%, 1.5 percentage points below target. [p.4] Priya owns the retention recovery plan. Product and Support contribute. A revised plan is due 18 July and the COO will approve it. Finance forecasts annual recurring revenue of approximately £4.2m by 31 December 2026. The dashboard footnote lists active customers as 12,408.
Extraction scope
Extract performance metrics, targets, forecasts, deadlines, and named roles from the Q2 review.
Output and normalization rules
Use YYYY-MM-DD where the year is stated; otherwise keep the written date and flag it. Preserve original currency and units. Cite page labels; do not merge conflicting values.

Exemplo de saída

Metrics: M1 Active customers | 12,480 | customers | June, year not stated | Actual | Q2 target 13,000; +8% YoY | p.2. Conflict M1b: dashboard footnote says 12,408; do not resolve. M2 Retention | 91.2% | percent | Q2 | Actual | 1.5 percentage points below target; implied target must not be calculated unless requested | p.2. M3 ARR | approximately £4.2m | GBP/year | by 2026-12-31 | Forecast | baseline not specified | p.4.

Dates: D1 18 July, year not stated | revised retention plan deadline | p.4. D2 2026-12-31 | forecast horizon | p.4. Owners: O1 Priya | accountable owner | retention recovery plan | p.4. O2 Product and Support | contributors | plan | p.4. O3 COO | approver | revised plan | p.4. O4 Finance | forecast author | ARR | p.4.

Relationships: M2→O1 and D1; plan→O2/O3; M3→O4/D2. Review the active-customer conflict and confirm the year for June and 18 July.

Por que isso funciona

  1. 1

    Typed tables prevent a target, forecast, and actual from collapsing into one unlabeled number.

  2. 2

    A relationship table retains which owner and date belong to which metric or action.

Verifique o resultado

  • Does every value retain its unit, period, status, scope, and locator?

  • Are owners' roles explicit rather than inferred from nearby names?

  • Are ambiguous and conflicting entries preserved for review?

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 metrics, dates, and owners from a report”?

For “Extract metrics, dates, and owners from a report,” prepare Source report, Extraction scope, and Output and normalization 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 metrics, dates, and owners from a report” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—Traceable metric, date, and owner tables with relationships and missing fields—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 metrics, dates, and owners from a report”?

The published test record for “Extract metrics, dates, and owners from a report” 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