DYSARTISANIDEAS, FORGED INTO FORM.Search the episode library ↗

THE INNOVATION FORGE / O.R.E. Reports

AI in admissions: define the boundaries before scaling

Review AI in enrollment work through evidence quality, data controls, human escalation and clear limits on what institutions will optimize.

Mineral samples, a geometric diagram and a brass instrument arranged in a wooden study tray.
Examine the evidence and the choices behind the tools.

THE IDEA, IN A MINUTE

Make the responsibilities as explicit as the automation.

In O.R.E. Report 002, David Dysart examines automation, prediction and student engagement alongside the governance choices they require. Inventory AI tools, question outcome claims and design a bounded review before expanding a workflow.

01 / THE RECORDING

Watch the episode.
Or find your moment.

Read the evidence at the right scale

AI can draft an email, answer a routine question or contribute a prediction to an enrollment workflow. Each use changes a different part of the work. O.R.E. Report 002 groups the discussion around automation, prediction and engagement, then asks who remains responsible for their consequences.

Keep the evidence categories separate. The EducationDynamics article from July 2025 summarizes survey respondents' adoption and perceptions; it does not establish outcomes for every institution. The September 2021 Brookings analysis provides historical criticism of enrollment algorithms. Vendor case studies discussed in the episode describe particular implementations, often alongside other process changes. Reported gains can suggest a question to investigate, but they do not establish what AI alone caused or what another institution should expect.

In the recording · 05:23 ↗

Map the tool, the data and the person responsible

Begin with a working inventory rather than a list of product names. For each AI-enabled feature, describe the communication or decision it influences, the information it receives and the person responsible for reviewing its use. Include features embedded in an existing CRM, not just separately purchased assistants.

Follow the data beyond the input screen. Record whether information reaches an outside model, who can access it, how long it is retained and what controls have actually been checked. An unknown answer belongs in the review queue. It should not disappear behind a vendor's general assurance or a familiar platform name.

In the recording · 14:04 ↗

Test one workflow with a visible handoff

The report proposes a bounded AI-and-human pairing before wider adoption. Choose a routine service question that can be tested with fictional examples. Define the approved information the assistant may use, the situations it must escalate and how a person can request human help without repeating their story.

Measure more than message volume. Review answer accuracy, unresolved questions, response time and the effort staff spend correcting or completing the interaction. Compare like periods and document other changes that could explain a difference. A faster first reply is useful only if the next step is accurate and the handoff works when the question becomes complicated.

In the recording · 14:38 ↗

Keep prediction open to challenge

Historical data records earlier opportunities and institutional choices as well as student behavior. A model can reproduce those patterns while appearing consistent. The episode therefore calls for equity reviews and rejects using predictive scores as the sole basis for denying admission or reducing aid.

An educational model review can examine the target, observation period, missing information and errors without making decisions about individual applicants. Ask whether a prediction is being treated as a fact, whether performance differs across groups and whether a changed process has made older data less relevant. Removing one variable does not establish fairness; related inputs may preserve the same pattern. Qualified institutional reviewers need evidence and authority to question the use.

In the recording · 15:27 ↗

Give oversight a practical job

The proposed governance group brings enrollment, financial aid, technology, security, research and student perspectives into the review. Give it concrete work: examine new uses, document minimum privacy and transparency standards, review major changes and record decisions about prohibited uses.

Staff literacy belongs in that process. Let frontline colleagues critique fictional chatbot exchanges for accuracy, clarity, tone and escalation. A disclosure should describe the actual workflow. Do not promise that people review every message if they only sample outputs, or advertise human assistance without a dependable route to it.

In the recording · 16:16 ↗

Write down what an improvement cannot cost

Optimization requires an objective, and objectives leave things out. The report asks leaders to name both their priorities and the outcomes they will not accept in pursuit of better enrollment or revenue figures. Those limits need an owner and a place in the evaluation.

Before expanding a workflow, write down what success means, what would trigger a pause and who can make that call. Keep evidence of student experience and access beside operational metrics. Reviewing those boundaries when a tool or policy changes helps keep institutional responsibility visible instead of treating a favorable dashboard as sufficient approval.

In the recording · 18:31 ↗

03 / A SMALL EXPERIMENT

Review three fictional AI proposals

Review these fictional proposals for data handling, evidence quality and human escalation.

An essay-summary feature has an incomplete inventory

A fictional team lists a new essay-summary feature as 'inside our CRM.' Its test uses invented text, but the vendor documentation says a separate model provider processes requests. The inventory names no data owner, retention period or access controls. What should the review record before any proposed use with student information?

Compare your reasoning

Document the complete data path, the outside processor, the information sent, retention and access arrangements, and the functional and technical owners. Flag unknown controls for privacy and security review rather than treating the CRM interface as proof that data stays there. Keep the exercise synthetic while those questions remain unresolved.

Revisit this moment · 14:04 ↗
A reply-time improvement becomes a causal claim

A fictional service test records replies within 24 hours for 100 of 200 inquiries before a chatbot trial and 150 of 200 afterward. During the same period, the team also adds evening staffing and rewrites its FAQ. A slide says, 'AI improved timely replies by 50%.' What can the figures establish, and what is missing?

Compare your reasoning

The observed rate rose from 50% to 75%: a 25-percentage-point increase, or a 50% relative increase. The figures do not isolate AI's contribution because staffing and the FAQ also changed, and the inquiry mix may differ. Label the result as an observed change, check comparable periods and question types, and review answer accuracy, unresolved cases and staff effort before making a causal claim.

Revisit this moment · 15:20 ↗
A promised human route fails the test

In a fictional chatbot rehearsal, the welcome message promises access to a counselor. A test user asks for a person after receiving an unclear deadline answer. The bot repeats the FAQ twice, gives no contact route and marks the conversation resolved. What should the reviewers change and retest?

Compare your reasoning

Provide a usable human-contact path and an escalation rule for an explicit request or unresolved answer. Preserve the question for the receiving staff member and avoid marking a case resolved just because an automated reply was sent. Retest the handoff, the accuracy of the deadline information and the disclosure about supervision. Do not have the bot invent exceptions or decide eligibility.

Revisit this moment · 17:50 ↗
Build a test card to take with you

Notes stay in this tab. Reloading clears them.

04 / INSIDE THE STUDIO

The seams are part
of the story.

Behind the episode

The report moves from reported adoption and case studies to practical governance proposals. The closing song returns to the same responsibility question: what an institution asks a model to optimize shapes the work that follows.

Revisit the studio moment · 05:23 ↗

Closing song

The closing song reflects on data, institutional priorities and human responsibility.

Hear the song in the episode

Art from the workshop

Mineral samples and study instruments sit together in a wooden tray.

Open the artwork ↗

KEEP THE IDEA MOVING

Where would you take it next?

CONTINUE EXPLORING