Faculty Credentialing and Activity Software: Can You Prove Every Instructor Is Qualified for Every Section?

Why faculty qualification collapses two weeks before a term starts

It is the second week of August. A department chair has just lost an adjunct to a better offer and has covered the section with someone he knows from industry. That person has a bachelor's degree, eleven years of practice, and no graduate hours in the discipline. The section is already published, students are registered, and the chair genuinely believes this is the strongest instructor available. Whether the institution can defend that assignment depends on a tested experience justification that nobody has written, signed by someone with authority, filed where a site visit team can find it in three years.

Multiply that by 90 adjuncts hired between late July and the first day of class. The dean's office is chasing official transcripts that arrive in September or never. Somewhere there is a spreadsheet listing faculty and courses that was accurate on the day it was built, which was during the last reaffirmation.

The stack is usually Banner, Colleague, PeopleSoft or Workday for HR (Human Resources) and section assignments, a shared drive of CVs and scanned transcripts organised by whoever last owned it, Interfolio for search and sometimes for review, Watermark Faculty Success or Anthology Faculty if the institution invested, and Excel everywhere else. The thing none of them holds is the join that accreditors actually ask about: this person, this credential, this section, this term, and the reason it is acceptable.

In the faculty affairs projects we have delivered, the recurring pattern is a scramble of several months before a site visit, where staff assemble a faculty roster with credentials for every section taught in the review period. That work is expensive, it is repeated every cycle, and it produces a document rather than a capability. Meanwhile the actual risk sits quietly in the sections nobody checked at hire time.

Problem 1: qualification is per section per term, and your systems think it is per person

A faculty member with a doctorate in history is qualified to teach the survey course and not obviously qualified to teach the research methods course cross listed with sociology. The same person may be qualified in one program and not in another under a specialised accreditor. Qualification is a relationship between a credential and a specific course, evaluated for the term in which it is taught.

Watermark Faculty Success and Anthology hold rich faculty profiles, and Interfolio handles search and review well. What they do not do out of the box is read your section assignments every term and tell you, before the term starts, which assignments lack a documented qualification basis. That check requires knowing your course to discipline mapping, which is institution specific, and your accreditor's rule, which differs by program.

What a custom build does: map every course to a teaching discipline once, with a documented owner, then evaluate each term's section assignments against the credentials on file. The output is a list for each dean two weeks before the term, not a report after the fact. The widely cited SACSCOC guideline of 18 graduate semester hours in the teaching discipline for undergraduate instruction is expressible as a rule against transcript coursework, and the coursework has to be recorded at the level of individual graduate courses with discipline tags, not as a degree title. That is the modelling decision that makes the whole system work, and it is the one institutions skip because entering transcript detail is tedious. It is tedious once. The alternative is tedious every cycle forever.

Problem 2: tested experience is where the risk lives, and it is unwritten

Both major regional accreditors permit qualification based on relevant professional experience rather than graduate credit, and this is how business, nursing, criminal justice, art and trades programs staff their studios and clinics. The permission is real. The requirement attached to it is a documented justification with specific evidence, approved by someone with authority, not a chair's confidence.

Nothing off the shelf enforces this, so it happens in email, and in the year of the site visit the institution writes 200 justifications retroactively for sections taught four years ago by people who have since left. That is the single most common finding risk in this area, and it is entirely self inflicted.

What a custom build does: make tested experience a first class record attached to a person and a discipline, with the evidence fields your accreditor expects, a required narrative, a named approver, and an approval date that must precede the term of the assignment. The system refuses to mark an assignment qualified on tested experience with an approval dated after the term began. That constraint feels bureaucratic until the first time it saves a program. Where AI does one useful and narrow job here: read the CV a new adjunct submits and draft the structured experience record for a human to verify and edit, because getting a chair to fill a form in August is the real obstacle and reducing it to a review task changes compliance rates materially.

Problem 3: credential documents have states, and a scanned PDF has none

An official transcript sent directly from the granting institution is different evidence from an unofficial copy the candidate uploaded. A licence has an expiry date and a verifying board. A foreign degree usually needs a credential evaluation from an approved evaluator. A shared drive holds all of these as files with names like Smith_transcript_2.pdf and knows nothing about any of it.

What a custom build does: model each credential as a record with a type, a source, a verification state, a verifier, a verification date, and an expiry where applicable. Unofficial on file, official requested, official received and verified, and expired are different states with different consequences, and an assignment can be conditionally qualified pending official receipt with an automatic escalation date. Licences with expiries generate reminders to the faculty member and the dean before they lapse rather than after. The document is stored alongside the record, but the record is the asset. A site visit team asking for evidence gets a link and a state, not a folder.

Problem 4: dossiers are a confidentiality problem before they are a workflow problem

Promotion and tenure cases carry legal weight and get litigated. The dossier moves from candidate to department committee to chair to college committee to dean to university committee to provost, and at each level the visibility rules differ. External reviewer letters are confidential from the candidate at most institutions. The candidate can respond to some materials and not others. Committee members recuse themselves and must lose access. Some institutions permit the candidate to add material after a negative recommendation at a lower level, and some do not.

