Pro Tip: Using ChatGPT Projects to Organize Your AI Workflows by Client or Department

What You'll Learn

• What ChatGPT Projects includes that regular conversations do not
• The exact custom instructions prompt that makes each project smarter
• Which documents to upload first and why order matters
• How to use Projects for client work, departmental management, and strategic planning
• The three mistakes to avoid when setting up your first projects

A business development director uses ChatGPT every day. She works on five active client accounts, each with its own context: the industry, the stakeholders, the current priorities, and the specific communication style each client expects. Every morning she opens ChatGPT and spends 3 to 5 minutes re-explaining who she is working with before she can get to the actual work.

Multiply that ramp-up time across five clients, five sessions per day, 20 working days per month. The math is 25 to 50 hours per year spent explaining the same context the model already knew yesterday.

ChatGPT Projects, launched December 13, eliminates that re-explanation. Each project maintains persistent memory, stores uploaded documents, and applies custom instructions to every conversation within that workspace. The setup takes 20 minutes per project. The time savings begin on the first session after setup.

SUBSCRIBER BREAK -- Premium Content Below

The Projects Setup Prompt

Use this as the custom instructions for each new project. Replace the bracketed fields for each specific project.

This project covers work related to [CLIENT NAME / DEPARTMENT / INITIATIVE]. Background: [2-3 sentences describing the client's business, the department's function, or the initiative scope and objectives] Key stakeholders: - [Name, Title]: [Brief description of their role and priorities] - [Name, Title]: [Brief description of their role and priorities] Current priorities (as of [MONTH YEAR]): 1. [Priority 1] 2. [Priority 2] 3. [Priority 3] Communication guidelines: - Output format: [bullet points / numbered lists / executive summary + detail] - Tone: [formal / professional-casual / technical] - Length: [concise under 200 words / standard / comprehensive] Always do the following in this project: - Flag any assumption I should verify before using this externally - Note if my question touches a topic covered in an uploaded document - Reference specific document names when drawing from uploaded files

What Documents to Upload First

First (upload on day one): the client brief or project charter, the most recent meeting notes or status report, and any style guide or communication preference document. Second (within the first week): relevant market or competitive data you reference regularly, financial models or data summaries, product or service documentation for the client's questions. Third (as needed): historical meeting notes, previous deliverables for reference, background reading you want available but rarely need. Upload highest-value context first; Projects retrieval prioritizes recency in some implementations.

Three Project Categories That Work Best

• Client relationship projects. Each active client gets its own project with brief, SOW, most recent status notes, and client-specific reference documents. Every email draft, analysis request, and meeting prep query runs through the client's project context.
• Departmental management projects. Current quarter's goals, team roster with roles, weekly metrics dashboard, and department budget. Use it for weekly report preparation, headcount planning, and strategic planning queries.
• Strategic initiative projects. Upload the initiative charter, current status deck, decision log, and stakeholder map. Every update, analysis, and communication related to the initiative runs through this single project context.

The Three Setup Mistakes to Avoid

Uploading too many documents at once: start with 3 to 5 core documents and add more as you identify specific gaps. Writing generic custom instructions: "Be professional and thorough" is not useful. "Return all analysis as a 3-point executive summary followed by supporting detail" is actionable. Not updating priorities monthly: the instructions are a snapshot. Build a monthly habit of reviewing and updating the priorities field for active projects. Stale context is worse than no context because it produces confidently wrong framing.