Editable report prompts: inspect structure and rendered pages

Last updated: 7 Oct 202611 min read

tutorial

An editable-report prompt should specify both logical document structure and rendered appearance. Use actual title and heading styles, meaningful text rather than images of paragraphs, descriptive labels for figures, and a reading order that matches the intended flow. Define page constraints such as margins, repeated headers, and where a decision summary may split. After generation, render every page and inspect it at reading size for clipping, orphaned headings, footnotes that drift from their claim, and charts too small to read. Text extraction checks whether expected words exist; rendered inspection checks whether people can use the page. Neither check alone is sufficient.

Operational case

North Quay's report contains a decision summary, count reconciliation, an overdue-record list, and a pending-validation note. A generated page places the pending note in a narrow callout; its last line is clipped in the PDF preview. Text extraction still finds the words, so a text-only check would pass. The layout is repaired, then all pages are rerendered. The heading hierarchy is checked in the editable file rather than inferred from bold text. The figure describing the 38/6/3 split gets a purpose-based text alternative that states the values without duplicating an adjacent paragraph word for word.

Structure: title -> decision summary -> counts -> overdue records -> limits.
Editable file: heading styles, selectable paragraphs, labeled figure.
Render gate: inspect every page at reading size.
Text gate: expected counts and pending note remain extractable.
Failure: clipped callout -> repair layout -> rerender all pages.

Performance and operating cost

Rendering P pages and checking their text is at least O(P) page operations; image inspection also scales with pixel area. A change to a shared header or style can affect every page, so rerender the whole document after that edit. Manual review focuses on high-risk page boundaries, figures, and footnotes rather than reading every line twice. A smaller font may hide overflow but can make the report unreadable; fix the underlying layout or shorten the content with the decision owner instead.

Common Mistakes

Do not equate bold text with a real heading hierarchy.
Do not approve a file from text extraction while its rendered note is clipped.
Do not shrink type to conceal overflow without checking readability.

Connected lessons

prompt engineering

document delivery