Uploading your report template and mapping it once

Pental generates reports, proposals, invoices and attestation letters from your own DOCX templates rather than imposing a house format. You upload the document you send today, review how its placeholders and tables map to live data, and from then on generation is a click. This guide covers the upload and what makes it go smoothly.

Pick the right file to upload

Use a real, recent report rather than a stripped-down sample: the cover page, the styles, the appendices and the tables you actually ship. Remove the client-specific content if you like, but keep the structure. The mapping step reads structure, so a template that reflects your true document produces a better result than an idealised one.

What happens on upload

• The document is read and its structure identified: headings, tables, the sections that repeat per finding, the fields that come from the engagement.
• You are shown the proposed mapping and can correct anything the platform read differently from how you intended.
• Once accepted, the mapping is saved. Rendering afterwards is mechanical: the same engagement produces the same file, byte for byte.

Rendering is deterministic on purpose. When a returning client puts this quarter next to last quarter, the only differences should be the findings.

What makes a template map cleanly

• Use real Word heading styles rather than manually bolded paragraphs. Structure the generator can see is structure it can keep.
• Let tables use a header row marked as a header row, so it repeats correctly when a table crosses a page.
• Keep the per-finding section as one clear block: heading, details table, evidence, remediation. That block becomes the repeating unit.
• Avoid text boxes and floating frames for content that varies. They are positioned absolutely and do not reflow when the text inside them grows.
• Keep numbering driven by Word list styles rather than typed numbers, so inserted findings renumber themselves.

Filenames

Generated documents follow your own naming convention, configured alongside the templates. Set it before your first delivery so what lands in a client inbox already matches their filing and your own archive.

Iterating later

Templates are not frozen. When you improve the document, upload the new version and review the mapping again. The change applies to future generations; documents already delivered are unchanged, which is what an audit trail requires.