Term: System prompt
~6 min read
Estimated time: ~6 min read — for the in-app brief plus opening the primary source.
What this is
The system prompt is the standing instruction that sets role, rules, tone, and limits before the user asks anything.
Everyday example
A customer assistant is told, before anyone types: stay on approved products, never invent a discount, hand off complaints to a person. That standing brief is the system prompt.
The system prompt is the hidden standing instruction — tone, role, and rules the user does not see.
- It is how a brand or enterprise tool stays on-policy across chats.
- It can conflict with what the user types; the stack decides who wins.
- You should know who writes and approves it.
- Changing it can change every answer without a model upgrade.
Next action: Ask who owns the system prompt for your customer-facing or HR bot — and when it was last reviewed.
What changes in how you lead
How decision rights, process, and ownership should change.
- Legal and brand should see standing instructions, not only the user-facing script.
- Treat system-prompt changes as a controlled release.
Compare related ideas
System prompt vs Prompt
A prompt is this task. The system prompt is the house rules that apply to every task in that product.
Open PromptSystem prompt vs Guardrails
The system prompt is written instruction. Guardrails also include technical blocks, permissions, and escalation — the full control set.
Open GuardrailsDeep dive
Marketing: approved claims only; no invented promotions.
Legal: do not present output as formal advice; flag when counsel is required.
HR: stay inside published policy; escalate edge cases.
Support: human handoff for fraud, hardship, or complaints.
Ask vendors who writes and reviews the system prompt, how it is versioned, and whether you can audit it.