Skip to content
All posts

Guide · · 3 min read

Why every program team still keeps a master spreadsheet

Early career teams keep a master spreadsheet even with Workday in place. Why the HRIS can't hold program data, and how to keep the sheet from breaking.

Jacob Moeckler

Co-founder & CEO

Ask an early career team where the real data lives and they'll usually point to a spreadsheet, even with a full HRIS in place. The HRIS was built to manage employees, and an early career program runs on information an employee record doesn't hold.

What the HRIS was never designed to hold

  • People who aren't employees yet. Accepted interns exist for months before their first day.
  • Program attributes. Cohort, class year, school, project, mentor, evaluation, conversion eligibility.
  • History across programs and years. Interned twice, then joined a rotational program.
  • Placement dates. The real start and end of a placement don't always match the system's start date.
  • Reasons. Why someone declined, didn't get an offer, or left.

So the team builds what it needs. That's the right instinct.

Why the spreadsheet wins

It's flexible, it's fast, and it belongs to the people running the program. You can add a column the morning a leader asks a new question. No ticket, no release cycle.

Why it eventually breaks

  • Copies multiply. Each team member keeps a version, and they disagree.
  • It resets every cycle. This year's tab doesn't know about last year's people.
  • It lives in one person's head. When the builder leaves, the logic goes with them.
  • It can show you who's behind, but it can't do anything about it. You still email each person one at a time.

Keep what works, fix what doesn't

  1. Split ownership with the HRIS. Pull what it owns, like start date, department, manager, and departure. Own everything program-specific.
  2. One master with one owner. Everyone else views or contributes through it.
  3. One row per person. Attach programs and years to them instead of adding a new row each summer.
  4. Know your breaking point. It usually arrives when more than one person edits, when you run more than one program, or when leadership asks for trends across years.

From Jacob: Every program team I've talked to keeps its own master spreadsheet, even the ones with Workday. When I ask why, the answers are practical: the start date in the system isn't the real placement start, the intern doesn't exist in the HRIS until weeks before day one, and there's no field for half of what leadership asks about. These teams have built their own processes and systems from scratch, often more than once. That spreadsheet is proof of how much the job asks of them.

FAQ

Should we try to move everything into the HRIS?

Usually no. Customizing an HRIS for program data is slow and expensive, and the program changes faster than the configuration can.

Is a shared drive with good naming enough?

For one program and one person, often yes. The trouble starts with multiple editors and multiple years.

How teams run this in Springbird

Springbird keeps what makes the spreadsheet useful and removes what makes it fragile.

  • Connects to Workday for the HRIS and recruiting fields it owns, plus file import for anything else, so you stop retyping them.
  • Program data, history and reasons for each person in one place, carried forward every year instead of reset.
  • The whole team works from the same data, instead of five copies that disagree.
  • Act from the same place you track, and send a reminder, survey or task to any filtered group in a few clicks.

Book a demo →

See Springbird on your own programs

Book a demo