Disclosure verification. Every disclosure. Evidence attached.
Disclosure Verification is the flagship capability. It reconciles what each researcher personally attested — biosketch, current and pending, training, appointments — against authoritative sources the researcher does not control, and turns the result into an evidence-graded certification-readiness view for your AOR.
What it produces
- An exception report per researcher, per certification cycle — with each exception carrying the source that generated it.
- A certification-readiness view for the AOR — verified items, open exceptions, and the documented resolution of each.
- An immutable evidence snapshot per certification, ready for sponsor audits, IG inquiries, or litigation defense.
What it verifies
Verification runs against the classes of information research security regulations now require institutions to certify:
- Publications and affiliations that corroborate — or contradict — the researcher's disclosure.
- Effort commitments and appointments across institutions.
- Funding and current-and-pending support, including foreign sources.
- Research security training status against the applicable window.
- Restricted-party and exclusion-list matches through Screening.
What it does not do
- It does not build profiles of your researchers. It verifies what each researcher attested — nothing more.
- It does not auto-adjudicate. AI accelerates reconciliation; your compliance officers review every exception before it becomes a determination.
- We deliberately do not publish the rules or thresholds by which evidence is graded. That is a design decision, not an omission — an evaluation methodology that is public is a methodology that can be gamed.
Nothing to rip out
Disclosure Verification runs on top of the disclosure system of record your institution already operates. It connects to authoritative external sources (ORCID, eRA Commons, sponsor data, U.S. government restricted-party lists) and to internal systems (HR/effort, training records) — and verifies what already flows through your workflow.
Frequently asked questions
How can verification surface something a researcher didn't disclose?
Because research leaves a public record. Publications carry affiliations and funding acknowledgments; ORCID carries appointments; sponsor and institutional systems carry awards, effort, and travel. When a disclosure is silent about something that record shows — a foreign affiliation on a paper's byline, a grant acknowledged in print — the mismatch surfaces as an exception, with the evidence attached. And where the record cannot answer, the platform reports "not verifiable" rather than assuming compliance. That fail-closed honesty is deliberate: an unverifiable claim is a finding, not a pass. The source set is designed to expand — additional scholarly and commercial intelligence sources can be incorporated as institutional partners require.
See verification on realistic examples.
A briefing walks through disclosure verification against a scoped researcher cohort — with your compliance context, in about 30 minutes.