One Story, Ready to Send

Write a focused brief

State the question, what changed during the period, what evidence is needed, and the intended channel. Name the person who can verify the result. A request for ‘a nice story’ is too vague to assign.

Separate fact from interpretation

For each number or outcome, record its source, period, and verifier. Distinguish activities delivered from changes in people’s lives. Do not describe all program results as caused by one gift unless that attribution is supported.

Check permission and representation

Confirm the proposed use of names, images, quotes, and individual details is permitted and appropriate. If permission is unclear, use an aggregate program update or another approved example. An old approved photo is not proof of a new event.

Review in the right order

Have the program reviewer check accuracy before the relationship owner checks relevance and tone. Give each reviewer a deadline and a specific decision. Consolidate edits so the author is not reconciling contradictory versions.

Deliver and record

Check the recipient and channel, deliver the approved version, and save the delivery date and version reference. A reply or failed delivery creates new work with an owner. Record what remains unanswered and when you expect to follow up.

Put it to work

Suggested session: 30 minutes to brief the update. Bring the relevant records and allow additional time for preparation and delivery.

• Identify the audience, the commitment or question, the reporting period, the owner, and the delivery date.
• Ask the program team for existing evidence before commissioning new content. A verified short update can be more useful than an elaborate story collected late.
• Confirm who may approve facts and who may approve use of personal stories or images. Store sensitive material in the appropriate controlled location.

When the plan changes

• Missing data: explain what is known and give a realistic next check date.
• Conflicting numbers: resolve the discrepancy with the source owner before including the figure.
• Consent unclear: change the content, not the permission record.
• A material error is discovered after delivery: assign a correction and preserve the record of both versions.

What finished looks like

• The update answers the stated question or clearly identifies the outstanding answer.
• Facts, reporting period, and permissions have been checked.
• The approved version and delivery are recorded.
• Replies and unresolved promises have a next owner.

See whether it helps

Track days from brief to approved update, days waiting on each handoff, and corrections after delivery. Use those observations to shorten the slowest handoff; do not make the whole process faster by dropping factual review.