Published Updated

A university approves an extension to a research award, but its institutional research view still shows the old project end date. The amendment is in the sponsored-programmes file; the researcher profile and project report have not caught up. Staff need to identify the approved change and confirm which system accepted it.
A research-administration application can work alongside a current research information system (CRIS). Start with the capabilities your institution already uses, then assign ownership of project facts, researcher relationships, documents and reporting. FormKiQ can manage the governed research file and its reviews while a connected CRIS maintains the agreed institutional views.
A CRIS connects information about research, including staff, organisations, funding and outputs. The euroCRIS overview describes its relationships with repositories, HR and other institutional systems. Research administration and research-information management can therefore overlap around the same people and projects.
Some products also provide grant workflows. For example, Elsevier documents Pure's Award Management module for the application-to-award lifecycle, alongside core research data, reporting and portal modules. Check the installed modules, document controls and workflows before deciding what to replace or connect. A separate document application needs a clear purpose in the institution's operating model.
FormKiQ fits when you want proposal, award, research-decision and reporting evidence together in a document-centred business application in your AWS environment. A CRIS can continue to support the institution's chosen research profiles, relationships, outputs and reports. Agree the boundary field by field, including any award-administration features retained in the CRIS.
| Information | Authoritative source | Information to connect |
|---|---|---|
| Person and affiliation | The institution's selected identity, HR or CRIS source. | Stable person and organisation references, with the role that applied to each approved submission. |
| Proposal and award | The chosen research-administration workflow and approved award records. | Submitted proposal, award terms and amendments linked to the agreed project fields. |
| Protocol and ethics decision | The responsible institutional or ethics process and its recorded decision. | Exact protocol revision, decision evidence and only the status information approved for the target view. |
| Research outputs and reporting | The designated CRIS, repository and reporting sources. | Output and project identifiers linked to the applicable funding and supporting documentation. |
| Closeout | The research office's reviewed closeout process. | Accepted reports and completion decisions connected to the final project status. |
Keep a stable project reference across the dossier, award and CRIS record. Match people through the institution's chosen identifiers rather than names alone. Record who owns each shared field, which approved change may update it, when the change takes effect and how a rejected update is resolved. A later affiliation change should preserve the participant role associated with the earlier submitted file.
A study can also depend on a separate data-access permit or agreement. Link the effective authority, approved dataset specification, authorised users and any conditions on released outputs to the project. An award or ethics approval does not replace that separate decision. If the dataset or permitted users change, preserve the amendment and its effective date; earlier results remain tied to the inputs and authority used at the time. The analytics environment retains its own controlled data and execution records, while the project file connects the relevant decisions and evidence.
Retain the reviewed documents, authority, effective change and affected project.
Map approved field changes and source references to the intended CRIS record.
Verify the receiving record and keep rejected, unresolved or corrected updates visible.
A proposed extension and an accepted amendment are different states. Retain both, and use the approval required by the institutional process before updating an authoritative end date or investigator relationship. When another system owns a decision, retain its returned evidence and reference rather than treating document upload as approval.
The integration guide describes stable identifiers, mapped source ownership, duplicate handling and reconciliation. If a CRIS update times out, inspect the intended record before repeating it. Check the approved source state before applying delayed updates so an older message cannot silently replace a newer accepted fact.
This fictional connected workflow extends RES-1042, the community-mobility study in the solution example. The research office receives a request for a no-cost extension and an additional co-investigator while the existing award terms remain recorded.
The administrator adds the request to the existing project dossier and identifies the affected award, proposed end date and participant. The accepted project facts remain distinguishable from the pending request.
The office records the sponsor and institutional decisions required for this amendment. The responsible ethics process determines whether its records or review need updating. The approved change remains linked to the applicable documents and protocol revision.
The institution matches the co-investigator to its existing person record and confirms the approved role. An unresolved match is assigned for correction before the integration creates or changes that relationship. Participation in the project does not itself grant access to restricted documents.
The configured integration sends the accepted end date, participant relationship and permitted evidence references. It records the target project identifier and update outcome. Restricted protocol content stays within its authorised document access path.
The owner checks that the CRIS accepted the amendment and that its project view shows the approved facts. The dossier preserves the earlier terms, request and decisions. Later reports and closeout follow the Research and Grant Administration workflow against the continuing project file.
Choose what each destination audience may see. An internal research-office record, a researcher profile and a public research portal can need different information. A permitted status summary can link to restricted evidence without distributing the underlying protocol, participant-related material or confidential correspondence to every viewer.
Confirm access at the document destination and review any fields exported to the CRIS or portal. Correcting a shared status does not automatically withdraw copies or metadata already exported elsewhere. Include correction, deletion, retention and access-change responsibilities in the agreed integration, while preserving required project history.
For a change to the study itself, the protocol-amendment guide follows an extra interview through ethics review, document release and the required participant transition. It preserves which approved documents governed earlier participation rather than substituting the newest consent form.
Choose the research workflows you need and the capabilities already in place. Where FormKiQ manages the project evidence, connect it to the agreed CRIS records through stable identities, approved changes and confirmed updates. Staff can then follow an institutional fact back to the documents and decision that support it.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.