What to Expect at Your First Meeting With a UCLA Dean of Students Reviewer

When a UCLA student receives a notice from the Office of Student Conduct, the first formal step is usually a meeting with a Reviewer. Under UCLA's Interim 2026 Student Conduct Code, that Reviewer — not a panel, and not a committee — is the person who will investigate the allegation, weigh your account against the evidence, and issue a determination. For most cases, this meeting is the single most consequential moment in the entire process. Treating it as a casual conversation is the most common, and most costly, mistake students make.

This guide walks through what to expect, what the Reviewer is actually looking for, and the things students routinely say that damage their own cases. Process information current as of April 2026.

Where the Meeting Happens and Who You Meet With

The Office of Student Conduct sits within UCLA's Dean of Students Office at 1206 Murphy Hall. The Reviewer is a staff member of the Office of Student Conduct assigned to your case. They are not a faculty disciplinarian, and they are not a prosecutor. Their role under the Interim 2026 Code is to gather the facts, develop a complete understanding of the allegation and your response, and issue a determination that stands unless you successfully trigger a hearing by contesting responsibility in writing when Suspension or Dismissal is proposed.

Understanding this role — investigator and decisionmaker, in one person — is the key to preparing correctly.

What the Reviewer Is Looking For

In every meeting, the Reviewer is evaluating three things.

First: credibility. Does your account hang together? Does it match the evidence? Do your answers today track with what you said in earlier emails, written statements, or conversations with the instructor?

Second: consistency with the documentary record. Drafts, version histories, research notes, timestamps, emails, tutoring records, citations — the Reviewer wants to see whether your narrative is supported by the artifacts of the work. A strong narrative without documentary support is weaker than a mediocre narrative with a clean paper trail.

Third: responsibility and insight. Where responsibility is clear, the Reviewer wants to see that the student understands what happened and why it violated the Code. Where responsibility is contested, the Reviewer wants to see a specific, evidence-based account of why the allegation is wrong.

Students who walk in treating the meeting as a negotiation or as a venue to "tell their side" without a focused plan usually undercut themselves on all three dimensions.

What Students Commonly Say That Hurts Them

The single most damaging pattern is over-talking. Under the Interim 2026 Code, the Reviewer does not have to force answers out of you. If you fill silence with speculation, self-diagnosis, or apologies, the Reviewer will incorporate all of it into the file.

Specific things that routinely cause damage:

• "I was stressed / overwhelmed / not myself." This reads as either an excuse or an admission. Neither helps. Context matters, but it should be delivered through documentation, not volunteered as the headline explanation.
• "I know this looks bad." This is a concession. Do not concede appearance. Explain the work.
• "I guess I should have..." Anything that starts this way is a partial admission of responsibility that will end up quoted in the determination.
• Speculating about what the professor thinks. You have no idea what the professor believes; do not mind-read into the record.
• Discussing other incidents. Answer the allegation in front of you. Do not volunteer prior assignments, prior courses, or prior conversations the Reviewer did not ask about.
• Minimizing the stakes. "This isn't really a big deal" lands badly in a process where Suspension and Dismissal are the highest-tier sanctions and transcript notations for Dismissal last 50 years.

What to Bring

Go in with:

1. A written chronology. Dates, times, the sequence of the assignment, when you worked on it, with what sources.
2. The documentary backbone. Drafts showing progression, research notes, citations, emails, writing center or tutoring records. Organized and labeled.
3. The syllabus and assignment prompt. The exact instructions matter; the Reviewer will be comparing your work against them.
4. Your written position. A short, tight statement of your account of the allegation, ready to hand over and read from if helpful.
5. Your Advisor. Under the Interim 2026 Code, you may bring one Advisor to any meeting or proceeding in the review process. The Advisor provides support, guidance, and advice, but may not speak on your behalf. AdvocatED commonly serves as the Advisor and coaches the student through the meeting in real time.

How the Meeting Typically Unfolds

The Reviewer will explain the process, confirm the allegation, and ask you to respond. Expect open-ended questions early ("Can you walk me through how you completed this assignment?") and more pointed questions later ("This section of your submission matches these external sources. How do you account for that?").

Under the Interim 2026 Code, you are not required to answer every question, and you are not under oath. You are, however, creating a record. The determination the Reviewer eventually issues will quote from, and lean on, what you say in this meeting.

After the meeting, the Reviewer may request additional materials, schedule a follow-up, or move directly to a determination. For most cases, the Reviewer's determination and proposed sanction arrive in writing within a defined timeframe after the meeting.

When the Meeting Could Lead to a Hearing

If the Reviewer proposes Suspension or Dismissal as the sanction, and you contest responsibility in writing by the specified deadline, the case moves to a Student Conduct Hearing before a Hearing Officer. Otherwise — whether because a lesser sanction is proposed, or because you do not contest responsibility in writing — the Reviewer's determination stands.

This is why the meeting and the written response are not the "first round" in a larger contest. They are usually the whole contest.

What Preparation Looks Like

Preparation is not memorization, and it is not script-writing. It is three things: (1) knowing exactly what you want the Reviewer to understand by the end of the meeting, (2) knowing what evidence supports each point, and (3) knowing what you are not going to say — the topics and admissions you will stay away from regardless of what you are asked.

AdvocatED advisors work with UCLA students and families to prepare exactly this. We review the allegation and documentary record, identify the themes the Reviewer will likely focus on, build the chronology, draft the written position, rehearse the meeting, and attend as your Advisor under UCLA's Interim 2026 Code. If you have a notice scheduling a Reviewer meeting, reach out as soon as possible — the window between notice and meeting is short, and preparation needs that time to be effective.