Skip to main content

Editing System Prompts

A practical guide to safely editing system prompts, including when to edit, how to edit, and best practices for making changes.

When to Edit System Prompts​

Good Reasons to Edit​

✅ Update factual information

  • Program name changes
  • Policy updates
  • Contact information changes
  • New requirements or deadlines

✅ Improve response quality

  • Users consistently misunderstand responses
  • Tone doesn't match expectations
  • Responses are too long/short
  • Missing important context

✅ Fix errors or inconsistencies

  • Incorrect information in prompt
  • Conflicting instructions
  • Outdated examples
  • Grammar/spelling mistakes

✅ Add new capabilities

  • Handle new question types
  • Cover new topics
  • Improve edge case handling
  • Add examples for clarity

Bad Reasons to Edit​

❌ Don't edit for temporary changes

  • One-time events
  • Temporary office hours
  • Short-term exceptions

Why: Use cache entries for temporary information instead.

❌ Don't edit to fix single bad responses

  • One user got a wrong answer
  • Response was confusing once

Why: Check if it's a pattern first (review 10+ conversations). Single issues might be user-specific or cache-related.

❌ Don't edit without understanding impact

  • "Let's try changing this and see what happens"
  • Making changes based on hunches

Why: Prompt changes affect ALL responses. Test changes thoroughly before deploying.

❌ Don't edit to circumvent limitations

  • Trying to make AI access real-time data
  • Attempting to give AI capabilities it doesn't have

Why: System prompts control behavior, not capabilities. AI can't access live data, databases, or external systems through prompt changes alone.

Before You Edit: Essential Prep​

Step 1: Read and Understand Current Prompt​

Don't skip this! Even if you think you know what the prompt says.

Steps:

  1. Navigate to ⚙️ Prompt Configuration
  2. Click System Prompt tab
  3. Read the ENTIRE prompt carefully
  4. Note any sections related to your planned change

Questions to ask:

  • How does the current prompt handle this topic?
  • Are there related rules or examples?
  • Will my change conflict with existing instructions?

Step 2: Identify What Needs to Change​

Be specific. Vague goals lead to vague changes.

Bad: "Make responses better" Good: "Add rule: Always mention application deadlines when discussing admissions"

Bad: "Fix the tone" Good: "Change from formal to friendly-professional. Use contractions, shorter sentences, and conversational language"

Write down:

  • What you're changing (specific section/rule/example)
  • Why you're changing it (evidence: user feedback, patterns, errors)
  • Expected outcome (how responses should change)

Step 3: Review Conversation Data​

Before making changes, check if there's evidence the change is needed:

  1. Go to Conversations
  2. Look for patterns related to your planned change
  3. Find at least 5-10 examples

Example:

  • Planned change: Add rule to cite sources more prominently
  • Evidence: 8 conversations where users asked "Where did you get this info?"
  • Action: Proceed with change (clear pattern)

If you can't find evidence: Reconsider whether the change is necessary.

How to Edit: Step-by-Step​

Accessing the Editor​

Steps:

  1. Log in to Admin Panel
  2. Click ⚙️ Prompt Configuration in sidebar
  3. Click System Prompt tab
  4. You'll see the current prompt in a text editor

Making Changes​

Step 1: Locate the Section to Edit​

Use Ctrl+F (Cmd+F on Mac) to search for keywords.

Example: If editing a rule about source citations, search for "source" or "cite"

Why: Don't rely on memory. The prompt may be long and complex.

Step 2: Edit with Care​

