The Long Return Institute
← Make something for your community
A working guide

Make a community newsletter.

Give people one dependable place to find what is happening, what has changed, and what they can do next.

You can begin with a small issue: a few checked notices, useful dates, and a clear way to report a correction. Choose a pace you can keep.

Editable text template (Markdown): an issue outline, item block, and source-check notes. Open it in any text editor; no account needed.

Build your first issue

Six steps you can repeat.

  1. Choose your readers and rhythm.

    Name the community you are writing for, the area or subjects you cover, and your next issue date. A monthly issue you can maintain is more useful than a weekly promise you cannot keep. Say who publishes it and whether it is independent or officially authorized.

  2. Make a short source list.

    Start with responsible organizers, public offices, schools, libraries, and community sources relevant to your readers. Check the previous issue for corrections and expired notices. Keep a record of each source, when you checked it, and what you found—even when nothing changed or a page was unavailable.

  3. Check the details people will act on.

    Confirm dates, locations, deadlines, participation requirements, and contacts with the responsible source. A repost or flyer is a lead; it may be outdated. If sources disagree, say what is unresolved and offer a way to check. Never fill a gap by guessing.

  4. Write each item for a reader’s next step.

    Use a clear title, why it matters, who it is for, the date and place, and one useful action. Add the source and check date beside the item. Put your community’s material first; group regional material separately. Repeat essential flyer details as text.

  5. Ask another person to use the draft.

    Can they find the next date, explain who may participate, and follow the source or contact link? Ask them to name what remains uncertain. Check a phone view and a printed page. Keep private family details, protected cultural information, and material with uncertain permission out of the issue.

  6. Publish, correct, and keep the record.

    Save the exact issue and its source notes. Name a correction contact and the person who will update it. When something changes, date the correction, repair every affected copy, and preserve the earlier version in the archive. Leave enough notes for another person to prepare the next issue.

A usable starting point

One item should answer these questions.

Item template · replace every bracket

[Plain title of notice or opportunity]

What and why
[What is happening and why these readers may care.]
Who
[Who may attend, apply, or ask. Do not infer eligibility.]
When and where
[Date, time, time zone, place, and any deadline.]
Next step
[One action and the responsible organizer or office.]
Source and status
[Source link, date checked, and anything awaiting confirmation.]

The starter includes an issue outline, an item block, and separate working notes for sources, review, and corrections. Keep those working notes out of the public issue when they contain private material.

A final read

Make it dependable, then let it grow.

Explaining one complicated issue? Make a community briefing instead →

About this guide and its sources

This draft guide and starter were prepared on 19 September 2026. They adapt The Long Return’s weekly source-sweep practice into a general publishing guide. They do not replace the complete controls for the Pit River Weekly Check-In.

Basis: The Long Return Mandatory Weekly Source-Sweep Control Document, v1.0, 6 August 2026; Community Briefing Template and Protocol, v1.1 candidate, and its Language and Output Audit, 11 September 2026. The briefing protocol remains a candidate pending its recorded adoption exercises and owner decision. These new guides have not yet completed reader testing.

The guide’s preparation date does not verify the facts in a newsletter you create. Record the checks for your own issue. A file update does not mean all its facts were rechecked.

Suggest a correction to this guide · How Institute work is made