LeapYear
Afore CapitalGreenlight turns each protocol into site-specific startup requirements, validates submitted regulatory documents — identity, version, credentials, signatures — and gives sponsors a live command center for activation risk across every site.
Institution names describe prior team experience only. No endorsement or affiliation implied.
Most startup teams know whether a document was uploaded. Far fewer know whether it is complete, current, consistent, accepted, and activation-ready.
That gap is where weeks of slip accumulate. Greenlight closes it.
One pipeline. Site-specific requirements at the front. Evidence-backed readiness at the back. A sponsor command center over the whole thing.
Greenlight reads your protocol and resolves a curated regulatory-template library into the exact requirement set for each site, each IRB, and each person — PI, sub-I, coordinator. No template fishing, no missed forms.
Sites upload through a tokenized link — no login. AI plus deterministic checks reconcile identity across forms, catch protocol-version mismatches, and flag credentials expiring before target-ready. Every finding cites a document, page, and field.
A live readiness rollup per site: days-to-ready, open findings, projected activation cut vs. baseline, and a stall score that predicts which sites are about to slip. IRB packets assemble on demand for WCG, Advarra, and local.
Every finding carries a document, page, and field citation, plus a severity and confidence. Findings are discrepancies, never auto-fixes — an explicit human disposition writes its own audit event.
PI identity mismatch across 1572, CV, license, personnel
evidence ·1572 § 1 vs CV header · p. 1
Protocol version inconsistency across signed documents
evidence ·Site signature dated against v3 · current v4
Credential expires before site target-ready date
evidence ·PI license expires 2026-08-12 · target 2026-09-30
Signature missing or signed date invalid
evidence ·1572 § 8 · signature absent
ICF requirement has no accepted document (blocks IRB)
evidence ·ICF v4 uploaded · not yet accepted
Required document uploaded but not yet accepted
evidence ·Financial disclosure · proposed, awaiting review
Greenlight replaces spreadsheet tracking and inbox chasing with evidence-based readiness — across every site, on every day.
Move from “site selected” to “ready to enroll” with fewer review cycles. The dashboard tracks activation cut vs. baseline per site.
Validation surfaces only the discrepancies that actually need a human decision. Your CTAs review findings, not full packets.
Identity, version, credential, and signature checks fire the moment a document lands — not at the IRB or sponsor QC.
See the same readiness picture your CRO sees, evidence and all. Quality conversations move from anecdote to artifact.
Every status — Ready, At Risk, Blocked — points to a specific document, page, and field. Nothing is opinion.
Each site carries a stall score derived from missing docs, open blockers, overdue requirements, and chase history. You see slip risk before it hits.
Greenlight is PHI-free by structural design, with immutable document versions, a hash-chained audit history, and per-tenant isolation enforced at the database row.
Greenlight tracks regulatory evidence — FDA forms, IRB approvals, CLIA/CAP, credentials, signed protocols — never patient data. PHI-free is a structural boundary, not policy.
document_versions are immutable from insert. A current-version pointer tracks the latest approved release; the full lineage stays queryable for audit.
Every action — human or agent — appends to a per-tenant contiguous sequence with a SHA-256 prev-hash chain. The chain cannot be silently rewritten.
Row-level security keyed on a JWT tenant claim, backed by same-tenant composite foreign keys so cross-tenant joins fail even from service-role code.
Early access is open to a small cohort of sponsor clinical-operations teams. Tell us about your active studies and we’ll be in touch within 48 hours.