chatgpt-organising-project-work
ITIAN ChatGPT Academy
Technology Simplified — Solutions That Work
Organise Long-Term Project Work
Turn a growing Project into a dependable workspace with focused chats, searchable names, decision records, milestones and a lightweight review routine.
Learning Objectives
By the end of this lesson, you will have an organisation plan that helps you find decisions, understand status and resume work without rereading everything.
Structure
Separate work into focused chats.
Name
Create searchable titles and keywords.
Record
Capture decisions and milestones.
Maintain
Review sources, chats and next actions.
The resumption test
A well-organised Project should let you return after four weeks and answer five questions quickly: What are we building? What is approved? What changed? What is blocked? What happens next? If those answers require reading every conversation, the organisation system needs improvement.
Six Pillars of an Organised Project
One clear purpose
Keep unrelated work in separate Projects so context, files and memory stay useful.
Focused chats
Use one conversation for one workstream, decision or deliverable instead of one endless chat.
Searchable names
Include the subject, action, milestone or date that you are likely to search later.
Approved sources
Keep a maintained source register and distinguish source-of-truth material from drafts.
Decision records
Save concise, reviewed summaries of decisions, owners, reasons and consequences.
Review rhythm
Close loops, remove clutter, update milestones and record the next action regularly.
A Practical Chat Structure
Start small. Add a workstream only when it has a distinct purpose, sources or review cycle.
| Chat | Purpose | Example title | Finish each session with |
|---|---|---|---|
| Orientation | Purpose, boundaries, instructions and current status | 00 — Project Brief and Current Status | Updated status and next review date |
| Planning | Scope, milestones, sequence, risks and dependencies | 10 — Roadmap and Milestones — Q3 2026 | Approved plan changes |
| Sources | Source register, conflicts, gaps and verification | 20 — Sources and Evidence Register | Changed sources and unresolved conflicts |
| Production | Create one deliverable or related set | 30 — Module 4 Lesson Production | Output path, validation and next page |
| Review | Quality assurance, feedback and acceptance checks | 40 — QA and Approval Record | Pass/fail result, owner and required fixes |
| Decision log | Durable record of approved choices | 90 — Decision Log | Date, decision, reason, owner and impact |
Naming That Works With Search
Use visible meaning
A good title combines two or three useful signals:
- Workstream: Sources, Planning, Build, Review
- Deliverable: Academy Home, Module 4, Brand Guide
- Status or time: Approved, Draft, 2026-07
Pattern: [Sequence] — [Workstream] — [Deliverable] — [Milestone]
Avoid title fog
- New chat
- Ideas
- More changes
- Final final version
- Question
These titles provide few search clues. Rename with specific words that also appear in the conversation.
Search tip
OpenAI’s current chat-history search supports keywords from titles and conversation content, with exact matches currently recommended. On the web, use the sidebar search or Ctrl+K on Windows. Archived conversations remain searchable even when they are not visible in the sidebar.
Keep Decisions Separate From Discussion
| Decision record field | What to capture | Example |
|---|---|---|
| ID and date | Stable reference and approval date | DEC-014 · 15 July 2026 |
| Decision | The approved choice in one sentence | Use the ITIAN master template for all ChatGPT Academy lessons. |
| Reason | Evidence and trade-off | Maintains brand consistency and reduces maintenance. |
| Owner | Person or role with authority | Academy owner |
| Affected work | Pages, sources, deadlines or people | Module pages and future landing pages |
| Review trigger | When the choice must be reconsidered | Master-template version change |
A conversation can contain exploration, rejected ideas and corrections. A decision record identifies what was actually approved.
Branch, Move, Archive or Delete?
Branch
Explore an alternative direction without changing the original conversation. Branched chats appear alongside the original and are labelled as a branch.
Move
Place an eligible chat in the correct Project. Review it first because it inherits that Project’s instructions and context.
Archive
Hide a chat from the active sidebar without deleting it. Archived chats remain searchable and can be managed in Settings.
Delete
Use only when the chat is no longer required and retention rules allow it. Deleted chats cannot be recovered through the interface or support.
Do not use Delete as a tidying shortcut
Before deleting, check whether the conversation contains an approval, evidence, deliverable or legal record that must be retained elsewhere. Project deletion is even more serious: it permanently removes the Project’s files, chats and instructions and cannot be undone.
The Six-Step Maintenance Cycle
Orient
Open the Project brief, confirm purpose, current milestone, owner and next action.
Work in focus
Use the matching workstream chat or create one with a meaningful, searchable name.
Close the session
Record output, decisions, unresolved questions, blockers and the next concrete action.
Promote knowledge
Save reviewed summaries or decision notes as Project sources when they merit reuse.
Review the system
Check stale chats, duplicate files, source versions, milestones and privacy boundaries.
Archive a milestone
Write a milestone summary before starting the next phase so history remains understandable.
Interactive Project Organisation Planner
Generate a copy-ready starter structure. Do not enter confidential information into this training tool.
Weekly Review Template
Ask these seven questions
- What was completed since the previous review?
- Which decisions were approved, changed or reversed?
- Which source versions changed?
- What is blocked, and who owns the next action?
- Which chats should be renamed, branched, moved or archived?
- Does any information now sit outside the intended privacy boundary?
- What is the single next milestone and its acceptance test?
Save a concise reviewed summary when it will help future chats. Do not allow the summary to silently replace authoritative source material.
Recommended: 16:9, captioned, showing naming, search, branching, decision records and the weekly review.
Future screenshot plan
- Focused Project chat list
- Search and Ctrl+K
- Branch conversation option
- Move to project option
- Archive and delete controls
- Saved milestone summary
Refresh screenshots whenever interface labels change.
Practical Activity: Organise Your Practice Project
Apply this system to the Project built in earlier lessons. Complete all ten items before continuing to Shared Projects.
Quick Knowledge Check
Answer all five questions before continuing to Lesson 4.7.
Lesson Summary
Seven ideas to remember
- One Project should have one clear purpose and boundary.
- Use focused chats instead of one endless conversation.
- Choose titles containing words you will search later.
- Separate approved decisions from exploratory discussion.
- End every work session with status, blockers and the next action.
- Branch alternatives, and review carefully before moving, archiving or deleting.
- Use a lightweight review rhythm to keep chats, sources and milestones current.
Official OpenAI references
- Projects in ChatGPT — Project search, moving chats, saved responses, branching and deletion.
- Search Chat History — current search steps, keyboard shortcuts, exact-match behaviour and archived-chat visibility.
- Delete and Archive Chats — current controls, recovery limits and archived-chat management.
Interface labels and features can change. Recheck official guidance before updating screenshots or plan-specific instructions.