AI-generated illustration.
A memorial card and a funeral order of service have different purposes. A card is a small keepsake; an order of service helps guests follow the ceremony. Before preparing either in Riga, agree the content, languages and recipients. Only a checked version approved by one family representative should go to print.
There is no need to fit a complete biography, detailed timetable and funeral announcement onto one sheet. Too much wording leads to small type that can be difficult for people with reduced vision. Start with the purpose and information order. This guide concerns content preparation; printing availability, quantities and production times require separate agreement.
For a memorial card, families often choose an agreed name, checked life dates, a portrait and a brief remembrance text. Discuss each element with relatives. A lengthy biography is optional. If the card will be kept for years, avoid private contact details or organisational information that is useful only on the day.
An order of service needs the sequence: opening, contributions, music and closing, at the level of detail actually agreed. Do not list a speaker whose participation is unconfirmed. Check religious content with the responsible minister or ceremony leader. A design sample does not establish the practice of a particular tradition or the wishes of this family.
Do not leave names and dates scattered through separate messages. Collect them in one document and identify who checked uncertain points. Review Latvian diacritics, compound surnames and forms used in other languages separately. Automatic transliteration does not decide which spelling the family wishes to preserve on a personal remembrance item.
Select a short quotation or poem deliberately, checking its wording and attribution where appropriate. Do not reproduce a long passage merely because it appeared online. A text written by relatives also needs proofreading. Resolve the wording before design begins so the designer is not expected to infer meaning from unfinished drafts or contradictory messages.
| Element | What to check | Who confirms it |
|---|---|---|
| Name and dates | Spelling and every number | Family representative |
| Portrait | Selected image and crop | Close relatives |
| Programme | The agreed ceremony sequence | Ceremony leader |
| Another language | Meaning, names and sequence | A competent speaker |
| Print proof | Readability at actual size | Order representative |
Agree quantities and distribution separately. The number of cards is not automatically identical to the guest count: some copies may be kept for family members, while a couple may share a programme. Mention relatives abroad before printing. Posting a physical keepsake and sending a digital copy are different arrangements, so establish what is wanted.
Latvian, Russian and English versions may differ in length. Matching the number of lines mechanically can create awkward wording or type that is too small. Every version should contain the same checked facts and a clear ceremony sequence. Translate a personal remembrance naturally while preserving the family's intended meaning.
Separate language versions or one bilingual sheet may work. Choose according to the audience and readability rather than assumptions based on surnames. Separate text blocks clearly so that no guest receives incomplete information. If the ceremony includes interpretation, the printed programme should reflect the actual arrangements rather than promise an unconfirmed translated contribution.
Use a family-approved image of sufficient quality. Ask to see its crop within the full design, not merely as a separate photograph. If other people appear, agree an appropriate crop or another portrait. Do not send an entire private album when only one file is required. Keep the original and the approved version distinguishable from drafts.
Giving a card to attendees and publishing its image on social media are separate decisions. Do not include a private video-call link, access code or family telephone number in a public version. If using a QR code, check its destination, access conditions and long-term purpose. The code itself does not protect the information behind it.
An enlarged screen image may look attractive but become difficult to read on paper. Where possible, inspect an actual-size proof. Check contrast, margins, folds and the position of the name. After a correction, reread the whole layout: line breaks and neighbouring content may have moved even when only one number needed changing.
Decide who will bring the materials and offer them to guests. Otherwise a small task can fall between several helpers. Check the final programme against actual changes. If printed information is no longer correct, agree with the leader how to explain the update calmly. Avoid distributing different versions with contradictory instructions for what happens next.
Discuss organisational questions through the Riga-Rituals contacts and funeral arrangement information. Verify any named venue with the responsible organiser; the Riga cemetery section provides orientation. Save the approved file in the family folder together with an explanation of its intended use and distribution.
Give the digital copy a clear name and version date. A file called final-new-two is easily confused with a rejected proof. If a relative later asks for a keepsake, it should be clear which material the family approved and whether it was intended for further sharing. Keep private access details in a separate message.
No. They serve different purposes, and separate materials can be clearer and easier to read.
Check the original file quality and its crop in the complete proof. A small preview cannot establish the printed result.
A competent speaker reviews each text, while the family representative compares names, dates and the ceremony sequence across versions.
Keep it out of publicly distributed materials. Send access details separately to the intended remote participants.
One previously appointed family representative after the content, languages and full layout have been checked.