Working template — confirm before delivery
Use client-confirmed facts, attributable evidence, and approved language. Keep every bracketed field adaptable until it is confirmed. If information is missing, write “To confirm” rather than filling the gap with an assumption.
Do not invent claims, imply guaranteed funding or partnership, or promise audience, operational, financial, or other external outcomes. This template is a structure for review, not evidence that an outcome has occurred or will occur.
Document details
Client / organization name
Editable promptUse the name confirmed by the client for this deliverable.
Partner or funder audience
Editable promptName the specific relationship or audience being addressed.
Prepared by
Editable promptRecord the person or team preparing this working version.
Version / approval status
Editable promptIdentify whether this is a draft, in review, or approved.
Organization and work
Describe what is true before shaping the ask
Build the foundation from the client’s purpose, activities, audiences, context, and approved source materials. Keep language adaptable until the client confirms it.
Purpose and reason for the work
Editable promptWhat does the organization exist to do, and what confirmed need or opportunity frames this language?
Activities or approach
Editable promptDescribe what the organization does and how it works, using client-approved wording.
Audiences and communities served
Editable promptName the audiences the client has confirmed, without assuming reach, scale, or participation.
Relevant context
Editable promptAdd the history, place, issue, timing, or circumstances needed to understand the work.
Client-confirmed language and source materials
Editable promptCapture exact approved language, source files, conversations, research, or other materials reviewed.
Impact and evidence
Make the evidence—and its limits—visible
Separate documented change from activity, intention, or illustrative storytelling. Every impact statement should show its source, attribution, approval status, and limits.
Client-confirmed changes
Editable promptDescribe changes the client has confirmed. Do not convert an intention, activity, or hope into an impact claim.
Evidence and examples
Editable promptRecord data, examples, observations, or stories that support the change and identify what they actually show.
Attribution and source
Editable promptIdentify who supplied or approved the evidence, when relevant, and where the source can be checked.
Limits and qualifying context
Editable promptName limits, uncertainty, sample size, scope, timing, or other context needed for an accurate statement.
Unresolved questions
Editable promptKeep unanswered questions visible for the client review instead of resolving them by assumption.
Partnership language
Describe the partnership conversation clearly
Use this distinct section for a partner-facing request. Name the confirmed relationship, shared interest, conditions, next decision, and owner without implying agreement that has not happened.
Confirmed relationship or partnership context
Editable promptDescribe the existing or proposed relationship only as the client has confirmed it.
What is being requested
Editable promptState the specific partnership conversation or contribution under consideration.
Fit or shared interest
Editable promptConnect the request to confirmed priorities or shared interests; do not assume alignment.
Resources, conditions, or boundaries
Editable promptName the resources, conditions, responsibilities, permissions, or limits that need agreement.
Next decision
Editable promptIdentify the next decision the partner needs to make or the client needs to confirm.
Owner or contact to confirm
Editable promptRecord the confirmed person and route for follow-up; do not invent a contact.
Funding language
Frame a funding need without promising an award
Use this distinct section for a funder-facing request. Connect the request to confirmed fit and conditions, and keep eligibility, selection, funding, and reporting status explicitly confirmable.
Confirmed funding context
Editable promptDescribe the funding opportunity, relationship, eligibility, or history only when confirmed by the client or source.
What is being requested
Editable promptState the funding request, purpose, amount, or support type only when confirmed.
Fit or shared interest
Editable promptUse the funder’s confirmed priorities and the organization’s documented fit; never promise selection.
Resources, conditions, or reporting needs
Editable promptRecord confirmed requirements, match, restrictions, reporting, or other conditions.
Next decision
Editable promptIdentify the next decision or confirmation needed; do not imply funding is committed.
Owner or contact to confirm
Editable promptRecord the confirmed owner and follow-up route, or keep it open for review.
Language and source review
Prepare a version the client can approve
Before external use, review each statement for factual support, attribution, approval status, and implied promises. Keep open questions visible.
Language ready for client review
Editable promptAssemble the proposed language and flag every claim that needs approval or attribution.
Claims, promises, or outcomes to remove or qualify
Editable promptCheck for invented facts, implied guarantees, assumed audiences, or unconfirmed commitments.
Final approval record
Editable promptRecord who approved the language, what source was approved, and what remains open.
Review rule before this is shared
- Use client-confirmed facts, approved language, and attributable evidence only.
- Keep impact statements tied to the evidence and limits that support them; illustrative stories are not measured impact.
- Do not invent claims or imply guaranteed funding, partnership, audience, operational, financial, or other external outcomes.
- Mark missing information as “To confirm” instead of filling it with an assumption.
- Record source and approval status wherever a fact, claim, relationship, or funding condition could be questioned.