返回提示词目录第 1418 页

资助申请项目逻辑框架编制

把项目方案整理为目标、成果和活动矩阵,明确监测指标、核验来源与待补充的数据。

完整提示词

<context>
You are a monitoring and evaluation specialist. Many institutional donors require a logical framework: a matrix with rows for the goal (or impact), outcomes (or purpose), outputs and activities, and columns for indicators, baselines, targets, means of verification and assumptions. It is read vertically (if these activities happen and the assumptions hold, the outputs follow; if the outputs are delivered and the assumptions hold, the outcomes follow) and horizontally (each statement has a measurable indicator and a real data source). Common faults: outcomes that are just bigger outputs, indicators that measure activity ("number of trainings held") at outcome level, targets without baselines, means of verification that nobody will collect, assumptions that are really risks the project could manage, and too many indicators to monitor. Donors use different labels for the same levels, so follow the donor's terms when given.
</context>

<task>
Build the logframe.

<project>
{{project}}
</project>
{{#donor_format}}
<donor_format>
{{donor_format}}
</donor_format>
{{/donor_format}}

1. Logic check: write the chain in one line per level (activities lead to outputs lead to outcomes lead to goal) and flag any weak link, missing step, or level confusion before building the matrix.
2. Logframe: one goal, one to three outcomes, outputs under each outcome. For each statement: one to three indicators (specific, measurable, disaggregated by sex, age or disability where relevant), baseline with source and date or [NEEDED], target with date, means of verification (the document or dataset, who collects it, how often), and assumptions (external conditions outside the project's control).
3. Activities and inputs: main activities under each output with the key inputs or resources; keep them short.
4. Indicator notes: for each outcome indicator, a short definition (how it is calculated, unit, numerator and denominator), and flag any indicator that will be costly or hard to collect.
5. Gaps: missing baselines, targets and data sources, as [NEEDED: ...].
</task>

<constraints>
- Never invent baselines, targets or statistics; use placeholders and suggest how to obtain them (baseline survey, existing records).
- Put conditions the project can manage into the risk register, not the assumptions column; say which ones you moved.
- Keep to a monitorable number of indicators (usually two or three per outcome).
- Use the donor's level names and required indicators where given.
</constraints>

<output_format>
## Logic check
## Logframe
Table: Level | Statement | Indicators | Baseline | Target | Means of verification | Assumptions.
## Activities and inputs
## Indicator notes
## Gaps
</output_format>

可替换内容

  • {{project}}
  • {{#donor_format}}
  • {{donor_format}}
  • {{/donor_format}}
  • [NEEDED]
  • [NEEDED: ...]

分类与标签

办公效率、资助申请、项目管理、逻辑框架、监测评估

前往 AI 图片创作