Is this right for us?
Building your own, or bringing one in.
Some campuses should absolutely build their own. The difference is not a matter of principle. It comes down to protected time, subject-matter depth, and who owns assessment.
Almost every administrator we speak with agrees the programming is needed. Where they differ is whether to write it themselves or bring in something already built, and that question usually gets settled by whoever is most enthusiastic in the room rather than by what the division can sustain.
It is a fair question with a real answer, and the answer is different by campus. What follows is the version we would give a colleague: what building genuinely requires, where it tends to stall, and how to compare the two paths in the only currency that matters here: staff time.
Start here
Five things the campuses that build well have
These come as a set rather than a menu. The familiar pattern is holding two or three, feeling encouraged, and starting anyway.
If all five hold, build. A program written on your campus, for your students, wired into your own advising and co-curricular record is better than anything you can bring in, and nobody with an alternative on offer, including us, should try to talk you out of it.
The honest risks
Where building reliably stalls
None of these show up in year one. All of them show up in year three, and all of them are easier to plan for now than to discover then.
Which campus do you have
Signals worth reading down
A signal is not a conclusion. Two or more pointing the same way usually is, and where they conflict, the tiebreaker is which version still exists in three years without the person currently driving it.
| If this is true of your campus | Leans toward | Why |
|---|---|---|
| Protected authoring time is written into someone’s workload | Build your own | This is the one nothing substitutes for. Where it genuinely exists, what you build can be better than anything you bring in, because it can be exactly yours. |
| Your governance culture is genuinely closed to outside affiliation | Build your own | Worth testing rather than assuming: recognition pathways are often narrower in memory than in the actual policy. But if the answer is a real no, building is the honest route. |
| Your students need recognition that travels off campus | Bring one in | Accreditation and credit review are multi-year institutional projects. If that is the requirement, it settles the question by itself. |
| Staff hours are what you are short of | Bring one in | This is the whole trade: recurring authorship and facilitation become an advisor commitment. It is a good trade when hours are the scarce thing. |
| It needs to be running next semester | Bring one in | A build compressed into one term produces events rather than a program. If the timeline is immovable, plan around it rather than half-building. |
| A well-liked in-house program already exists | Neither yet | Settle scope first, in writing, with the colleagues who built it. A second program layered over an unresolved boundary produces two weak programs and a personnel problem. |
How to compare
Compare in staff hours across three years
The comparison people usually run puts a fully-imagined first year against an established alternative. Doing it in hours, three years out, is both fairer and much easier.
- List every recurring task by semester. Curriculum revision, session facilitation and its preparation, recruitment, student-leader training, assessment collection, reporting, and the risk and travel administration nobody remembers until it arrives.
- Put an hours figure on each for a professional staff member. Estimate high. The first draft of a build plan is always optimistic and the second draft usually still is.
- Do it three times: year one, year two, year three. Year three is where the paths genuinely diverge.
- Run the same list for the option you would bring in, using its published hours per semester. If nobody will give you a number, treat that as the answer to a different question.
- Stop calling the in-house option free. It is paid for in your colleagues' time, and naming that is what makes the comparison honest with your own leadership.
For a published reference point on the other side: the NSLS asks roughly 10 to 20 hours per semester of an advisor, because a trained student executive board leads each chapter and the NSLS provides the programming. Where those hours actually go is broken down on the advisor time commitment page, and what arrives alongside them is on what's included.
Context
Agreement on the need, disagreement about the route
In our own 2026 research, 88.2% of administrators said their students would benefit from extra leadership-development training, and 77.6% wished for greater resources to connect with students. Almost nobody is arguing about whether this matters.
Which is why the route question deserves a straight answer rather than a persuasive one. If your campus holds the five conditions above, write your own and do it well. If it does not, bringing something in is not a compromise. It is how you get the programming without asking one colleague to absorb it.
Administrator figures: the NSLS State of Higher Ed 2026.
The third path
Hybrid is legitimate, and rarer than people claim
Bringing in a core curriculum and a recognition spine while building campus-specific tracks on top of it is a genuinely good design. You get maintained content and external recognition without giving up the parts that should be local.
It only fails when hybrid is the word used for indecision, two full programs running side by side because nobody would choose. The test is one sentence: which layer owns curriculum, which owns recognition, and who advises what. If you cannot say it in a sentence, you have a scheduling conflict and two disappointed colleagues.
If bringing one in is the direction, the useful next step is the questions worth asking us, and what makes a program work covers what to look at first.
Talk through your campus goals
Explore the program, responsibilities, and next steps with our partnerships team.
Questions colleagues ask about building versus bringing one in
Should we build our own leadership program or bring one in?
Build if five things all hold: protected authoring time written into someone’s workload, subject-matter depth already on staff, assessment owned by someone other than the curriculum author, the program attached to a role rather than a person, and campus-level recognition being enough for your students. Bring one in when staff hours are the scarce resource, when your students need recognition that travels off campus, when it has to be running next semester, or when your division has already been through turnover. Most campuses hold two or three of the five and proceed as though that were enough, which is the most common way these projects stall.
When is building genuinely the better choice?
When you have real protected time and real subject-matter depth, and when the point of the program is specifically that it is yours. A program you author can be tuned to your mission, sequenced around your own academic calendar, and integrated with your advising and co-curricular record in ways nothing external will match. Campuses with a leadership studies faculty presence, stable staffing, and a governance culture that resists outside affiliation should build, and should not be talked out of it by anyone with an alternative to offer.
How should we compare the two options fairly?
In staff hours across three years, and in whether the program survives one resignation. List every recurring task by semester, covering curriculum revision, session facilitation and its preparation, recruitment, student-leader training, assessment collection, and reporting, then put an hours figure on each for a professional staff member and repeat it for year two and year three. Year three is where the two paths diverge, because that is when a curriculum needs its second revision and a founding advisor has often moved on. Also stop describing the in-house option as free: it is paid for in your colleagues’ time.
What does hosting an NSLS chapter ask of our staff?
Roughly 10 to 20 hours per semester from one advisor. Chapters are student-led, so the advisor supports a student executive board rather than running the programming, and executive board training is included. Hosting a chapter costs the institution nothing, with no chapter dues and no fees, so what you are weighing is staff time and campus recognition, not spending.
Is a hybrid approach a real option?
Yes, and it works well when it is deliberate: bring in a core curriculum and a recognition spine, then build campus-specific tracks, a signature capstone, or discipline-linked cohorts on top of it. It fails when hybrid is the word used for indecision, meaning two full programs running in parallel because nobody would choose. The test is one sentence: which layer owns curriculum, which owns recognition, and who advises what. If you cannot say it in a sentence, it is not yet a hybrid.
What if we build and it does not work?
Decide in advance what that would look like and when you will check. Two honest signals are a second-year cohort smaller than the first with no explanation you believe, and being unable to answer when someone asks what changed. Write both into the proposal with a date attached. A build with a stated review point is a reasonable institutional risk; a build without one becomes a program nobody will say is over, occupying a colleague’s time for years.
Sources. Administrator figures, 88.2% saying students would benefit from extra leadership-development training and 77.6% wishing for greater resources to connect with students, are from the NSLS State of Higher Ed 2026. The advisor commitment of roughly 10 to 20 hours per semester is published at info.nsls.org/our-program; executive board training at nsls.org/our-program. Hosting a chapter costs the institution nothing, so this page compares the two paths in staff hours and states no institutional figure of any kind.
