The useful result is a short briefing with a source location beside every important claim. A polished paragraph without those references leaves you rereading twelve pages to find out whether the numbers are right.
Attach the file and give it a job
In ChatGPT, select +, then Add photos & files, and attach your brief. OpenAI lists DOCX, PDF, and TXT for documents; export a Google Docs file as DOCX or PDF first. Spreadsheet formats include XLSX, XLS, CSV, and TSV; presentations use PPTX. Availability depends on the account and client. OpenAI's upload guide
Before attaching anything, choose a copy you are allowed to use with your organization's AI tools. Remove information the task does not need. For this event briefing, the room capacity matters; attendees' personal contact details do not.
Give the file an identifiable name such as Volunteer-event-brief-v3.pdf. In your request, name the file and explain who will read the result. That makes it easier to catch a response based on the wrong attachment or aimed at the wrong audience.
A complete prompt for the team briefing
Copy this request after attaching your document. Replace the brackets before sending it.
Use the attached [FILE NAME] to prepare a briefing for [TEAM/ROLE]
who must prepare for [EVENT].
Use only this attachment for factual claims. Do not look up or invent
missing arrangements, people, deadlines, prices, or approvals.
First identify the document title and any version/date stated inside it.
If you cannot read a section needed for the task, name that section.
Produce:
1. A short overview of the event and what our team must do.
2. A table: task or decision | stated requirement | source location |
assigned person if explicitly stated | unresolved question.
3. A separate list of conflicting instructions and missing decisions.
Prioritize arrival and setup, room capacity, accessibility arrangements,
equipment, and closing responsibilities. Omit unrelated background.
For every deadline, quantity, cost, and assignment, include a page
number plus heading where available. If the file has no stable page
numbers, use the section heading and a short identifying phrase.
Never invent a page reference. Mark unstated details “Not specified.”
Keep proposed next steps separate from instructions in the source.
End with the five facts a human should verify before sending this.
The source locations are requested evidence, not a guarantee that the answer is correct. Open the document and check them. If a cited heading does not contain the claimed requirement, correct the briefing before anyone relies on it.
What a useful answer should look like
Here is an illustrative desired format, written for this guide. These fictional details are not output from a ChatGPT session and do not describe a real event.
| Task or decision | Stated requirement | Source location | Assignment | Open question |
|---|---|---|---|---|
| Set up the room | Set out 24 chairs before 9:30 a.m. | Room setup section | Not specified | Who can enter the building early? |
| Prepare equipment | Bring two display adapters | Equipment checklist | Event coordinator | Which connection does the projector use? |
| Confirm accessibility | Keep the marked entrance route clear | Access arrangements section | Not specified | Who checks the route on arrival? |
Each question points to a decision the document has not settled. Do not let a plausible suggestion turn into an assigned responsibility without someone agreeing to it.
If the real brief says “capacity 24,” that does not necessarily mean “set out 24 chairs.” Ask for the exact wording and inspect the surrounding paragraph. Capacity, expected attendance, and a setup instruction are different facts.
Check the figures before the wording
Start with anything that would change what a teammate does: dates, times, quantities, costs, and names. Follow each reference back to the document. Check whether a time means arrival, doors opening, or the event starting, and preserve any time zone the brief states.
Then read for omissions. A summary can include the main setup list while missing an exception elsewhere, such as equipment that must stay unplugged until the venue contact arrives. Search the source for the relevant equipment name and read the nearby instructions.
Use a focused follow-up when something is unclear:
Recheck the arrival and setup rows against the attachment.
For each row, show the exact supporting sentence and its location.
Separate event start time from team arrival time. Flag contradictions;
do not resolve them by choosing whichever sounds more likely.
Once the facts hold up, shorten the briefing for its audience. A setup crew needs actions and exceptions near the top; the person approving the event may need the unanswered decisions first.
If the upload fails
For documents, OpenAI currently lists a 512 MB maximum and a separate two-million-token cap. A small file can still hit a text limit. Document upload limits
For an upload-limit error, check the account, wait for any displayed retry time, and inspect Settings > Storage. Failed attempts may count toward the rate limit. Check OpenAI Status if uploads keep failing; save the error, timestamp, browser, and request ID for support. Upload troubleshooting
For this task, you can also prepare a smaller permitted extract containing the relevant sections. Keep headings and version information so the eventual briefing still has traceable references. Explain which sections you excluded rather than asking for a whole-document conclusion from an extract.
Send the checked briefing
Keep the original brief where your team maintains it. Send the checked summary with the document's version and the unresolved questions that still need answers. Name whoever will confirm those answers before setup begins.
Optional: read an HTML review copy in NOS
If you already have an HTML version of the briefing, you can use NOS to read that review copy. Check that its source references and open questions survived the formatting. Keep the authoritative event brief and approval process in your team's chosen tools.