Once you start using GenAI regularly, a new problem appears: you might get a different style and structure every time, even when the task is similar. This is frustrating in university work, where consistency matters (web posts, internal reports, emails, lesson materials, documentation). The solution is to communicate with GenAI in a way that is repeatable – so outputs keep the same “skeleton” even when different people write the prompt.
That is exactly what RICCE is for. It is a beginner-friendly framework that helps you tell GenAI: who it should act as, what to do, what the situation is, what the limits are, and what a good output looks like. The key idea is simple: if you want stable outputs, give stable instructions.
What RICCE means
R – Role: Who should GenAI act as? (editor, coordinator, teaching assistant, policy drafter…)
I – Instructions (or Input): What should it do and what result do you expect?
C – Context: Who is it for and why? What is the situation?
C – Constraints: Rules: length, tone, must-have facts, what to avoid, what to verify, safety/ethics.
E – Examples: One or two short micro-examples of format (not full content) – so the structure is obvious.
Think of RICCE as “make it predictable + make it team-friendly”.
RICCE examples (beginner level, ready to copy)
1. University website event post (team-consistent)
Role: Act as a university website editor.
Instructions: Write a short event post inviting employees to a GenAI workshop.
Context: Audience is university staff. Goal is to inform and encourage registration.
Constraints: 120–160 words. Plain English. Friendly and professional. Include date and time exactly as provided. Do not invent the room; write “Room will be confirmed by email.” Avoid jargon.
Examples (format):
- Example A: Title → 1 short paragraph → 3 bullets → call to action
- Example B: Title → short intro → “Key info” bullets (When/Who/Why) → call to action
2. Internal project update email
Role: Act as a project coordinator.
Instructions: Draft an internal update email after a partner meeting.
Context: Audience is the project team. Goal is alignment and action.
Constraints: Max 200 words. Neutral tone. Include: 3 key decisions, 3 next steps (owner + deadline if known), and 1 risk/unknown. No personal data. If something is missing, mark it as “not specified”.
Examples (format):
- Example A: Subject → Summary → Decisions → Next steps → Risks
- Example B: Subject → “What we agreed” → “What is pending” → “Who does what”
3. Short explanation for beginners (student-facing)
Role: Act as a teaching assistant for beginners.
Instructions: Explain “prompting” in simple language.
Context: Students have never used GenAI before.
Constraints: 6–8 sentences. One analogy. End with 3 practical tips. No technical jargon.
Examples (format):
- Example A: Short definition → analogy → 3 tips
- Example B: “What it is” → “Why it matters” → “Try this” bullets
4. Report from a business trip / visit
Role: Act as an administrative officer writing for internal use.
Instructions: Create a structured trip report.
Context: Audience is the internal department leadership/team.
Constraints: Use headings. Include goals, main activities, outcomes, and recommendations. Mention partners (organisation names only). No personal data. Keep it concise.
Examples (format):
- Example A: Goals → Activities → Outcomes → Recommendations
- Example B: Purpose → Summary → Key outcomes → Follow-up actions
5. Slide outline for a workshop (staff training)
Role: Act as a workshop designer.
Instructions: Create a slide outline for a 20-minute intro to CARE and RICCE.
Context: Audience: university staff, mixed experience level. Goal: practical takeaways.
Constraints: 8 slides max. Each slide max 3 bullets. Include 2 “bad prompt vs improved prompt” pairs.
Examples (format):
- Example A: Slide-by-slide outline with titles + bullets
- Example B: Outline + “Speaker notes” (1 sentence per slide)
6. Creating a reusable template (feedback, email, rubric)
Role: Act as an academic writing coach.
Instructions: Create a feedback template for short essays (reusable).
Context: Used by instructors to speed up feedback while staying supportive.
Constraints: Keep it short. Include placeholders. Avoid vague phrases like “Good job” without specifics.
Examples (format):
- Example A: Strengths / Improvements / Next step
- Example B: “You did well in…” / “To improve…” / “Next time, try…”
A quick RICCE starter you can reuse
Role: …
Instructions: …
Context: …
Constraints: …
Examples (format): …
Example (super short):
Role: university web editor. Instructions: write event post. Context: staff invitation. Constraints: 140 words, simple English, include date/time, no invented room. Examples: Title + intro + bullets + CTA.