Staffing a campus leadership program with no new headcount

The post-mortem on a failed campus leadership program almost never says what actually happened. It says interest declined, or priorities shifted, or the budget moved. What happened is that one person was doing everything, that person had another job, and the program was one reorganization away from nobody’s responsibility.

Advisor capacity is one of the most common reasons campuses decline structured leadership programming, and it is a legitimate objection. It is also a design problem with known fixes.

The constraint is real, so design for it

In our State of Higher Ed 2026 research, 77.6% of administrators said they wished for greater resources to connect with students and only 32.9% said their budget is adequate to serve student needs. No plan that assumes a new position is going to survive that.

The good news is that the staffing model most likely to fail is also the pedagogically weaker one. A program where professional staff run every session has removed the thing it was built to teach.

Put students in the operating roles

The design that lasts is straightforward: a student executive board runs the program, and a staff member holds what students cannot.

Students own recruitment, scheduling, session facilitation, communications, and the term calendar. They are better at recruitment than you are, because peer invitation outperforms institutional email by a wide margin, and running the program is the leadership experience the program exists to provide.

The advisor owns four things students cannot hold: institutional memory across cohorts, risk and policy compliance, the relationship with the rest of the division, and continuity through graduation. That is a real job, and it is a supervisory one rather than an operational one.

For scale, the NSLS publishes an advisor commitment of 10 to 20 hours per semester: a trained student executive board leads each chapter, and the NSLS supplies the programming. Whatever you build or bring in, that is the order of magnitude to plan against. If your design needs meaningfully more from a professional staff member every week, it has a staffing problem it has not solved yet: see the advisor time commitment for how those hours actually distribute across a term.

Three structural choices that do the work

Recruit the next board before the current one graduates. The handoff should overlap by a term, not happen in May. Outgoing officers train incoming officers while the work is still fresh, and the advisor supervises a transition rather than performing one.

Write the recurring calendar down, and let students own it. Every recurring task, with its month and its owner. This is the difference between a program that runs and a program that someone remembers to run. It also makes the advisor role delegable, which matters the first time that person is on leave.

Attach the program to a role, not a person. “Advised by the Assistant Director of Student Involvement” survives a resignation. “Dana runs it” does not. Write it into the position description so the next hire inherits it deliberately instead of discovering it.

Where the hours actually go, and how to reduce them

Advisor time concentrates in four places, and three of them are compressible.

Recruitment and nomination is heaviest in the first two weeks of a term. Compress it by moving nomination into an existing process (faculty already identify strong students for other purposes) rather than running a standalone campaign.

Programming logistics (rooms, calendars, speakers) is the easiest to hand off entirely, and the most commonly retained out of habit. A program you bring in usually removes the hardest part of it: the NSLS includes six broadcast speakers a year, which means the calendar is not the advisor’s to fill.

Continuity and records is small per week and catastrophic if skipped. Keep it, and keep it in a shared location rather than an inbox.

Escalation (a conflict, a policy question, a student in difficulty) is unpredictable and irreducible. This is the part of the role only a professional can hold, and protecting time for it is the point of delegating everything else.

Borrow capacity you already have

Three sources of help exist on most campuses and go unused.

Graduate assistants in higher education or student affairs programs need practicum hours and supervised program-management experience; a leadership program is close to an ideal placement. Faculty who already advise honor societies or capstone projects will often take a session or a project review without a formal appointment. And alumni of the program itself are the cheapest facilitators you will ever find: they know the material, and returning to teach it is a credible thing to ask.

None of that is a substitute for a named advisor. All of it reduces what the advisor personally has to deliver.

Test the design before you launch it

One question predicts durability better than any other: if the person championing this program took another job next term, what would remain?

If the answer is a documented calendar, a trained incoming student board, materials in a shared location, and a position description naming the advising duty, the program will survive. If the answer is a shared drive nobody has opened, you have a two-year program regardless of how good those two years are.

That question also belongs in any external evaluation. When you ask a provider what the program takes, ask for hours per term as a number, and ask what happens on their side when your account manager leaves. The full list is in questions worth asking us.

Do this next

Write your program’s recurring calendar in one sitting: every task, its month, and whether a student or a staff member owns it. Then count the staff-owned rows. If more than a handful cannot be moved to a student, the design needs another pass before it needs a hire. The build-or-bring-one-in comparison is where that decision goes next.