How to Use Claude Projects to Read, Summarise and Draft Documents

What you need

• A Claude account. Projects are open to free accounts too, but a free account can create up to five projects [1].
• A few documents or text files you want Claude to work with, such as trip notes, meeting notes or a rough letter.
• A web browser and time to check Claude’s answers.

Step by step

1. Open the Projects section. Hover over the left side of your account and select Projects. This is where your projects are listed.
2. Create a new project. Click “+ New Project” in the upper right corner. This gives you an empty workspace to fill.
3. Name it and describe it. Give it a clear name, such as “Summer trip”. Claude does not see the name or description, so write them for yourself [1].
4. Find the project knowledge area. It sits on the right side of the project’s main page. Anything you add here is used across all chats in that project [1].
5. Click the “+” button. This lets you add content to the project [1].
6. Upload your files. Choose documents, text files or code snippets. Pick only the files you need, so Claude stays focused [1].
7. Let Claude process the files. Claude reads what you added and uses it as background context for chats in this project [1].
8. Add instructions. Describe how you want Claude to respond, for example using a more formal tone. Then click “Save instructions”. Claude applies these to every chat in the project [2].
9. Start a chat inside the project. Open a new chat from within the project page. Context from your files is not shared with chats outside the project unless you add it to the project knowledge base [1].
10. Ask for a summary. Type a prompt like the one below. Use the code block as a starting point and change the details to suit your files.

Using the documents in this project, summarise the key dates, costs and decisions in five short bullet points.

Example: for a trip-planning project, this gives you a quick list of flight times and hotel dates to compare with your original notes.

11. Ask for a draft. Type a follow-up prompt that asks Claude to write from the same files.

Using the same documents, draft a short, friendly email to my travel companion confirming the plan. Keep it under 150 words.

Example: this produces a first draft of a message you can read, change and send yourself.

12. Move an existing chat into the project if needed. Click the dropdown arrow next to the chat name, select “Add to project”, then choose the project in the Move chat window that appears [1].

Tips and common mistakes

• Do not expect Claude to read the project description. Put any information Claude needs into the uploaded files or the instructions.
• Save your instructions. If you type instructions but do not click “Save instructions”, they will not apply to your chats.
• Start chats inside the project. A chat started outside it will not use the project’s files [1].
• Keep projects tidy. Starring a project gives you quick access from your projects and chats list. Archiving helps you declutter finished work, and it does not remove members or change sharing settings [1].
• Check memory settings. Each project has its own memory. To keep a project’s memory separate from your account memory, turn off “Use account memory” under Memory on the project’s page [1].
• Look in every tab. If you cannot find a project, check “Your projects”, “Organization” and “Shared with you” on the Projects page [1].

Use it responsibly

• Check every answer. Compare summaries and drafts with your original documents before you rely on them. AI can miss details or state things confidently that are wrong.
• Protect your privacy. Never paste or upload passwords, bank details, ID numbers or other people’s private information you do not have permission to share.
• Follow the rules. Check what your workplace or school allows, and follow the service’s own terms. If you are on a Team or Enterprise plan, sharing and permission settings are controlled by your organisation, and you can choose between letting only invited members see a project or sharing it with your wider organisation [1].
• Keep your account secure. Use a strong, unique password, do not share your login, and review who has access to any shared project. As the project creator, you can remove a member’s access [1].