Endowment season without midnight proofreading
QuillWeaver Engineering
• 4 min
In October, most advancement offices export the same messy CSV from Raiser’s Edge, Bloomerang, or Salesforce: one row per endowed fund, with some donors holding a single scholarship and others holding eight funds across three departments.
That shape of data breaks standard office tools immediately. Word mail merge expects one flat row per letter, so multi-row tables split awkwardly across pages and per-donor charts are out of the question. InDesign Data Merge forces teams to maintain two or three separate templates and eyeball hundreds of exported pages late at night before the printer deadline.
One flat CSV, variable-length reports
QuillWeaver reads that multi-row export directly and groups rows by donor_id:
donor_id,donor_name,anonymous,fund_name,market_value_2026,gifts_2026
D004,Anonymous,true,Community Reading Fund,48200,0
D012,Alder Creek Foundation,false,STEM Scholarship Fund,312400,25000
D012,Alder Creek Foundation,false,Visiting Author Chair,189000,10000
You do not need nested Excel VLOOKUP or TEXTJOIN formulas to flatten multiple funds onto one row. One template in QuillWeaver Designer adapts automatically to each donor:
- Single-fund or anonymous donors get a three-page report with the right salutation (
Dear Friendor named greeting), and empty gift tables are suppressed so there are no awkward blank headers. - Multi-fund donors flow onto four, five, or more pages with repeating table headers, running headers naming the current fund, a vector SVG five-year chart, and accurate
Page 1 of 5footers. - Special characters in legal names and four-line corporate trustee addresses are escaped and measured against real font metrics before export.
Catching mistakes before the print run
Before exporting or emailing, QuillWeaver runs a fit check across every donor in the CSV. It flags clipped addresses, stranded headings, and missing required fields like a blank email address. If one donor row has a missing email, that record is set aside in a review list while the rest of the batch finishes. (We wrote more about that in why one bad spreadsheet row should never ruin 200 receipts.)
The Friday-afternoon finance correction
Every stewardship director knows the email from finance right before mailing: “One fund’s market value changed by $142. Can we re-run the reports?”
With Word or InDesign, re-running means re-exporting and re-checking the entire stack. QuillWeaver hashes each donor’s inputs and template into a SHA-256 manifest. When you fix one row in the CSV and run again, every unchanged donor PDF is reused from the local cache and only the updated donor is re-rendered. Every other file stays byte-for-byte identical.
Donor lists and giving histories stay on your own computer: QuillWeaver Personal runs locally with no cloud uploads and no per-PDF fees, and registered nonprofits and schools get 50% off. See the Nonprofits & Fundraising workflow, try the charitable tax receipt sample, or check Pricing.
Keep reading
All posts- Nonprofits • 3 min
Why one bad spreadsheet row should never ruin 200 receipts
A blank email address on row 9 should not crash your whole mailing or send a half-empty PDF. How record validation and caching keep batches moving.
- Layout craft • 4 min
Catching clipped pages before you hit send
Your template looks spotless on three sample rows, until client #418 has a four-line trust name. How pre-flight fit checks stop silent overflows.