A wedding programme and a wedding invitation do different jobs. The invitation asks a guest to come: date, time, place, and how to reply. The programme is day-of paper. It goes into their hands after they have arrived, and it tells them what will happen in the room.
If hymns, a wedding-party list, and a note about phones are sitting on the card that goes in the post, you are writing two documents on one rectangle. The type shrinks. The reply line gets lost. Move the overflow. Let the invitation stay an ask. Put the run of show on a programme, a single card, or a sign at the door.
The invitation is not a run of show
The invitation has one hard job. A guest who has never been to your venue needs to know when to leave the house. They need an address they can type into a map. They need to know whether dinner follows, and how to say yes or no.
That is already a full card. Hosts, names, date, time, place, a reply. Dress can live on a details card if the main card is tight. A wedding invitation is a letter that arrives weeks before the day. It is not a booklet, and it is not a script.
Ceremony order does not help anyone RSVP. Neither does the title of the processional. Neither does a list of attendants. Those lines wait until the guest is walking in or already seated. They belong with day-of event paper, the family that includes programmes, menus, and the cards people pick up on the day.
The overflow starts when the invite is treated as the only paper that will ever exist. Every later decision gets poured onto that one rectangle. The reading. The phone request. Both sets of parents. The card begins to look like a poster. Guests skim it and still miss the time.
A save the date is thinner still: names, a date, a city. Then the invitation does the asking. Then the programme does the explaining. Three jobs, three objects. If you want the full piece list, I wrote about how much paper a wedding actually needs. This is only about the words, and which object they live on.
A useful test: if a line would still matter after the guest has found their seat, it is not invitation copy. If a line would still matter before they have booked a train, it is not programme copy.
What guests need in their hands that day
A wedding programme is a small map of the ceremony. People pick it up at the door, or find it on the chair. They glance at it while the music starts. Then they put it down.
What they need in that glance is narrow.
- The couple’s names, the date, and the place should be on it, so the paper still makes sense if it goes home in a bag.
- The order of the ceremony should run in the sequence it will actually happen.
- The people standing up there should be named when guests will not already know every face.
- Readings, songs, and rituals should be named when a guest from outside your tradition would otherwise sit through them in the dark.
That last point is why programmes still exist. A short civil service among cousins who already know the plot does not need a booklet. A Mass, a Jewish ceremony, a Hindu or Persian rite, or any bilingual service often does. Guests need to know when to stand, when a reading starts, and what the ritual in front of them is called. The officiant can say some of that out loud. Paper saves them from saying all of it. Ask that officiant which headings they want, and in which order. I set type. I do not write liturgy.
American English calls this a program. I write programme, because that is the spelling I use. Same object. Same job. The letters in the word are not what guests are asking when they sit down.
Optional lines live here too. A quiet memorial. A thank you to parents. A request to keep phones away. None of those belong in the envelope that went out weeks earlier. They belong in the hour of the ceremony, when a guest can actually act on them.
I do not print programmes, and I do not run the service. I design the files: a print-ready PDF at 300dpi with bleed, a texting size, and a stories size, in one shared folder. You send those files to whichever printer you like. How the finished stack reaches guests is a hosting choice. A basket, a table, an usher, or a chair all work.
Names, readings and songs without a booklet
A booklet is one shape, not a requirement. If the ceremony is a few beats long, a single card printed on both sides will hold the order and the names. A folded sheet gives you four panels: a cover, the order, the people, and a back for thanks or memory. Lyrics and spoken responses are the thing that forces more pages. If guests must sing or answer, they need the words in front of them. If they only listen, titles are enough.
How you list names should match the invitation’s tone. If the invite used full names and a formal request line, the programme can too. If the invite was first names and a warm ask, do not suddenly print a maid of honour as if a different wedding had started. Parents, step-parents who actually stand with you, the wedding party, and the officiant are the usual set. Grandparents if you want them seen. Children in the party if guests will wonder who that is.
Readings want a source and a reader. A verse, a poem title, and the name of the person walking to the lectern is enough. You do not need the full text unless the room is meant to follow along. Songs want a title and, if it matters, who is singing. Keep the same level of detail from line to line so the page does not look like two documents glued together.
When the ceremony includes a ritual guests may not know, one short line under the heading is enough. A gloss such as the families sharing tea tells a guest more than a pretty name with no explanation. They are holding a card, not a book.
Ceremonies without traditional roles can use the names people chose. Processional. Vows. Rings. Recessional. You do not have to label which partner walks when. If the list of people is long and the ceremony is short, put the names on the back and keep the front as a clean order. Guests follow the hour with their eyes. They look up the people afterwards.
Keeping the programme in the same family as the invite
The programme should feel as if it came from the same hand as the invitation. Same type family. Same colour story. Same level of formality in the wording. It does not have to be a copy of the card. Matching every ornament is how day-of paper starts to look stiff.
I wrote about making a party match without matching for colour. The same idea applies to the words. If the invitation said “the honour of your presence”, the programme can stay in that register. If it said “join us”, the programme can say “order of ceremony” without borrowing grammar it did not earn.
Cover type can be larger. Body type has to be readable at arm’s length, in shade or in sun. Guests who cannot see small print will simply not read the thing, and then the object was only decoration. Leave space. Do not drop the size to fit another verse.
You do not need a new look for the day. Once an invitation exists, day-of paper can follow it. Finish the invite. Lock the type and the colours. Then set the programme in that language. Menus and table numbers can follow the same way.
For most invitations I ask a printer for 110lb cover stock with an uncoated finish. A programme is a different object. If it folds, the shop that scores it should tell you what that sheet will do. I do not pick their press, and I do not mark up the paper. You pay the printer directly.
The files are yours outright, forever. You can reprint as many times as you like. Delivered files are flat, so you cannot edit them. If a name changes, send me the change and I will set a new file.
When a sign on the way in does the job instead
Not every ceremony wants a stack of paper. A short service with no hymns, no long party list, and no ritual to explain can live on a sign at the entrance. Names, date, a simple order, and one practical line about phones. Guests read it as they walk in. Their hands stay free.
A sign is also the right object when you would otherwise print a programme nobody needs at their seat. If the only extra content is a phone request and a memorial line, those two can sit on a board by the door.
Outdoor ceremonies make a stack of paper into something that blows, wilts, and gets left on wet chairs. A sign still does the job when the order is short. If you want a card anyway, a single sheet is easier to hold than a booklet that wants a lap you do not have on a lawn.
Set the sign in the same family as the invitation. Same type. Same colours. Large enough to read without stopping the line. That is still day-of paper. I can design it with the menus and the rest of the room. I do not print the board.
Skip a hand-held programme when the officiant will narrate every step, the room is small, and everyone already knows who is who. Add one when a guest from another tradition would otherwise miss the meaning of what they are watching. That is the whole decision. It is not fashion. It is not a rule with a fine attached.
If you are unsure, write the order of service on a scrap of paper. If it is four lines, a sign will do. If it is a page of names, songs, and responses, guests need something in their lap.
The invitation is the ask you send ahead. The programme is the map you hand over at the door. If a sentence only helps someone once they are in the room, it was never invitation copy. Put it on the paper they hold that hour, or on the sign they pass, and let the card in the envelope do one thing well.