Where you are

Trial horizon: Phase 2 reading out · End-of-Phase-2 meeting in ~4 months · Phase 3 start ~9 months · NDA a future milestone, not a near one.
Documents in flight now: Phase 2 CSRs, Phase 3 protocol, Investigator’s Brochure update, EOP2 briefing book, IND amendments.
Current state: small team, CRO-heavy · Veeva Vault (basics) · AI authoring pilot · Smartsheet + email for tracking.

Target operating model & build order

Principle: get the documents you’re writing today right, in a function that can scale — the submission is an output it produces much later, not the finish line we build toward.

1. Purpose

Define how regulatory documents are created, reviewed, approved, versioned and retired so that every document is uniquely identified, traceable and controlled.

2. Responsibilities

• Author — drafts and revises; applies the correct document type and metadata.
• Reviewer — confirms content and compliance; records review in the system.
• Approver — applies the Part 11 electronic signature; sets effective date.
• Quality — governs the procedure; audits the trail.

3. Procedure

1. Each document receives a unique ID per the taxonomy (Appendix A).
2. Draft → review cycle is captured with full audit trail.
3. Approval via 21 CFR Part 11 e-signature; effective date set on final approval.
4. Versioning: minor (x.1) for editorial, major (x.0) for content changes.
5. Superseded documents are retired, not deleted; retained per records policy.

Appendix A — Document taxonomy (excerpt)

Purpose — what this document is for

Frame your questions for the Agency and make the case that the proposed Phase 3 program is adequate. It’s a persuasive, data-grounded argument — not a data dump, and not a rehash of the protocol.

What must go in it

1. Product & regulatory background — mechanism, indication, development history, prior FDA interactions.
2. Summary of data to date — nonclinical and Phase 1/2 results that support the proposed program.
3. Proposed Phase 3 design & rationale — endpoints, population, comparator, statistical plan.
4. Specific questions for the Agency — each one answerable yes/no or with concrete guidance.
5. Benefit-risk & open issues — what you already know the reviewer will ask.

How to write it well

• Lead with the questions — the reviewer reads to answer them, so make them findable and precise.
• Every claim traceable to a specific study, table or prior correspondence — derive it, don’t restate it.
• Numbers are consistent across the briefing book, the protocol and the CSRs — one source of truth.
• Anticipate the pushback and address it in the text, don’t wait for the meeting.

Common pitfalls

✗ Vague questions the Agency can’t answer  ·  ✗ efficacy claims not tied to a result  ·  ✗ numbers that disagree between sections.

Derive from (don’t retype): Phase 2 CSRs · Phase 3 protocol synopsis · Investigator’s Brochure · prior FDA meeting minutes. Review criteria: traceability · clarity of the ask · internal consistency.

Documents & status

Authoring & handoff checklist

• ✓ Each document follows the content template & standard
• ✓ Claims traced to a source study / table
• ✓ Naming matches the taxonomy; delivered PDF/A, text-searchable
• □ Numbers reconciled across documents (one source of truth)
• □ Review & approvals captured in eDMS with audit trail

Status key: ✓ Met · ◐ In progress · ◐ Gap — each gap maps to a remediation step in the blueprint.

Summary

0 errors  ·  2 warnings  ·  result: PASS (submission-ready)

The filing is a long way off — but the content you author today validates clean because it was written to standard from the start. That’s the point of getting the documents right early.

“Ready” isn’t a submission out the door — it’s every dimension at a level where the documents you write are right, defensible, and scale with the pipeline. The blueprint sequences the moves from now to target.