Weekly Church Bulletin Workflow Without Publisher

The hard part of a Sunday bulletin is not software. It is the same every week: gather hymns and announcements, update last week's file, have someone check names and times, print copies, and get a file to people who are not in the room. Microsoft Publisher used to be the place that file lived. It does not have to be.

This is a workflow you can run after Publisher's retirement. It assumes you may still have old .pub files, and that at least one person can convert them. It does not assume a designer on staff.

Convert your Publisher files

Get editable PowerPoint files and PDFs from your .pub files.

Start free preview

The Files You Need (Only Two Going Forward)

Stop treating the Publisher file as the bulletin. Keep:

A working file you edit each week (PowerPoint is the usual destination from a .pub conversion; Canva, Google Slides, or a browser editor also work).
A PDF you print, email, and post.

The .pub original, if you still have it, goes in an archive folder and is not part of Sunday's loop. Back up those originals once so you are not depending on a single PC.

If you do not have a working file yet, convert last week's good bulletin. Bulletin Rescue uploads .pub files, shows a free watermarked preview of page one, and provides PowerPoint plus PDF after a one-time $29 lifetime purchase. You can open the converted design in the browser editor to change text, or download the PowerPoint and work in PowerPoint, Google Slides, Keynote, or Canva. Fonts and spacing can shift; check the preview. Save downloads within 24 hours. The product does not write .pub files and is not affiliated with Microsoft.

Convert the master as well as last week, if you have a template. Publisher templates after retirement explains why the master is the file to invest in.

Roles, Even in a Tiny Church

Write names down. A workflow fails when "the bulletin person" is on vacation.

Compiler gathers hymns, readings, and announcements (often the pastor or office).
Editor updates the working file.
Reviewer reads a PDF for wrong dates, misspelled names, and last week's leftovers.
Printer produces the stack (or sends the PDF to a copy shop).
Publisher-to-web/email posts the same PDF.

In many congregations one person holds three of those roles. Still name a backup editor who knows where the working file lives.

A Week That Fits on One Page

After Sunday (or Monday). Duplicate last week's working file. Name the copy with next Sunday's date: 2026-11-16-bulletin.pptx. Do not type over last week's file until the PDF of last week is saved in the archive.

Midweek. Replace the parts that change: date, liturgical day, hymns, sermon title, prayer list, upcoming events. Leave the masthead and standing notices on a master page or a locked layer if your tool has one.

Deadline. Pick a freeze time (Thursday noon is common). Announcements that arrive later go in next week or in verbal notices, unless they are pastoral emergencies.

Review. Export PDF. The reviewer opens the PDF, not the working file, so they see what will print. Check page two. Check the fold. Check that "last Sunday's picnic" is gone.

Output. Print from the PDF. Post the PDF on the website. Attach or link it in email. Do not send the working file to the congregation.

Archive. Keep the dated working file and the dated PDF. That pair is next year's template when someone asks "what did we do for Advent 1?"

Printing without Publisher, emailing the bulletin, and posting it on the website are the three output guides that plug into this loop.

Where Volunteers Should Edit

Choose one working tool and write it on the workflow sheet. Switching every week is how files get lost.

PowerPoint / Google Slides / Keynote. Best if you converted from Publisher and the layout is a set of text boxes. Slides is easiest when people use Chromebooks. Expect small layout differences between applications; edit in the one you will actually use.

Canva. Best if the bulletin is becoming a designed handout and volunteers already know Canva. Import PPTX if you have it, then save a Canva template.

Browser editor in Bulletin Rescue. Useful for people who want to change text and export PDF/PNG without installing Office. Lifetime access covers conversions and the editor. Free accounts can save a small number of projects; lifetime accounts can save more. This is optional, not required, for the workflow.

Word. Use it for a text-heavy newsletter, not for a tightly designed folded bulletin, unless your bulletin is already basically a Word document. See Publisher vs Word for newsletters.

Scribus or Affinity Publisher. Reasonable if one trained person produces a polished multi-page newsletter. Poor if the editor changes every quarter. Scribus is free; Affinity is a paid desktop app that does not open .pub natively.

Free tools are enough for many churches. Pay for a layout app only if someone will use the features.

Quality Checks That Prevent Sunday Morning Surprises

Build a short list and reuse it:

Liturgical date and calendar date match
Service time is correct (especially around holidays)
Hymn numbers match the hymnal you actually use
Names on the prayer list are spelled as the family spells them
Page two is not blank because an object sat off the canvas
PDF file size is small enough to email
Folded bulletins are printed duplex with the correct flip

Conversion leftovers to watch the first few weeks: substituted fonts that wrap a heading onto an extra line, a missing logo, or a photo that shifted. After the template is stable, those fade.

What to Do With the Old Publisher Computer

If the office PC still opens Publisher, use it as a conversion station for remaining .pub archives, not as the weekly editor. Each week you stay in Publisher is a week a substitute cannot produce the bulletin from home.

When you are done converting masters and recent issues, you can leave Publisher installed or not. Microsoft no longer supports it as a current product. Running unsupported software has security tradeoffs your IT volunteer may care about; the workflow itself should already be on PDF plus a modern working file.