The Scenario
An IR director at a community college fields a request from the VP for Student Success: "Send me our retention rate." He knows that retention could mean fall-to-fall for first-time, full-time students; it could mean term-to-term persistence for all enrollees; it could mean developmental-ed sequence completion; or it could mean the IPEDS GRS definition for the latest cohort. Half the requests he gets use these interchangeably when they are not interchangeable.
“"Retention vs. persistence—sounds simple, but half the requests we get use it interchangeably, when it's not!" — IR Director, Community College (Clema 50+ interview whitepaper)”
How Clema fits the workflow
The data dictionary is the source of truth
The IR director uses the Data Dictionary to author plain-English definitions for "retention," "persistence," and "cohort" that map to the underlying tables. He reviews the AI-drafted definitions from the schema and sample data, then publishes them. From that point, every "retention" question carries the definition he set.
Agentic intake surfaces the ambiguity
When the VP asks in Chat for "retention rate," Clema's agentic intake prompts: "Which retention definition? Fall-to-fall for first-time, full-time, or term-to-term persistence for all enrollees?" The requester picks; the ambiguity is resolved before the IR director is in the loop.
Every answer ships with the definition shown
The sourced response returns the figure alongside the cohort definition, the IPEDS component (when relevant), and the warehouse table. The VP cannot misread the number because the definition is on the figure, not assumed.
The definition survives the next requester
When the same question comes in from a dean next month, Clema uses the same definition. The IR director does not re-litigate it. The definitional drift that used to consume a clarification cycle is handled at the data dictionary layer.
What This Scenario Shows
The whitepaper found that 73.5% of institutions cited vague or unclear requests as a top challenge, with 52.9% reporting extensive follow-up clarification. The root cause is often definitional, not technical: the requester does not know they are using a term ambiguuously, and the IR team spends the cycle clarifying what they meant.
Clema addresses the root cause by making the definition part of the answer. The data dictionary is the governance layer that determines what a term means at this institution; the conversational layer surfaces that definition on every figure so the ambiguity is gone before it becomes a cycle. For the community college IR director, this is the move that converts "retention" from a recurring clarification cycle into a one-time governance decision. See the multi-layer data definitions blog for the deeper treatment of why one term carries five definitions across IPEDS, state, and internal reporting.
See your definitions on every answer
Book a demo with the definitional drift scenario built for your institution, or start a 14-day free trial on a sample source.
Book a Demo