Faculty Credentialing Software Problems: The 6 That Cost Real Money, and How to Avoid Them

Why does the scope stop at a faculty profile with a credentials tab?

Because a profile is what everyone can picture. Name, rank, department, degrees, a place to upload the CV and the transcript. It demos well, it is quick to build, and it looks like the answer to the question the provost asked.

It is not, because qualification is a relationship rather than an attribute. A faculty member with a doctorate in history is clearly qualified for the survey course and not obviously qualified for the research methods course cross listed with sociology. The same person may qualify under your regional accreditor and not under a specialised one governing a different programme. The evaluation happens per course, per term, under the rule that applies to that programme.

The design decision that makes the whole system work is unglamorous: record graduate coursework at the level of individual courses with discipline tags, not as a degree title, and map every course you teach to a teaching discipline with a documented owner. Only then can a rule such as the widely cited eighteen graduate semester hours in the teaching discipline be evaluated as logic rather than as a judgement someone makes by squinting at a CV.

Institutions skip this because entering transcript detail is tedious. It is tedious once. The alternative is tedious every review cycle, forever, and under time pressure.

What goes wrong when you migrate CVs, transcripts and degree records?

The migration in this category is not a data transfer. It is a chase and an audit, and it is where timelines slip.

Three problems repeat. First, an official transcript sent directly from the granting institution is different evidence from an unofficial copy the candidate uploaded, and a shared drive holds both as files named Smith_transcript_2.pdf with no way to tell them apart. Migrate them as documents and you have moved the ambiguity rather than resolved it. Second, a meaningful share of adjunct files are missing official transcripts entirely, because they were requested in September and never arrived. That is a chase, not a build, and it is usually the largest single task in the project. Third, foreign degrees frequently need a credential evaluation from an approved evaluator, and the evaluation is a separate document with its own status.

Model each credential as a record with a type, a source, a verification state, a verifier, a verification date and an expiry where one applies. Unofficial on file, official requested, official received and verified, and expired are four different states with four different consequences, and an assignment can be conditionally qualified pending official receipt with an automatic escalation date. Start the transcript chase before development starts, not after, and load the two colleges with the highest adjunct exposure first so the pre term check produces value while the rest is still arriving.

Why do SIS, HR (Human Resources) and scholarly data integrations break after launch?

Three feeds, three different failure modes.

The section assignment feed is the one that matters most, and it usually breaks on timing rather than on data. Banner, Colleague, PeopleSoft and Workday all expose instructor assignments, and a weekly refresh is fine in October and useless in the two weeks before a term when the assignments are actually changing daily. Institutions discover this in their first August, which is the worst possible August.

The HR feed breaks on governance. Reading employment data and academic data together often crosses a permission boundary that nobody negotiated during design, and in Workday in particular that conversation involves people who were not in the project.

Scholarly data feeds break on identity. ORCID and Crossref return records that may or may not belong to your faculty member, and a system that imports them automatically will attribute a publication to the wrong person, which is the fastest way to lose faculty trust permanently.

Run the section feed daily and increase it to hourly in the two weeks before a term. Settle the HR data governance question in discovery with the people who own the policy, not the people who own the database. And never auto attribute scholarship: import candidates and require a claim step where the faculty member confirms which records are theirs.

What happens when tested experience and dossier confidentiality are not covered?

These are the two gaps that carry legal weight, and they are usually the two cut when the budget tightens.

Both major regional accreditors permit qualification based on relevant professional experience rather than graduate credit, and that is how business, nursing, criminal justice, art and trades programmes staff their studios and clinics. The permission is real. What comes with it is a documented justification with specific evidence, approved by someone with authority. Nothing off the shelf enforces that, so it happens in email, and in the review year the institution writes hundreds of justifications retroactively for sections taught four years ago by people who have since left. That is the most common self inflicted risk in this area.

Dossier confidentiality is the other. Promotion and tenure cases get litigated, and the discovery request asks who saw which document and when. Folder permissions set once cannot answer that.

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 the system requires to precede the term of the assignment. Refuse approvals dated after the term began. For dossiers, model access as a matrix of role, stage and document class evaluated at read time and logged on every view, with recusal removing access immediately and visibly in the audit trail. The workflow is straightforward. The access control is the value, and it is the part that is hardest to retrofit.

Should you build custom or configure what you already own?

If you are under roughly 150 instructors on a single campus with one accreditor and stable full time faculty, do not build. A shared drive with a real naming convention and an attentive dean genuinely works at that scale.

Above that, look at what you already pay for before assuming a build. Interfolio handles faculty search and review seriously, and for many institutions it is the right buy for that half alone. Watermark Faculty Success is the correct answer when your activity taxonomy is close to conventional and your real pain is annual reports rather than credentialing, and Anthology Faculty occupies similar ground. All of them hold rich faculty profiles and none of them will tell your deans, two weeks before classes, which assignments lack a documented qualification basis.

Build when two or more are true. You hire a significant number of adjuncts inside the last month before a term. You rely on tested experience in more than one programme and the justifications are written retrospectively. You carry multiple specialised accreditors with different qualification rules. Your promotion and tenure bylaws differ by college and your current tool forces one process. Or a site visit has already produced a finding here.

One caution worth stating plainly: the activity reporting half of this category is a commodity and the credentialing half is not. If a demo spends most of its time on publication dashboards, you are being shown the easy half.

How do hidden costs get into the quote?

• Specialised accreditors counted as one. Business faculty qualification categories, nursing accreditor rules and engineering programme criteria are each their own rule set with their own evidence expectations.
• Bylaw variation priced as configuration. Access rules that differ by college multiply the role, stage and document class matrix, and each variation has to be tested rather than assumed.
• Collective bargaining agreements. These add procedural steps and deadlines that must be enforced rather than documented, which is a different and larger piece of work.
• Transcript coursework entry. This is the largest data preparation task in the project and it is human work. If it is not a named line with an hour estimate, it will arrive as a surprise.
• Missing official transcripts. If a third of your adjunct files lack them, that is a chase that runs on other people's response times, not yours.

The honest bands from Digital Heroes delivery experience: $50,000 to $110,000 over 10 to 14 weeks for a first release covering credential records with coursework detail, tested experience with approval controls, verification states and per section qualification checking against live section assignments, and $130,000 to $300,000 over 6 to 12 months for the full platform.

What separates a build that works from one that fails here?

Ask 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 course level rather than degree level, the accreditor rule expressed as logic, and a tested experience record whose approval date must precede the term. A developer who describes a faculty profile with a credentials tab has not understood the question, and will build the demo rather than the system.

Ask how they would handle a promotion case that goes to litigation. If read logging and a role by stage access matrix are not the first two things they mention, they will build a document workflow that becomes a liability in discovery.

Ask what they will do so faculty never enter a publication twice. If the answer does not include ORCID or Crossref import with a claim step, adoption fails and the activity data is worthless within two review cycles.

Ask when the section assignment feed runs. Weekly is a wrong answer in August.

Then settle ownership in writing before kickoff: the repository, the cloud accounts, the credential records and the right to hire another firm. At Digital Heroes the client owns the code from the first commit. Faculty credential files are accreditation evidence, and access to them should never depend on a vendor relationship staying healthy through your next review cycle.