What Does a Conditional Approval Require?
A late report. Conflicting numbers. A safety signal that pauses the work. Regulated Gate Decision Support asks how those findings should change permission to proceed.
From the research of Mark Julius Banasihan
Essay draft · Based on practitioner accounts in Syner-G’s IND webinar. Timestamps refer to the supplied automated transcript; accounts are paraphrased. The RGDS example is separate and illustrative.
A report is marked final. A medical writer checks its synopsis against the data inside and finds that the concentrations disagree. The document is ready to be used, yet one of its numbers needs an answer.
In Syner-G’s Navigating Successful IND Submissions, medical writer Kasturi Puram recounts encountering this kind of inconsistency in source reports (38:51). She describes asking the team to confirm the correct value, even when the appendix gave her a reason to suspect which one it was. The account identifies a moment of scrutiny. It leaves the subsequent correction and submission outcome unspecified.
The word “final” makes a document easier to accept. A visible contradiction gives the reader a reason to stop. Whether that interruption protects the work depends on what happens next: someone must resolve the discrepancy, examine its implications and carry the correction into the documents that relied on it.
This is the problem Regulated Gate Decision Support addresses. Permission to proceed can depend on evidence that is incomplete, disputed or still changing. The institution needs to preserve both the permission and the conditions that give it meaning. A person finding a problem must also have a route to change what follows.
The last report changes the work
An Investigational New Drug application, or IND, brings together evidence for a proposed clinical investigation. FDA’s overview of the application describes its nonclinical safety evidence, manufacturing information and clinical protocols. For the people who may enter a study, errors in that connected account can matter beyond the document where they first appear.
Puram describes drafting with placeholders while reports are still arriving, then carrying information between summaries, the investigator’s brochure and the protocol (07:38). This lets useful work proceed before every source is final. It also creates a dependency: when the source changes, the people preparing each dependent document need to know.
The deadline can obscure that dependency. Discussing a pivotal toxicology report expected only four days before a planned submission, regulatory specialist Drew Barlow says the team would challenge whether the timetable was realistic (43:43). He distinguishes that situation from a late manufacturing or stability data point. These are planning examples, with timing dependent on the evidence and program; they provide no universal turnaround promise.
A team leader can ask which work may continue while that report is pending and which decision must wait. Those permissions can differ. Drafting a section, finalizing its account of the evidence, submitting an application and beginning a study are separate actions. An internal approval should state the action it authorizes; regulatory requirements remain separate.
Regulated Gate Decision Support records a phase-gate decision: a point where an authorized team decides whether work can proceed, must stop or needs more evidence. Its reference implementation preserves the question, alternatives, evidence gaps, accepted risks, responsible people and follow-up obligations. Applied to the scheduling problem, it would ask what the pending report could change and who must examine it before the next action is authorized.
A reason to reopen the decision
Puram also recalls a project where a signal in a dog toxicology study led the team to pause IND writing and seek clarification through a pre-IND interaction. A briefing document was prepared, and the resulting input was incorporated into the IND (47:49). The transcript does not identify the compound, the signal or the eventual regulatory outcome.
Here, an emerging concern changed the course of the work. To reconstruct that decision, a later reviewer would need more than the revised schedule: what prompted the pause, who authorized it, what question required clarification and what the response changed. The webinar supplies a practitioner’s account of the intervention. It is not a record of RGDS use.
The same discipline applies outside drug development. A supplier check may uncover a discrepancy, or a late test may alter a planned software release. A condition has practical force when the person responsible for the next action can withhold permission and knows what evidence would justify reconsideration.
The repository’s AI-assisted readiness example describes a decision about a non-clinical evidence package for an Investigational New Drug submission. A toxicity report awaits final sign-off, and longer-duration stability data is pending. The authored record chooses a conditional go. It is an illustration of the record structure, not evidence that an actual submission could appropriately proceed on these terms.
Two obligations make the choice more specific. A scientific adequacy owner must provide the final signed toxicity report before filing. A manufacturing and stability readiness owner must supply the longer-duration dataset and update the dependent summaries and tables. Each condition identifies an owner, a due date and the evidence needed to close it.
Both follow-up actions remain marked open in the example. That matters more than the reassuring presence of a recorded approval. The record tells a reviewer what is still owed; it does not establish that either obligation was fulfilled. Its historical example dates likewise do not turn those entries into current operational deadlines.
The example also preserves an assumption: the audited draft report will not change materially when signed. Puram’s account of inconsistent numbers shows why final status alone cannot settle that question. The comparison is this essay’s analysis; the authored RGDS example is separate from the webinar accounts. A reviewer would still need to examine changes and decide whether the original rationale holds.
The difference between a condition and a task is consequential. A task asks someone to do something. A condition defines what permission depends on. If the two are treated interchangeably, a workflow can continue while the condition sits on a task list. A record needs to make their relationship legible to the person who controls the next action.
Reading the illustrative record
Permission recorded.
Conditions still open.
A conditional go
The example records human approval subject to two obligations.
Evidence to close
A signed report and additional stability data, with dependent records updated.
Judgment still required
A changed report may require reconsidering the original rationale.
Outcome unestablished
Both follow-up actions remain open. Completion is not demonstrated.
A valid record is a start
The decision-log schema checks whether information has the required form. Additional semantic checks examine selected relationships between fields. For example, a conditional go needs conditions, and disclosed AI use requires review information under the implementation’s rules. These checks can expose omissions that a reader might otherwise miss.
The documented local review reports that all six illustrative records passed strict validation and all nine regression tests passed. Additional checks found that removing conditions or human-review information from the AI-assisted example could pass structural validation while failing the additional semantic checks. The validation mode therefore changes what a pass establishes.
Those results concern the representation of a decision. A field containing a person’s name cannot authenticate their participation. A complete-looking evidence reference cannot establish the quality of the source. Even a record that passes all configured checks may rest on an unsupported assumption or describe an action that never occurred.
This boundary makes the validator useful without asking it to do the reviewer’s work. Software can check that a closure requirement is present. A qualified person must determine whether the supplied evidence meets it. The institution must then ensure that this determination reaches the process whose permission depends on it. These are connected responsibilities, each requiring its own evidence.
Assistance without transferred authority
The AI assistance policy permits bounded work such as drafting, comparison and extraction, while reserving decisions, approval and risk acceptance to people. Regulated Gate Decision Support can also be used without AI. When AI contributes, the record is meant to identify the contribution and its review rather than let generated prose disappear into the institution’s account.
Consider an AI assistant summarizing the kind of report Puram describes. This extension is hypothetical; her account does not attribute the discrepancy to AI. A model could carry one conflicting value into a fluent summary without making the disagreement visible. The reviewer would need the source passages, the authority to reject the summary and a way to prevent dependent drafts from continuing to use it. Recording that someone reviewed the output would leave those practical questions unanswered.
The related AI Assistance Governance work asks whether material decision claims can be reconstructed from inspectable non-AI sources. Its assessment distinguishes checking the record’s structure from examining the substantive basis for its reasoning. Keeping those questions separate prevents a technically valid document from being mistaken for an independently supported decision.
Preserving that distinction also means preserving history. Reassessing a decision without relying on model output should not erase the fact that AI contributed to the original process. The original disclosure, the reviewer’s changes and the sources supporting the final rationale each tell a different part of the story.
A projection is an invitation to test
The Regulated Gate Decision Support independent study explores ten questions about decision reconstruction, AI accountability, implementation and possible institutional benefits. It provides the earlier research context for the work, including literature synthesis and modeled scenarios. “Independent study” identifies the author’s research; it does not establish independent validation of the implementation.
Its quantitative projections need to be read on that basis. One scenario compares a 45-day decision cycle with a proposed 22-day cycle across fifteen decisions. The arithmetic gives 345 summed decision-days. It does not show that a program finished 345 calendar days earlier. Decisions may overlap, waiting time may differ from staff effort, and a faster decision may leave the overall completion date unchanged.
The study also discusses financial value and possible regulatory developments. Those estimates and forecasts should remain distinguishable from observed outcomes and current requirements. The current reference implementation does not establish savings, reduced deficiencies or regulator acceptance. Linking the study makes its assumptions available for examination without importing every projection as a result.
The core evaluation plan is explicitly prospective. It asks whether the approach improves decision readiness, retrieval, evidence quality and governance execution. A useful study could compare how accurately reviewers reconstruct matched decisions with and without the structured records, recording omissions, disagreement and time. Speed would matter alongside accuracy, not as a substitute for it.
A separate inquiry would need to follow conditions into operations. Did a hold prevent the next action? Did the responsible person receive the evidence in time? Was an adverse finding allowed to change the decision? A record that is easy to retrieve could still describe a process in which nobody had practical power to intervene.
The approval must remain answerable
Return to the inconsistent report. Puram describes recognizing the discrepancy and asking for confirmation. Following that concern through an institution would require evidence of the answer, the corrected source and the judgment about its consequences. A revised number might leave a decision intact or change its basis. The record should let a later reviewer distinguish those possibilities.
If work has already proceeded, the inquiry extends downstream. Which documents relied on the old finding? Which teams received the earlier permission? What can be corrected, and what consequence remains? Closing the original task cannot establish that dependent records and actions were corrected with it. Evidence of delivery, revision and execution is needed to trace that propagation.
These are conditions to examine in future use, not accomplishments demonstrated by the example set. The reviewed core release is v2.0.1; the earlier study identifies itself separately as v1.4. The schema, participation profile and study retain their own versions and evidence boundaries. Their relationship gives readers several ways to inspect the proposal without collapsing them into one claim of effectiveness.
An institution does not finish its responsibility when it records a conditional approval. It has made a commitment about what must happen next. Regulated Gate Decision Support gives that commitment a structure that others can examine. Whether it keeps its force depends on people being able to recognize a reason to pause, exercise authority and establish what changed as a result.