Tips:

  • ✅ Make ONE change at a time (don't edit multiple sections simultaneously)
  • ✅ Keep the same formatting style (bullets, bold, numbering)
  • ✅ Preserve existing structure (don't reorganize while editing)
  • ✅ Be specific and clear (avoid ambiguous language)
  • ❌ Don't delete sections without understanding their purpose
  • ❌ Don't add contradictory rules

Example Edit:

Before:

3. Always Cite Sources: When providing factual information, cite the
   source document.

After:

3. Always Cite Sources: When providing factual information, cite the
   source document with specific page numbers. Format: "According to
   [Document Name], page [X]..."

What changed: Made citation format more specific and explicit.

Step 3: Add a Change Description​

After editing, you'll see a "Save Changes" modal.

Required field: "Describe what changed and why"

Bad descriptions:

  • "Updated prompt"
  • "Fixed things"
  • "Made changes"

Good descriptions:

Added explicit rule to include page numbers in source citations.
Reason: 12 users in last 2 weeks asked for more specific source info.
Expected result: Responses will now say "HFIM Handbook, page 45" instead
of just "HFIM Handbook".

Why this matters: Change descriptions create an audit trail. If the change causes problems, you'll know why it was made and can decide whether to revert.

Step 4: Save Changes​

Steps:

  1. Click "Save Changes" button
  2. Modal appears: "Describe what changed and why"
  3. Write clear description (see above)
  4. Click "Confirm and Save"
Hot Reload Warning

Changes take effect immediately. The chatbot will use the new prompt for the next user question.

Testing Your Changes​

Internal Testing (Before Saving)​

Use the Preview Feature (if available):

  1. Make your changes in the editor
  2. Click "Preview" (if available)
  3. Test with sample questions
  4. Verify responses match expectations
  5. If good → Save. If not → Edit more.
Testing Questions

Prepare 5-10 test questions that would be affected by your change. Ask these before and after editing to compare results.

Post-Save Testing​

After saving, test the live chatbot:

  1. Open the chatbot in a new tab (user-facing interface)
  2. Ask questions that should be affected by your change
  3. Verify responses reflect the new prompt
  4. Check 5-10 different phrasings of the same question

Example Test Plan:

  • Change: Added rule to mention application deadlines in admissions questions
  • Test questions:
    • "How do I apply to HFIM?"
    • "Tell me about admissions"
    • "What's the application process?"
    • "Can I join the HFIM program?"
  • Expected: All responses now mention deadline

Monitoring After Changes​

For 24-48 hours after saving, monitor:

  1. Conversations → Check 20-30 new conversations
  2. Negative Feedback → Has it increased?
  3. Response Quality → Do responses match expectations?
  4. User Comments → Any feedback about the change?

If issues arise: Be ready to revert (see Change History)

Common Editing Scenarios​

Scenario 1: Update Contact Information​

Task: Email address changed from info@uga.edu to hfim@uga.edu

Steps:

  1. Search for info@uga.edu in prompt (Ctrl+F)
  2. Replace with hfim@uga.edu
  3. Verify no other references to old email
  4. Save with description: "Updated contact email to hfim@uga.edu per IT notification 1/15/26"

Test: Ask "How do I contact HFIM?" and verify new email appears.

Scenario 2: Change Response Tone​

Task: Make responses less formal and more friendly

Steps:

  1. Find tone/style section (search for "tone" or "style")
  2. Modify instructions:

Before:

Maintain a professional, formal tone. Use complete sentences and proper
grammar at all times.

After:

Maintain a professional but friendly tone. Use conversational language,
contractions (you're, we're), and shorter sentences. Be warm and
approachable while remaining informative.
  1. Add examples showing the new tone:
**Example**:
User: "What is HFIM?"
Response: "HFIM stands for Hospitality and Food Industry Management!
It's a degree program at UGA that prepares you for exciting careers in
hotels, restaurants, event planning, and tourism. You'll learn..."
  1. Save with description: "Changed tone from formal to friendly-professional. Added examples. Based on feedback that responses felt too stiff."

Test: Ask 10 different questions and verify tone is consistently friendly.

Scenario 3: Add New Topic Coverage​

Task: Add guidance on how to answer internship questions (new topic not previously covered)

Steps:

  1. Find Knowledge Scope section
  2. Add to "Your Knowledge Base" list:
• Internship opportunities and application processes
  1. Find Core Rules or Topic Handling section
  2. Add specific instructions:
**Internship Questions**:
When asked about internships, provide:
1. Available internship programs (from handbook)
2. Application process and deadlines
3. Credit hours and requirements
4. Contact: internships@uga.edu
  1. Add example Q&A:
**Example**:
User: "How do I get an internship?"
Response: "The HFIM program requires a 3-credit internship (HFIM 4950).
You can apply through..."
  1. Save with description: "Added internship question handling. Knowledge base expanded to cover internship programs. Based on 15+ unanswered internship questions in last month."

Test: Ask various internship questions and verify comprehensive, consistent responses.

What NOT to Edit​

Don't Remove Core Safety Rules​

Example of what to KEEP:

1. Never make up information or guess
2. Always cite sources
3. Admit when uncertain
4. Don't provide personal advice
5. Stay on topic (HFIM-related)

Why: These rules prevent hallucinations, misinformation, and inappropriate responses.

Don't Edit Formatting Instructions Without Reason​

Example:

• Use bullet points for lists
• Use bold for emphasis
• Keep responses 50-200 words

Don't change unless: Consistent feedback shows format issues.

Don't Add Overly Complex Rules​

Bad:

When answering questions about courses, if the question contains a course
number, first check if it's a 1000-level, 2000-level, 3000-level, or
4000-level course, then determine if it's in Fall or Spring, then check
prerequisites, then...

Why: Too complex. AI may miss steps or misinterpret.

Better:

For course questions, provide:
1. Course description
2. Prerequisites
3. Semester offered
4. Credit hours

Rule of thumb: If a rule requires more than 3 steps, simplify or break into separate rules.

Emergency Rollback​

When to Rollback​

Revert changes immediately if:

  • ❌ Responses are clearly wrong or harmful
  • ❌ Negative feedback spikes suddenly
  • ❌ Chatbot stops responding correctly
  • ❌ Unintended behavior (off-topic, inappropriate, confusing)

How to Rollback​

Steps:

  1. Go to ⚙️ Prompt Configuration
  2. Click System Prompt tab
  3. Click "Change History" (if available)
  4. Find the version before your edit
  5. Click "Restore This Version"
  6. Confirm restoration

Learn more: Change History Guide

Best Practices Checklist​

Before saving any prompt change, verify:

  • I read the entire current prompt
  • I have evidence this change is needed (conversations, feedback, patterns)
  • I edited only ONE section or topic
  • My change is clear and specific
  • I didn't add contradictory rules
  • I wrote a detailed change description
  • I have 5-10 test questions ready
  • I know how to rollback if needed
  • I'll monitor conversations for 24-48 hours after saving

Collaboration and Communication​

If Multiple Admins Edit Prompts​

Establish a protocol:

  1. Announce edits (email, Slack, shared doc)

    Subject: System Prompt Edit - Internship Coverage
    I'm adding internship guidance to the system prompt today at 2 PM.
    Will monitor for issues. - Jane

  2. One edit at a time - Don't have multiple people editing simultaneously

  3. Review each other's changes - Use change history to see what teammates modified

  4. Coordinate testing - Share test results and feedback

Documenting Decisions​

Keep a log (spreadsheet, doc, wiki) of major prompt changes:

DateEditorChange SummaryReasonOutcome
1/15/26JaneAdded internship rules15+ unanswered questionsPositive: internship responses improved
1/20/26JohnChanged tone to friendlyUser feedback: too formalMonitoring: TBD

Why: Creates institutional knowledge, helps onboard new admins, tracks what works.

Common Mistakes and How to Avoid Them​

Mistake 1: Editing Without Testing​

Problem: You save changes and immediately walk away.

Consequence: Issues go unnoticed until users complain.

Solution: Always test with 5-10 questions immediately after saving. Monitor conversations for 24 hours.

Mistake 2: Overly Vague Changes​

Problem: Adding rules like "be more helpful" or "improve quality"

Consequence: No measurable change because AI doesn't know what "helpful" means.

Solution: Be specific. "Include contact email at end of admissions responses" is actionable. "Be helpful" is not.

Mistake 3: Making Multiple Changes at Once​

Problem: Editing 5 different sections in one save.

Consequence: If responses get worse, you don't know which change caused it.

Solution: One change per save. If you need to make multiple edits, save between each change and test individually.

Mistake 4: Ignoring Existing Structure​

Problem: Adding new rules that contradict or overlap with existing ones.

Consequence: Confusing instructions, inconsistent responses.

Solution: Read the full prompt. Understand existing rules. Integrate new rules smoothly.

Mistake 5: No Change Description​

Problem: Saving with description "updated prompt" or leaving blank.

Consequence: If you need to revert or understand why a change was made, no context exists.

Solution: Always write detailed descriptions (see examples above).

Next Steps​

Now that you understand how to edit prompts:

  1. Learn about Change History - Track and revert changes
  2. Learn about Testing Changes - Validate edits before deployment
  3. Understand Hot Reload - How changes take effect immediately
  4. Review Best Practices - Advanced prompt management strategies

Remember: Prompt editing is powerful but risky. Always test, monitor, and be ready to revert. Quality > speed!

Last updated on