Organize Files, Instructions, and Conversations

Structure a Project for Maximum Efficiency

You already know how to create a project—it takes about a minute. Making it genuinely useful is a different story: it requires discipline in selecting files, writing instructions, and managing conversations. The difference between a project that works for you and one that’s just a cluttered drawer comes down to these three areas. This lesson gives you concrete methods for each.

Organize Files

Let’s start with the question everyone asks: which files should you upload? The answer boils down to one criterion—documents that ChatGPT needs to consult regularly within the project. Four categories come up repeatedly in practice:

The last row is often underestimated: providing three already-published articles teaches ChatGPT more about your style than ten lines of instructions trying to describe it. Showing beats explaining.

As for formats, ChatGPT accepts most of what you handle daily: PDF, DOCX, and TXT; spreadsheets like XLSX, XLS, CSV, and TSV; PPTX presentations; images; and text pasted directly. However, be aware that OpenAI warns an accepted file may be too long, too complex, or too poorly structured to be read in full: a 200-page report won’t be utilized like a targeted 15-page document on the subject. If you have a choice, split it up.

A few hygiene habits complete the setup. Name your files clearly: “website-redesign-brief-2026.pdf” makes sense, “doc1.pdf” does not—and ChatGPT itself relies on these names when you say “look at the brief.” Dedicate one file per theme rather than combining the commercial brief and the graphic charter in a single PDF. Replace obsolete files with current versions; otherwise, ChatGPT will confidently cite outdated information. And limit the volume: too many files dilute ChatGPT’s attention, so keep only the essentials.

Two other sources complement files. A successful response (a summary, a decision memo, an analysis) can become a project source: open that message’s menu and choose Add to project sources to reuse it in future conversations. And in a private project, Add sources also accepts app links, such as a Google Drive file or folder, or a Slack channel: Lesson 10 covers this.

Write Effective Instructions

For project instructions, a four-section structure has proven effective: context (who you are, what the project is, what the constraints are), objectives (what you expect from ChatGPT in this project), rules (format, tone, language, specific restrictions), and sources (how to use the project files). Here is that structure applied to a real case, a company newsletter:

## Context
Weekly newsletter project for DataFlow company 
(data engineering startup, 80 employees). The newsletter informs 
existing customers about new features and 
best practices.

## Objectives
- Draft each edition
- Propose topics based on data trends
- Adapt tone to our brand voice (see guide-style.pdf file)

## Rules
- French, informal "tu" form (our audience is tech)
- Maximum 800 words per newsletter
- Always include: 1 product update, 1 technical tip, 1 useful link
- Never mention competitors by name

## Sources
- guide-style.pdf: our editorial charter, follow for tone
- past-newsletters.pdf: examples of the last 5 editions
- product-roadmap.xlsx: upcoming features (confidential)

Note the “Sources” section: it doesn’t just list files; it states what each one is for. This prevents ChatGPT from pulling from the confidential roadmap to write a public paragraph, or ignoring the style guide when it’s needed. Also note the overall conciseness: three pages of instructions won’t be followed any better than ten well-structured lines.

Project Memory

Every project has a memory setting, chosen at creation and modifiable later in Project settings, under Memory; the change may take a few hours. With Default memory, the project follows your usual memory: your memories remain active, and on Plus and Pro, ChatGPT can also rely on previous conversations within the project, prioritizing its conversations and files. With Project-only memory, the project becomes sealed: your saved memories are not used there, its conversations can refer to each other but not to those outside, and vice versa. This is the right choice for a confidential client folder. Two consequences to know: ChatGPT Work is not available in a project with memory limited to the project, and a shared project automatically and permanently switches to project-only memory (Lesson 11).

Manage Conversations

That leaves the third pillar, the most neglected one: managing conversations inside the project. First reflex: one thread per topic, with descriptive titles: “Newsletter #23 — Draft,” “Q1 Customer Data Analysis,” “May Topics Brainstorm.” The sidebar search relies on titles as well as message text, and a list of “New conversation” items becomes unreadable after a week.

Second reflex: know when to open a new conversation. Three situations justify it. First, a new topic: each distinct theme deserves its own thread—drafting newsletter #24 has no place in the customer data analysis thread. Second, a completed task: when a conversation has reached its goal, start fresh rather than piling on. Third, a saturated context: if a conversation becomes very long, early information may be lost; it’s better to restart with a summary. Conversely, stay in the same conversation when you’re iterating on the same document, progressively refining an analysis, or when previous exchanges in that thread are still needed to you. A 200-message conversation that mixes everything is the classic symptom of a poorly managed project.

Your Turn

Put the method to the test. Revisit the project created in the previous lesson, or create a new one, and run through the complete method:

1. Add 2 or 3 reference files with descriptive names
2. Write structured instructions following the context / objectives / rules / sources model
3. Open a first conversation and ask a question that requires consulting a file
4. Open a second conversation on a different topic and verify that the instructions apply
5. Save a good response with Add to project sources, then check the project’s memory setting in Project settings

As you work, keep in mind that project organization is never set in stone: a project with files from last year and outdated instructions will yield outdated responses. Plan to dust it off at each major stage of the real project, and resist the temptation to add files “just in case”: every file must have a clear role.

Official sources: Projects in ChatGPT (OpenAI Help Center: files, instructions, saved sources, app links, project memory) · Uploading files and audio to ChatGPT (formats, partially read files) · Finding your chats, projects, and files in ChatGPT (search by title and content)

Key Takeaways

• Add targeted, well-named files: one file per theme, only the essentials
• Structure your instructions in four sections: context, objectives, rules, sources
• Choose the project memory: Default memory, or Project-only memory for a sealed folder
• Update files and instructions regularly, or risk outdated responses
• A well-organized project is a permanent assistant that knows your context