Megal Publisher
HomeUpdates for a event programme

Publishing guides · Repeatable revision workflow

Update and reuse a event programme

Create a controlled revision of a event programme without carrying stale facts or accidental layout changes into the next edition.

Open Megal Publisher Read the relevant instructions

Practical publishing guidance based on Megal Publisher’s documented page, text, image, table, review and output tools.

Practical workflow

Work through the publication in a fixed order

Separate content, structure and proofing decisions so a late correction does not undo earlier work.

Start from a clean approved master

Separate schedule data from contextual copy and issue a named final version when timings or participants change.. An approved master should contain the stable grid, text roles, repeated artwork and empty or clearly marked variable fields. Do not use the only archived final file as a scratch copy. Duplicate the project or page, give the revision a meaningful name and keep the previous approved output available for comparison.

Use a change list

Before editing, list every field affected by the new edition. For a event programme, that includes potential changes to event title and date, welcome or context, running order, people and contributor notes and venue, sponsor and contact information. Add dependencies: a changed date may also alter a deadline, QR destination or terms line; a replaced image may require a new caption, credit and alt text. Check off changes only after they appear in the proof.

Keep repeated elements controlled

Use master pages for genuinely repeated page furniture and duplicate stable page structures where appropriate. Do not detach or individually modify repeated elements without a reason. When a change affects the grid or typography, inspect all pages because text can reflow and image relationships can shift beyond the page currently visible.

Close the revision properly

Update the publication name, issue date or version before export. Run design, proofing and accessibility checks, then compare the new proof with the change list. Create a folded dummy, verify page imposition with the printer and recheck the final running order before release.. Store the editable .mpub, approved PDF and source notes together. This disciplined close prevents allowing biographies or sponsor content to displace the schedule attendees need most and makes the next edition safer.

Use before sign-off

A short working checklist

Controlled update workflow

  1. Duplicate the approved master and give the revision a clear identity.
  2. Write a change list that includes dependent captions, links and conditions.
  3. Update repeated content through the shared structure where possible.
  4. Inspect all pages after layout, font or image changes.
  5. Run factual, visual and accessibility review on the new proof.
  6. Archive the editable file, approved output and change notes together.
Keep the source and proof together. Megal Publisher can keep the page objects editable in an .mpub project. Preserve the source facts and the approved output as separate records so later changes can be checked.

Continue the workflow

Related event programme guides

Move to the next production decision or compare the same task for another publication format.

Foundational references: Microsoft Publisher alternative · Direct PUB import evidence · Megal Publisher instruction manual.

Build the reviewed version in Megal Publisher

Start from a blank page or an appropriate editable design, keep source facts beside the project and make a fresh proof after the final change.

Open Megal Publisher