A PDF can contain a whole report when you only need one process, system or comparison. Tell the agent which section matters and what the diagram should explain. Sign in before working from documents; the file, page and storage limits for your account apply.
Choose a scope within the document
Name the section or page range and the intended audience. A management overview and an implementation diagram use different detail even when they come from the same source. Specify the diagrams you need rather than expecting one output for every page.
For a long brief, ask for a system overview plus a detailed flow for the area under review. The page count is an input limit, not an instruction about the number of output diagrams.
Account for text and scanned pages
A text PDF exposes readable characters; a scanned page requires visual interpretation. Mixed files can contain both. Small footnotes, multi-column reading order, rotated tables and faint scans can change what is understood. Check important labels and numerical values against the original page.
If the document contradicts itself, preserve the ambiguity in the conversation and resolve it explicitly. A confident-looking diagram does not prove that the source was consistent.
Review evidence before the handoff
Check that each major node and relationship comes from the selected material or from a clarification you supplied. Separate the source’s current process from any improvement you asked the agent to propose. Save the reviewed version before exporting it.
For a single screenshot instead of a document, use image to diagram. The first-diagram guide walks through scope, review and revision.
Make it about your work
Edit this starting prompt, then send it when you are ready.