Book a call
Menu
Field Guide · level 3 · Power features

When should work live in a project, and how do you set one up?

20 min · as of Oct 2026
You will be able to

Tell when a job belongs in a project rather than a single chat, set one up from start to end in Claude or ChatGPT (or a notebook in Gemini) with its files and instructions, and know who can see it and what it remembers (as of Oct 2026).

Part of Hand it the workTime about 20 minutes, with the try-itChecked 16 Oct 2026

Three things to take away

  1. 1

    A project is a folder of files and instructions for work you come back to. Every chat inside it starts already knowing that background, so you stop pasting the same files and rules in each time.

  2. 2

    Use a project for repeat or long-running work: a weekly report, a piece of work that runs for weeks, material your team shares. A one-off question stays in a plain chat.

  3. 3

    Before you add files, check two things: who can see the project, and what it remembers. Claude and ChatGPT both let you keep a project's memory apart. Gemini has no "projects" by that name; its nearest thing is a notebook.

In plain words

Which setting does what

Projects sit next to three other settings. They are easy to mix up.

SettingApplies toUse it forThe lesson
Your standing instructionsEvery chatWho you are, your role, how you like answerscoming
A projectThe chats inside that projectThe files and rules for one piece of workThis one
A skillAny chat, when the task matchesA how-to you repeat in many placesopen lesson
MemoryWhat the AI picks up from your chatsCheck it, and keep it apart for sensitive workcoming

Project or plain chat?

The jobWhere it goes
One question, one answerA plain chat
The same report every week, from the same templateA project
A piece of work over several weeks, with many filesA project
Material your whole team works fromA shared project
A how-to you use in many different projectsA skill
Answers drawn only from a pile of your own documentsA project, or a Gemini notebook
As of Oct 2026 · read 16 Oct 2026

In your assistant

Menus move often. If something here is missing, the usual reasons are a rollout still in progress, your plan, your country or an admin setting.

Claude

What a project holds: its own chats, its own files (Claude calls them knowledge) and its own instructions. On Free you can make up to five projects. Pro, Max, Team and Enterprise can hold much more material.

Set one up, start to end

  1. Make a new project and give it a plain name, such as "Weekly team update".
  2. Add three to five files to its knowledge: the template, one or two good past examples, and any reference sheet the work needs.
  3. Write the project's instructions (a starter is below).
  4. Decide on memory. Each project has its own memory. To keep it fully apart from the rest of your account, turn off "Use account memory" for that project.
  5. Start every chat for this work inside the project.
  6. For a bigger job, just ask in the same chat. Cowork is now part of ordinary Claude, and your projects carried over when it merged.

Sharing: on Team and Enterprise plans you can share a project with colleagues, with "Can view" or "Can edit".

On the desktop app: a Cowork project can also hold folders from your computer, links and its own memory. It lives on your computer only, and you can link a claude.ai project to it.

Coming: a new beta version of projects, where "a project is one conversation", is rolling out in stages to some Pro and Max users, starting with Claude Code. Existing projects stay as they are for now.

ChatGPT

Set one up, start to end

  1. Select New project in the sidebar and give it a name.
  2. Add files. You can also add links from Google Drive and Slack as sources.
  3. Add instructions: open the three-dot menu (•••), then Project settings. Project instructions override your general ones, so put anything specific to this work here.
  4. Choose its memory: Default memory or Project-only memory.
  5. Start a chat in the project, and choose Chat or Work. Work uses the project's files and instructions for a longer task.
  6. Save useful answers back into the project, so the next chat can use them.
  7. Share it if your team needs it, with chat or edit access.

Two rules about memory that catch people out: shared projects always use project-only memory, and Work is not available in project-only projects. So if you want to hand over tasks with Work inside a project, keep it on Default memory and do not share it. For team material, share the project and use Chat inside it.

Limits by plan (files, and people you can share with): Free, 5 and 5. Plus and Go, 25 and 10. Pro, 40 and 100. Sharing works on every plan.

Not the same thing: Space (on Pro, Business and Enterprise) gathers Pages and files to share. Projects stay separate from it.

Gemini

  • No "projects" by that name. The nearest thing is a notebook. Make one in the Gemini app or in Gemini Notebook (renamed from NotebookLM on 16 Jul 2026), and it syncs between the two.
  • Answers from your own files: Gemini Notebook is built for answers drawn only from the sources you add. It can now also run code to analyse data in your sources (Ultra and Workspace business plans first).
  • Saved instructions: use a skill instead. Go to Customize, then Skills (lesson: What is a skill, and why is it replacing the prompt pack?). The Customize menu in the left sidebar also sets how Gemini responds to you.
  • Work and school accounts: your admin controls these features, and chat history is kept for 18 months by default.
