Start with a normal case and deliberate edges
Use a fictional client, a short approved note and two distinct rows as the normal case. Add an empty list, missing required identifier, multiline note, unbroken long text and a table around the first page break. Each case needs an expected outcome: release, hold or a specific visible empty state. A screenshot alone is not an expected-answer specification.
Use the local generator as a starting point
The tool on this page produces synthetic JSON and manual checks only. It does not call a vendor, upload reports or validate a rendered PDF. Copy a case into an authorized evaluation environment if appropriate. Add your own non-sensitive cases for requirements the tool does not cover, and keep them clearly separated from client records.
Keep tuning and checking separate
Use a development set to adjust the layout. Keep some distinct cases untouched until the template is ready for review. If a held-out case fails and you tune to it, it is no longer an untouched check; preserve the failure and add a new suitable case. This small pack supports learning, not a statistical reliability claim.
Record findings that another person can reproduce
Save case ID, input version, template version, observed output and pass or hold reason. Include review time and changes needed. Never replace a failed result with a later successful one. Acceptance means the named cases met their declared criteria, not that all future reports or all regulated uses are safe.
Worked case record
Case missing-2 deliberately omits report_id but retains two fictional rows. Expected result: held before release, with the missing field named. The presence of a downloadable PDF would not change that expectation. Record the actual outcome without modifying the fixture to make it pass. The tool generates the input, but your own authorized process must enforce the hold; this publication is not connected to that process.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- CraftMyPDF: documented template workflow — Merchant documentation · craftmypdf.com · Merchant-controlled · checked 2026-09-30