Deploying a Current Research Information System (CRIS) or research information management (RIM) platform — Pure, Symplectic Elements, Converis, VIVO, or a comparable system — is a data-migration and integration project first, but its success is decided somewhere else: whether faculty actually keep their records current once the go-live date has passed. A technically flawless implementation with low researcher engagement produces exactly the outcome institutions build a RIM system to avoid — stale profiles, incomplete publication lists, and research offices back to chasing CVs by email for every report and dossier. This guide covers the adoption side of a RIM rollout: the change-management planning, communication strategy, incentive design, and self-deposit workflow decisions that determine whether faculty treat the new system as their own record of truth or as one more mandatory form to ignore.
For the technical side of a rollout — data mapping from legacy systems, integration points, and implementation sequencing — see the companion Elsevier Pure CRIS implementation and data-migration checklist. This guide assumes that work is underway or complete and focuses on the people side: getting faculty to use the system once it exists.
Why faculty adoption is the harder half of a RIM rollout
Most of what an institution wants a CRIS to hold cannot be pulled automatically from Scopus, Web of Science, or an HR feed. As the Association of College and Research Libraries notes in its overview of research information management systems, “much of the information an institution may want to capture about their faculty does not have a source and requires manual entry” — honors and awards, students mentored, journal editorships, and society memberships among them, along with non-federal grants and discipline coverage gaps that are especially pronounced in the humanities and social sciences, where automated bibliographic sources are thinner. ACRL also names the predictable consequence directly: RIM implementations run into “organizational or political roadblocks: resistance from faculty, a lack of resources for data entry, or funding issues.”
That gap between what a vendor’s automated feeds can populate and what an institution actually needs on a profile is the reason a RIM rollout is a change-management project, not just a systems-integration one. Someone has to do the manual entry, correct mismatched or duplicate imported records, and keep the record current after go-live — and in most RIM deployments, that someone is the faculty member, not the research office or library.
Applying a change-management framework to a CRIS rollout
Two widely used organizational change-management frameworks translate directly onto a RIM deployment, and institutions running structured rollouts typically draw on one of them rather than treating change management as an informal afterthought to the technical project plan:
- ADKAR (Prosci) — a five-stage individual-change model: Awareness of why the system is changing, Desire to participate, Knowledge of how to use it, Ability to actually do the work (claiming records, entering data, correcting imports), and Reinforcement to sustain the behavior after go-live. Applied to a RIM rollout, most stalled adoptions fail at Desire or Reinforcement, not Awareness or Knowledge — faculty know the system exists and, after a training session, know how to use it; they simply don’t see a reason to keep using it once the mandatory launch-week push is over.
- Kotter’s 8-step model — an organizational-level sequence: create urgency, build a coalition, form a strategic vision, enlist volunteers (departmental champions), remove barriers (friction in the deposit workflow), generate short-term wins (visible, working profiles early), sustain acceleration, and institute the change in standard practice (folding CRIS data into promotion and reporting workflows so there is no parallel process to maintain).
Neither framework was written for research administration specifically, but both point to the same practical conclusion for a RIM rollout: the launch event itself is a small part of the work. Sustained faculty engagement depends on continued reinforcement (ADKAR) and on institutionalizing the new workflow into standard practice so the old, parallel way of reporting research activity genuinely goes away (Kotter) — not on a single training rollout.
Stakeholder mapping and communication strategy
A RIM rollout touches more constituencies than the research office running the project, and each needs a different message because each has a different stake in the outcome:
- Faculty and researchers — the end users being asked to review imported records, correct mismatches, and in many rollouts, claim and deduplicate their own author records. The message that lands is “what’s in it for me” (WIIFM): less time re-entering the same CV information into five different forms, not an abstract institutional-reporting benefit they don’t directly experience.
- Departmental administrators and chairs — often the people actually doing data entry on behalf of busy faculty, or fielding complaints when a profile looks wrong. They need practical workflow training and a clear escalation path, not just a system announcement.
- The library — frequently holds bibliographic expertise and, where an institutional repository already exists, owns deposit and open-access-compliance workflows that need to connect to the CRIS rather than run as a second, disconnected process for faculty to maintain.
- Research office / RIM team — usually the project owner and the audience responsible for governance decisions (what counts as a “verified” record, who approves records that feed external reporting) after go-live.
- Institutional leadership — the audience for the dashboards and reporting the system was purchased to support. Leadership sponsorship is what makes data-quality expectations enforceable across departments that might otherwise treat profile maintenance as optional; without it, adoption stalls at the department that decides it isn’t a priority.
Messaging to faculty and messaging to institutional leadership should rarely be the same message delivered twice. Leadership communication can reasonably lead with reporting accuracy, REF/ERA-style assessment readiness, or grant-portfolio visibility. Faculty-facing communication that leads with those same institutional benefits routinely reads as “this system exists to monitor you,” which is one of the most common and most damaging resistance points in a RIM rollout (see below) — faculty-facing messaging should lead with time saved and control over their own public profile instead.
Incentive design: linking self-deposit to work faculty already have to do
The rollouts that sustain engagement past the launch period are the ones that make the CRIS the single place a researcher’s activity data lives, rather than an additional form layered on top of existing ones. Practical incentive-design moves that reduce this to genuine time savings rather than added work include:
- Feed the annual activity report or promotion-and-tenure dossier directly from CRIS data, so faculty populate one record instead of re-typing the same publication list, grants, and service activity into a separate CV document each cycle.
- Auto-populate what can genuinely be automated — Scopus/Web of Science publication feeds, an HR appointment feed, an ORCID-linked works list — so manual entry is reserved for the categories no external source captures (awards, mentoring, editorial service, non-federal grants), rather than asking faculty to re-enter data the system could have pulled in itself.
- Connect self-deposit to open-access compliance where a funder or institutional OA policy already requires it, so depositing into the CRIS satisfies a mandate the researcher has to meet anyway instead of creating a second deposit step alongside the repository.
- Make the researcher-facing profile genuinely useful to the researcher — a public profile page, a CV export, an ORCID sync — so there is a direct personal benefit to keeping the record accurate, not only an institutional one.
Self-deposit workflow design: minimizing friction
Adoption research on institutional systems consistently points to friction, not attitude, as the largest driver of non-use: a workflow that takes ten clicks and three logins gets abandoned regardless of how well the launch communication was written. Concrete friction-reduction steps for a RIM self-deposit workflow include:
- Single sign-on so faculty aren’t maintaining a separate login for the CRIS alongside every other institutional system.
- ORCID integration for authentication and for pulling a researcher’s existing works list, rather than asking them to search and claim publications one at a time from a blank profile.
- A claiming/deduplication interface that surfaces likely matches for confirmation (yes/no) rather than requiring free-text search and manual record creation for every publication.
- A short list of mandatory fields at first deposit, with optional enrichment (grant linkage, dataset relationships, keywords) left for later rather than gating an initial deposit behind every field the reporting team would eventually like to have.
- Mobile- or email-triggered light-touch review (“confirm these three imported publications are yours”) instead of requiring faculty to log into the full system interface for routine confirmations.
Common resistance points and how to address each
| Resistance point | What it sounds like | How to address it |
|---|---|---|
| Perceived surveillance | “This is just a tool for administration to monitor my output.” | Lead faculty-facing communication with personal benefit (time saved, a public profile, a CV export), not institutional reporting; be transparent about what data feeds external reports and who can see what. |
| Unclear WIIFM (what’s in it for me) | “I already have a CV, why do I need to maintain this too?” | Make the CRIS profile feed the annual report/P&T dossier directly, so it replaces existing work rather than adding to it; demonstrate this concretely in training rather than asserting it will happen eventually. |
| Extra work / duplicate data entry | “I already entered this in the grants system / repository / my CV.” | Prioritize integration work (ORCID, HR feed, repository connection, existing grants system) before or alongside launch so faculty aren’t asked to re-key data that already exists somewhere in an institutional system. |
| Data quality and trust concerns | “The imported record has the wrong co-authors / wrong journal / duplicates.” | Budget real time for data cleanup before go-live rather than launching with visibly wrong imported data — researcher trust is hardest to rebuild in the first weeks after launch, when a wrong record is what everyone sees first. |
| No visible leadership priority | “Nobody above the research office actually cares whether I keep this updated.” | Secure and visibly communicate leadership sponsorship; where the institution ties CRIS data to P&T or annual review processes, that linkage itself signals priority more effectively than a policy memo. |
Rollout sequencing: pilot departments and champions
Change-management literature applied to institutional technology adoption (see Kotter’s “enlist volunteers” step above) consistently favors a phased rollout over an all-at-once, institution-wide launch:
- Pilot with a willing department or school first — ideally one with active research output and a chair or associate dean willing to champion the effort — rather than launching simultaneously across every unit regardless of readiness.
- Recruit departmental champions — faculty who use the system early, encounter and report friction, and can answer peer questions informally. A peer answering “does this actually save me time” carries more weight with resistant colleagues than a research-office training session.
- Fix friction surfaced in the pilot before broader rollout — workflow problems found with fifteen early users are dramatically cheaper to fix than the same problems discovered after a full-institution launch generates hundreds of support tickets at once.
- Sequence communication ahead of each wave — departments should hear from their own chair or associate dean that the rollout is coming and why, not learn about it from an unexpected system email.
Measuring adoption after go-live
Reinforcement (the “R” in ADKAR) requires knowing whether adoption is actually happening, not assuming it from the go-live date. Practical adoption metrics for a RIM rollout include: profile completion rate by department, self-deposit rate versus records requiring administrative entry, time from publication to record creation, the volume of researcher-initiated corrections (a proxy for both engagement and data quality), and login/usage frequency outside of mandated reporting windows. A rollout that only sees activity in the weeks before an annual report deadline is a rollout where the system hasn’t become part of ordinary faculty workflow — the goal Kotter’s model calls “instituting the change” — and is a signal to revisit incentive design and friction points rather than a one-time launch problem to be solved and left alone.
Frequently asked questions
Is faculty resistance to a new CRIS/RIM system normal?
Yes. Resistance to research information management systems is well documented in the higher-education library and research-administration literature, and it is rarely resolved by better initial training alone — it typically reflects unclear personal benefit, duplicate data entry, or distrust of imported data quality, each of which has a specific, addressable fix rather than requiring faculty attitudes to simply change on their own.
Should the library or the research office own faculty communication during a RIM rollout?
Both typically have a role, but the earlier either establishes a genuine seat at the project table, the more influence it has over how the system is designed and communicated. Research-library guidance on RIM implementation specifically notes that early involvement affects whether the library ends up in “a leadership and advocacy role” versus “a purely administrative role” after go-live — the same logic applies to any unit hoping to shape adoption rather than just execute launch logistics.
Does linking a CRIS to promotion and tenure review help or hurt adoption?
It generally helps adoption of the underlying data (faculty have a strong incentive to keep P&T-relevant records accurate) but requires care in framing: if the connection reads as “this is now being used to evaluate you more closely,” it can reinforce surveillance concerns rather than incentive alignment. Framing it as the system doing double duty — one record serving both the researcher’s own dossier and institutional reporting, rather than two separate processes — addresses the incentive without triggering the resistance point.
How long does it take faculty adoption to stabilize after a RIM go-live?
This varies by institution size, discipline mix, and how much of the record can be auto-populated versus manually entered, and there is no single verified industry-wide figure to cite. Institutions running phased, champion-supported rollouts with strong integration work (reducing manual entry) generally see adoption stabilize faster than those relying on a single mandatory launch-week push followed by no further reinforcement.
