Skip to content
All posts

Guide · · 3 min read

Interns who come back: tracking returners, extensions, and multi-year participants

Returning interns, extensions, boomerangs, and co-op rotations break most program data. How to track non-linear paths without losing history.

Jacob Moeckler

Co-founder & CEO

The clean model of a program is one intern, one summer, one outcome. Real programs don't work that way. Sophomores come back as juniors. Interns extend part-time into the fall. Co-ops rotate between school and work. Some interns convert into a development program instead of a job. If your data assumes the clean model, these people get counted twice or lost entirely, and they're often your best pipeline.

The patterns, and what each one breaks

PatternWhat happensWhat breaks in the data
Returning internSame person, a second summerCounted as two people; the first summer's outcome disappears
ExtensionStays on part-time into the school yearEnd date is wrong; looks like a non-completion or a duplicate
BoomerangLeaves, then returns later in a different programHistory is split across unrelated rows
Program to programConverts into a rotational or development programCounted as "no conversion" if only full-time offers count
Co-op rotationsAlternating terms at work and schoolEach term looks like a new hire

The fix: a person with enrollments

The structure that handles all of these is simple. One person record. Each program, cohort, and year is an enrollment attached to that person, with its own status and outcome. Placements sit under each enrollment. A returning intern is one person with two enrollments, not two people.

Decide the rules once

Most reporting arguments are really rules nobody wrote down. Settle them before the season:

  • Does converting into a development program count as conversion? (Usually yes.)
  • Does an extension count as completing the summer program? (Usually yes, with the extension recorded separately.)
  • Is a returning intern eligible for an offer after their first summer, or only their last?

Write the answers into the program guide so every team counts the same way.

Why this is worth the effort

Returners and extensions are early signals of mutual interest. A student who comes back, or a manager who asks to keep someone into the fall, is telling you something about likely conversion. Lose the history and you lose the signal.

From Jacob: When we built demo data for Springbird, the typical intern was easy. The hard records were the ones every program team recognized right away: the intern extended part-time into the school year who came back the next summer, the co-op on alternating terms, the person who left and returned through a different program years later. In most spreadsheets, those people are three rows that don't know about each other. They're also often the people most likely to convert.

FAQ

Should returners go through the full recruiting process again?

That's a program choice. Either way, the decision should be visible on their record with the first summer's evaluation attached.

How do we report a class that includes returners?

Report people and enrollments separately: "58 interns, 64 placements" is clearer than a single number.

How teams run this in Springbird

Springbird is built around the person, so non-linear paths keep their full history.

  • One person, repeatable enrollments by program and year, each with its own status and outcome.
  • Placements and extensions recorded with their own dates, so a part-time fall extension doesn't overwrite the summer.
  • Employee type tracked separately from enrollment, so someone can be full-time and an active program participant at the same time.
  • Class year that moves with the person, so last summer's junior shows up as this summer's senior.

Book a demo →

See Springbird on your own programs

Book a demo