Start to end

Your first project, start to end (15 minutes)

  1. Pick one piece of work you repeat, such as a weekly update.
  2. Gather three to five files you are allowed to use with AI: the template, one or two good past examples, and a short sheet of terms or names it should know.
  3. Write a short instruction. This starter is made up for this lesson. Change it to fit.
This project is for: our weekly team update.
Who reads it: my team and my manager.
Always: use only the files in this project and the notes I paste in.
Always: one page, plain words, the three headings in the template.
Never: add numbers that are not in my notes. Never send or share anything.
If something is missing: ask me. Do not guess.
  1. Make the project with the steps for your tool above, and add the files and the instruction.
  2. Run the first chat. Paste this week's notes and ask for the update.
  3. Fix the instruction, not just the answer. If it gets something wrong, change the instruction, so next week starts right.
  4. Tidy it once a month. Replace old files and remove anything that is no longer true.
On your own work · nothing private

Try it (10 minutes)

Use made-up or public material. Nothing private goes in.

  1. Choose the work (1 minute): one job you do at least every two weeks.
  2. Make the project (4 minutes) in your tool, with two made-up files: a short template and one example.
  3. Add the starter instruction (2 minutes) above, changed to fit.
  4. Test it (3 minutes): start a chat in the project, paste three made-up notes and ask for the result. Then ask "Which files did you use?" and check that it names yours.
Three questions · pick one answer each

Quick check

  1. 1You write the same weekly update every Friday, from the same template. Where should it live?

    The answer: A It is repeat work for one job. Standing instructions apply to every chat, so they are the wrong home for one job's rules.
  2. 2In ChatGPT, you share a project with two colleagues, then try to hand over a task with Work inside it. What happens?

    The answer: C For tasks with Work, use a project on Default memory that you have not shared.
  3. 3Where do you find "Projects" in Gemini?

    The answer: B A notebook made in the Gemini app syncs with Gemini Notebook.
0 of 3 answered
Read the whole lessonThe idea in full, the worked examples, common mistakes and what to check

The idea

Picture the weekly team update. Every Friday you open a new chat, paste in the template, paste in last week's update as an example, explain who reads it, and only then paste this week's notes. Five minutes of setup before any work happens, every week.

A project keeps all of that for you. You put the template, a good example and your rules in once. From then on, every chat you start inside the project already has them. You paste in this week's notes and ask.

It also keeps the work together. All the chats about one piece of work sit in one place, next to the files they used.

Common mistakes

  • One huge project for everything. It mixes old and new, and the AI uses the wrong file. One project per piece of work.
  • Old files left inside. If last year's price list is in the project, the AI will use it. Tidy it monthly.
  • Confidential files in a shared project. Everyone with access can work from them.
  • Instructions that fight each other. In ChatGPT, project instructions override your general ones. Keep them consistent.
  • Forgetting memory. Personal memory can follow you into work, and the other way round. Turn off "Use account memory" for a project in Claude, or choose "Project-only memory" in ChatGPT.
  • Assuming a colleague can see it. A project is yours until you share it.

What to check before you trust it

  • It used your files: ask "Which files did you use for this?" and check the answer names yours.
  • It used the newest version: if two versions of a file are in the project, remove the old one.
  • It followed the instruction: right format, nothing added that was not in your notes, questions asked instead of guesses.
  • The content is right: a project makes the work consistent, not correct. Check names, numbers and dates against your sources (lesson: How do you check an AI answer before you use it?).

Keep it safe

  • Put in only files your company allows you to use with AI, on your work account.
  • Check who has access before you add anything. In Claude, "Can view" or "Can edit"; in ChatGPT, chat or edit access.
  • Keep the memory of a sensitive project apart: "Use account memory" off in Claude, "Project-only memory" in ChatGPT (Work is then not available in that project).
  • Remove people who have left the work, and delete files that are out of date.
Checked against · read 16 Oct 2026Every claim, its source and the date read

As of: product steps as they were on the vendors' own pages on 16 Oct 2026.

Every product line in this lesson comes from Neosaipien's platform reference (checked on the vendors' own pages, 16 Oct 2026).1, 3.2, 3.3 and 6.2. Its sources were each read on 16 Oct 2026. The vendor pages behind this lesson:

Where next

Back to level 3, Power features