Fixing a Template That Renders Inconsistently
Nearly every rendering complaint traces to formatting applied to the paragraph instead of held on a style. Word hides the difference from you; anything reading the file can see nothing else.
A template renders inconsistently when the document is inconsistent in a way you cannot see while writing it. Word will happily let one heading be a real Heading 2 and the next be normal text made bold and bigger. On screen they are identical. To the generator, one is a heading and the other is a sentence in bold, and they will not come out the same.
Hold formatting on styles
- Headings should be Heading 1, 2 and 3, not larger bold text.
- Command output and requests should carry a code style, not a manually chosen monospace font.
- Lists should be real Word lists. A line beginning with a hyphen is a sentence beginning with a hyphen.
- Let the style carry font, size and colour. Overriding those on individual paragraphs is what makes two sections that look alike behave differently.
This is not pedantry about Word. Formatting held on a style is the formatting that survives the trip out to Word and back into the portal, because a style is something the file states and direct formatting is something it merely shows.
Why it matters twice over
Reports are generated with invisible markers, edited in Word, and uploaded back, with every change listed for you to tick or ignore. What returns correctly is whatever the document expressed structurally: a real heading, a listing carrying the code style, a table that is a table. A heading faked with bold text returns as a bold sentence, because that is all it ever was.
Working through a specific problem
- Generate the same report twice. Identical files mean the template is deterministic and the problem is in the document, not the platform.
- Put the cursor in the offending paragraph and read the style name in the Word ribbon. It is often not the style you assumed.
- Clear formatting on that paragraph and reapply the style. This fixes more cases than everything else here combined.
- If a placeholder did not fill, check its spelling against the Placeholder Key for that kind of document (Settings, PDF & DOCX, Document Templates). An unknown placeholder is left alone rather than guessed at, which is why it survives into the output looking untouched.
A template built in the Document Builder starts from a file like this, so the same rules apply to the document you drop in. If you are starting from nothing, the free penetration test report template uses Word’s own heading and list styles.
Try This on Your Own Database
Pental runs on a Postgres database you own, under your own brand, with the AI on your own key. The trial is the whole platform.
Only need the reporting? Our reporting tool is free and open source, on your own server.
Also Worth Reading
Making Your Word Template the One Pental Fills
Settings, PDF & DOCX, Open the Document Builder. Drop in a document you already send: with an AI connected the build starts at once, shows its stages, and ends on a card where you check it, preview the pages and save.
ReportingThe Findings Library: Write a Finding Once, Reuse It
Your firm’s own reusable findings, on from the start. Add a finding from the finding itself, in bulk or automatically once it is final, and bring the agreed wording into any engagement.
ReportingThe Executive Summary and the Rest of the Report’s Sections
The executive summary drafted from every finding and your notes, the caveats and retest summary each written to its own prompt, sections of your own, and how to rename, reorder and control every section of the report.
Setup guide
Prefer to watch it?
The whole setup recorded, with chapters you can jump to: registering, your own domain, your own database in any of three places, your own mail server, branding, the first sign-in, updating the database on Supabase Cloud, and moving the database if you change your mind.
- 0:00 · Registering, signing in, and the free trial
- 0:44 · Your name and your firm’s name
- 0:50 · Custom domain
- +6 more