返回提示词目录第 1495 页

数据报告方法与局限说明撰写

根据分析材料说明数据来源、指标口径、处理过程和局限,生成报告附注及待补充问题清单。

完整提示词

<context>
Most misreadings of a report come from things the methodology note should have said: that "active users" excludes trials, that the latest month is incomplete, that a region changed its recording system, that percentages are of respondents rather than of the population, or that a change of two points is within the margin of error. Notes fail when they are missing, buried, written in analyst jargon, or so long that nobody reads them. A good note tells this audience where the numbers come from, what each one means, what was done to the data, what could make them wrong, and how to read them, in the order a reader needs it.
</context>

<task>
Write a {{length}} methodology note for {{audience}}.

<analysis>
{{analysis}}
</analysis>

1. Read the analysis and list every source, metric, filter, transformation and known issue it mentions.
2. Write the note in this order, leaving out headings that have nothing under them:
   - What this shows: the scope (population, places, period) and the question it answers, in one or two sentences.
   - Sources: each source, its owner, the date range and when it was extracted or refreshed.
   - Definitions: each metric in plain words, with the formula where it helps, and what is included and excluded.
   - What was done to the data: cleaning, exclusions with counts if given, imputation, weighting, joins, and any modelling.
   - Limitations and known biases: coverage gaps, self-selection, measurement or recording changes, incomplete recent periods, revisions, small numbers and suppression, each with its likely effect on the figures (direction and rough size where known).
   - How to read the numbers: rounding, percentages versus percentage points, which comparisons are valid and which are not (across regions, across years with a definition change), and uncertainty such as confidence intervals or margins of error if they apply.
   - Changes since the last version, and a contact, as placeholders if not given.
3. For short: keep only what this audience needs to avoid misreading the numbers, in plain bullets, and point to the full note for the rest. For full: include every definition and decision, still in plain language, with technical detail in clearly marked sub-points.
4. List gaps: anything the note should say but the analysis does not tell you (for example no extraction date or no definition of a key metric), as questions for the analyst.
5. Before you answer, check that every statement in the note is supported by the analysis text and that the vocabulary suits {{audience}}.
</task>

<constraints>
- Never invent a source, date, count, definition or limitation; use a bracketed placeholder and list it under gaps.
- Write for {{audience}}: no unexplained jargon, and no reassurance that hides a real limitation.
- State limitations plainly and specifically ("the latest month is missing about a fifth of late-arriving claims"), not as generic disclaimers.
- If the analysis description is too thin to write any definitions, ask for the metric definitions and sources and stop.
</constraints>

<output_format>
## Methodology note
The note, ready to paste beside the report or dashboard.
## Gaps found
Numbered questions for the analyst, or "None".
</output_format>

可替换内容

  • {{length}}
  • {{audience}}
  • {{analysis}}

分类与标签

办公效率、报告附注、指标口径、数据局限、仪表盘说明

前往 AI 图片创作