Never admit a cohort you cannot place

August 16, 2026 · 6 minute read · For surgical technology program directors

Programs rarely get into trouble because the teaching was bad. They get into trouble because a cohort was admitted that the clinical sites could not hold.

Clinical capacity is a counting problem, and counting it the usual way hides the shortfall until it is too late to solve.

Count seats by term, not by year

An annual number is comforting and useless. Say you need 36 clinical placements across the year and your sites have confirmed 40. That reads like a surplus.

Break it into terms and it can turn into this: spring needs 18 and has 12, summer needs 18 and has 28. The year is fine. Spring is six students short, and six students without a placement is a cohort that does not graduate on time.

Students rotate in a specific term at a specific site. Count them there.

Only confirmed counts

Requested is not confirmed. A site that received your ask letter is not a seat. A site that said "probably, send me the paperwork" is not a seat.

Keep both numbers if it helps you work the list, but let only the confirmed number touch your capacity math. The gap between requested and confirmed is your real exposure, and it is worth looking at every week during the ask season.

Didactic terms should not be counted at all

If your program runs four didactic quarters and then two clinical quarters, only two terms need seats. Spreading the requirement across all six makes every term look comfortably covered while the two that matter are short.

Mark which terms are clinical and which are on campus, then count only the clinical ones. This sounds obvious written down. It is not obvious inside a spreadsheet that treats every term as an identical column.

Silence is a decline

Clinical sites almost never send a no. They send nothing.

So a follow-up rule does more for your capacity than better ask letters do. Pick a window, ten days is reasonable, and treat any site silent that long as needing a second contact. Not a rewrite of the ask. A short, specific nudge naming the term and the number.

The programs that hold capacity are not the ones with the best relationships. They are the ones who follow up on a schedule instead of on a feeling.

Agreements expire quietly

Every affiliation agreement has an end date, and nobody is going to remind you of it. A student rotating at a site whose agreement lapsed last month is a compliance problem that started as a calendar problem.

Watch expirations ninety days out, not at expiration. Renewal takes a legal review at most hospitals, and legal review does not move quickly for a document nobody is chasing.

Ask for flexibility, not for a block

An ask that says "I need 6 students placed Monday through Thursday, January 8 through March 20" gives the site one way to say yes and many ways to say no.

An ask that states what you need and then names what you can flex on, the number of students, the days of the week, the start date, converts better. Not because it is a clever technique, but because the person on the other end is solving a staffing puzzle and you just handed them room to move.

Send it from your own mailbox, address a person by name, and say when you will follow up. Then follow up when you said you would.

Build the site bank before you need it

The worst time to look for a new clinical site is the term you discovered you were short. Sites approached in a hurry can tell, and hospital onboarding takes months regardless of goodwill.

Keep a standing list of every facility in your region with its current standing: agreement in place, waiting on a reply, not yet approached, declined, paused. Work the "not yet approached" column a little every quarter, including the quarters you are fully covered.

Capacity gets built in the terms you do not need it.

The rule underneath all of it

Never admit a cohort you cannot place. Confirm the seats first, in the terms the students will actually be out, from sites that have said yes in writing.

Everything else here is just the bookkeeping that makes that rule checkable.