Higher-education administrative systems
Higher-education administrative systems, replaced and rebuilt to institutional standards
Every college runs on administrative applications that never made it into the ERP: the student-health records system, the research institute’s project tracker, the departmental database one staff member built years ago and still maintains. They work until they don’t, and when they fail, they fail with student data, compliance obligations, and an accreditor’s questions attached. Watkyn replaces and builds these systems for colleges and universities, integrated with the student-information and identity systems you already run, and documented so your own staff can operate them.
Our higher-education work includes a 42-month health-compliance and operations platform for Saint Louis University, single sign-on and identity integration for Horry-Georgetown Technical College, and a project-management application for a West Virginia University research institute.
Evaluating us for an RFP or selection process? Start with the record below, then review our methodology and government delivery record.
The administrative system nobody wants to touch
Most institutions can name it. It’s the application a department built for itself when central IT had no capacity: an Access or FileMaker database, a spreadsheet with macros, a vendor product nobody renewed, or a web app written by someone who has since left. It holds real records, people depend on it every day, and the person who understands it is the only reason it still runs.
The cost shows up slowly. It can’t pull enrollment or employee data from the student-information system, so staff re-key it. It can’t use campus single sign-on, so access is managed by hand. It has no audit trail, so compliance questions are answered from memory. And when the one person who maintains it retires, the department discovers that the process lived in their head.
Replacing that system is a smaller project than an ERP migration and a more consequential one than it looks. The replacement has to carry the data and the rules intact, integrate with the institution’s systems of record, handle regulated data correctly, and be documented well enough that the next person can run it. That is the work this page describes.
The administrative systems we’re asked to replace or build
Three shapes come up most often. Find yours:
Student health and compliance
Health records, immunization and screening compliance, exemption workflows, and state reporting, with a simple web experience for thousands of students and a controlled core for clinical staff.
Research institutes and administrative units
Project, commitment, and milestone tracking for centers, institutes, and sponsored-programs offices that need a configurable system without an enterprise-wide rollout.
Identity and systems integration
Single sign-on (SAML 2.0, Microsoft Entra ID), user provisioning, and integrations with Banner and other campus systems, so a departmental application behaves like part of the institution.
Something else? Enrollment and operational tools, compliance and reporting systems, and departmental databases follow the same method.
How a replacement engagement runs
Administrative systems are replaced on an academic calendar, between terms and around reporting deadlines. The method below fits that rhythm.
Step 1
Discovery and a written plan (fixed fee)
We sit with the people who use the system and the person who maintains it, inventory the data and the rules built into the old application, and map the integrations it needs: student-information system feeds, single sign-on, reporting. You receive a written plan: the recommended platform, data model, integration design, a migration plan for the records you hold, and a fixed price for the build. The plan is yours to keep.
Step 2
A fixed-price build, validated by your staff
The system is built against the plan, with staff testing it on real records before cutover. Data is migrated and reconciled against the old system. Go-live is scheduled around your calendar, staff are trained, and the documentation set is handed over so the department can run and extend what it owns.
Under an RFP or selection process
We respond to solicitations and deliver against the agreements that follow, with structured documentation and defined deliverables. Our Saint Louis University engagement was a direct institutional engagement; our government work has been delivered under formal procurement contracts since 2020. Both records are open to your evaluation committee.
Not sure whether to replace, extend, or retire the system?
Work we’ve delivered for colleges and universities
Higher-education engagements delivered with structured documentation and defined deliverables, described as they appear on our higher-education page.
Saint Louis University
Health-compliance and operations systems for an 18,000-student university
A multi-year suite of health-compliance and operations systems for an 18,000-student university: ContactPath contact tracing and case management, vaccination-compliance tracking with automated state immunization (HL7) reporting, community vaccination clinic operations integrated with Missouri’s infectious-disease monitoring system, and integrations with university identity, email, and student-information systems. 42 months, 2020–2024. Quickbase, with AWS integration.
After two years of licensing, the university purchased a perpetual, unlimited-user ContactPath license and made the platform permanent student-health infrastructure. Read the Saint Louis University case study.
Horry-Georgetown Technical College
Single sign-on and identity integration for a college’s Quickbase environment
Custom single sign-on (SAML 2.0 / Microsoft Entra ID) and user-provisioning integration for the college’s Quickbase environment: external authentication, self-service account sign-up, and realm administration. 2024–2025.
Relevant to IT and security teams that need standards-based identity integration and secure, governed access to cloud applications.
West Virginia University
Project management for a research institute
Project-management application for the Institute for Sustainability and Energy Research (WISER), built collaboratively as a subcontracted Quickbase engagement, with staff training and enablement so the team could maintain and extend it themselves. About 10 months, 2022–2023.
Relevant to university research centers and administrative units that need a configurable project-management system built with knowledge transfer, without requiring an enterprise-wide rollout.
Point Loma Nazarene University
A working system handed off to run independently
Deployed and customized ContactPath, Watkyn’s Quickbase contact-tracing and case-management application, with roles, workflows, data import, and SMS/Twilio integration, then handed it off for the institution to operate and adapt on its own. 2020–2021.
Relevant to institutions that want a working system they can own and run themselves, with a clean handoff rather than long-term vendor dependence.
Scope, duration, and environment for each engagement are on our higher education page. Our government record, including the consolidation of four legacy applications into one platform for a state agency, is on the Government page. References available where permitted, on request.
Replace the application, or replace the ERP?
Some administrative problems are really ERP problems: when finance, HR, and student records all need to change together, the answer is an ERP or student-information-system program, and we’ll say so. We haven’t delivered an ERP or student-information-system replacement for a college, and we won’t present our work as if we had. What we deliver is the layer around those systems: the departmental and administrative applications that integrate with them.
Quickbase suits departmental and operational systems that need to be running within a term: compliance tracking, program and project management, case management, and internal workflows, with a custom web front end when thousands of students or employees need a simple interface. We’re a Quickbase partner. See Quickbase Development.
Caspio fits public- or student-facing database applications with many external users. We’re a Caspio Gold Partner. See Caspio Development.
When the data model is specific to the institution, or the system has to meet state-reporting or regulated-data requirements a platform can’t, we build custom software on AWS; see custom software development for institutions.
For institutions replacing aging financial systems, we offer Acumatica ERP implementation; our Acumatica practice is new, and we say so plainly.
What replacing an administrative system has to get right
The risks in a departmental replacement are specific. These are the ones we design against.
Records and rules migrate incompletely, and the old system has to stay alive
Data inventoried in discovery, migrated and reconciled against the source before cutover, with the business rules in the old application documented and rebuilt deliberately.
The new system can’t talk to Banner, so staff keep re-keying
Student-information-system feeds, single sign-on, and email integration designed in from the start, as in our Saint Louis University and Horry-Georgetown Technical College work.
Student or health data is handled by habit rather than by design
Least-privilege access, role-based permissions, and data handling scoped to the governing agreement; our Saint Louis University health-compliance work was delivered under signed HIPAA Business Associate Agreements.
Go-live lands in the middle of registration
Deployment rehearsed in staging and scheduled around the academic calendar, in controlled steps with validation checkpoints.
Staff are trained once and left with a vendor dependency
Train-the-trainer sessions, user and administrator guides, and a handoff that leaves the department able to operate and extend the system, as Point Loma Nazarene University did.
The replacement becomes the next one-person system
Documentation and a version-controlled project record, so the system outlives any individual on either side.
We approach institutional projects from inside the institution.
Matt Parks, Watkyn’s president, holds a Ph.D. in political science from Boston University and served as Chief Academic Officer and Interim Provost, and professor of politics, at The King’s College in New York, NY, giving Watkyn direct experience with the governance, accreditation, budgeting, and administrative realities colleges face. We treat your constraints as the starting conditions of the work. Behind that sits a documented six-phase delivery process and a team structured so no project depends on one person, the most common failure mode in institutional software.
Why institutions choose Watkyn for administrative systems
We’re the right fit for small and midsize colleges, technical colleges, faith-based institutions, research centers and institutes, and the administrative units of larger universities that need a departmental or administrative system replaced or built by a senior partner who understands institutional accountability. We’re not an enterprise ERP integrator, and we’ll tell you early if a project is better handled another way.
Watkyn LLC is a software development and consulting firm, operating since 2015, that replaces and builds departmental and administrative applications for colleges and universities: student-health and compliance systems, research-institute project tracking, identity and single sign-on integration, and the systems around the ERP and student-information system rather than the ERP itself. Watkyn’s delivered higher-education work includes a 42-month health-compliance and operations platform for Saint Louis University (the ContactPath application, which the university ultimately purchased under a perpetual license), single sign-on and identity integration (SAML 2.0 / Microsoft Entra ID) for Horry-Georgetown Technical College, a project-management application for West Virginia University’s Institute for Sustainability and Energy Research (WISER), and ContactPath deployed and customized for Point Loma Nazarene University. Watkyn has not delivered an ERP or student-information-system replacement for a college and offers Acumatica ERP implementation as a new practice. Watkyn is a Quickbase partner and a Caspio Gold Partner and works remotely with institutions across the United States.
Operating since 2015
Quickbase Partner
Caspio Gold Partner
A full team behind the work
Documented six-phase methodology
Government, higher education, nonprofit, and commercial delivery experience
Ongoing support after launch
Evaluating a broader modernization? See our higher education page for ERP, AI governance, and the full record.
Questions higher-education buyers ask about administrative systems
Yes. Departmental and administrative applications, the systems around the ERP and student-information system rather than the ERP itself, are the higher-education work we do most. For Horry-Georgetown Technical College we built single sign-on and user provisioning for the college’s Quickbase environment; for Saint Louis University we built and integrated a suite of health-compliance systems that the university made permanent. We scope the replacement around your calendar, your systems of record, and the data the old system holds.
Not yet, and we’d rather tell you than let you find out. Our Acumatica ERP practice is new, and we have not delivered a student-information-system replacement. What’s proven is the layer around those systems: integration with Banner, identity, and state reporting; data migration validated before cutover; and institutional documentation standards. If your project is an ERP or SIS program, we’ll say so early.
That integration is part of the design. Our Saint Louis University platform took automated feeds from Banner and sat behind the university’s identity controls; for Horry-Georgetown Technical College we built SAML 2.0 and Microsoft Entra ID authentication with self-service provisioning. Discovery maps every system the application has to talk to before the build begins.
We address data handling during discovery and design around least-privilege access, role-based permissions, secure integrations, documentation, and client-specific contractual requirements. Where FERPA, health data, or other regulated information may be involved, we scope the work around the governing agreement, the institution’s policies, and the data-handling requirements identified during discovery. Our Saint Louis University health-compliance work was delivered under signed HIPAA Business Associate Agreements, and we require BAAs of subcontractors on those engagements.
That is the standard we build to. Point Loma Nazarene University took over ContactPath and ran it themselves after a clean handoff; West Virginia University’s research institute received training and enablement to maintain and extend its application; Saint Louis University took over the portal code, deployment procedures, and day-to-day operations in a structured 2024 handoff. Documentation and training are part of every engagement.
Yes. Responding to solicitations and delivering against the resulting agreements is core to how we work. Send us the RFP and we’ll give you a straight read on fit before you invest time evaluating us.
The departmental systems named at the top of this page: Access and FileMaker databases, spreadsheets with macros, vendor products nobody renewed, and web applications written by staff who have since left. Data is inventoried in discovery, staged during development, then validated through a parallel run before cutover.
A typical engagement leaves you with a requirements specification, system architecture, data model and dictionary, migration and integration plans, a security and access-control design, test and UAT records, training materials, user and administrator guides, a go-live checklist, and a support plan, plus change logs and status reports throughout.
Tell us about the system your institution needs to replace.
Send us a few details about the application, who depends on it, and the systems it has to work with, and a senior Watkyn team member will respond with one of three answers: this looks like a fit; this may be better handled another way; or let’s have a short call to understand the constraints.
Want the bigger picture first?
See Higher Education or Custom Software Development
Governing AI use on campus?
