Stories worth sharing

A strong alumni story gives readers a relevant idea, perspective, or way to connect. Keep the focus on what the audience can learn; confirm factual details and obtain permission for the material you plan to publish.

For example, a story about a career transition can explain the choices and skills involved without suggesting that every reader will have the same outcome.

Worked example: story brief

A fictional planning brief—not an attributed story or quotation.

Working title: Skills that travel across roles

Purpose: offer alumni a practical reflection on how skills from one role can support a new kind of work. Audience: alumni exploring a professional transition.

  • Central question: Which skills proved useful in the transition, and how were they demonstrated?
  • Details to verify: role descriptions, sequence of events, dates, and any organization or project names.
  • Permission check: confirm the contributor's approval for final wording, chosen name or attribution, and any image before publication.
  • Suggested format: a 500-word Q&A with a short opening summary and three practical takeaways.

From idea to published story

Keep responsibility and review visible at each stage.

  1. 1

    Propose

    The program owner records the audience, useful angle, and reason the story matters.

  2. 2

    Confirm

    The story editor checks facts, names, dates, permissions, and any image rights with the relevant contributors.

  3. 3

    Review

    Share the draft with the contributor for factual and attribution review; resolve open questions before approval.

  4. 4

    Publish and follow up

    Publish through an approved channel, share the finished link with the contributor, and record any agreed follow-up.

Editorial questions

Use these checks before a story goes live.

What makes a story relevant to alumni?

It answers a real reader question, shares a practical perspective, or creates a clear way to participate. A person's title alone is not a reader benefit.

Can a draft include details that have not been confirmed?

Keep unconfirmed details out of publish-ready copy. Mark open questions in the working draft, then verify them with an appropriate source before approval.

What if someone changes their mind about participating?

Pause publication or remove material still under your control, then follow the organization's established process for handling the request.