Skip to scenario
Back to the business caseSubmissions ยท Implementation

Assemble controlled sources into a reviewable draft

The drafting step follows source selection and evidence checks. Approval of source statements does not automatically approve their new arrangement or summary.

Follow the process
Business goal
Manage risk
Business metric
Cost of compliance

Preserve scope from source to submission section

Regulatory owners establish the required sections, baseline, and review criteria. Use controlled source statements and authoritative evidence references.

The task in this example

Draft the device-description and labeling sections for the IP-20 software update.

  1. Step 1

    Set the section structure

    Use the required submission template.

    System

    The regulatory system provides section requirements and versioned templates.

  2. Step 2

    Retrieve labeling

    Select current approved statements for the baseline.

    Content team

    Retain statement identity, approval state, effective date, and applicability.

  3. Step 3

    Connect supporting evidence

    Follow claims to requirements and test records.

    Ontology and knowledge graph

    Expose missing or mismatched relationships rather than inventing support.

  4. Step 4

    Draft the sections

    Summarize and arrange the approved material.

    Model

    Preserve claim limits and attach source references; unsupported elaboration must be rejected.

  5. Step 5

    Review and sign off

    Regulatory affairs evaluates the final text.

    People

    Check meaning, consistency, completeness, and evidence for the submission context before sign-off.

This framework provides a practical baseline shaped by experience. Every organization operates under distinct technical and operational realities that require tailored design and governance. While you can adapt these measures independently, we frequently partner with teams to customize governance, integrations, and rollout. Performance outcomes will naturally vary.

Why these content layers matter

Intelligent content

Maintain indications, warnings, and claims as reusable controlled units rather than uncontrolled copies.

Taxonomy

Classify product, software baseline, statement type, and intended submission context consistently.

Ontology and knowledge graph

Connect claims to the requirements and test evidence that support them; preserve those relationships in the draft.

Verify the result and handle exceptions

Compare every included statement with its approved baseline and inspect claim-to-evidence links. Review summaries for altered meaning as well as copied-text accuracy.

Missing evidence, superseded statements, and unresolved scope differences return to the responsible owner. Keep the draft unapproved until regulatory review resolves them.

How we work
with your team

We can guide your team, work alongside it, or deliver the work for you. Combine these approaches as your needs and capacity change.

Lead

Build capability

We guide your people through the work, building capability that stays with your team.

Support

Add specialist backup

Your team owns the work. We provide experienced backup and specialist help where you need it.

Do

Delegate delivery

We handle work that is one-time, specialized, or outside your core business, without adding an ongoing burden to your team.

How much submission review is spent reconciling source text?

Intuitive Stack can help structure controlled statements and evidence relationships with your regulatory and documentation owners.