1.1.1 - Regulatory Operations Workflows and Accountability
0% read
Regulatory Operations Foundations
Regulatory operations workflows and accountability
Regulatory operations turns approved regulatory content into controlled, technically valid submissions and maintains the evidence showing what was submitted, when, and under whose authority. This lesson introduces the people, handoffs, deliverables, and accountability boundaries that make that process reliable.
What you will learn
Distinguish regulatory strategy, regulatory affairs, regulatory operations, medical writing, document management, publishing, quality control, dispatch, and correspondence responsibilities.
Trace a submission document from authoring through review, approval, controlled handoff, publishing, validation, transmission, acknowledgment, tracking, and archival.
Identify the operational records needed to demonstrate document readiness, submission completeness, and lifecycle traceability.
Recognize when an entry-level associate should execute an approved instruction, hold a workflow, or escalate a decision.
Build a responsibility matrix assigning ownership, review, publishing, independent quality control, and authorized release decisions.
Blueprint mapping: Regulatory Operations Foundations - Teams and Submission Scope - Regulatory Operations Workflows and Accountability. Weight: not specified.
Estimated study time: 20-25 minutes.
PREREQS None.
OUTPUTS Choose the correct responsible role, reconstruct a controlled submission workflow, complete a responsibility matrix, and determine when a submission must be held or escalated.
WHY
Why it matters
A technically well-formed electronic submission can still contain the wrong document version, missing approvals, or inconsistent application metadata. Regulatory operations controls these preventable operational failures.
FDA electronic submission requirements apply to covered regulatory submissions. They do not independently require an individual to earn this certificate.
As of November 1, 2026, supported eCTD standards, validation expectations, and eCTD v4.0 transition planning make reliable handoffs and traceability essential operational skills.
The most important accountability distinction is between preparing and releasing submission materials and deciding their scientific, regulatory, or legal acceptability.
The big idea: Regulatory operations manages the controlled execution and evidence of a submission. The sponsor remains responsible for its regulatory obligations, authorized decisions, and submitted content.
KEY TERMS
Key Terms & Must-Know Facts
Regulatory strategy
The planned regulatory approach for a product, application, or activity, determined by authorized regulatory decision-makers.
Regulatory affairs
The function coordinating regulatory interpretation, submission requirements, regulatory commitments, and interactions with health authorities.
Regulatory operations
The function organizing submission plans, controlled content, publishing activities, delivery, acknowledgments, reconciliation, and records.
Medical or technical writing
The preparation and revision of scientific, clinical, quality, or regulatory source content under designated author and reviewer responsibilities.
Document management
The governance of document identifiers, versions, statuses, controlled copies, access, and approved source records.
eCTD publishing
The technical assembly of approved documents and metadata into the supported electronic Common Technical Document submission structure.
Quality control (QC)
A defined inspection against acceptance criteria, including document, metadata, lifecycle, or package checks.
Technical validation
The evaluation of an electronic submission package against applicable machine-readable and technical acceptance rules.
Dispatch
Authorized transmission of a prepared submission through an applicable FDA-supported electronic delivery process.
Acknowledgment
A response or status artifact associated with electronic transmission or agency processing; different acknowledgments communicate different states.
Regulatory information management (RIM)
The organized maintenance of regulatory application, submission, commitment, status, and planning information.
Responsibility matrix
A role assignment tool showing who prepares, reviews, approves, checks, releases, or tracks specified work.
Audit trail
A controlled history of relevant record events, maintained according to applicable electronic-record and organizational requirements.
Submission archive
The controlled retained record of submitted content, associated metadata, transmission evidence, and related operational documentation.
1.1.1.1 Must-know facts
Regulatory operations does not independently approve scientific conclusions, select a legally required submission category, or make sponsor-level regulatory commitments.
Every submission document needs an identifiable owner, controlled version, status, and intended placement or purpose.
A passed technical validation does not establish scientific approval or prove that all business-process controls were satisfied.
Independent QC and authorized release approval are distinct actions even when an organization combines some administrative roles.
A transmission attempt is not equivalent to documented agency receipt or acceptance.
IND regulatory serial numbering and eCTD sequence numbering are separate identifiers.
When information is incomplete or contradictory, the associate should preserve the evidence, hold the affected action where required, and escalate through the defined process.
Applicable FDA standards and organizational procedures determine detailed execution; regional workflows should not be assumed interchangeable.
CORE
Core content
1.1.1.2 1. Who owns each part of a submission?
A Explanation: execution versus decision authority
WHY THIS IS TESTED: Entry-level associates routinely receive requests from people who contribute to the same dossier but hold different authority. The correct next step depends on the decision being requested, not on job seniority alone.
Choose regulatory operations for execution activities such as inventory maintenance, controlled handoffs, metadata coordination, publishing, and tracking. Choose the designated regulatory decision-maker for classification, interpretation, strategy, and commitments. Choose the responsible content owner and authorized reviewers for scientific revisions and approval.
Roles may overlap in small organizations, but accountability cannot be assumed from access to a software system. A person who can upload or publish a file is not automatically authorized to approve it. See Fig 1.
Identify the requested action.
Determine whether the action is content creation, regulatory decision, operational execution, or approval.
Match the action to the designated accountable role.
Check documented delegation or authorization.
Execute within authority or escalate before proceeding.
Fig 1. Functional ownership of a submission Exam takeaway: Regulatory operations coordinates execution without inheriting scientific or sponsor-level decision authority.
flowchart TD
A[Submission requirement] --> B[Regulatory affairs and strategy]
B --> C[Content owners and writers]
C --> D[Authorized scientific review]
D --> E[Document control and regulatory operations]
E --> F[Publishing and technical QC]
F --> G[Authorized release and dispatch]
G --> H[Acknowledgment tracking and archive]
Inspect against defined technical and operational criteria.
A QC pass is not final release authorization.
Authorized release decision-maker
Approve package release under the organization's process.
Authorization must be documented.
Dispatch and tracking
Transmit, monitor responses, and reconcile status.
Unexpected failures require escalation.
Functional responsibility cards Exam takeaway: Identify the nature of the decision before assigning the person responsible.
{"prompt":"Square professional regulatory-operations educational illustration on a white background, cool blue-gray palette with amber accent. Show four aligned labeled workstations: Regulatory Affairs with an application strategy document, Content Owner with a reviewed report, Publishing Associate with an eCTD package tree, and Authorized Release with a signed checklist. Clear boundaries and short arrows between roles; flat vector, legible labels, no real company logos.","caption":"Functional responsibility cards","size":"1024x1024"}
B Worked example: a request to change a submission type
A 46-year-old regulatory operations associate coordinates an NDA submission for a product intended for adults with diabetes and hypertension. During preparation, a writer requests that the package be labeled as a different postapproval submission category because the document is short. The writer also mentions that a previous version received no major technical errors.
Identify the task: Determine who can approve changing submission classification.
Extract key facts: The classification is being changed based on document length, not on an authorized regulatory determination.
Apply the rule: Regulatory classification belongs to the designated regulatory authority within the sponsor's process.
Eliminate distractors: A short document and previous technical validation do not establish the correct reporting pathway.
Verify: Record the requested change, obtain regulatory confirmation, and update publishing instructions only after the decision is authorized.
C Common decision trap
Tempting wrong action: Let the publishing associate change the submission category because the associate manages the package metadata. Why tempting: The category appears in the publishing workflow. Eliminating clue: The request changes a regulatory determination, rather than merely correcting an approved metadata entry.
D Checkpoint
Question: Who should resolve an unapproved change in the regulatory classification of a postapproval submission?
A. Publishing associate
B. Document control coordinator
C. Designated regulatory affairs decision-maker
D. Independent technical QC reviewer
Answer: C. A is tempting because publishing applies the classification, but does not authorize it. B is tempting because document control manages approved versions, but does not determine regulatory pathways. C is correct because the classification requires authorized regulatory judgment. D is tempting because QC detects inconsistencies, but QC cannot independently approve a new regulatory classification.
If you missed this: Review Who owns each part of a submission? - focus on the distinction between executing metadata instructions and authorizing regulatory classifications.
1.1.1.3 2. Following a document through the controlled workflow
A Explanation: ready for publishing versus ready for release
WHY THIS IS TESTED: A document may be approved for publishing while the overall submission remains incomplete. Conversely, a technically valid package may still be awaiting release approval or a required reconciliation.
A controlled submission has multiple gates. Source readiness establishes that a document is approved and identifiable. Publishing readiness establishes that the correct document, placement instructions, and metadata are available. Technical readiness establishes that package checks have passed. Release readiness establishes that an authorized person has approved transmission. Dispatch and subsequent acknowledgments provide separate evidence of delivery and processing.
Each handoff should have a documented status, owner, and outcome. See Fig 2.
Author and review source content.
Approve the controlled document and record its identity.
Handoff to publishing with approved placement instructions.
Build and independently check the package.
Obtain authorized release and transmit.
Track acknowledgments, reconcile records, and archive.
Fig 2. Controlled submission document lifecycle Exam takeaway: Approval, technical validation, transmission, and acknowledgment are distinct workflow milestones.
flowchart LR
A[Authoring] --> B[Scientific review]
B --> C[Approved source]
C --> D[Controlled handoff]
D --> E[Publishing]
E --> F[Technical validation and QC]
F --> G[Release approval]
G --> H[Transmission]
H --> I[Acknowledgments]
I --> J[Reconciliation and archive]
Table 2. Evidence expected at controlled workflow gates
Controlled handoff evidence Exam takeaway: The transferred file must agree with its approved document record and destination instructions.
{"prompt":"Square clean educational regulatory publishing illustration. Side-by-side panels titled CONTROLLED HANDOFF and UNCONTROLLED HANDOFF. Left shows approved document version 3, matching inventory version 3, green consistent status indicators and a publisher receiving the approved package. Right shows document version 2, inventory version 3, amber mismatch and a HOLD marker. White background, blue-gray vector icons, concise accurate labels, no branding.","caption":"Controlled handoff evidence","size":"1024x1024"}
Handoff discrepancy decision Exam takeaway: A mismatched source version is resolved through controlled correction before publishing proceeds.
flowchart TD
A[Receive source package] --> B{File matches approved inventory?}
B -->|Yes| C[Record receipt and publish]
B -->|No| D[Place affected file on hold]
D --> E[Contact document owner]
E --> F[Receive approved correction]
F --> B
B Worked example: an approved PDF with a conflicting version
A submission for a product studied in adults aged 58 to 76 includes clinical reports describing diabetes, kidney disease, and hypertension. The controlled document system lists a clinical report as approved version 4. A publishing folder contains version 3, labeled final. A separate project email notes that the study completed on schedule.
Identify the task: Decide whether the PDF is ready for publishing.
Extract key facts: The document version conflicts with the approved record.
Apply the rule: Publishing requires the controlled, authorized source.
Eliminate distractors: A final filename and favorable project status do not establish source approval.
Verify: Hold the affected item, request the correct approved file, compare identifiers, and record resolution.
C Common decision trap
Tempting wrong action: Publish version 3 because it is labeled final. Why tempting: File labels suggest readiness. Eliminating clue: The authoritative controlled record identifies version 4 as approved.
D Checkpoint
Question: An approved inventory shows version 5, but the publishing folder contains version 4. What is the most appropriate next step?
A. Publish version 4 and flag the discrepancy afterward.
B. Rename version 4 as version 5.
C. Confirm the correct source with the document owner and update the controlled handoff.
D. Use version 4 if technical validation passes.
Answer: C. A is tempting because it preserves the deadline, but knowingly introduces a version mismatch. B is tempting because the visible labels would align, but renaming does not change document approval. C is correct because the underlying controlled source must be reconciled. D is tempting because technical validation is a formal gate, but it cannot verify scientific approval status by itself.
If you missed this: Review Following a document through the controlled workflow - focus on controlled source identity before technical package validation.
Quick Recall:
True or false: An associate who can publish a document is automatically authorized to approve its regulatory classification. False.
Fill in the blank: An approved document version must match the controlled document _____. Record or inventory.
Question: Does successful technical validation equal authorization to dispatch? No.
1.1.1.4 3. Operational deliverables, metadata, and reconciliation
A Explanation: package completeness versus recorded completeness
WHY THIS IS TESTED: Regulatory operations associates are often responsible for demonstrating what was expected, what was actually packaged, which issues remain, and whether the submission record agrees with delivered materials.
Start with an approved submission plan. Use a document inventory to identify content and status, metadata records to identify application and sequence information, PDF inspection logs to record file checks, submission checklists to record readiness, and issue logs to manage deviations. Reconciliation compares controlled expectations with actual outputs rather than relying on memory or package filenames.
Common inventory fields include document identifier, document title, version, owner, approval status, planned CTD location, intended sequence, actual filename, handoff status, QC result, and disposition. The exact field names depend on the organization's systems.
Metadata must agree across source records, the approved submission plan, publishing instructions, and the final package. In particular, distinguish IND regulatory serial numbers under 21 CFR 312.23 from eCTD sequence numbers. The two serve different purposes. See Fig 3.
Read the approved submission plan and scope.
Build or update the controlled document inventory.
Check source identity, metadata, and planned placement.
Reconcile actual publishing outputs to expected content.
Log and resolve discrepancies with authorized owners.
Retain completion evidence and final records.
Fig 3. Submission reconciliation inputs Exam takeaway: A reconciled package requires agreement among approved scope, controlled sources, metadata, and published output.
flowchart TD
A[Approved submission plan] --> E[Reconciliation]
B[Controlled document inventory] --> E
C[Application and sequence metadata] --> E
D[Published package and QC results] --> E
E --> F{Consistent and complete?}
F -->|Yes| G[Release readiness evidence]
F -->|No| H[Issue log and corrective handoff]
H --> E
Track required content, ownership, versions, and status.
Does each required document have a controlled identity?
Metadata entry
Record approved application and sequence information.
Does metadata agree with authorized records?
PDF inspection record
Document checks of readability, navigation, hyperlinks, and file usability where applicable.
Was the actual deliverable inspected?
Submission checklist
Confirm completion of required workflow gates.
Are all applicable required checks complete?
Content reconciliation
Compare planned content with published content.
Is every difference explained and authorized?
Issue log
Track discrepancies, owners, actions, and closure evidence.
Can unresolved items be located and assessed?
Dispatch record
Preserve transmission details and references.
Can the sending event be traced?
Acknowledgment and archive record
Document processing status and retain the submission history.
Does the retained status match available agency evidence?
Document inventory anatomy Exam takeaway: Inventory records must distinguish planned content, approved source identity, and actual publishing status.
{"prompt":"Square educational vector infographic showing a simplified regulatory document inventory spreadsheet with six columns: Document ID, Version, Approval, CTD Placement, QC, Status. Three example rows: M1-001 v2 Approved Passed Ready; M3-014 v4 Approved Pending Hold; M5-021 v1 Draft Not started Blocked. Blue-gray professional palette, amber highlights on unresolved statuses, highly legible large text, white background, no logos.","caption":"Document inventory anatomy","size":"1024x1024"}
Two identifiers, two purposes Exam takeaway: The IND regulatory serial and eCTD sequence identifier must not be treated as interchangeable.
{"prompt":"Minimal square comparison diagram for FDA regulatory operations. Left blue card labeled IND REGULATORY SERIAL with example 000 and caption Regulatory numbering. Right blue card labeled eCTD SEQUENCE with example 0000 and caption Electronic submission sequence. Central separator marked DISTINCT IDENTIFIERS. Small note: Examples only; verify actual approved records. White background, clean vector style, cool blue gray and amber accent, no distracting objects.","caption":"Two identifiers, two purposes","size":"1024x1024"}
B Worked example: metadata conflict
A new IND submission involving adults with asthma, hypertension, and diabetes has an approved regulatory record showing IND regulatory serial 002. The publishing work order lists eCTD sequence 0007. A coordinator assumes both values should match because they describe the same submission. An unrelated source PDF has correctly functioning bookmarks.
Identify the task: Determine whether the two identifiers constitute an error.
Extract key facts: The values describe different numbering systems.
Apply the rule: Verify each against its own authoritative record and applicable specifications.
Eliminate distractors: Numerical inequality alone does not prove a mismatch, and PDF bookmarks do not determine sequence identity.
Verify: Reconcile the approved IND regulatory serial separately from the eCTD sequence designation and document any actual discrepancies.
C Common decision trap
Tempting wrong action: Change the eCTD sequence to match the IND regulatory serial. Why tempting: Both are numeric identifiers associated with the same application activity. Eliminating clue: They belong to separate regulatory and technical numbering systems.
D Checkpoint
Question: Which control most directly detects an omitted approved document before release?
A. Compare the approved submission inventory to the final published package.
B. Confirm the dispatch timestamp against the calendar.
C. Compare the IND regulatory serial to the eCTD sequence.
D. Verify the PDF has searchable text.
Answer: A. A is correct because expected-to-actual reconciliation detects missing items. B is tempting because transmission is an auditable event, but timing does not establish completeness. C is tempting because metadata consistency matters, but those identifiers are not a content-completeness control. D is tempting because readable PDFs are important, but PDF quality does not establish document inclusion.
If you missed this: Review Operational deliverables, metadata, and reconciliation - focus on comparing the approved inventory against actual published content.
1.1.1.5 4. Responsibility matrices, release authority, and escalation
A Explanation: who performs the task versus who accepts responsibility
WHY THIS IS TESTED: An associate must recognize that completing an assigned technical action does not confer approval authority. Ambiguous roles can allow missing reviews, unauthorized releases, or unresolved issues to move downstream.
A responsibility matrix assigns each workflow activity to its designated performer, reviewer or checker, accountable approver, and informed stakeholders. Organizations may use a RACI framework: Responsible performs the work; Accountable owns the decision or outcome; Consulted contributes input; Informed receives status. A RACI matrix supports role clarity but does not override legal sponsor obligations, required signatures, delegated approval limits, or established procedures.
For major release decisions, distinguish four questions: Is the source approved? Has independent QC been completed where required? Has an authorized person approved release? Is the dispatch operator using the approved package and destination? See Fig 4 and Fig 5.
Identify the workflow activity and its required outcome.
Assign the person performing the work.
Identify required reviewers and independent checks.
Identify the authorized accountable decision-maker.
Record approval and release evidence.
Escalate gaps in authority or unresolved blocking findings.
Fig 4. RACI responsibility matrix Exam takeaway: Performing an action and holding accountability for its approval are different responsibilities.
{"prompt":"Square regulatory operations teaching infographic showing a clean RACI matrix. Columns: Content Owner, Regulatory Affairs, Publishing, QC, Release Authority. Rows: Approve source, Confirm category, Assemble package, Check package, Authorize dispatch. Use example R, A, C, I letters only where illustrative, with footnote Organization-specific assignments vary. Blue-gray table, one amber highlighted accountable cell per row, white background, crisp accessible typography.","caption":"RACI responsibility matrix","size":"1024x1024"}
Fig 5. Release or hold decision Exam takeaway: Unresolved blocking defects or missing authorization require a controlled hold rather than an informal workaround.
{"prompt":"Square two-column operational decision infographic. Left panel labeled RELEASE shows approved sources, complete reconciliation, successful required QC and authorized signoff leading to a transmission icon. Right panel labeled HOLD shows unresolved source mismatch, blocking technical finding or missing authorization leading to issue logging and escalation. White background, cool-blue gray and amber, flat vector professional training style, very readable labels, no logos.","caption":"Release or hold decision","size":"1024x1024"}
Responsible regulatory or operations lead for unresolved status
Interpretation note: This matrix illustrates separation of responsibilities; the actual individual or position assigned to each role depends on sponsor governance, documented delegation, and organizational procedures.
Escalation and release gate Exam takeaway: A blocking finding should remain visible until authorized resolution and documented rechecking.
flowchart TD
A[Package ready for QC] --> B{Required checks complete?}
B -->|No| C[Log issue and hold]
C --> D[Assign resolution owner]
D --> E[Correct and recheck]
E --> B
B -->|Yes| F{Authorized release recorded?}
F -->|No| G[Request release decision]
F -->|Yes| H[Dispatch approved package]
B Worked example: pressure to release
A 39-year-old publishing associate is preparing an electronic submission containing reports from adults with hypertension and chronic kidney disease. Technical validation passes, but an independent QC reviewer reports that a required approved document is missing. The submission is scheduled for that afternoon, and a project manager asks for immediate dispatch because the application metadata is correct.
Identify the task: Determine whether dispatch can proceed.
Extract key facts: A required approved document is missing and the QC finding remains unresolved.
Apply the rule: Submission completeness and authorized release must be established independently of technical validation.
Eliminate distractors: Schedule pressure and correct metadata do not resolve missing content.
Verify: Record the issue, hold the affected release, coordinate correction, repeat relevant checks, and obtain documented release authorization.
C Common decision trap
Tempting wrong action: Release the submission because validation passed and the project manager supports dispatch. Why tempting: Both suggest operational readiness. Eliminating clue: Independent QC has identified an unresolved required-content omission.
D Checkpoint
Question: A package passes technical validation but lacks required authorized release approval. What should the publishing associate do?
A. Dispatch because technical validation is the final gate.
B. Ask the dispatch operator to approve the release retrospectively.
C. Hold dispatch and obtain documented authorization through the assigned process.
D. Archive the package as submitted and correct the status later.
Answer: C. A is tempting because technical validation provides strong evidence of technical readiness, but does not establish release authority. B is tempting because the dispatcher controls transmission, but an operator may lack approval authority. C is correct because release requires the designated authorization. D is tempting as a records-management workaround, but would create a false submission history.
If you missed this: Review Responsibility matrices, release authority, and escalation - focus on the separation of validation, QC, release authorization, and dispatch.
Quick Recall:
Fill in the blank: The person who performs a task is designated ____ in RACI. Responsible.
True or false: A project deadline overrides an unresolved blocking QC finding. False.
Question: What evidence is needed before an authorized dispatch? Required readiness checks and documented release approval.
TRAPS
Exam Traps & Differentiators
Operational failures frequently arise when two legitimate activities are treated as interchangeable. The key is to identify which approval, verification, or authority boundary the scenario actually concerns.
Table 5. Similar activities with different control purposes
Looks similar
But is not the same
Discriminating clue
Document labeled final
Controlled approved source
Authoritative approval status and version.
Publishing instruction
Regulatory classification authorization
Whether a regulatory determination is changing.
Technical validation pass
Release approval
Designated authorized signoff.
Transmission confirmation
Complete agency processing
Specific acknowledgment and status evidence.
Document present in package
Submission inventory reconciled
Expected-to-actual content comparison.
IND regulatory serial
eCTD sequence identifier
Different numbering purpose and authoritative source.
Common traps and distractors:
Deadline-based release: Tempting because an official timeline is approaching; eliminate when a required release gate remains incomplete.
Filename-based approval: Tempting because final appears in the filename; eliminate when the controlled version or approval record disagrees.
Validation-based content acceptance: Tempting because technical validation is formal and automated; eliminate when a required document is missing from the approved inventory.
Publishing-based regulatory interpretation: Tempting because the publisher enters submission metadata; eliminate when the underlying regulatory category is not authorized.
Dispatch equals completion: Tempting because the transmission application reports success; eliminate when required subsequent acknowledgments remain unverified.
Scenario language cues:
If the scenario says unapproved classification change, think regulatory affairs escalation.
If it says conflicting source versions, think controlled document handoff.
If it says missing document after publishing, think inventory-to-package reconciliation.
If it says technical pass but unresolved QC finding, think hold and corrective action.
If it says transmitted but acknowledgment missing, think status investigation and tracking.
4. Perform or hold. Execute approved technical work; hold and escalate unresolved decisions or blocking defects.
5. Reconcile and document. Record corrections, QC results, release authorization, transmission, acknowledgments, and archive status as applicable.
Submission associate's operational checklist Exam takeaway: Every workflow stage should produce evidence supporting the next authorized action.
{"prompt":"Square clean educational vector infographic showing a five-stage regulatory operations checklist: Identify task, Confirm owner, Verify records, Execute or hold, Reconcile and archive. Each stage has a distinct document or workflow icon, connected in order, with a small amber exception path from Execute or hold to Escalate. White background, cool blue-gray palette, thin outlines, large readable labels, no logos.","caption":"Submission associate's operational checklist","size":"1024x1024"}
1.1.1.6 What is coming next?
The course uses November 1, 2026 as its content baseline and includes preparation for January 2027 FDA high-severity validation expectations and eCTD v4.0 transition activities. For this foundational topic, the practical implication is stable: maintain accurate source records, controlled metadata, documented checks, and clear release authority. The specific supported version, acceptance rules, and applicable enforcement details must be confirmed against current FDA implementation information before actual submission.
eCTD v4.0 introduces different message, submission-unit, context-of-use, and document-reuse concepts. These change technical workflows, but they do not remove sponsor accountability or the need for controlled approvals.
QUIZ
Self-check quiz
Choose the most appropriate operational action for each scenario.
1.1.1.7 Question 1
A writer requests a new CTD location for an approved report, but the revised placement has not been confirmed by regulatory affairs. What should the publishing associate do?
A. Use the revised location because the writer owns the content.
B. Maintain the approved placement until the responsible regulatory function confirms the change.
C. Publish in both locations to avoid an omission.
D. Select the location used in the previous sequence.
1.1.1.8 Question 2
Which record most directly supports verification that every planned document was included in an assembled submission?
A. Approved source-document inventory reconciled with published output.
B. Regulatory correspondence contact list.
C. Annual submission planning calendar.
D. Electronic gateway transmission history.
1.1.1.9 Question 3
Technical validation passes, and the package is complete, but release approval has not been recorded. What is the correct next step?
A. Dispatch and collect the approval afterward.
B. Ask the publisher to sign on behalf of the release authority.
C. Retain the package as ready and obtain documented authorization before dispatch.
D. Treat the validation report as the release approval.
1.1.1.10 Question 4
An IND regulatory serial is 003, while the eCTD sequence is 0012. Which conclusion is most appropriate?
A. The sequence must be changed to 0003.
B. The regulatory serial must be changed to 012.
C. The two values are automatically invalid because they differ.
D. Each identifier must be independently reconciled against its applicable authoritative record.
1.1.1.11 Question 5
An electronic submission is transmitted and an initial delivery confirmation appears. The expected subsequent agency processing acknowledgment is not yet available. Which action is most appropriate?
A. Mark the submission fully accepted based on the initial delivery evidence.
B. Track the outstanding status, investigate according to procedure, and preserve all available transmission evidence.
C. Immediately rebuild and retransmit the same sequence without assessing status.
D. Close the issue when the internal dispatch checklist is complete.
ANSWERS
Answer key & explanations
1.1.1.12 1. Correct answer: B
A: Tempting because the writer owns the report; incorrect because content ownership does not automatically authorize CTD placement changes.
B: Correct because the approved mapping remains controlling until a designated regulatory decision-maker authorizes a change.
C: Tempting as a completeness safeguard; incorrect because duplicate placement is not a substitute for approved instructions.
D: Tempting because precedent can inform planning; incorrect because the current approved placement governs this action.
If you missed this: Review Who owns each part of a submission? - focus on regulatory placement authorization versus technical execution.
1.1.1.13 2. Correct answer: A
A: Correct because comparing expected controlled documents with actual published content detects omissions.
B: Tempting because correspondence supports regulatory administration; incorrect because contact information does not establish content completeness.
C: Tempting because calendars capture planned activities; incorrect because scheduling does not verify package contents.
D: Tempting because it establishes sending activity; incorrect because transmission history does not directly prove inclusion of all planned documents.
If you missed this: Review Operational deliverables, metadata, and reconciliation - focus on expected-to-actual document matching.
1.1.1.14 3. Correct answer: C
A: Tempting under deadline pressure; incorrect because retrospective approval bypasses the required gate.
B: Tempting because the publisher controls the package; incorrect unless that person independently holds documented release authority.
C: Correct because completion and validation do not replace authorized release approval.
D: Tempting because validation is a formal technical assessment; incorrect because it does not authorize dispatch.
If you missed this: Review Responsibility matrices, release authority, and escalation - focus on release approval as a separate control.
1.1.1.15 4. Correct answer: D
A: Tempting because matching values may appear consistent; incorrect because the systems are distinct.
B: Tempting because it harmonizes identifiers; incorrect because an IND regulatory serial cannot be changed merely to match an eCTD sequence.
C: Tempting because discrepancies usually require investigation; incorrect because different numbering systems need not have equal values.
D: Correct because each identifier has a separate purpose and must match its own authorized source.
If you missed this: Review Operational deliverables, metadata, and reconciliation - focus on distinguishing IND regulatory serials from eCTD sequence numbering.
1.1.1.16 5. Correct answer: B
A: Tempting because initial confirmation proves some progress; incorrect because it does not necessarily establish the later agency status.
B: Correct because acknowledgment tracking, investigation, and preservation of transmission evidence are part of controlled submission reconciliation.
C: Tempting as a rapid response to uncertainty; incorrect because unnecessary retransmission may create additional operational problems.
D: Tempting because internal dispatch work is complete; incorrect because acknowledgment reconciliation remains outstanding.
If you missed this: Review Following a document through the controlled workflow - focus on the distinction between transmission and subsequent processing evidence.
RAPID
Rapid review / cheat-sheet
Regulatory strategy - decides the authorized regulatory approach, not the technical file assembly.
Source approval - verify controlled version and status, not filename wording.
Publishing assignment - execute approved instructions rather than create regulatory decisions.
Document inventory - identify the expected submission scope before reconciling actual output.
Metadata control - reconcile each field against its designated authoritative record.
IND regulatory serial - keep distinct from eCTD sequence numbering.
Technical validation - establishes assessed technical compliance, not scientific or release approval.
Dispatch record - demonstrates a transmission action, not necessarily completion of agency processing.
Acknowledgment tracking - determine the actual processing state before closing submission tracking.
Issue log - preserve discrepancy, owner, action, and documented closure.
Responsibility matrix - distinguish the performer from the accountable approver.
1.1.1.17 Key points
Controlled submission work is a sequence of independently evidenced handoffs.
Technical competence does not confer scientific, regulatory, or release authority.
Approved source identity and package reconciliation are primary defenses against preventable publishing errors.
Unresolved blocking issues must be visible, assigned, corrected, and rechecked before authorized release.
Reliable tracking continues after transmission through acknowledgments and final archival.
See also: FDA Application Types and eCTD Coverage (ch01.s01.t02) develops the application-scope decisions that feed submission planning. Career Portfolio and Final Assessment (ch08.s02.t02) applies these workflow deliverables to entry-level regulatory operations job readiness.
End of your free lesson
Keep going with the full Regulatory Operations and eCTD Submissions Certificate Program
You just studied the way members do, in the same lesson interface. Full access unlocks every lesson, the question bank and flashcards for a full year.