A document merge should start with one row and one generated file. Use DocForge to check template fields, file naming, output folder access, and PDF layout before producing a full batch from Google Sheets.
The starter contains synthetic rows, including one deliberately blank name for a controlled failed-row check. Import it only into a copied test Sheet.
This controlled 31-second proof shows why a document migration starts with one duplicate template, one synthetic source row, and one output file that you open before considering a batch.
The YouTube player loads only after you press play. Controlled installed-user smoke with synthetic data.
Before generating a batch of PDFs from Google Sheets, generate exactly one PDF from one sample row. Open the file and inspect field values, layout, file name, and destination folder before selecting more rows.
Confirm every placeholder in the Google Docs template is filled by the expected sheet column.
Make sure the generated file lands in the folder you expect and can be found again.
Include a stable identifier such as name, ID, date, certificate number, or request number.
Open the file and check page breaks, spacing, signature blocks, tables, and repeated fields.
Generate one certificate from one roster row and verify name, course, date, and certificate ID.
Generate one offer, acceptance, vendor, or notice letter before processing the full sheet.
Turn one form-response row into a PDF summary for review, then expand after the layout works.
Test one document packet before generating a folder of PDFs for printing or sharing.
Watching the proof is not a successful first run. Complete these checks on your own copied Sheet and duplicate template before the feedback and review actions appear.
One-file test confirmed. Keep the copied Sheet, duplicate template, and generated file as your evidence. If anything was unclear, send setup feedback before running a batch.
No checkout is live. This invitation appears only after the self-reported one-file checklist is complete.