Recipient lists are the reusable data layer behind XERIA’s personalized and batch PDF workflows. Instead of rebuilding recipient information for every job, you can maintain recipient records inside XERIA and use the appropriate list when you prepare personalized documents. A well-maintained list reduces repetitive entry and helps keep names, e-mail addresses, identifiers, filenames, passwords, trace values, and delivery information consistent across repeated jobs.
Managing recipient lists is therefore not only an address-book task. The list can directly influence what appears on a recipient-specific watermark, which trace information is associated with a copy, how an output file is named, which password or permissions are applied, and where a document is delivered. Treat recipient data as controlled production data and review it before every important batch.
The Short Answer
Create a recipient list in XERIA for a meaningful project, client, campaign, publication, or distribution group. Add or import the recipients you actually need, maintain the relevant fields consistently, remove obsolete or test entries, and review the list before selecting it for a personalized batch.
You can maintain recipient information inside XERIA rather than re-importing a spreadsheet for every job. Excel remains useful when you already have a structured external list or need to onboard many recipients at once, but the saved XERIA list can become the working source for later batches.
How Recipient Lists Fit into XERIA
A recipient list is a reusable set of recipient records stored for later use in list-based workflows. Each record can hold the values required by your process, while different lists can separate unrelated audiences or projects. Keeping separate lists makes it easier to avoid mixing recipients from different clients, reports, campaigns, or distribution cycles.
The important distinction is between the list and the document job. A list stores recipient data; a later batch uses selected recipient records together with the PDF, watermark, protection, naming, trace, and delivery settings you configure for that job. Updating a list changes the recipient data available to future workflows, so production lists should be maintained deliberately.
1. Create a Recipient List
Step 1: Decide What the List Represents
Before creating a list, define its purpose. A useful list normally corresponds to a stable recipient group such as a client project, a report distribution group, a training cohort, an investor mailing, or another repeatable audience. Avoid one large miscellaneous list when unrelated recipients can be separated more clearly.
Step 2: Create the List in the Recipient Area
Open the recipient-list area in XERIA and create a list for the intended group. Use a clear name that helps you recognize the list later. The exact name is an operational choice, but it should make it difficult to confuse the list with another project or an older distribution cycle.
Step 3: Add Recipient Records
Add the recipients needed for that list. Enter only the information relevant to your workflow and keep the meaning of each field consistent from one record to another. If you already have a prepared spreadsheet, importing can be faster than entering many records manually.
Step 4: Review the List Before First Use
Before the first production batch, inspect the list as a whole. Confirm that the intended recipients are present, test entries are removed, important values are populated, and the list does not contain records from another project. This review is especially important before recipient-specific PDF generation.
2. Maintain the Recipient Fields Your Workflow Needs
Different workflows need different recipient data. XERIA can use recipient information for identification, personalization, file naming, trace-oriented workflows, password-related values, and delivery. Do not populate fields simply because they exist; maintain the values that your actual batch configuration will use.
- Name or full name for recipient identification and personalized text
- E-mail address when the workflow includes e-mail delivery
- Organization, department, or grouping data when relevant
- Recipient code or another stable reference used by your process
- Password, filename, trace, or delivery values when the workflow requires them
- Only project-specific data that is appropriate to retain in the recipient list
3. Keep Recipient Records Current
Recipient lists become less reliable when old and current data are mixed. Review lists periodically and before important distributions. Update values that have legitimately changed, remove or exclude obsolete records, and keep test recipients clearly separated from production recipients. If a list is no longer used, avoid selecting it simply because it appears familiar.
- Correct changed names, e-mail addresses, organizations, or other active values
- Remove or exclude obsolete recipients before future production
- Keep temporary test recipients out of production lists
- Review duplicate recipients and duplicated recipient codes
- Confirm that project-specific fields still belong to the current project
- Use clear list names so current and older recipient sets are not confused
4. Check Data Quality Before a Batch
A recipient list may be technically complete and still be wrong for the job. Data quality checks should therefore focus on both format and context. Confirm that a recipient belongs in the selected distribution, that personalization values are correct, and that any field used in a filename, password, watermark, trace code, or delivery step contains the value you intend to release.
- Check for missing names or other values required by the job
- Review e-mail addresses before e-mail delivery
- Look for unexpected spaces, copy-paste artifacts, or unsupported characters
- Check duplicate records and reused identifiers
- Confirm that password or filename values are assigned to the right recipient
- Verify that trace-related values and recipient identity remain consistent
5. Use Excel Import When It Is the Better Source
If your recipients already exist in a structured Excel sheet, you can import them into XERIA rather than entering a large list manually. The important part is to review detected columns, map the source columns to the intended XERIA fields, inspect sample rows, choose the correct import target, and review the result before production.
Excel is an onboarding method, not a requirement for every future batch. Once the records are stored in XERIA, you can work from the saved recipient list. For the complete import workflow, see [Import an Excel Recipient List into XERIA](/resources/articles/import-excel-recipient-list-into-xeria/).
6. Use the Right List for Personalized Batch Production
When you prepare a personalized batch, the selected recipient list determines which records are available to the job. Review the list name and recipient count before processing. If the project requires only part of a broader list, make sure the intended recipients are the ones included in the batch rather than assuming the whole list is correct.
The recipient data can then feed the configured personalization and distribution steps. Depending on the workflow, that may include visible recipient-specific watermarks, trace information, passwords, output filenames, e-mail delivery data, or other supported recipient values. The list does not replace the batch configuration; it supplies data to it.
7. Treat Recipient Lists as Sensitive Operational Data
Recipient lists may contain personal, commercial, or project-specific information. Protect them with the same care you apply to the documents they help distribute. Limit unnecessary data, keep the Windows endpoint and local storage protected, and avoid copying production recipient data into uncontrolled test files or unrelated spreadsheets.
- Store only the recipient data required for the intended workflow
- Keep the Windows account and workstation protected
- Avoid unnecessary exports or duplicate copies of recipient data
- Keep test data separate from production recipient information
- Review who has access to the workstation and stored recipient data
- Apply your organization’s privacy, retention, and data-handling requirements
Common Recipient-List Mistakes to Avoid
Most list problems are operational rather than technical. The wrong list can be selected, an old recipient can remain active, a test address can survive into production, or a value copied from another project can remain attached to the wrong person. A short preflight review is therefore one of the most useful safeguards before generation.
- Using one miscellaneous list for unrelated projects or clients
- Leaving test recipients in a production list
- Reusing an old list without reviewing changes
- Keeping duplicate recipients or conflicting identifiers
- Assuming imported values are correct without checking the result
- Starting a batch before verifying the selected list and recipient records
Practical Best Practices
Use recipient lists as reusable production assets rather than temporary data dumps. Keep each list purpose-specific, maintain stable identifiers where appropriate, remove obsolete values, review high-impact fields before distribution, and use Excel import only when it improves the workflow. Consistency between recipient identity, watermark, trace information, filename, and delivery records makes later review and investigation much easier.
- Give each list a clear purpose and recognizable name
- Keep unrelated recipient groups separate
- Maintain only the fields the workflow actually uses
- Review lists before every important production batch
- Use Excel import for structured bulk onboarding, not as a mandatory repeated step
- Keep recipient identity consistent across personalization, trace, filenames, and delivery records
How Recipient Lists Support XERIA Workflows
Recipient lists provide structured input to XERIA’s list-based personalized workflows. They allow recipient data to be maintained independently from the PDF being processed, so the same list can be reused with later documents when that is appropriate.
XERIA can use recipient records in workflows that include visible and personalized watermarks, trace codes, optional QR trace information, password and permission settings, personalized batch generation, controlled e-mail delivery, cloud-connected outputs, Mail Log records, and trace-oriented analysis. The exact fields used depend on the batch configuration you choose.
Frequently Asked Questions
Do I need to create a new recipient list for every PDF?
No. A recipient list can be reused across later documents when the same recipient group and data remain appropriate. Create a new list when separating projects, clients, campaigns, cohorts, or distribution cycles makes the workflow clearer and safer.
Can I add recipients without using Excel?
Yes. Excel is an optional bulk-import source, not the only way to maintain recipient data. Recipient records can be maintained inside XERIA, while Excel import is useful when you already have a structured external list or need to onboard many records at once.
What should I review before using a recipient list in production?
Confirm the list identity, intended recipients, important names and e-mail addresses, duplicate records, recipient codes, and any password, filename, trace, or delivery values used by the batch. Also remove test or obsolete records that should not receive production output.
Can the same recipient list be used for different workflows?
Yes, if the saved records contain appropriate data for those workflows. A list supplies recipient information, while the batch configuration determines how that information is used for watermarking, protection, naming, trace, or delivery. Review the fields before reusing a list in a different context.
Conclusion
Creating and managing recipient lists in XERIA is about building reliable reusable data for personalized distribution. Create purpose-specific lists, maintain only the fields you need, keep records current, use Excel import when it is efficient, and review the selected list before every important batch. Well-managed recipient data reduces repetitive work while improving consistency across personalization, protection, trace, naming, and delivery.