How to Reuse Files and Instructions with ChatGPT Projects

Set up one project for your recurring task

Use a project when several conversations need the same background. ChatGPT projects share uploaded sources and project instructions across their chats. A new chat must be started inside the project to use that shared context. OpenAI's Projects guide describes this arrangement.

Here is a small weekly-report setup you can adapt:

Sign in at ChatGPT on the web and create a project named Weekly Team Update. Open an existing project if you already have one for this task. The web guide supports using projects for ongoing work.
Use Save file beside each of the three samples below to download it. In your project, open Sources, use its file-upload control, and select the downloaded files. Confirm that all three filenames appear before continuing.
Open the project's instructions control, paste the reusable instruction template below, and save it. Reopen the control to check that the text was saved. Keep weekly dates and changing facts in the source files and task prompts.
Start a chat from within this project. Run the source check below before asking for a report.

These steps cover uploaded ChatGPT project sources, rather than a folder on your computer. Simply creating the project does not give it access to your local files. The Projects documentation makes that distinction.

Prepare three small source files

For a first run, use this fictional example. Choose Save file to download each sample, or Copy to put its text in your own plain-text file. Keep the filenames unchanged so the prompts match them.

team-context.txt: Audience, project name, and purpose. Update it when the team or purpose changes.
report-format.txt: Required sections and length. Update it when the reporting format changes.
week-2026-10-19.txt: Facts for this reporting period. Create a new dated file each week.

Save this as team-context.txt:

Project: Help Center Refresh (fictional example)
Audience: Operations manager
Purpose: Report progress, next actions, and decisions needed.
Use plain US English. Explain unfamiliar terms.

Save this as report-format.txt:

Use these sections, in this order:
1. Summary: no more than two sentences
2. Completed
3. Next actions: include owner and due date when supplied
4. Blockers and decisions needed
5. Information to confirm
Keep the report under 250 words, excluding source references.

Save this as week-2026-10-19.txt:

Reporting period: October 19-23, 2026
Completed: Maya reviewed 8 help articles.
Next action: Leo will test the search filters by October 28, 2026.
Blocker: Publishing is waiting for accessibility review.
Decision needed: The operations manager must assign a reviewer.
Unknown: No deadline was supplied for assigning that reviewer.

The missing deadline is deliberate: it gives you a specific way to check whether the draft invents details. The correct handling is to flag the missing deadline, without assigning one.

Save reusable project instructions

Use this as a starting template, then adjust it to your own reporting needs. The filenames and report structure are suggestions for this example, not special ChatGPT commands.

Help me draft weekly updates for Help Center Refresh.

Read team-context.txt for the audience and purpose.
Follow report-format.txt for the report structure and length.
Use the dated weekly notes I name in each request for progress facts.
Do not carry progress facts forward from an older week unless I ask.

Preserve names, numbers, dates, and completion status from the sources.
Do not turn planned work into completed work.
Put missing or conflicting details under Information to confirm.
For each progress claim, name the source file and its supporting line.
If you cannot read a required file, identify it and stop before drafting.

Draft for my review. Do not send or publish the update.

The template separates recurring requirements from changing facts. OpenAI's prompting guidance recommends supplying relevant context, defining the result, and flagging missing information instead of guessing. These instructions request that behavior; they do not guarantee it.

Use three prompts to check, draft, and repeat

Prompt 1: Check the source context

Run this in a new chat inside Weekly Team Update:

Before writing, read team-context.txt, report-format.txt, and
week-2026-10-19.txt. List the reporting period, audience,
required sections, and missing deadline. Quote the line that
supports each answer and name its source file.
If any file is unavailable, identify it. Do not draft the report yet.

Compare the answer with your original files. A confident statement that the files are available is not enough: the quoted details should match. In this example, the answer should identify the operations manager as the audience and the reviewer-assignment deadline as missing.

Prompt 2: Draft the report

Once the source check matches, send:

