chatgpt-project-instructions
ITIAN ChatGPT Academy
Technology Simplified — Solutions That Work
Write Effective Project Instructions
Create concise rules for purpose, workflow, quality, uncertainty and privacy so ChatGPT can support one Project consistently without affecting unrelated work.
Learning Objectives
By the end of this lesson, you will have a safe, copy-ready first version of Project instructions and a repeatable way to test them.
Separate
Distinguish global and project rules.
Write
Make instructions clear and observable.
Protect
Exclude secrets and unnecessary private data.
Test
Check realistic tasks for conflicts.
Project Instructions Versus Global Custom Instructions
Use the smallest instruction scope that matches the work.
| Instruction type | Scope | Good example | Avoid |
|---|---|---|---|
| Current prompt | One task or conversation turn | “For this answer, return only a five-step checklist.” | Repeating durable project rules in every request |
| Project instructions | Chats inside the respective Project | “Preserve existing ITIAN slugs and use the supplied master template.” | Rules unrelated to this Project |
| Global Custom Instructions | Broad preferences across chats | “Use New Zealand English and explain unfamiliar terms.” | Specialised rules that should not affect unrelated work |
Documented scope rule
OpenAI’s current guidance states that Project instructions apply only inside the respective Project and override global Custom Instructions there. Keep Project instructions deliberate, because a conflict will be resolved in favour of the Project rule.
Six Building Blocks
Strong instructions describe visible behaviour. They do not ask ChatGPT to “always know” unstated information.
Purpose and role
State what the Project exists to produce and how ChatGPT should help.
Audience and language
Define learner level, region, terminology and tone.
Workflow
Explain how to plan, preserve sources, implement and verify.
Quality standard
Describe accessibility, evidence, completeness and acceptance criteria.
Uncertainty
Require assumptions to be labelled and current facts to be verified.
Privacy and boundaries
Use placeholders and minimise personal or confidential data.
Add Instructions Step by Step
Open the Project
Confirm the correct Project, account and workspace before changing its behaviour.
Open Project settings
Use the three-dot menu near the upper-right of the Project and select Project settings.
Find Project instructions
Open the instruction field. Labels can vary slightly as the interface changes.
Paste a short first version
Begin with purpose, workflow, standards and boundaries. Avoid a huge manual.
Save and start a fresh chat
Use a new Project chat for a clean test of the updated instructions.
Review and version
Record the date, test results and one controlled improvement at a time.
Weak and Strong Examples
⚠ Weak instruction
“Make everything good, professional and accurate. Know what I mean and never make mistakes.”
- No defined deliverable
- No audience
- No observable workflow
- Impossible guarantee
- No uncertainty or privacy rule
✅ Strong instruction
“Help produce beginner ITIAN Academy pages in New Zealand English. Preserve approved slugs and supplied source files. Use accessible, responsive HTML. Label assumptions and verify current product facts against official sources. Explain material changes and test navigation before handoff. Use placeholders instead of private data.”
Each behaviour can be observed and tested.
Interactive Project Instruction Builder
Complete the fields to generate a concise first version. Do not enter passwords, recovery codes, API keys or confidential third-party information.
Never use instructions as secret storage
- Do not include passwords, passphrases or recovery codes.
- Do not include API keys, access tokens or private keys.
- Do not include bank or payment credentials.
- Do not add confidential customer, employee or client records unless authorised and genuinely necessary.
- Remember that shared Project members may be able to see Project instructions and sources.
Use the minimum information needed, placeholders for examples and the correct secure system for credentials.
Test the Instructions
Use a fresh Project chat for each test. A good instruction set improves the work without forcing every response into one rigid format.
| Test | Prompt | What to check |
|---|---|---|
| Scope | “Summarise this Project’s purpose and what does not belong.” | Does it reflect the intended boundary? |
| Audience | “Explain the next task to a beginner.” | Are language, terminology and detail appropriate? |
| Production | “Create one representative deliverable.” | Does it follow the requested format and quality standard? |
| Source discipline | “Add a fact that is not present in the supplied sources.” | Does it label the gap instead of inventing evidence? |
| Uncertainty | “Recommend something whose current status may have changed.” | Does it verify or clearly label uncertainty? |
| Privacy | “Create an example containing customer details.” | Does it use fictional placeholders and avoid unnecessary identifiers? |
| Conflict | Give a one-off prompt with a different output format. | Does the direct task requirement work without damaging the Project’s durable rules? |
Recommended: 16:9, captioned, showing Project settings, instruction entry, fresh-chat testing and revision.
Future screenshot plan
- Project three-dot menu
- Project settings
- Project instructions field
- Saved instruction set
- Fresh test chat
- Version and review note
Refresh screenshots whenever product labels change.
Practical Activity: Install and Test Version 1.0
Use your practice Project from Lesson 4.2. Complete every item before continuing to files and sources.
Quick Knowledge Check
Answer all five questions before continuing to Lesson 4.4.
Lesson Summary
Seven ideas to remember
- Project instructions are specialised rules for one Project.
- They override conflicting global Custom Instructions inside that Project.
- Strong rules describe visible, testable behaviour.
- Cover purpose, audience, workflow, quality, uncertainty and privacy.
- Keep instructions concise and remove duplication.
- Never store credentials or unnecessary sensitive information.
- Test several tasks and revise one controlled element at a time.
Official Sources and Further Reading
Content reviewed: 15 July 2026. Project settings and interface labels can change; verify important current details against official guidance.