Template or AI rewrite?
Use templates for controlled assembly; AI requires explicit consent and manual factual review. Schema validation does not establish truth.
Elysia Tools
Navigation
Workflow Playbook
Reconcile obituary versions, a spoken eulogy and a memorial card against approved facts, review photo privacy and verify the exact files before family-authorized delivery.
New to this workflow? Follow the steps in order, starting with the first tool below. Already know what you need? Jump straight to the matching step — every tool in this workflow is listed in the comparison table.
First tool: Obituary, eulogy and memorial card builder
Hubs
| Tool | What it does | Category |
|---|---|---|
| Obituary, eulogy and memorial card builder | Create three obituary lengths, a spoken eulogy and a printable memorial card privately, with editable drafts and optional AI rewriting. | Document Tools |
| Image Metadata Extractor | Extract comprehensive metadata from images including EXIF, IPTC, XMP, and technical information | Media |
| Text Diff | Compare two text inputs and show differences | Text Processing |
| Text Statistics | Analyze text statistics (characters, words, lines) | Text Processing |
| PDF Text Extractor |
Hubs
| Extract text content from PDF documents with support for page selection, formatting options, and multi-language processing |
| Document Tools |
| File Hash Verifier | Calculate MD5/SHA1/SHA256 hash values for files and verify against expected hashes | Utilities |
This workflow is for a family member or editor preparing memorial materials, not official death registration, legal paperwork or public-record research. Name one factual reviewer and one distribution owner. Preserve authorized spellings, supplied dates, venue details and memories with a revision date. Mark disagreements and unknowns; do not infer age from incomplete dates, a cause of death, surviving relatives, beliefs or achievements. Stop delivery while a material fact remains disputed.
The studio offers template assembly and optional AI rewriting. Real AI use requires consent and transmits supplied text for processing; do not submit unnecessary private information. A template run through an API is not inherently local merely because it uses no AI. Generic helpers also have their own processing paths: use synthetic or explicitly approved redacted copies, and use trusted local utilities for confidential originals. AI output validation checks structure and bounds, not factual fidelity. Review all three obituary lengths, the eulogy and card independently against the source.
Photographs are optional. Confirm family permission and usage rights, then check identity, orientation, framing and potentially revealing metadata on an approved copy. Metadata inspection neither strips data nor anonymizes the visible scene. Inspect the actual exported image/card instead of assuming a preview guarantees the delivered artifact. Use text diff to explain edits, not to judge truth automatically. Names, dates and ceremony details must remain consistent across versions. Do not let a warmer rewrite invent relationships or speak for all mourners. Rehearse the eulogy aloud; estimated reading time and generic text statistics cannot account for pauses or emotion.
Export TXT or DOCX for review and printable HTML for the card, then open the downloaded files. A later form edit does not prove an earlier export updated. Check the final edited card text, not only the input fields. If using the browser to save a PDF, inspect paper size, margins, scaling, backgrounds, all pages, font coverage and photograph placement. Extract text from an approved PDF copy as an additional check for omissions; extraction cannot establish visual layout, correct reading order or accessibility. If the file has no extractable text, use visual comparison rather than treating empty extraction as an empty card.
Retain the approved source, final files and a separate review note stating reviewer, date, recipients and withheld private information. Recheck after every last-minute ceremony change. Keep hashes for the exact final artifacts, using a local utility when files are confidential; never upload a private original just to obtain a checksum. Hashes identify bytes, not family consent or factual truth. No automatic publication is part of this workflow. Use general print preparation for complex imposition and broader editorial review for style, but neither substitutes for family factual approval.
Workflow playbook
Keep an approved source sheet and generate the five editable texts without filling factual gaps.
Inspect only a permitted safe copy for orientation and metadata; independently prepare the approved image or omit it.
Compare source and revisions, review every version and rehearse the eulogy aloud.
Inspect TXT/DOCX and printable HTML; if saving a PDF, extract its text and also review it visually.
Use templates for controlled assembly; AI requires explicit consent and manual factual review. Schema validation does not establish truth.
Use only an authorized image. Metadata inspection does not remove metadata or grant reuse rights; omit the image if permission or privacy is unresolved.
Review the eulogy by timed rehearsal and the card in actual print preview; character counts do not prove timing or layout.
Record explicit family approval and permitted recipients; calculate a checksum only on an authorized copy or locally.