These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Research Management System
- Implementation and migration
How a Research Management System rollout works
Pilot one funded program and trace its work, evidence and research outputs.
Agree the program boundary
Choose one funded program, its owner, period and budget. Name the award reviewer and the person responsible for expense and outcome evidence.
Map existing identities
Match People to Users, projects to protocol references, outputs to external identifiers and every child record to its program or measure.
Configure the pilot
Load an award with restrictions, an assigned activity, a milestone, a measure, a research project and an output. Define the status handoffs with the team.
Rehearse decisions
Review a proposed award, a supported claim, an unsupported claim and a period result. Check the evidence and the person who decides.
Reconcile and release
Compare awards, expense amounts, outcome periods and output identifiers with their source. Obtain the program and finance owners' acceptance before expanding.
What the customer provides
- Program owners, planned periods, budgets and current statuses.
- Award documents with funder, amount, date and restrictions.
- Staff identity, project protocol references and output identifiers.
- Expense categories, evidence sources, outcome definitions and reporting periods.
Changing it afterwards
Review a changed award restriction with the Reviewer before applying it to later expense decisions. Check the impact of changing a measure definition on prior results. Rehearse duplicate protocol and output identifiers before importing another batch. Keep the original source evidence available during correction.
Set up Research Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.