PDF workflow · Synthetic example
Turn a selectable-text PDF into an approved video summary.
The source document is the start of the workflow, not the finished message. Extract readable text, tie claims to it, review the wording, and check the final video before it goes to a client.
Choose a PDF the current parser can read
The current report path extracts text blocks from a PDF and records their page locations. Use a PDF where you can select and copy the report text. A scanned page or an image-only PDF has no extractable text for this parser; it needs a separate text extraction step before it can be used here. PPTX, XLSX, and image uploads belong to other asset workflows and are not parsed into this report-to-briefing path.
Good input for this path
A PDF with selectable table labels, values, dates, and notes. Check that copied text preserves the figures and that the report is under the current 10 MB upload limit.
Stop and repair the input
Text cannot be selected, a table loses its values when copied, or the report omits the context needed for a material claim. Fix the source before drafting a client summary.
Worked example: source to approved wording
The public synthetic benchmark PDF (page 1) reports August and September 2026 figures. Its table supplies the numerical basis; its notes leave the cause of the change unresolved. The summary should preserve both facts.
| PDF evidence | Client wording | Review point |
|---|---|---|
| Ad spend $18,400 → $20,700 | “Ad spend increased 12.5%.” | Keep the periods and check the calculation. |
| Tracked revenue $123,000 → $105,400 | “Tracked revenue fell about 14.3%.” | Preserve “tracked” and the rounding. |
| Landing-page conversion 8.9% → 7.1% | “Conversion fell 1.8 percentage points.” | Do not call this a 1.8% decline. |
| No established cause in report notes | “The report does not establish why this changed.” | Keep this warning in the video and text. |
The approval gate matters
- Extract and inspect. Confirm that the parser found the intended page text and did not drop a minus sign, date, unit, or table label.
- Map claims to evidence. Keep the source location beside each material claim. Treat calculations and recommendations as distinct from reported facts.
- Resolve unsupported wording. The synthetic report suggests possible creative or audience issues, but neither is established. Keep the explanation open or gather more evidence.
- Approve a fixed script. The reviewer edits and explicitly approves the client-facing words before rendering. Review should include the warning and any next-step question.
- Check both outputs. Read the written summary and watch the video. Confirm that the narration, on-screen figures, and approved wording agree.
Synthetic approved-summary excerpt
“September spend increased to $20,700 while tracked revenue fell to $105,400. Landing-page conversion declined from 8.9% to 7.1%. The report does not establish why. The next check is whether the conversion decline was concentrated by device, campaign, or traffic source.”
Limits before a client sees it
Selectable text helps extraction, but it does not prove the report is complete or correct. Human review is still needed for source quality, calculations, causation, and the rendered video. A failed extraction or unsupported claim should stop approval until the input or wording is corrected.
Related guides
Inspect the finished synthetic example.
The prospect demo includes the PDF, source figures, approved transcript, and playable client video.
Explore the prospect demo