Preparing and managing an internship program

Before the first day: what "prepared" actually means

A program is prepared when three things exist before a single student starts: a written learning objective for the placement, a supervisor who knows what they are being asked to watch for, and a shared definition of what a successful internship looks like that is not just "the student showed up." Most programs have the placement logistics solved and skip straight past these three, which is why the assessment conversation later gets stuck: there was nothing agreed on to assess against.

Setting learning objectives the supervisor can actually use

A learning objective written for an accreditor ("students will demonstrate professional competency") is useless to a site supervisor who has never seen it and would not know what to do with it if they had. Write objectives in terms of what the supervisor will actually observe: not "communication" but "leads the daily team check-in by week three," not "professionalism" but "flags a missed deadline to their supervisor before it is discovered." The NACE competencies are the vocabulary underneath these; the objectives are what that vocabulary looks like in a specific role.

Briefing the site supervisor

A fifteen-minute conversation before the placement starts prevents most of a semester's worth of vague end-of-term feedback. Cover four things: what the program is trying to develop (not just get done), what "good" looks like at the midpoint versus the end, how and when the supervisor will be asked for feedback, and that a single-use rating link with no account requirement is coming, so it does not read as spam when it arrives. Supervisors who were briefed respond to the assessment request at a meaningfully higher rate than ones who were not; the request makes sense to them because they were told to expect it.

A pre-launch checklist

• Learning objectives written in observable terms, not competency-framework

language, and shared with the supervisor.

• Supervisor briefed on what they will be asked to observe and when.
• Placement mapped to a term and a cohort, so the results roll up rather than

scattering as one-off placements.

• A defined midpoint check-in, not just a beginning and an end.
• The rating mechanism (single-use link, no account) explained to the

supervisor in advance.

Where preparation ends and assessment begins

Preparation sets up what to look for. Assessment is collecting the self- and supervisor-rating once the placement is underway and comparing them. Programs that build the two as one step tend to write assessment questions that do not match what anyone actually briefed the supervisor to watch for, which is the single most common reason a first assessment cycle produces confusing results. Get the preparation right and the assessment step becomes straightforward.

Frequently asked questions

Do we need learning objectives for every internship, or just the paid ones?

Every one you intend to assess. An unassessed placement can run without objectives; the moment you want evidence of what the student gained, you need something written down before it started to assess against.

How is this different from a syllabus for a for-credit internship course?

A syllabus covers grading and academic requirements. These objectives are narrower and more practical: specific, observable things a site supervisor watches for and rates, feeding into a cohort report rather than a grade. The two can and often should coexist.