Research Compliance Orchestration Built to Keep IRB, Ethics, and Export Control on One Protocol Record
A protocol moves from submission through risk assessment, conditional approval, amendments, and continuing review, with the record staying current for as long as the study runs, not just at initial approval, so a later year still matches what an earlier one described.
Trusted by energy operators worldwide
The amendment that outran the original approval
A protocol amendment changes one data-collection procedure, and from that point the original IRB approval no longer fully covers what the study is doing until continuing review catches up. A study running for three years on an approval describing what it did in year one is a finding waiting to happen, whether it surfaces in a routine audit or a for-cause review.
Research Compliance Orchestration tracks a protocol, human subjects, animal ethics, or export control, from submission through risk assessment, conditional approval, every amendment, and the continuing review that keeps the approval current. A protocol enters the queue with its risk category and required reviewers attached, is assessed against the applicable standard, and can be approved outright or with conditions that stay tracked rather than noted once and forgotten.
A change to an approved protocol is submitted as an amendment and reviewed before it takes effect, keeping the approval current instead of trailing behind the study, and every submission, review, condition, and amendment stays attached for as long as the study runs, so year three is still covered by an approval matching current procedures.
What breaks when protocol compliance runs on a shared drive and a spreadsheet
Amendments drift from the approval on file
A changed procedure gets used in practice before the amendment that covers it is actually approved.
Continuing review dates get missed
A protocol's required annual or periodic review comes and goes without anyone flagging it in time.
Conditions attached to an approval get lost
An approval granted with conditions has no reliable way to confirm those conditions were actually met.
No single record across IRB, ethics, and export control
A study that touches more than one compliance area gets tracked in separate places that do not talk to each other.
Six modules. Built to keep an approval current for as long as the study runs.
Every module ships with default forms, routing, and dashboards. Configure each one to match your protocol review process.
Protocol submission
A new protocol, human subjects, animal ethics, or export control, enters the queue with its risk category and required reviewers.
Review and risk assessment
A protocol is assessed against the applicable standard, human subjects, animal ethics, or export control, with reviewer notes on the record.
Approval with conditions
A protocol can be approved outright or with specific conditions, and those conditions stay tracked on the record.
Amendment tracking
A change to an approved protocol is submitted as an amendment and reviewed before it takes effect, keeping the approval current.
Continuing review scheduling
A protocol's required continuing review date is tracked automatically and escalates as it nears, instead of relying on a calendar reminder.
Full protocol history
Every submission, review, condition, and amendment stays attached to the protocol for as long as the study runs.
From request to system of record in four steps
Submit
A new protocol enters the queue with its risk category, IRB, ethics, or export control, and the reviewers it requires.
Review
The protocol is reviewed against its risk category, with any amendment to an approved protocol routed through the same review before it takes effect.
Approve
The decision is recorded as approved outright, approved with conditions, or returned for revision.
Record
The protocol's periodic continuing-review date is tracked and escalates automatically as the deadline approaches, keeping the record current.
What changes when protocol compliance runs on Kissflow
| Process | Before Kissflow | On Kissflow |
|---|---|---|
| Protocol submission | Email or a paper form | One intake queue by compliance area |
| Amendments | Used in practice before formal approval | Reviewed and approved before taking effect |
| Conditions on approval | Tracked informally, if at all | Attached to the record and monitored |
| Continuing review | Missed or caught late | Scheduled with automatic escalation |
| Cross-area visibility | IRB, ethics, and export control tracked separately | One protocol record across all three |
| Sponsor or audit questions | Reconstructed from files and memory | Full protocol history on demand |
Connects to your research systems; your IRB and export control systems of record stay authoritative
Kissflow does not replace a dedicated IRB or export control system of record where one exists. It is where a protocol's submission, review, conditions, amendments, and continuing review get orchestrated as one process, especially where those pieces currently live in separate places.
.svg){kind=logo}
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
Built to keep an approval current, not just granted once
Live in weeks
Protocol types, review routing, and continuing review schedules are configured in the visual builder, and the AI Builder can generate a starting workflow from a description of your compliance review process.
Amendments reviewed before they take effect
A changed procedure does not get used in practice ahead of the approval that covers it.
Continuing review that does not get missed
A protocol's required review date escalates automatically as it approaches.
Conditions that get tracked, not lost
An approval granted with conditions keeps those conditions visible and monitored on the record.
Role-based access
Investigators see their own protocols; compliance staff see the full review queue across IRB, ethics, and export control.
A history that survives a sponsor or audit question
Every submission, review, condition, and amendment stays attached to the protocol indefinitely.
Related apps
Grant Proposal Approval & Compliance Management System
Where a proposal checks whether its IRB or export control status is cleared before it can be submitted; see the FAQ for the difference.
Cross-Office Research Coordination Hub
Coordinates the department, sponsored programs, and this compliance review around a single award.
Student Grievance & Title IX Case Management
A different kind of case-managed compliance process, for conduct and complaints rather than research protocols.
We help research compliance offices keep a protocol approval current for as long as the study actually runs.
.gif)
“If a company cannot enable everybody to use AI, they will never get the true benefit of AI. Platforms like Kissflow allow us to put that capability in the hands of our users in a safe way.”
Vagesh Dave
GVP & CIO at McDermott International, Ltd
See The Full Story
“Advanced automation of all processes is easy to set up. I cannot imagine how to manage workflows without this software.”
Tanay Tiwary
Global Head - Digitalization & Business Improvement
See the Full Story
“Kissflow supports rapid application development by building a working application prototype in the shortest amount of time.”
Maria Theresa Cabigon
CIO, SN Aboitiz Power Group
See The Full Story
See what Kissflow can do for you
Talk to usGot questions? We're here to help.
Get SupportNot necessarily. Where a dedicated system of record already exists, this app can orchestrate the process around it, submission, review, amendments, and continuing review, especially where those steps currently live in separate places.
Grant Proposal Approval & Compliance Management System routes a research proposal through the sign-offs, including a check that IRB or export control status is cleared, before it goes to a sponsor. This app is where that IRB, ethics, or export control review actually happens: protocol submission, risk assessment, approval with conditions, amendments, and the continuing review that keeps the approval current for as long as the study runs.
The change is submitted as an amendment and reviewed before it takes effect, so the approval on file always matches what the study is actually doing.
A condition attached to an approval, an additional consent step or a data security requirement, stays visible on the protocol record until it is confirmed met.
Yes. Protocol types, review routing, and continuing review schedules are configured in the visual builder, and the AI Builder can generate a starting workflow from a description of your compliance review process.
Access is role-based. Investigators see their own protocols; compliance staff see the full review queue across IRB, ethics, and export control.
Configuration and AI-assisted setup typically move initial rollout to weeks, not a multi-month systems project.
Kissflow is certified to SOC 1, SOC 2, SOC 3, and ISO/IEC 27001, supports HECVAT review, and is built to support FERPA and GLBA Safeguards obligations, with data residency options in the US, EU, APAC, and Oceania.
