Upload a document, ask a question, get a straight answer. The chat is deliberately simple to operate, so this is not a manual. It is a list of things worth asking, because the hardest part of any chat tool is knowing what to type into an empty box.
Three things worth knowing before you start
Give it the document, not a summary of the document. Paste or upload the real thing. It reads faster than you do and it does not get bored on page 40.
Ask the question you actually want answered. "Summarise this" gets you a summary you did not need. "Which of these clauses would cost us money if the supplier walked away in month three" gets you something you can act on.
Push back. If the first answer is too long, too vague or aimed at the wrong reader, say so. "Shorter, for a board paper" or "assume the reader has never seen this project" will change the answer entirely.
Worked examples by document type
The long documents nobody has time to read twice, where the risk is always in a clause somebody skimmed.
What are the termination clauses, notice periods and any automatic renewal traps in this contract? List every obligation that falls on us, with the deadline attached to each one. Where does this tender response fail to answer the question that was actually asked? What is missing from this specification that a contractor could later claim as a variation? Compare the payment terms here against 30 days net and tell me where we are worse off.Where the useful content is buried under headings, and somebody now needs a version they can send onward.
Draft a one page stakeholder update from these minutes. No jargon, lead with what changed. Pull out every decision made and every action assigned, with owners and dates. Rewrite this for a reader who has never seen the project, keeping every number intact. What did this report avoid saying? Where is it hedging? Turn this policy into a checklist my team can actually follow on site.Spreadsheets that have been passed between four people and have started to disagree with themselves.
What is inconsistent, missing or double counted in this sheet? Which line items have moved the most since the original budget, and by how much? Summarise this tracker as five bullets for someone who will not open the file. Are there rows here that contradict each other? Point at the specific cells. What questions should I be asking about this data that I have not asked?Slides written to persuade, which is exactly why they are worth interrogating before you present or approve them.
What claim in this deck is least supported by evidence? What will the first three questions from the board be, and can this deck answer them? Condense this 30 slide pack into the five slides that actually carry the argument. Rewrite the executive summary so it leads with the decision being asked for. Where does this proposal quietly assume something that has not been agreed?Comparison is where this earns its keep: two versions of a contract, this month's tracker against last month's, a specification against the tender that answered it. Ask what changed, what is inconsistent, or which one is more favourable to you.
What it accepts, and what it will not
| Format | What it reads |
|---|---|
| Text-based PDFs of any length. Contracts, reports, specifications, drawings registers. | |
| DOCX | Word documents including headings, tables and lists. |
| XLSX | Excel workbooks. Every sheet is read, so a multi-tab budget comes through whole. |
| PPTX | PowerPoint decks. Slide text and speaker notes. |
A PDF that is really a photograph of a page contains no text to read, so the upload will come back with an error rather than a wrong answer. If a document was scanned from paper, run it through optical character recognition first, or copy the text in by hand. Password-protected and encrypted PDFs are refused for the same reason: the content cannot be reached.
| Limit | Detail |
|---|---|
| Messages | 500 per month. Your running count sits in the sidebar. |
| Uploads | 20 documents per month. |
| File size | 10MB per document. |
| Document context | Around 900 pages of text held open at once, across all loaded documents. This is usually the first ceiling you will meet, and the only one that is not a simple count. |
| Resets | Monthly, on the same date you first used the product. The sidebar shows your reset date. |
Every document you have loaded is re-read in full each time you send a message, which is how follow-up questions work without re-uploading anything. It also means a few very long documents cost far more to keep open than many short ones. The sidebar shows how much of that allowance you are using; if you are close to it, remove a document you have finished with and the space comes straight back.
Uploaded files are read to answer your question and are not saved to any server, database or backup, on our side or anyone else's. They are not used to train anything. Close the tab and they are gone. That promise holds whether or not you use the PM Command Centre alongside this.
- ▶It will tell you when it does not know. If the answer is not in the document, you get told that rather than a confident invention. Treat any answer you intend to act on as a draft to verify, the same as you would a colleague's first pass.
- ▶Name your reader. "For the client", "for my finance director", "for a contractor on site" changes the vocabulary, the length and what gets left out.
- ▶Ask for the format you want. A table, five bullets, an email you can send as-is, a checklist. Saying so up front saves a round trip.
- ▶Keep the thread going. Follow-up questions keep the document in view, so you can drill from a summary into one clause without re-uploading anything.
- ▶Different tool for structured project data. If you want meeting notes turned into risks, decisions, budget lines and a Gantt chart that persist between sessions, that is the PM Command Centre, not this chat.