A practical playbook for faculty, staff, and administrators — 2026 edition
Section 1 of 11
←→ navigate sections · Tab moves within a section
Welcome to Context Engineering
By 2026, the way colleges put AI to work has shifted. The early focus on writing the perfect prompt has given way to context engineering — the art and science of orchestrating the entire information environment that an AI model operates within, including memory, retrieval, tools, and state.
🆕 What's new in this 2026 edition
Broader audience: Now framed for faculty, staff, and administrators — not just teaching examples, but advising, financial aid, registrar, IT, accreditation, grants, and HR.
Six operations, not four: Phil Schmid and others have extended the original four-pillar framing to also cover Offloading and Retrieval. We cover all six.
Context rot: Chroma's 2025 research and Anthropic's engineering guidance show that more context is not always better. There's a new section and an interactive simulator.
RAG vs. MCP: A clear explanation of Retrieval-Augmented Generation and Model Context Protocol — what they are, when each fits, and how colleges are starting to use them.
Agentic AI considerations: What changes when the AI takes multi-step actions on your behalf (e.g., drafts an email, books a room, queries the SIS).
FERPA-aware patterns: Concrete guidance on what to put in (and keep out of) context when student records are involved.
Why context engineering matters across the college
Whether you're a faculty member designing a tutor, a financial aid counselor drafting personalized award letters, an IT director standing up an AI helpdesk, or a dean preparing for a Middle States visit — the quality of what AI gives you back is mostly determined by the context you give it. Prompts are the tip of the iceberg; context is everything beneath the waterline.
What you'll learn
1
Conceptual foundation
The shift from prompt engineering to context engineering, and why production-grade college use cases demand it
2
The six operations
Writing, Selecting, Compressing, Isolating, Offloading, and Retrieving context — and when each applies
3
Real college applications
Worked examples across teaching, advising, financial aid, registrar, IT, accreditation, and program review
4
The hard problems
Context rot, RAG vs. MCP, agentic systems, FERPA, and accessibility built into the context itself
5
Hands-on practice
An interactive context builder, a context rot simulator, and downloadable templates you can adapt
A note on framing: Context engineering isn't only a technical skill. It's a way of thinking that asks "what does the AI actually need to know to do this well — and what should it not see?" That question applies just as much to a writing-feedback bot as it does to a chatbot that quotes financial aid policy back to a student.
♿ Accessibility is part of the context
Whenever AI generates HTML, web pages, or digital course materials, your context must include explicit WCAG 2.1 (Web Content Accessibility Guidelines) requirements. Without them, AI-generated output routinely fails Section 508 of the Rehabilitation Act and the ADA — producing low-contrast colors, missing alt text, and inaccessible interactive elements. This module shows exactly where and how to include these requirements in every context you build.
Context Engineering vs. Prompt Engineering
Understanding the distinction between these approaches is crucial for modern educators leveraging AI in their practice.
🎯 Prompt Engineering
✍️ Crafting individual prompts
🔄 One-shot interactions
🎨 Focus on clever wording
📝 Static instructions
🔍 Trial and error approach
⚡ Quick demos and prototypes
🏗️ Context Engineering
🔧 Building dynamic systems
🔄 Multi-turn conversations
📊 Managing entire context windows
⚙️ Runtime information assembly
🎯 Production-ready solutions
🏫 Scalable educational applications
The Context Engineering Mindset
"Think of an LLM like a CPU, and its context window as RAM. Your job as a context engineer is like an operating system - load that working memory with just the right code and data for the task." - Andrej Karpathy
Why This Matters in Education
Consider This Scenario:
Prompt Engineering Approach: "You are a helpful math tutor. Help this student with algebra."
Context Engineering Approach: A system that dynamically loads the student's learning history, current curriculum standards, identified misconceptions, preferred learning style, recent assessment results, and relevant examples - all formatted optimally for the AI to provide personalized, pedagogically sound assistance.
🎓 Educational Impact
Context engineering enables AI to understand not just what a student is asking, but their learning journey, capabilities, and educational context.
📈 Scalability
While prompt engineering creates one-off solutions, context engineering builds systems that work reliably across hundreds or thousands of students.
🔒 Reliability
Context engineering reduces hallucinations and inappropriate responses by providing comprehensive, accurate information to the AI.
♿ Accessibility Compliance
Context engineering is the mechanism for ensuring AI-generated HTML meets WCAG 2.1 Level AA. A prompt says "build a page." A context specifies the exact contrast ratios, ARIA roles, semantic structure, and alt text requirements that make that page legally and educationally accessible.
The Six Operations of Context Engineering
The original four-pillar model (Write, Select, Compress, Isolate) is still the right place to start. As production AI systems matured through 2025–2026, practitioners — most notably Phil Schmid and the Anthropic engineering team — added two more operations to handle external knowledge and external systems. The result is a six-operation model that better reflects how college-grade applications actually work.
✍️
Writing
Capturing what just happened so it can inform what happens next — notes, summaries, profile updates.
🎯
Selecting
Choosing which pieces of available information actually belong in this turn's context.
🗜️
Compressing
Condensing long histories or documents into smaller, faithful summaries that preserve what matters.
🔒
Isolating
Keeping different students, sessions, or tasks from leaking into one another.
📦
Offloading
Moving information out of the prompt and into a tool, file, or database the AI can call when needed.
🔍
Retrieving
Pulling just-in-time information from an authoritative source (a course catalog, a policy database) into the prompt.
Detailed Exploration with College Examples
1. Writing context
Purpose: Make sure the AI remembers what just happened so the next interaction builds on it.
Faculty example: A tutoring system tracks which calculus concepts a student has mastered, which they struggle with, and which teaching strategies have worked best for them. Each session writes back to that profile.
Staff example: An advising assistant logs what was decided in last week's meeting ("student declared Cybersecurity ACA major, plans to take NETW 107 in Spring") so the next session opens with that as already-known context.
2. Selecting context
Purpose: Pull only the slice of available information that's relevant to this turn.
Faculty example: When a student asks about photosynthesis, the system selects their current Biology unit, their prior chemistry knowledge, and the relevant learning objectives — but not their unrelated history with quadratic equations.
Admin example: An accreditation drafting tool selects only the Middle States standards and evidence items relevant to the current section being drafted, not the entire self-study.
3. Compressing context
Purpose: Fit essential information into a finite context window without losing what matters.
Faculty example: A summary like "Student shows strong visual learning preference, has mastered basic algebra but struggles with word problems, responds well to real-world applications" replaces hours of session transcripts.
Staff example: A financial aid assistant compresses a student's prior FAFSA history into a one-paragraph summary instead of pasting in three years of award letters.
4. Isolating context
Purpose: Prevent information from one student, course, or session from contaminating another.
Faculty example: Strategies that worked for an advanced student aren't carried over verbatim into responses for a struggling learner who shares only their first name.
Staff example — FERPA critical: An advising session for Student A must not be visible to Student B even if both are using the same chatbot. Isolation is implemented through session boundaries, scoped retrieval, and role-based access — not just "trust the model."
5. Offloading context (new in the six-operation model)
Purpose: Move information out of the prompt and into an external store the AI can reach for when it needs it. This is the antidote to stuffing everything into the context window.
Faculty example: Instead of pasting an entire syllabus into every prompt, store it in a file and let the AI fetch the relevant section via a tool call.
IT example: A helpdesk bot doesn't carry the full IT knowledge base in its prompt; it offloads to a search index and pulls back only the article(s) that match the current ticket.
6. Retrieving context (new in the six-operation model)
Purpose: Fetch just-in-time information from authoritative sources so the AI grounds its answer in real, current data instead of memory or guesswork.
Faculty example: A research assistant retrieves the actual abstracts of cited papers rather than relying on the model's recollection (which can hallucinate).
Admin example: A registrar bot retrieves the current academic calendar and your institution's withdrawal policy before answering a student's "Can I still drop without a W?" question, rather than relying on what the model remembers from training.
♿ Applying the six operations to accessibility
The same operations apply directly to producing WCAG 2.1 AA compliant output:
Writing: Store your institution's approved accessible color palette (web-safe hex values with verified contrast ratios) so the AI reuses them consistently.
Selecting: Pull the relevant WCAG 2.1 Success Criteria for the content type being generated — different criteria apply to video (SC 1.2.2), color (SC 1.4.3), and keyboard navigation (SC 2.1.1).
Compressing: Summarize your accessibility requirements into a reusable block rather than re-explaining them from scratch every session.
Isolating: Keep accessibility requirements in their own named section so the AI treats them as non-negotiable constraints, not stylistic suggestions.
Offloading: Maintain a single canonical accessibility-requirements document and reference it rather than retyping it.
Retrieving: When the AI needs the official WCAG criterion language, retrieve it from a trusted source rather than relying on the model's recollection.
Context Rot: Why More Context Isn't Always Better
One of the most important findings of 2025–2026 is that large language models do not use their advertised context windows uniformly. Performance degrades as input length grows — even when the relevant information is technically present. This is called context rot, and it changes how you should think about packing information into prompts.
Context rot: The measurable degradation in LLM output quality as the input grows longer, even well below the model's stated context window limit. Documented across all frontier models by Chroma's 2025 research.
The three failure modes
📉 Attention dilution
The model's attention budget is finite. Every token added forces it to spread that attention more thinly. Important constraints get crowded out by less important detail.
🕳️ Lost in the middle
Stanford's research showed a U-shaped recall curve: models reliably attend to information at the start and end of context, but accuracy drops 30%+ for material buried in the middle.
🌀 Distractor interference
When context contains many items that are semantically similar to the answer, the model is more likely to grab the wrong one. The more similar the distractors, the worse this gets.
What the research actually says
Chroma (2025) tested 18 frontier models across 8 input lengths and found degradation at every increment, not just near the limit. Anthropic's own engineering team has confirmed this: even models with 1M+ token windows show measurable drops well before that ceiling. A larger window doesn't fix context rot — it just gives you more room to fill with noise that hurts your accuracy.
Try it: interactive context rot simulator
Adjust the controls to see how three variables — input length, position of the key information, and distractor density — combine to predict accuracy degradation. This simulator uses a simplified model of patterns documented in the Chroma and Stanford research; it's intended to build intuition, not produce production predictions.
94%Estimated accuracy
−2%Length penalty
−1%Position penalty
−3%Distractor penalty
Adjust the sliders to see how each factor affects expected accuracy.
Five practical mitigations
1. Keep the most important constraints near the top or the bottom
If your system prompt includes a non-negotiable rule (e.g., "Never quote a tuition number; always link to the bursar page"), put it first or last. Don't bury it after eight paragraphs of background.
2. Compress aggressively after each major turn
For multi-turn assistants — advising bots, IT helpdesks, long tutoring sessions — summarize older history into a short paragraph instead of carrying every prior message verbatim. Anthropic recommends doing this periodically rather than every turn to manage cost.
3. Offload reference material; retrieve on demand
Don't paste your 80-page faculty handbook into every prompt. Store it externally and let the model retrieve only the relevant section (this is exactly what RAG is for — see the next section).
4. Watch out for similar-looking distractors
If your retrieval system returns five course descriptions that all start with "Introduction to…" the model is more likely to pick the wrong one. Either rerank results to prioritize the best match, or include differentiating fields (course number, credit hours, semester offered) prominently.
5. Don't conflate context window size with capability
Marketing materials emphasize "1M token context!" Reality: most models exhibit serious degradation by 50K–100K tokens. Treat context as a finite, expensive resource — not free RAM. Anthropic's framing: every token spent depletes an "attention budget."
What this means in practice
For most college use cases, the right context is smaller and more carefully chosen than instinct suggests. A tight, well-structured 2,000-token prompt with a clear constraint up front and retrieved facts at the end will usually outperform a 50,000-token prompt that "includes everything just in case."
RAG vs. MCP: Two Ways to Get External Information In
Two patterns dominate how production AI systems actually pull external information into their context. They sound similar — both are about getting outside data to the model — but they solve different problems. Understanding the distinction will save you from picking the wrong architecture for a college use case.
🔎 RAG — Retrieval-Augmented Generation
The pattern: When a user asks a question, your application first searches a knowledge base (typically a vector database of document chunks), pulls back the most relevant passages, and includes them in the prompt before sending it to the model.
Where the intelligence lives: In your application code. You decide what to search, how to chunk, and how to rank results.
Use RAG when: You need to ground answers in a corpus of mostly-static documents (policy manuals, accreditation evidence, course descriptions, archived faculty senate minutes).
🔌 MCP — Model Context Protocol
The pattern: An open standard (introduced by Anthropic in late 2024 and now widely adopted) that lets an AI model discover and call external tools and data sources through a uniform interface. The model itself decides when to call which tool.
Process: Discover → Understand → Plan → Execute → Integrate
Strengths: Excellent for live, structured data and actions — querying the SIS, checking room availability, sending a draft email for review, looking up a current grade.
Where the intelligence lives: Partly in the model — it chooses tools. The tools themselves enforce permissions and FERPA boundaries.
Use MCP when: You need real-time data or you need the AI to take action in another system (e.g., look up a student's account balance, draft a registration email, query Banner/Workday).
How they fit together in a college context
In practice, larger college deployments use both. A 2025 study in Applied Sciences on adaptive intelligent tutoring described exactly this hybrid: RAG for the knowledge base (course content, prior materials), MCP for live signals (current learning goals, instructor flags, policy constraints), and an agent-communication layer on top.
Worked example: a student-advising assistant
A community college builds a chatbot that helps students choose Spring 2027 courses.
RAG handles: The course catalog, program requirements for each major, prerequisite chains, the academic calendar, registration policies.
MCP handles: "Which courses has this student already completed?" (queries the SIS via a tool), "Is ENGI 211 open in Spring?" (queries the schedule), "Draft an email to the student's advisor flagging this conflict" (queries the email system).
Isolation handles: The student is authenticated; tools only return data scoped to that student's record. The AI never sees data for any other student.
⚠️ FERPA implications of MCP
The moment an AI can call tools that return non-directory student data (grades, financial aid status, disability accommodations, disciplinary records), you are subject to FERPA. Practical guardrails:
Identity verification: The user must be authenticated before any tool returns protected data.
Scoped tools: The "get student GPA" tool only returns the GPA of the authenticated user — never accepts a student ID as a parameter from the model.
No training data leakage: Confirm in your vendor agreement that prompts containing student data are not retained or used to train models.
Audit trail: Log every tool call. If a student requests their records under FERPA, you must be able to show what the AI saw and when.
Quick decision guide
📚 Reach for RAG
📘 The information lives in documents
📜 The information is mostly stable
🎯 Quality of retrieval is the main lever
🚫 No action is being taken on another system
💡 Examples: FAQ bot, policy lookup, syllabus Q&A
🛠️ Reach for MCP
⚡ The information is live or changes by the minute
🔐 The data lives in a system with permissions
✉️ The AI needs to do something (send, file, create)
One sentence summary: RAG makes the AI know more; MCP lets the AI do more. Most production college applications eventually need both.
Context Engineering Across the College
Context engineering is not just a teaching tool. The same patterns apply to advising, financial aid, the registrar, IT, HR, accreditation work, and grant writing. Each card below names the primary audience, the type of context that matters most, and an example application.
Faculty & instructional applications
Faculty
🎯 Personalized tutoring
AI tutors that know each student's learning history, prior misconceptions, and current learning objectives. Builds on session-by-session memory written back to a profile.
Faculty
📝 Rubric-aware feedback
Assignment feedback that's anchored to your actual rubric, the course learning objectives, and the student's prior submissions — not generic "this is well-written" filler.
Faculty
🔍 Course design
AI that helps draft modules using your existing course shell, your department's pedagogical conventions, and the relevant program learning outcomes — all loaded as context.
Faculty
💬 Office hours overflow
A 24/7 Q&A bot grounded in the syllabus, lecture transcripts, and the textbook — bounded so it never gives answers to graded assignments.
Student services & staff applications
Staff
🎓 Academic advising assistant
A bot that knows the student's declared major, completed courses, and the program's required sequence — and retrieves the live course schedule before recommending next-term classes.
Staff
💰 Financial aid first-line support
Grounded in your office's published FAQs, the federal Title IV calendar, and standard SAP appeal language. Hands off to a human counselor for any case-specific account question.
Staff
📋 Registrar inquiry triage
Answers common questions ("How do I add a class after the deadline?") using the current academic calendar, current policies, and the petition form — then routes harder cases to staff with a structured summary.
Staff
🖥️ IT helpdesk co-pilot
Reads the incoming ticket, retrieves the relevant KB article, and drafts a reply for the technician to review. Trained on your institution's actual systems (Canvas, Banner, your SSO, your VPN).
Staff
♿ Disability services workflow
Drafts accommodation letters using the approved template and the specific accommodations on file for that student — never invents accommodations not previously approved.
Staff
📞 Admissions inquiry chatbot
Grounded in the current viewbook, application deadlines, transfer-credit policies, and program descriptions. Identifies prospects who need a human admissions counselor.
Administrative & leadership applications
Admin
📊 Program review drafting
Given your enrollment trends, retention rates, advisory committee minutes, and assessment results, drafts the analytical sections of a program review — for a chair to revise, not replace.
Admin
📜 Accreditation evidence narrative
Reads the relevant Middle States (or your accreditor's) standard, retrieves the institutional evidence already collected, and drafts the narrative connecting the two.
Admin
💼 Grant proposal assistance
Given the RFP, your institutional profile, prior successful proposals from your office, and the project's evaluation plan — drafts the project narrative in the funder's preferred voice.
Admin
👥 HR & faculty search support
Given the position description, your institution's hiring policies, and an applicant's submitted materials, drafts an initial-screen evaluation against rubric criteria — flagged for committee review.
Admin
📈 Board & cabinet briefings
Given recent KPIs, departmental updates, and prior board minutes, drafts a one-page briefing in your institution's standard format.
Admin
🏛️ Policy drafting
Given a model policy from a peer institution, your governance handbook, and applicable state regulations — drafts a policy for review that already reflects your institutional voice.
Case study: the adaptive literature discussion bot
Challenge: Create an AI that can facilitate meaningful literature discussions for students at different academic levels in the same online course.
Context engineering solution:
Writing: Track each student's analytical depth, discussion style, and literary knowledge base across the term.
Selecting: Pull relevant text passages, critical perspectives, and appropriate discussion questions based on student level.
Compressing: Summarize key themes and previous discussions while maintaining nuance.
Offloading: Keep the full primary text in a retrieval store rather than the prompt.
Retrieving: Fetch specific passages the student is referencing rather than relying on model recall.
Subject-specific applications
🧮 Mathematics
Context: Student's mathematical foundation, problem-solving strategies, common error patterns.
Application: Adaptive problem generation with scaffolded hints; checks for negative-number and order-of-operations misconceptions before they propagate.
🔬 Science & engineering
Context: Lab experience, conceptual understanding, safety protocols, available equipment, current experiment.
Application: Pre-lab safety briefing tied to this lab; troubleshooting help for actual lab equipment on your campus.
📚 Language arts
Context: Reading level, cultural background, writing goals, prior submissions.
Application: Culturally responsive writing feedback and reading recommendations grounded in your reading list.
🎨 Creative arts
Context: Artistic background, medium preferences, creative goals, the project brief.
Application: Critique that engages with the student's specific choices rather than generic encouragement.
💻 Computing & CS
Context: Course language and version, the specific assignment, the student's current code, the rubric.
Application: Debug help that explains why rather than just patching code — bounded so it never solves graded problems wholesale.
⚕️ Allied health & nursing
Context: Scope of practice for the student's program level, clinical site protocols, applicable patient safety rules.
Application: Case-study walkthroughs that respect scope-of-practice boundaries and emphasize patient safety.
Ethical considerations for college context engineering
Privacy & FERPA: Non-directory student information (grades, financial aid status, disability status, disciplinary records) requires explicit FERPA-aware handling. Identity verification, scoped retrieval, and audit logging are not optional.
Bias: Regularly audit context selection to prevent reinforcement of existing inequities — particularly in admissions screening, hiring, and academic alerts.
Transparency: Students and employees should know when they're interacting with AI and what context it has about them.
Human agency: AI drafts; humans decide. Especially for hiring, financial aid appeals, conduct, and academic standing.
Accessibility: All AI-generated digital materials must comply with WCAG 2.1 Level AA and Section 508. Specify explicit color contrast requirements (minimum 4.5:1 for normal text), ARIA landmark and role specifications, alt-text requirements, and keyboard navigation rules in every context that may produce HTML or web content. This is a legal obligation under the ADA, not an optional enhancement.
Vendor terms: Confirm in writing that prompts containing student or employee data are not retained or used to train models.
Before & After: Transforming Prompts into Context Engineering
See how standard educational prompts can be transformed into powerful context-engineered solutions that deliver reliable, personalized, and pedagogically sound results.
Example 1: Mathematics Tutoring Assistant
❌ Standard Prompt Approach
"You are a helpful math tutor. Help students solve algebra problems. Be encouraging and explain step by step."
Response Framework: Always ask "What do you think happens first?" before showing steps, use graphical representations when possible, immediately address if negative signs are handled incorrectly
Benefits:
Personalized to Alex's specific needs
Builds on previous learning
Proactively addresses known misconceptions
Uses preferred learning modality
Example 2: Essay Feedback System
❌ Standard Prompt Approach
"Grade this essay and provide feedback. Focus on grammar, structure, and content. Be constructive."
Problems:
No rubric or standards reference
Ignores assignment requirements
Can't adjust for student level
No consideration of learning goals
✅ Context Engineering Approach
ASSIGNMENT CONTEXT:
Course: English 101, Assignment: Persuasive Essay on Environmental Policy
Word Limit: 750-1000 words, Due: Week 8 of semester
RUBRIC CRITERIA:
- Thesis clarity (25%): Must present arguable position
- Evidence quality (30%): 3+ credible sources required
- Organization (25%): Intro-body-conclusion with transitions
- Grammar/Style (20%): College-level writing conventions
STUDENT CONTEXT:
Maria, ESL learner (Spanish L1), second semester, strong ideas but struggles with article usage and complex sentence structure, previous essays show good research skills but weak thesis statements
FEEDBACK PROTOCOL:
1. Start with content strengths
2. Address thesis development specifically
3. Limit grammar feedback to top 2 patterns
4. Provide specific revision suggestions
5. Include one model paragraph example
Benefits:
Aligned with specific assignment goals
Considers student's language background
Builds on previous feedback patterns
Provides actionable improvement steps
Example 3: Research Assistant for Graduate Students
❌ Standard Prompt Approach
"Help me find sources for my research paper. Suggest relevant articles and studies."
Problems:
No disciplinary context
Unclear methodology standards
No timeline or scope guidance
Generic search suggestions
✅ Context Engineering Approach
RESEARCH CONTEXT:
Discipline: Educational Psychology, Degree: PhD (3rd year)
Topic: Digital literacy interventions in K-12 settings
Research Question: "How do gamified digital literacy programs affect reading comprehension in grades 3-5?"
INSTITUTIONAL STANDARDS:
- APA 7th edition citation required
- University access: PsycINFO, ERIC, JSTOR
- IRB considerations for future empirical work
CURRENT PROGRESS:
- 23 articles reviewed so far
- Strong representation of gamification research
- Need more studies specifically on reading outcomes
- Gap identified: limited research on long-term retention
Benefits:
Targeted to specific research parameters
Follows disciplinary conventions
Builds on existing progress
Identifies specific gaps to address
Example 4: Language Learning Conversation Partner
❌ Standard Prompt Approach
"Practice Spanish conversation with me. Correct my mistakes and help me improve."
Problems:
No proficiency level specified
Unclear correction preferences
No topic or goal structure
Missing cultural context
✅ Context Engineering Approach
LEARNER PROFILE:
Sarah, B1 intermediate, English L1, learning Mexican Spanish
Strengths: Vocabulary, basic grammar | Weaknesses: Subjunctive, pronunciation of rr
Goal: Conversational fluency for medical volunteering
SESSION PARAMETERS:
- Topic focus: Healthcare/medical scenarios
- Error correction: Recasts preferred over direct correction
- Complexity: Introduce 2-3 new structures per session
- Cultural notes: Include Mexican healthcare etiquette
CONVERSATION PROTOCOL:
1. Start with warm-up question about previous session
2. Role-play: Patient interaction scenarios
3. Introduce new medical vocabulary in context
4. Practice subjunctive with health recommendations
5. End with reflection on progress and next session goals
PROGRESS TRACKING:
Last session: Mastered body parts vocab, struggled with "Es importante que..." constructions
Benefits:
Tailored to specific learning goals
Appropriate challenge level
Culturally relevant content
Builds systematically on progress
Example 5: Laboratory Safety Assistant
❌ Standard Prompt Approach
"Provide lab safety guidance. Tell me about proper procedures and safety equipment."
Problems:
No specific lab or equipment context
Generic safety advice
No emergency protocols
Missing institutional requirements
✅ Context Engineering Approach
LAB ENVIRONMENT:
Organic Chemistry Lab, University of State, Room 204
Equipment: Fume hoods (8), rotary evaporators (4), heating mantles
Current experiment: Synthesis of aspirin (undergraduate level)
STUDENT CONTEXT:
Second-year chemistry majors, completed safety training, previous experience with distillation
Common issues: Forgetting to check glassware, improper heating mantle use
INSTITUTIONAL REQUIREMENTS:
- All accidents reported to EHS within 24 hours
- Lab notebooks required for all procedures
- Instructor approval needed for equipment modifications
Benefits:
Specific to actual lab conditions
Addresses known student mistakes
Includes emergency procedures
Aligned with institutional policies
Example 6: Academic Advising Chatbot Staff
❌ Standard prompt approach
"You are a helpful academic advisor. Help students choose their courses for next semester."
Problems:
No knowledge of the student's program requirements
No awareness of what they've already completed
May invent course numbers, prerequisites, or policies that don't exist at your institution
No FERPA-aware boundaries — could discuss another student's record if confused
Won't know whether a course is actually being offered this semester
✅ Context engineering approach
IDENTITY & SCOPE:
Authenticated student session. Only retrieve data scoped to this student's record via the SIS-lookup tool. Never accept a student ID as a parameter from the conversation.
STUDENT CONTEXT (retrieved via tool):
Declared major: Cybersecurity ACA (Brookdale)
Completed: NETW 107, NETW 110, ENGI 103, ENGL 121
In progress: MATH 131, CIS 217
GPA: 3.4 | Credits earned: 28 of 60 required
PROGRAM CONTEXT (from RAG, Spring 2027 catalog):
Remaining required courses for Cybersecurity ACA, with prerequisites.
LIVE SCHEDULE (retrieved at conversation start):
Which of those remaining courses are actually scheduled for Spring 2027, with day/time and seats remaining.
ADVISING PROTOCOL:
1. Confirm student's intent (full-time vs. part-time, day vs. evening)
2. Recommend 2–4 courses from the actually-offered list that satisfy unmet requirements
3. Flag any conflicts in days/times
4. End with: "I recommend reviewing this plan with your advisor before registering. Want me to draft a message to them summarizing this plan?"
BOUNDARIES:
Never quote tuition, fees, or financial aid status. Never make claims about grade replacement or academic standing. Hand off to human advisor for any case-by-case petition.
Benefits:
Recommendations are grounded in the student's actual record
Only suggests courses that are actually offered next term
FERPA-scoped — never sees another student's data
Hands off appropriately rather than overreaching
Example 7: Program Review Drafting Assistant Admin
❌ Standard prompt approach
"Write a program review for the Cybersecurity associate degree program. Cover enrollment, retention, completion, and labor market alignment."
Problems:
Generic content that could describe any program at any college
Numbers will be invented if not provided
No alignment with your institution's program-review template
No reference to actual advisory committee findings
Won't include your specific labor market data
✅ Context engineering approach
INSTITUTIONAL CONTEXT:
Brookdale Community College, School of STEAM, Engineering & Technology Department. Five-year program review cycle. The completed review goes to the Curriculum Committee and the VP of Academic Affairs.
PROGRAM:
Cybersecurity ACA — 30-credit Academic Certificate of Achievement; prepares students for entry-level SOC analyst and IT-security technician roles; primary credential path includes CompTIA Security+ and EC-Council CEH.
DATA INPUTS (retrieved via tool):
- Five-year enrollment table (head count by term, by demographic)
- Course-level success rates for the certificate's required courses
- Term-to-term and year-to-year retention rates
- Lightcast labor market data for SOC code 15-1212 in Monmouth County
- Minutes from the most recent two advisory committee meetings
VOICE & FORMAT:
Match the analytical-but-not-defensive voice used in the prior cycle's reviews (which are provided as exemplars). Use Brookdale's preferred terminology (e.g., "academic certificate" not "certificate program"). Cite all data with source and as-of date.
BOUNDARIES:
Draft for chair revision. Do not propose new courses or curricular changes without flagging them as "discussion items pending advisory committee endorsement." Do not characterize any individual faculty member's performance.
Benefits:
Anchored in actual institutional data, not invented statistics
Matches the institution's preferred structure and voice
Tied to specific labor market evidence relevant to the region
Knows where its authority ends — flags rather than invents recommendations
Key transformation principles
Notice how each context-engineered version includes:
🎯 Specific context
Detailed information about the learner, environment, and goals
📚 Institutional standards
Alignment with your curriculum, rubrics, templates, and policies
🔄 Adaptive elements
Ability to build on previous interactions and adjust to progress
🛡️ Safety & ethics
Appropriate safeguards, FERPA awareness, and pedagogically sound approaches
Example 8: Accessible Course Page Generator Faculty
❌ Standard Prompt Approach
"Create an HTML page for my online course module on climate change. Make it look nice with colors and include an infographic."
Problems:
No color contrast requirements — AI may pick decorative but inaccessible colors
Infographic has no alt text — invisible to screen readers
No semantic HTML guidance — likely to use <div> soup instead of landmark elements
No ARIA attributes — interactive elements won't work with assistive technology
Likely WCAG 2.1 violations out of the box — fails Section 508 compliance
✅ Context Engineering Approach
ACCESSIBILITY REQUIREMENTS (WCAG 2.1 AA / Section 508):
Semantic Structure:
Use HTML5 landmarks: <header>, <main>, <nav>, <section>, <footer>. Heading hierarchy must be h1 → h2 → h3 with no skipped levels. First focusable element must be a skip-to-main-content link.
Color & Contrast (Web-Safe Colors):
Body text: #333333 on #ffffff — contrast ratio 12.6:1 ✅
Headings: #003366 on #ffffff — contrast ratio 13.4:1 ✅
Accent/links: #005b99 on #ffffff — contrast ratio 7.2:1 ✅
Warning callouts: #7a3b00 on #fff3cd — contrast ratio 5.1:1 ✅
Never use color alone to indicate meaning — pair with icon + label.
Images & Infographics:
All <img> elements require descriptive alt text. The climate change infographic must include: alt="Infographic showing global temperature rise of 1.1°C since 1850, with bar chart of CO2 levels by decade" plus a full text summary immediately below.
ARIA & Keyboard Navigation:
All interactive elements keyboard-accessible (tab order logical). Focus indicators visible with minimum 3:1 contrast. Dynamic content uses aria-live="polite". Tab panels use role="tablist", role="tab", role="tabpanel", aria-selected, aria-controls.
Self-Audit:
Before finalizing, review each element against WCAG 2.1 AA Success Criteria. Report any violations by criterion number (e.g., SC 1.4.3 Contrast Minimum) and provide corrected code.
Benefits:
Section 508 and WCAG 2.1 AA compliant from the first draft
Usable by students with visual, motor, and cognitive disabilities
Screen reader compatible — full semantic structure
Specified web-safe hex colors with verified contrast ratios
Built-in self-audit prevents violations before delivery
Practice Transformation Exercise
Take one of your current educational prompts and transform it using context engineering principles. Consider:
What student information would improve responses?
What institutional standards should be included?
How can the system build on previous interactions?
What safety or ethical considerations apply?
What WCAG 2.1 AA accessibility requirements must be met for any HTML output?
What specific web-safe hex color values and contrast ratios should the AI use?
Interactive Context Builder
Transform your standard prompts into powerful context-engineered solutions using this step-by-step builder. Each step guides you through the essential components of effective educational context engineering.
🛠️ Build Your Context-Engineered Prompt
Step 1: Choose Your Educational Context Template
Select the template that best matches your intended use case:
📚 Tutoring Assistant
One-on-one student support and explanation
📝 Assessment & Feedback
Grading and providing constructive feedback
💬 Discussion Facilitator
Leading classroom discussions and debates
🔍 Research Assistant
Supporting academic research and writing
🎯 Practice & Drill
Skill practice and repetitive learning
⚙️ Custom Context
Build from scratch for unique needs
Step 2: Educational Context & Standards
Establish the foundational educational framework for your AI system:
💡 Tip: Include specific standard codes when applicable (e.g., "CCSS.MATH.CONTENT.8.F.A.1") and mention any institutional policies that should guide AI responses.
Step 3: Student Profile & Learning Context
Define the learner characteristics that will help the AI provide personalized support:
💡 Tip: Include information about how students at this level typically learn best and what teaching strategies have proven effective in your experience.
Step 4: Pedagogical Strategy & Approach
Define how the AI should teach and interact with students:
💡 Tip: Consider your own teaching philosophy and successful classroom strategies. How can the AI embody these approaches?
Step 5: Content Knowledge & Resources
Specify what knowledge and resources the AI should have access to:
💡 Tip: Include specific examples that demonstrate the quality and format you expect. This helps the AI maintain consistency with your standards.
Step 6: Safety, Ethics & Boundaries
Define important safeguards and ethical considerations:
💡 Tip: Consider situations where AI assistance should be limited and human intervention is necessary, such as signs of student distress or complex interpersonal issues.
Step 7: Accessibility & Output Standards
Ensure all AI-generated HTML output meets legal and institutional accessibility requirements. Online educational materials must comply with WCAG 2.1 (Web Content Accessibility Guidelines, Level AA) as required under Section 508 of the Rehabilitation Act and reinforced by the ADA. Specifying these requirements in your context ensures the AI produces compliant output from the start.
📋 Why this matters: Without explicit accessibility instructions, AI-generated HTML often omits alt text, uses poor heading hierarchy, relies on color alone to convey meaning, and produces insufficient color contrast — all of which are WCAG 2.1 violations. Include these instructions in every context where the AI may produce HTML, web content, or visual materials.
💡 Tip: Ask the AI to validate its own output against WCAG 2.1 AA criteria before finalizing. Prompt: "Review the HTML you just generated and identify any WCAG 2.1 AA violations. List each issue, cite the relevant Success Criterion number, and provide a corrected version."
📋 Your Generated Context
Your complete context-engineered prompt will appear here as you progress through the steps:
Complete the steps above to see your generated context...
🎯 Context Quality Checklist
Use this checklist to evaluate your completed context:
✅ Completeness
□ Specific learning objectives defined
□ Student profile included
□ Teaching methodology specified
□ Examples and resources provided
⚖️ Balance
□ Detailed but not overwhelming
□ Flexible yet structured
□ Comprehensive yet focused
□ Safe and ethical boundaries set
♿ Accessibility (WCAG 2.1 AA)
□ WCAG 2.1 Level AA compliance required
□ Color contrast ratios specified (4.5:1 / 3:1)
□ Web-safe hex colors defined
□ ARIA roles & landmark requirements included
□ Alt text & multimedia captions required
□ AI self-audit instruction included
🔒 Safety & Ethics
□ Academic integrity guidelines set
□ FERPA/privacy considerations noted
□ Escalation triggers defined
□ Inappropriate request handling covered
⚠️ Important Reminders
Start Small: Test your context with a few students before full implementation
Iterate: Refine based on actual performance and student feedback
Monitor: Regularly review AI responses to ensure quality and appropriateness
Privacy: Always comply with institutional policies regarding student data
Hands-On Practice
Interactive Context Engineering Exercise
Practice building context for an educational AI assistant. Try different approaches and see how context engineering improves the quality and relevance of responses.
Scenario: Student Struggling with Essay Writing
Student Profile: Sarah, 10th grade, ESL learner, strong in STEM but struggles with persuasive writing, prefers structured approaches
Your analysis will appear here...
Context Engineering Checklist
Before Implementing Educational AI Systems, Ask:
Context Writing
□ What student information should be preserved?
□ How will learning progress be tracked?
□ What pedagogical strategies are most effective?
Context Selection
□ What knowledge is relevant to current task?
□ How do I prioritize different information types?
□ What educational standards apply?
Context Compression
□ How can I summarize without losing meaning?
□ What information is most critical?
□ How do I handle context length limits?
Context Isolation
□ How do I prevent cross-student contamination?
□ What information should be compartmentalized?
□ How do I manage session boundaries?
♿ WCAG 2.1 / Section 508 Compliance
□ Have I specified WCAG 2.1 Level AA as a hard requirement?
□ Are web-safe hex color values and contrast ratios (4.5:1 / 3:1) defined?
□ Are semantic HTML5 landmarks and ARIA roles specified?
□ Are alt text and caption requirements included?
□ Have I instructed the AI to self-audit output before delivery?
Practice Scenarios
Scenario A: Math Tutoring
Design context for an AI that helps struggling algebra students. Consider prior knowledge, common misconceptions, and effective teaching strategies.
Scenario B: Research Assistant
Create context for an AI that helps graduate students with literature reviews. Include research methodology, citation standards, and disciplinary conventions.
Scenario C: Language Learning
Build context for an AI language partner. Consider proficiency level, cultural context, learning goals, and conversation topics.
Scenario D: Lab Safety
Design context for an AI safety assistant in science labs. Include safety protocols, equipment knowledge, and emergency procedures.
Context Engineering Frameworks for Colleges
The CLEAR framework
A systematic approach to designing AI contexts for college use that are Comprehensive, Learner- and user-centered, Ethical, Adaptive, and Reliable. CLEAR was originally framed for teaching, and it works equally well for advising bots, helpdesk co-pilots, and accreditation drafting.
C
Comprehensive
Include all relevant information: learning or work objectives, user background, institutional standards, and policy requirements.
L
Learner- & user-centered
Prioritize the actual needs of the person on the other end of the AI — student, applicant, staff member, advisor — not the convenience of the technology.
E
Ethical
Ensure privacy (FERPA, HIPAA where applicable), bias mitigation, and transparent use of personal data. Include ADA compliance: all AI-generated digital content must meet WCAG 2.1 Level AA and Section 508 by design.
A
Adaptive
Design systems that adjust context based on new information, changing institutional policies, and evolving objectives.
R
Reliable
Build systems that consistently provide accurate, sound responses across diverse scenarios — and that fail safely (escalate to a human) when uncertain.
The TIGHT framework (2026): designing for context rot
CLEAR tells you what to include. TIGHT, an emerging shorthand reflecting 2026 research, tells you how to structure that context so the model actually uses it well. It directly addresses context rot.
T
Top-load constraints
Non-negotiable rules go at the very start of context. The U-shaped attention curve means the first tokens get the most attention.
I
Isolate sections
Use clear, named section headers so the model can treat each block as a distinct unit instead of a slurry of facts.
G
Ground in retrieval
For anything that changes — policies, schedules, student records, prices — retrieve at request time. Don't hard-code it into the prompt.
H
Hide what isn't needed
Omit context that doesn't pertain to this turn. Use compression to shrink older history. More tokens are not automatically better.
T
Tail the question
Place the actual question or task at the end of context. The end is the second-best position on the attention curve, and the most recent tokens are easiest to act on.
The context pyramid for college applications
Three-layer context structure
🎯 Interaction layer
The current conversation, the user's immediate question, real-time feedback within this turn
📊 Dynamic context layer
User profile, history, retrieved documents, tool results for this session
🏗️ Foundational layer
Curriculum standards, institutional policies, pedagogical frameworks, FERPA/accessibility constraints, the AI's role definition
Implementation strategies
🚀 Start small
Begin with simple context engineering in one course or one office before scaling to an institutional level.
🔄 Iterate rapidly
Test context designs with a small group of users and refine based on actual outcomes and feedback before broader rollout.
📏 Measure impact
Track outcomes, engagement, and reliability to validate that context engineering is delivering what you hoped — not just "AI" for its own sake.
🤝 Collaborate
Work with IT, instructional designers, the registrar, financial aid, accessibility services, and your users to design contexts that reflect real workflows.
Common context engineering pitfalls in college settings
Over-contextualization: Stuffing the prompt with every possibly-relevant document. Context rot research shows this often makes things worse, not better.
Static context: Hard-coding facts that change. Tuition figures, deadlines, course offerings, and policy language belong in retrieval, not the prompt.
Bias amplification: Context that encodes existing inequities, especially in admissions and hiring screens.
FERPA violations: Pasting student records into a public AI tool, or designing tools that return data for the wrong student, or failing to verify identity before disclosing protected information.
Vendor data leakage: Sending student or employee data to vendors whose terms allow retention or training-data use. Read the agreement.
Technical complexity: Building systems too complex for the people who actually use them to understand and maintain.
Omitting accessibility: Failing to include WCAG 2.1 AA and web-safe color specifications means AI-generated HTML will almost always have contrast failures, missing alt text, and inaccessible interactive elements — creating legal liability under Section 508 and the ADA.
Your state community college consortium's AI working group
Next steps in your context engineering journey
1
Experiment
Start with one low-stakes application in your role. Build a simple context-aware AI assistant for a specific task and run it for two weeks before scaling.
2
Collaborate
Connect with colleagues, IT, the registrar, financial aid, and instructional designers. Context engineering crosses functional silos and benefits from shared learning.
3
Scale
As you gain experience, expand to broader applications and larger user populations. Add RAG when you have a real document corpus; consider MCP when you need live system actions.
4
Innovate
Develop novel applications of context engineering that address specific challenges in your discipline, department, or institution.
Pedagogical knowledge: How AI can support different learning theories and educational approaches.
Ethical framework: Responsible AI use, FERPA, vendor evaluation, and bias auditing in educational settings.
Research methods: How to evaluate the effectiveness of context engineering in actual student/staff outcomes.
Accessibility standards: Complete WCAG 2.1 (and increasingly 2.2) training; use the WebAIM Contrast Checker to verify color choices; read the WAVE accessibility report for any page your AI produces.
Create your personal learning plan
Based on what you've learned, identify:
One specific context engineering application you want to implement in your role
Three skills you need to develop to make this successful
Two colleagues or campus partners you can collaborate with
A timeline for testing and implementing your first context engineering project
Remember: the next era is context-aware
Context engineering isn't just about getting better AI responses — it's about creating institutional ecosystems that understand, adapt to, and support each student, employee, and decision. As a faculty member, staff member, or administrator, you have the opportunity to shape how this technology develops and is applied in service of your college's mission.