How to Use ChatUp: Your First Session, Models, and Tools
ChatUp includes model choice, specialist starting points, and practical tools. Here is what each part is for and where its limits are.
Your downloads folder is full of documents you meant to read. Here is how to get a summary you can act on, and how to tell when the summary is wrong.

A useful PDF summary tells you what the document says and lets you check where each claim came from. Start with a short file, ask for page references, and compare the answer against the original before using it.
Download the fictional workshop memo (PDF). We created this short document for the exercise; it contains no customer or personal records. Page 1 contains the schedule, page 2 the budget and responsibilities, and page 3 the unresolved questions.
In ChatUp, sign in with the account that has workspace access. Use File Assistant as the document starting point, or a chat that offers a supported file attachment control. If your account reaches the Pro screen, review access there first. Upload availability depends on the selected model and current product support; wait for the file to be accepted before asking about it.
Paste this request, or customize it with the prompt generator:
Use only the attached workshop memo. Give me: (1) the date, time, capacity and registration deadline; (2) a budget table and its total; (3) each person's assigned task; and (4) the unresolved questions. Put a PDF page number beside every fact. Say “not stated” for the ticket price. Do not treat planned costs as money already spent.
This is an editor-written answer key checked against our sample file, not a captured AI response. Our September 17 review verified the sign-in and public prompt-building steps; the review account required Pro access before a live document response could be tested.
| Check | Correct information | PDF page |
|---|---|---|
| Schedule | October 12, 2026, 10:00–12:00 | 1 |
| Capacity and deadline | 24 seats; registration closes October 5 | 1 |
| Planned budget | Room $120 + materials $80 + refreshments $40 = $240 | 2 |
| Responsibilities | Alex confirms the room; Sam orders materials | 2 |
| Ticket price | Not stated | 2 |
| Open questions | Accessibility arrangements; whether refreshments are optional | 3 |
| Spending status | The budget is a plan, not proof of expenditure | 3 |
Open the PDF alongside the response and check every row. If a model says tickets cost $10, that is an unsupported inference from $240 ÷ 24, not a fact in the document. Ask it to remove that claim. A page reference is useful only when the referenced page actually supports the sentence.
For your own files, also check whether “page 3” means the PDF viewer’s third page or a printed page label. Ask the model to use viewer page numbers consistently. See the first-session guide if you are still setting up access.
When you upload a supported file, the selected model may receive the document itself or extracted text, depending on the provider. A grounded summary should describe what this document says, but the model can still infer, omit, or misread material.
Two practical cautions follow:
These are the best case. The structure is predictable, so you can ask for it directly.
Summarize this paper in five parts: the research question, the method, the sample, the main findings with the numbers, and the limitations the authors state themselves. Quote the limitation section rather than paraphrasing it.
That last instruction matters. Limitations are where a paper says what it does not prove, and it is the section most likely to be smoothed away in a summary.
Long, dense, and rarely needed in full. Ask for the shape first and the detail second.
Give me a chapter-by-chapter outline of this document with one sentence per section. Then mark the three sections that carry the most new terminology, and list the terms.
Contracts, policies, warranties, and manuals — the documents where the useful question is almost never “what does this say” but “what does this mean for me.”
I'm the tenant. Read this agreement and list: my obligations, the landlord's obligations, every fee and when it applies, the notice period on both sides, and anything that would be unusual in a standard residential lease. Quote the clause for each point.
Asking for the clause alongside each point turns the summary into a map of the document. When something looks wrong, you know exactly where to go and check.
Four patterns cover most of what people actually need:
Ask the summary to disagree with itself:
Review the summary you just produced against the document. List anything you stated that the document does not actually support, anything you inferred rather than read, and any figure you are less than confident about.
This is not a formality. It reliably surfaces the places where a number was pulled from the wrong row of a table or a hedged claim was reported as a firm one. Anything it flags, open the page and read it yourself.
ChatUp’s File Assistant accepts the document types and sizes published for currently available models. If you switch models, confirm that the new model accepts the attached file rather than assuming every model can read it. For long documents, outline first, then drill into the sections that matter.
If you want the fuller treatment of question design and verification, see AI PDF chat: how to ask better questions.
Not reliably. Scanned documents, handwriting, heavy multi-column layouts, password-protected files, and very large documents all reduce accuracy. Test with a question whose answer you already know before trusting the rest.
Good on structure and argument, weaker on specific figures, and weakest on anything read out of a table. Treat numbers as pointers to check rather than as facts to quote.
Read the data-handling terms of whatever tool you are using, and apply your own organization’s rules first. For anything genuinely sensitive — client material, medical records, unreleased financials — the safe default is not to upload it at all.
There is no single one, but the highest-yield version names your role, asks for a specific structure, and requires a quoted source per point. Everything else is refinement.
The point of summarizing a document is to find the two pages that actually matter and read those properly. Used that way, AI turns an unread folder into a shortlist. Used as a substitute for reading anything at all, it turns a document you have not read into one you incorrectly believe you have.
Google’s document understanding documentation describes how supported Gemini models process PDF content, including text and visual material. That provider capability does not establish which model or file limits are currently enabled in ChatUp. Check the attachment controls before uploading. The downloadable memo and answer key are our fictional exercise; they are not results from a paid model test. For a first task, follow the ChatUp walkthrough.
Try it in ChatUp
Run the prompts above against the model that suits the task, keep the useful context across chats, and pick it back up on any device.
Try for Free