Lesson 5 of 6 · Working with Documents and Data

Projects and knowledge

If you keep re-uploading the same price list, the same brand voice doc, the same contract template, you are doing the AI's filing for it. Every major tool now has a place to put standing knowledge. Here is what each one actually does.

The first few weeks with an AI tool go like this: you paste your price sheet, you get a great quote, you close the chat. Next week you paste the price sheet again. And the brand voice notes. And the service area list. By month two, half of every conversation is setup. The fix is a feature that has different names in different tools but the same shape everywhere: a folder that holds your instructions and your files, so every new chat starts already knowing them.

Two ingredients: instructions and files

Standing knowledge has two halves, and it helps to keep them separate in your head.

Instructions are the standing rules from AI Basics lesson 6: who you are, how you like answers, what to never do. "I run a gutter company in Washington, Utah. Prices are in the attached sheet. Never quote a price that is not in it." They are short, and they get read in full at the start of every chat.

Files are the reference material: the price sheet itself, your service agreement, three past proposals you were proud of, a list of neighborhoods you serve. They can be long. How they get read depends on size: small enough, and the whole set rides along in every chat; too big, and the tool switches to the librarian from lesson 4, fetching the relevant chunks per question.

Instructions tell the AI how to behave. Files tell it what is true about your business. Keep the two in their own slots and the whole thing stays predictable, which is the point of setting it up at all. Most bad results from a project come from putting one in the slot meant for the other: a 40-page brand guide pasted into instructions, or "always be concise" buried on page 12 of a file where retrieval may never fetch it.

Tap a tool to compare (features as of August 2026)

What it is: A workspace with its own instructions and a knowledge folder. Every chat inside the project starts with those files available.
On the free plan?: Yes. Free accounts can create up to five projects. Paid plans get unlimited projects.
Files: Up to 30MB per file. When the knowledge folder gets too big to fit the context window, paid plans switch to retrieval automatically and pull the relevant parts.
Best fit: Best when you want one place per client or per job type, with standing instructions and the reference files together.

Limits and names change often. Each card reflects the official help pages on the date this lesson was updated.

The chat tools: a folder per client or per job

Claude Projects, ChatGPT Projects, and Gemini Gems are the same idea with different trim. Each gives you a named space with its own instructions and files, and every chat you start inside it inherits both. As of August 2026, all three are available on free accounts, with limits: Claude Free allows five projects, ChatGPT Free allows five files per project, and whether a particular Gemini account can attach files to a Gem varies by plan and region, so look for the file option in the Gem editor.

The practical difference is where your business already lives. If your documents are in Google Drive, Gems can link a Drive file rather than copy it, and Google's help page says the Gem will use the most recent version. That is a real advantage for a price sheet that changes monthly. If you already use ChatGPT daily, ChatGPT Projects let you keep a project's memory separate from your other chats, so what it learns about one client stays with that client. If you like Claude's writing, Claude Projects were built around this workflow from the start and, on paid plans, handle a large knowledge folder by switching to retrieval automatically.

Gemini Notebook: the document-first tool

The fourth card is a different animal. Gemini Notebook, which Google renamed from NotebookLM in July 2026, starts from the documents instead of from a chat. You create a notebook, add sources (PDFs, Google Docs, websites, YouTube links, audio, pasted text), and then ask questions. Every answer cites the exact passage it came from, and it will not answer from anything outside your sources. It can also turn the pile into a summary, a study guide, or a spoken audio overview.

As of August 2026 the free tier is generous: up to 100 notebooks, 50 sources per notebook, each source up to 500,000 words or 200MB, and 50 chat questions a day. For a stack of reference material you want to interrogate, a year of meeting notes, every manual for the equipment you rent, the full text of a lease, it is the best fit of the four. For day-to-day drafting, it is the wrong tool; it is a reading room, not a writing desk.

The hard part, simply

The hard part is that standing knowledge is not memory. A project does not remember your last conversation. It re-reads the same folder every time.

Think of the difference between a binder on a desk and a coworker. The binder holds exactly what you put in it, and whoever sits at the desk tomorrow reads the same pages. The coworker remembers what you talked about yesterday, including the things you never wrote down. A project is the binder. Some tools also offer a coworker-style memory, but that is a separate feature with separate settings, and it is the one to be careful with.

Worked example: a St. George tint shop sets up a project with its price list and film specs. In one chat the owner says "we stopped carrying the ceramic 5 percent, take it off quotes." The AI complies, in that chat. The next morning, a new chat in the same project quotes the ceramic 5 percent again, because the price list in the binder still has it. Nothing is broken. The correction was said to the coworker and never written in the binder. The fix is to update the file, or add one line to the instructions.

What goes in the folder, and what stays out

The temptation is to upload everything. Resist it. A project works best when it holds the few documents that answer the questions you actually ask, and nothing that competes with them. For a quoting project at a Washington gutter company, that is the current price sheet, the service agreement template, and two past quotes that show the format you like. That is it. The old price sheet, the supplier catalog, and last year's proposals all stay out, because every one of them is a chance for retrieval to fetch the wrong version.

Two more things stay out for a different reason. Anything with customer names, phone numbers, or payment details does not belong in a standing folder on a personal account; lesson 6 covers why. And anything that changes weekly, like a schedule or a stock count, is better pasted fresh into the chat than stored in a folder that will be stale by Thursday. Standing knowledge is for things that stand still.

How to organize it so it keeps working

One project per job type, not one giant project. "Quotes," "Customer emails," and "Social posts" each get their own folder with only the files that job needs. Smaller folders stay inside the context window and skip the librarian entirely.
Keep files short and current. A two-page price sheet beats a forty-page catalog. When something changes, replace the file the same day. Stale files are the top cause of confident wrong quotes.
Name files like headlines. "Price list, effective Aug 2026.pdf" helps both you and retrieval. "Scan_0043.pdf" helps no one.
Put rules in instructions, facts in files. If a rule must never be missed, it goes in instructions, where it is read every time.
Test it after setup. Start a fresh chat and ask a question whose answer is in a file. If the answer is right and quotes the file, you are done. If not, the file may be a scan (lesson 1) or too large (lesson 2).

Try this yourself

Pick one job you do with AI every week. Create a project, Gem, or notebook for it, upload the one or two files that job always needs, and paste this as the instructions:

You help [business name], a [what you do] in [city], Utah.

Use the attached files as the source of truth for prices, services, and policies. If a question needs a fact that is not in the files, say so and ask me instead of guessing.

When you use a fact from a file, name the file. Keep answers short and practical. Never use hashtags or emojis.

Then open a new chat inside it and ask a question you know the file answers. Check that it names the file. Then ask one it cannot answer, and confirm it asks you instead of inventing. Ten minutes, and you never paste the price sheet again.

Put a reminder on your calendar for one month out: open the folder, check every file is still current, and replace anything that has changed. A project that is maintained is the closest thing to a trained employee these tools offer. A project that is not maintained is a very confident employee working from last year's prices.

Next lesson6. Privacy for your files

Last updated August 24, 2026