Compliance research

ASTM F2706-25 — FDA recognition transition and report handoff

FDA’s acquired supplementary sheets explicitly connect 11-346 to 11-443 and state declaration-acceptance date(s) for the replaced recognition: recognition 11-346: 2028-07-02. Compare the exact edition and recognition limitations with your reports before agreeing the submission evidence or further work.

Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.

Exact FDA recognition records

Compare the edition and the recognized portion

Read these columns together. A complete recognition is not a device-specific testing instruction. The limitations are the FDA’s public metadata; the licensed standard itself is not reproduced.

Recognition / editionPublic recognition limitationsDeclaration transition context
FDA 11-346
ASTM F2706-18

Standard Test Methods for Occipital-Cervical and Occipital-Cervical-Thoracic Spinal Implant Constructs in a Vertebrectomy Model

Complete

Complete standard

[2] [5]
Exported transition expiration: 07/02/2028
FDA 11-443
ASTM F2706-25

Standard Test Methods for Occipital-Cervical and Occipital-Cervical-Thoracic Spinal Implant Constructs in a Vertebrectomy Model

Complete

Complete standard

[1] [3]
No expiration date is stated in this acquired export row. That is not a guarantee of indefinite recognition.

What FDA’s transition statement says

Recognition 11-346 → 11-443

FDA recognition of ASTM F2706-18 [Rec# 11-346] will be superseded by recognition of ASTM F2706-25 [Rec# 11-443]. FDA will accept declarations of conformity, in support of premarket submissions, to [Rec# 11-346] until July 2, 2028. After this transition period, declarations of conformity to [Rec# 11-346] will not be accepted.

Exact statements were reconciled on both acquired sheets and against the old recognition’s exported date. [4] [6]

FDA public recognition metadata describes use of declarations of conformity in support of premarket submissions. A recognition transition is not a universal retesting deadline, a product ban, or proof that this standard applies to your device. The technical differences between licensed editions, adequacy of existing reports, buyer-specific route and final test scope remain incomplete. The comparison below does not reproduce the standard or establish FDA approval.

Method: Exact directed old-to-new statements are reconciled across both acquired sheets and the old export date. No name-similarity mapping or technical-clause inference.

Build your edition-to-report handoff matrix

Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.

  1. Which edition is actually in your evidence?

    Reconcile each report and declaration against ASTM F2706-25 and the replaced designation(s) ASTM F2706-18. Record amendments and the exact report/device revision. A similar standard number is not an edition match.

    Useful evidence: Report cover, method/edition references, amendments, declarations and device/configuration revision.

  2. Does the declaration cover the recognized portion?

    Use the complete FDA public limitation text in the comparison table. Map each listed exclusion, where present, to the relevant report sections and obtain a reasoned evidence assessment. Complete recognition still does not determine device applicability.

    Useful evidence: Recognition-to-report coverage matrix, excluded-clause assessment and the licensed edition used by your specialist.

  3. How does the recorded transition affect your submission plan?

    Record planned declaration/submission dates against the FDA sheet’s acceptance date(s): recognition 11-346: 2028-07-02. This concerns declarations supporting premarket submissions to the replaced recognition; do not treat it as a blanket deadline to retest or stop selling.

    Useful evidence: Submission plan, intended declaration references, dated recognition-sheet check and rationale for the chosen evidence route.

  4. What changed beyond the designation?

    Ask the specialist to assess the actual licensed edition/amendment differences for your design, materials, software and use environment. Separate a documented evidence gap from a changed title. This metadata comparison does not establish which tests changed or must be repeated.

    Useful evidence: Edition gap assessment tied to the device and existing evidence, with a bridging rationale and unresolved inputs.

  5. What should the quote include?

    Request a report/recognition reconciliation and a justified gap assessment first. Separate any proposed additional evaluation or testing, samples, methods, deliverables and exclusions; agree them only after applicability and existing evidence are assessed.

    Useful evidence: A scoped evidence-assessment quote; separately identified conditional work and report ownership.

Work packages and dependencies

Questions for providers

Sources and data dates

Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.

FDA — recognised standards metadata ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot b4d38ae5ee362b7697f4efc577b073dd81078364c9d9b78361a189b1e4cd6c78

  • [1] HTML tr 18 / Extent of Recognition / nested table · record 07a24d1a35cb0060bf1943474c3c6d316ce1df91900c1c44410237a66d14277a
  • [6] HTML tr 22 / Transition Period / nested table · record 5034d7273a63ea7e796a392bced015643f03e5caa826d08776dd2ba85cb02c5e

FDA — recognition metadata exported through the official search form ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 94ccf56dc846c7f6d78d6ad77dc6e87d1803ac3612af01d6894949e34c4a78d8

  • [2] CSV row 1214 · record 3381b24cc819707eaa6bcd7f9bb3069f4f8297b54f4c48fa0aad011114014464
  • [3] CSV row 66 · record 3e8106d21ae9dabd2955e6318073439893b75f22cb459ed8f4b64d3c215e2af4

FDA — recognised standards metadata ↗

Version not stated by the source · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot d7251d77db3474fb07b9e5e101c313931830d986bb9fb308c8397ee51e88c569

  • [4] HTML tr 22 / Transition Period / nested table · record 4d3ae24c88b6a21ff6d5c3c40111cfcc0393cb609fc2c80799a2dd7fd844c714
  • [5] HTML tr 18 / Extent of Recognition / nested table · record 4d8248f2460b122a65c30412724b2a1b96051abf7f81cbdac47a477ff3c9b664

Prepare an editable project brief

Confirm the facts, scope and contact preference before sharing your project. Preparing this page sends no provider outreach.

Choose work packages to discuss

Compare FDA 510(k) Submission Services