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.
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.
If preflight passed and the sample file used the right fields, name, and layout, leave a short Marketplace review or send setup feedback. Mention the one-row document test so future Google Sheets users can evaluate the first-run path.