Building, Growing & Leading a PA Program

Most accreditation guidance is written for a program at one moment: the site visit. The rest of the lifecycle gets far less attention, even though that is where the conditions for a clean review are actually built or lost. A program in its first cohort has different exposure than a program on its fourth continuing accreditation cycle, and a program adding twenty seats has different exposure than one absorbing an unplanned leadership change.

This pillar covers the leadership side of the work: launching, staffing, growing, and handing off a PA program. For the standards themselves, start with our ARC-PA Sixth Edition guide. For what happens when findings land, see Accreditation Findings & Remediation.

People and a backward-built timeline. An inaugural program director's first planning document should start at the site visit date and work backward, because almost every other decision inherits its deadline from that date. Scott Massey's planning guidance for founding directors puts the medical director in place roughly fifteen months before the visit, and a minimum of 2.0 FTE principal faculty plus 1.0 FTE support staff no later than nine months out. Those figures are planning targets drawn from his own program-development work rather than published thresholds, and they exist to force the hiring conversation early, while the institution still has time to act on it.

The advisory committee is the piece most often postponed and most often regretted. Regional chief medical officers, health-system leaders, faculty from the institution's other health programs, and practicing PAs give a new program both clinical-site reach and an outside read on its own plans. Recruit people who will push back rather than ratify.

The failure modes for new programs are consistent enough to name. Assessment is the big one: provisional programs face adverse action when they reach their first review without a completed analysis cycle, which is a data-collection decision made at matriculation, not a writing problem discovered later. Behind it sit three predictable pressures. New faculty arriving straight from clinical practice hit a first year of genuine chaos without formal mentoring. An inaugural cohort with no upperclassmen to set norms tends to test boundaries, which a student affairs committee should meet with documented expectations early rather than case by case later. And a new program director carries the heaviest institutional education load in the building while managing a team that has never done this before.

With a model, not an argument. Almost every PA program director eventually sits across from an administrator who has read the standards, noticed that they do not specify a different teaching load for PA education, and concluded that university-wide credit-hour expectations should apply. The administrator is usually right on the literal point and wrong on the substance, which is a difficult position to argue from without evidence.

The workable response is to translate PA-specific work into the currency the institution already uses. Scott developed an hour-equivalent framework over his years as a program director that assigns workload value to the parts of the job a lecture-credit model cannot see: lab instruction at the ratios PA education actually runs, course coordination for team-taught courses, clinical site visitation and evaluation, new course development, accreditation project work, and the administrative loads carried by directors and coordinators. It converts an argument about fairness into a table an administrator can price.

This also feeds directly into accreditation evidence. Standard C1.02 of the Sixth Edition asks a program to demonstrate sufficient principal faculty and sufficient administrative staff, and a defensible answer reads capacity and workload underneath the FTE count rather than resting on ratios. A program that already maintains a workload model has most of that analysis built. Our deep dive on the two questions of C1.02 covers the sufficiency case in full, and the workload framework article gives the model itself.