Draft the weekly report for October 19-23, 2026.
Use week-2026-10-19.txt for progress facts and follow the
project's audience and report-format requirements.
Include source filenames and supporting lines for progress claims.
Flag the missing reviewer-assignment deadline. Do not invent it.

Before sharing, check these four details yourself:

Detail to check	What the example supports
Completed work	Maya reviewed 8 articles
Planned work	Leo will test filters; the notes do not say testing is finished
Dates	The report covers October 19–23; Leo's due date is October 28
Missing information	The reviewer-assignment deadline remains unconfirmed

Treat source references in the answer as things to verify. Open the original files and compare them, especially for numbers, dates, and words such as “completed.”

Compare with a finished report

This is an illustrative report written for this guide, not a recorded ChatGPT response. Your draft can use different wording, but it should preserve these facts and leave the missing deadline unresolved.

Weekly update: October 19-23, 2026

Summary
Eight help articles were reviewed. Publishing is waiting for an
accessibility review, and a reviewer still needs to be assigned.

Completed
Maya reviewed 8 help articles. [1]

Next actions
Leo will test the search filters by October 28, 2026. [2]

Blockers and decisions needed
Publishing is waiting for accessibility review. [3]
The operations manager needs to assign a reviewer. [4]

Information to confirm
The deadline for assigning the reviewer was not supplied. [5]

Source references (week-2026-10-19.txt)
[1] "Completed: Maya reviewed 8 help articles."
[2] "Next action: Leo will test the search filters by October 28, 2026."
[3] "Blocker: Publishing is waiting for accessibility review."
[4] "Decision needed: The operations manager must assign a reviewer."
[5] "Unknown: No deadline was supplied for assigning that reviewer."

Notice that Leo's planned test is not listed as completed, and its due date falls after the reporting period. Both details come from the notes; neither needs to be “corrected” by inventing an earlier date or a finished task.

Prompt 3: Start the next week's report

Create and upload week-2026-10-26.txt with the next week's actual notes. Start a separate chat inside the same project, then send:

Prepare the report for October 26-30, 2026.
First read week-2026-10-26.txt and show its reporting period
and one supporting line so I can check the source.
Reuse team-context.txt and report-format.txt.
Use only week-2026-10-26.txt for this week's progress facts.
Do not treat last week's plans as this week's accomplishments.
If the new notes are missing or conflict with my requested period,
stop and ask me to resolve that before drafting.

A separate chat per report keeps each conversation focused; that approach is also recommended in the Projects guide. The date-specific source check helps you catch a wrong-week draft before it becomes a finished report.

Fix missing context or inconsistent reports

A chat cannot find your files

Check that the chat belongs to Weekly Team Update and that all three uploads appear in Sources. Run Prompt 1 and compare the quoted details with the originals. If a file is unavailable, upload it again before drafting.

Old facts appear in the new report

Name the current dated file explicitly. Ask for a revised draft using only that file for progress facts, then compare the revision yourself. A new reporting period needs new notes; last week's plans are not proof that the work finished.

The report format changes between chats

Reopen the project instructions and check that your saved template is present. Compare it with report-format.txt and remove contradictory requirements. Keep one current format.

A file on your computer changed

Upload the revised copy and identify which version to use. Do not assume the uploaded source changed with the local file.

You cannot find sources or project instructions

Check the selected account, workspace, and project. The official Projects guide describes shared sources and instructions, but does not specify an exact web menu path for editing instructions. Check the controls available in your project or ask your workspace administrator.

If those controls are unavailable, attach the three files and paste the instruction template into one ordinary chat. Repeat that setup when starting another ordinary chat.

If two source versions disagree, resolve the conflict in your files before generating another report. Renaming an old file does not by itself prevent a model from using its contents.

For real work, use material you are allowed to upload and check your organization's rules first. The fictional files above are enough to practice the process. Before sending any finished update, confirm its facts against the current sources and remove information the audience should not receive.