Interfolio does review and does it seriously, and for many institutions it is the right buy. Where custom work becomes justified is when your bylaws differ by college, when your rules about candidate response windows and recusal are not expressible in the product's model, or when you need the dossier to assemble itself from activity data you already hold rather than being uploaded again.

What a custom build does: model access as a matrix of role, stage and document class, evaluated at read time and logged. Every view is recorded, which matters because the discovery request in a denied tenure case will ask who saw what and when. External letters are stored with the solicitation record, the reviewer's own conflict declaration, and a retention rule. Recusal removes access immediately and is visible in the audit trail. The workflow part is straightforward. The access control part is where the value is, and it is the part that is hardest to retrofit.

Problem 5: faculty will not enter activity data twice, and you are asking them to enter it four times

The same publication is entered into the annual review form, the tenure dossier, the department's accreditation report, the college newsletter and a grant biosketch. Faculty response to this is entirely rational: they enter it badly, late, or not at all, and the resulting activity data cannot support any report you want to run.

What a custom build does: enter once, reuse everywhere, and pull from sources rather than asking. ORCID, Crossref and your institutional repository can populate publications with a claim step where the faculty member confirms which records are theirs. Grants come from your research administration system. Teaching comes from the SIS. What remains for manual entry is service and the narrative, which is the part faculty are willing to write because it is the part only they can write. The activity taxonomy has to be yours, since what counts as scholarship differs between your fine arts faculty and your engineering faculty, and a single national taxonomy will fit neither. Then the annual review form, the dossier, the accreditation table and the CV are all rendered from the same underlying records in different templates. That is the promise Watermark Faculty Success makes and mostly keeps at institutions whose taxonomy fits it, and the reason to build is usually that yours does not.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, the honest shape here is as follows. A focused first release, meaning the credential and transcript coursework record, tested experience with approval controls, document verification states, and per section qualification checking against live SIS assignments with a pre term report per dean, runs $50,000 to $110,000 and ships in 10 to 14 weeks. A full platform adding annual review, reappointment, promotion and tenure dossiers with a full access matrix and audit logging, external reviewer solicitation, activity capture with ORCID and Crossref import, CV and accreditation table generation, and specialised accreditor reporting runs $130,000 to $300,000 phased over 6 to 12 months.

What drives price up specifically in this category: the number of specialised accreditors, because AACSB faculty qualification categories, nursing accreditor rules and engineering program criteria are each their own rule set. The number of colleges with different promotion and tenure bylaws, since access rules that differ by college multiply the matrix. Collective bargaining agreements, which add procedural steps and deadlines that must be enforced not just documented. The state of your existing credential files, because if official transcripts are missing for a third of your adjuncts that is a chase, not a build. And how many graduate transcripts need coursework level entry, which is the largest data preparation task in the project.

What keeps price down: starting with adjunct and part time faculty in your two highest risk colleges. That is where the qualification exposure concentrates and where the pre term check pays back immediately.

Build versus buy, and when buying is the right call

Buy if you are under roughly 150 instructors on a single campus with one accreditor and stable full time faculty. A shared drive with a real convention and an attentive dean genuinely works at that scale, and Interfolio is a fair buy for search and review alone. Watermark Faculty Success is the right answer when your activity taxonomy is close to conventional and your main pain is annual reports rather than credentialing.

Build when two or more of these are true. You hire a significant number of adjuncts inside the last month before a term and cannot check them before students sit down. You rely on tested experience in more than one program and the justifications are written retrospectively. You carry multiple specialised accreditors with conflicting qualification rules. Your promotion and tenure bylaws differ by college and your current tool forces one process. Or you have been through a site visit where faculty credentials produced a finding or a recommendation, in which case the cost of building is small relative to what a follow up report costs you in staff time.

Our position: the activity reporting half of this category is a commodity and the credentialing half is not. If a vendor demo spends most of its time on dashboards of publications and little on how the system knows whether the person teaching section 004 next Monday is qualified, you are being sold the easy half.

How to choose a developer for faculty credentialing software

Ask them how the system decides that a specific instructor is qualified for a specific section. The right answer involves a course to discipline mapping, graduate coursework recorded at the course level rather than the degree level, an accreditor rule expressed as logic, and a tested experience record with an approval date that must precede the term. A developer who describes a faculty profile with a credentials tab has not understood the question.

Ask how they would handle a promotion case that goes to litigation. If they do not immediately talk about read logging and a role by stage access matrix, they will build a document workflow that becomes a liability in discovery.

Ask what they will do to avoid asking faculty to enter a publication twice. If the answer does not include ORCID or Crossref import with a claim step, adoption will fail and the data will be worthless within two review cycles.

Ask who owns the code and the credential records, in writing, before kickoff. You should own the repository, the cloud accounts and the right to hire another firm. At Digital Heroes the client owns the code from the first commit. Faculty credential evidence is accreditation evidence, and it should never depend on a vendor relationship remaining healthy.