返回提示词目录第 1298 页

撰写项目申请支持信

依据支持方关系、需求证据与实际承诺起草正式信函,并列出签署人需核实的事项和缺失信息。

完整提示词

<context>
Funders, panels and committees read many letters of support and discount the generic ones: "we fully support this excellent project" from a body that commits nothing and knows little. The letters that count show a real relationship, add evidence of need the applicant could not provide alone (the supporter's own waiting list, referral numbers or local knowledge), and make specific, quantified commitments. Panels also notice when several letters share the same wording, so each should read as the supporter's own. A letter of commitment, which binds the supporter to cash or resources, carries more weight and must be signed by someone with authority to commit. Planning committees can only weigh material planning considerations (such as design, amenity, traffic, community benefit), so support for a planning application should speak to those rather than to personal loyalty.
</context>

<task>
Write a letter of support to {{recipient}} from {{supporter}}.

<project>
{{project}}
</project>
{{#commitments}}
<commitments>
{{commitments}}
</commitments>
{{/commitments}}
{{#evidence}}
<evidence>
{{evidence}}
</evidence>
{{/evidence}}

1. If the project or the supporter's relationship to it is unclear, ask up to two questions and stop.
2. Layout: the supporter's letterhead placeholder, date, the recipient's name and address placeholders, and a reference line with the project title and the funding call or application reference.
3. First paragraph: who the supporter is (one sentence of standing: what they do, scale, area) and the statement of support for the named project and applicant.
4. Relationship: how long and in what way the supporter has worked with the applicant, with one concrete example from the input.
5. Need: the evidence of need from the supporter's own vantage point, with figures from the input. If none is given, write `[need: one figure or observation from your own work, e.g. waiting list, referrals]` rather than inventing one.
6. Commitments: each commitment as a specific, quantified line (what, how much, when, for how long). If none is given, keep the letter to support only, do not imply resources, and suggest under Notes what commitments would strengthen it.
7. For a planning application, frame support around material considerations named in the input (community benefit, design, accessibility, local employment) and avoid irrelevant ones.
8. Close: the expected benefit in one or two sentences and a contact for verification, then a signature block with name, title and organisation placeholders as needed.
</task>

<constraints>
- One page: about 250 to 400 words.
- Use only facts given. Never invent statistics, history, outcomes or commitments, even if asked to make the case stronger; use `[need: …]` placeholders and explain under Notes.
- Write in the supporter's voice, specific to them; avoid stock phrases ("wholeheartedly support", "excellent initiative", "will make a real difference") unless backed by a fact in the next sentence.
- Do not overstate the supporter's authority or describe the letter as a binding commitment unless the input says it is one.
</constraints>

<output_format>
## Letter
The letter, ready for letterhead.
## For the signatory to confirm
Bullets: each commitment, figure and claim the signatory must check, and that they have authority to commit.
## Notes
Placeholders, suggestions to strengthen it, and anything left out on purpose. "None" if nothing.
</output_format>

可替换内容

  • {{recipient}}
  • {{supporter}}
  • {{project}}
  • {{#commitments}}
  • {{commitments}}
  • {{/commitments}}
  • {{#evidence}}
  • {{evidence}}
  • {{/evidence}}
  • [need: …]

分类与标签

办公效率、项目申请、支持信、商务函件、签署核实

前往 AI 图片创作