Elysia Tools
Navigation
Workflow Playbook
Fill one finished PDF form with a list of records to get a copy per recipient, mark the whole batch with a watermark, split merged output back into individual files, and compress everything into one delivery ZIP.
Hubs
Fan-out inverts the usual editing posture — instead of working on one document longer, you work on one document once and multiply it. The template is finished first, fields settled and layout approved, because every defect it carries is about to be copied once per record. Then the record list is filled in: one row per recipient, every needed field present, no row half-complete. The batch filler stamps each record into its own copy, and the payroll variant does the same for salary slips with the slip layout built in. The first verification is arithmetic — records in, copies out, counts equal — followed by a spot check that two copies differ only in their filled fields. The output choice made here, one merged bundle or separate files, echoes through every step that follows.
A watermark on a batch is the distribution's signature, and it is applied after filling, not before. Marking the template would stamp identical text on every copy with no regard for the filled values; marking the finished copies puts the sign deliberately on top of final content. What the mark says is a decision worth a minute of thought — a document title or a confidentiality notice states status for the whole batch, while recipient-identifying text turns every leaked copy into a traceable one. The personal data itself already lives in the filled fields, so the watermark names the distribution rather than the person. Rotation, opacity, and tiling are tuned until the mark is legible at a glance without burying the numbers underneath — a watermark that hides the salary figure has failed at its only job.
The merged bundle is the honest choice for internal use — print it in one pass, archive it as one file, review it as one document. But individual delivery needs individual files, and plans change after fan-out. Batch splitting exists for exactly that turn — break the merged bundle by page ranges, or go single-page and regroup, to recover one file per copy. The discipline is the page arithmetic — after splitting, the parts must cover every page of the bundle exactly once, with no page lost between ranges and none duplicated across parts. A missing payslip page discovered after delivery is far more expensive than a count taken before it.
Compression is the final step because every pass costs a little image quality, so the batch deserves exactly one, taken when nothing further will touch the files. The depth follows the destination — screen-grade downsampling squeezes image-heavy pages under email attachment caps, while lighter settings preserve what a printer needs. Compressing at the end also means the checked size is the delivered size — what fits the channel's limit is literally what the recipient downloads, not an estimate from an earlier pass. The batch lands as one ZIP holding the full expected file list, which is itself the last verification — open it, count the files against the records, and the delivery is accounted for.
This page multiplies one finished PDF into personalized, marked, deliverable copies. Around it sit the neighbors with different jobs. Designing the document itself, or generating certificates, invoices, and reports from structured inputs, belongs to the templated generation and layout workflows. Proving authenticity — signatures, certificate sealing, invisible tracking — belongs to the signing and tracing workflow. Rescuing one damaged file or slimming a single document belongs to the repair workflow, and performing page surgery on one copy for print belongs to the assembly and print preparation workflow. Fan out here — and when a single document needs a single fix, send it to the single-document pages.
Workflow playbook
Feed the finished form template and the record list to the batch filler to get one filled PDF per record, or use the payroll variant when the batch is salary slips — choosing merged output or separate files now decides the later steps.
Apply the text watermark across every file with rotation, opacity, and tiling set so the mark is legible without burying the filled values — marking happens after filling, so the stamp lands on finished copies rather than the shared template.
Break a merged bundle back into individual files by page ranges or single-page mode when the delivery needs one file per recipient, verifying that the parts cover every page exactly once.
Run the batch through compression with image downsampling matched to the destination — screen grade for email caps, lighter for print — and collect the result as one ZIP sized for the delivery channel.
A merged PDF is one file holding every copy — convenient to print or archive in a single pass; a ZIP of separate files is what individual delivery needs, and batch splitting can recover separate files from a merged bundle later.
A distribution notice such as a document title or a confidentiality mark stamps status on the batch, while recipient-identifying text helps trace a leaked copy — the personal data itself already lives in the filled fields, so the mark names the distribution, not the person.
Screen-grade downsampling shrinks image-heavy pages hard enough for email attachment caps; lighter compression keeps print quality intact — pick by where the files land, and compress once, at the end.