Release Date: July 1, 2026

In-House PDF Rendering — Transition Away from Third-Party PDF Engine

We have completed a significant behind-the-scenes platform transition: Impact has fully migrated its PDF report generation away from the legacy third-party Silicon Publishing (Nucleus) rendering engine to a new EverTrue in-house PDF renderer.

What does this mean for your institution:

• Report PDFs are now rendered within EverTrue Impact platform — no external dependency on a vendor. 

• Existing workflows - including uploading recipient images, creating report templates, proofing templates, and generating report batches - continue to work exactly as before. 

Self-Service Manage Designs & Colors – Available to Customer Administrators

Impact administrators can now manage report designs and brand colors directly within the Impact Administration interface, without requiring EverTrue support team involvement. Click here to see a demo!  

Designs and Default Colors 

• View all available report designs and click into any design to configure its settings. 

• Set template fonts - choose heading and body fonts to be applied across reports for that design.

• Option to use default colors — when checked, design-level colors inherit from your organization's Default Colors settings rather than requiring manual entry per design.

• Set template colors - configure Primary, Secondary, and Body/Paragraph brand colors at the design level, with support for HEX, RGB, and CMYK color formats.

• A live color preview swatch updates as you enter values, with all three format equivalents (HEX, RGB, CMYK) displayed beneath for print production accuracy.

• Mark any design as inactive to hide it from non-admin users in the report template picker - inactive designs remain visible and manageable by administrators and can be reactivated at any time.

  • Existing Customers will see their previous Vendor rendered Classic Design shown as inactive following the July 1st release - these will not be visible to end users but remain accessible to administrators.

⚠️ Important: What Changes for Your Institution

There are a few important workflow changes that will need your attention. 

• Approval process — Any generated reports that have already been produced can proceed through the approval workflow without requiring regeneration. Users will still be able to approve batches that were created using the inactive design even after this release - no action is needed to complete your existing approvals

• Re-running report batches — Report batches tied to the inactive vendor design will not be able to be re-run. If a batch needs to be regenerated for any reason after July 1, it will need to be recreated using a report template created from active design. 

• Copying last year's reports for fall reporting — The workflow of copying a prior year's report template to use as the starting point for fall reporting will no longer be available for the inactive design. You will need to create a new report template for the active Classic. 

Bulk Import - Class Year Validation Now a Warning Instead of an Error

When performing a QA Page bulk import, a missing or non-numeric Class Year value previously caused the import to fail with a hard validation error, blocking the entire import batch. This validation has been updated to a warning across all Impact databases - imports will now proceed successfully, and the Class Year issue will be surfaced as a non-blocking warning for review. This change reduces friction for institutions whose recipient data does not include a Class Year for all records.

Report Batch PDF Not Generating for Funds with No Recipient Photos

What was happening:

When generating a report batch or proofing a template for a fund that had no recipient photos associated with it, the PDF would fail to generate entirely. The PDF rendering process was relying on image mapping data to look up the Fund ID and Template ID - if no images existed for a fund, that lookup returned no results and the generation process halted.

What was fixed:

The PDF generation process has been updated to retrieve the constituent package XML directly from the stored report data tables rather than depending on image mapping data. The Template ID is now passed explicitly during batch generation rather than being inferred. As a result, report PDFs will generate correctly for all funds regardless of whether recipient photos are present.

PDF Report Pages Overflowing into Footer

What was happening:

In certain report templates, recipient content was overflowing beyond the designated page area and spilling into the footer section. Additionally, a fund purpose section heading was appearing on reports even when no fund purpose content had been entered for that fund.

What was fixed:

Page overflow handling has been corrected to ensure recipient content stays within its designated page boundaries. The fund purpose heading is now conditionally rendered -it will no longer appear when no fund purpose has been entered for a fund.

Future roadmap 

Recipient Collection for Donor Relations / Stewardship Professionals (available in late 2026) 

We are currently developing the ability to collect multiple impacts per recipient and new flows to better manage recipient collection with statuses and approval views with editor and preview enhancements. We are building a foundation that will support future enhancements in 2027 to collect impact directly from recipients. Click here to see a demo!