Skip to content

Research handoff

How to document competitive medical-device research

Keep FDA source facts, coverage, and dates separate from your team’s assessment, proposed changes, and review decisions.

By MedTech Watch editorial · Published Nov 19, 2026 · Sources checked Nov 19, 2026 · Updated Nov 19, 2026

Record the research question, exact source identifiers, coverage and dates, your observation, and any proposed next step separately. Your team’s assessment and approvals belong in its own product or quality workflow.

Source fact: Identifier, excerpt, link, and dates; Team question: Relevance, uncertainty, and owner; Product work: Proposed change and independent review
A research handoff preserves the original source and the separate reasoning of the team.

Preserve a source someone else can inspect

Record the FDA identifier, original URL, exact applicant or recalling-firm name, relevant product code, source date, and access date. Quote only the part of the source that supports the observation. Keep the original wording distinguishable from your notes.

State the question and the limits

Write why the record matters to the research question. Name exclusions, missing fields, and any unresolved company relationship. A shared product code does not establish an identical intended use, and a record count does not establish market share or comparative safety.

Hand the question to the right workflow

Choose an owner and a next step. A proposed product change needs its own assessment, evidence, and review. Keep the research record linked to that work without presenting it as an automatically approved requirement or a completed surveillance activity.

Benchform is being developed by the same team for connected product and quality work. Its requirements-traceability guide offers a complementary example of how a team can connect its own records. Benchform is in early access; qualification and approval for official quality use remain pending.

Use a small, consistent research note

The downloadable worksheet captures a question, source reference, observation, uncertainty, and owner. It is a research aid, not a validated quality record or regulatory report. Keep your organization’s own controls for official work.

  • Research question and scope
  • FDA identifier and original source link
  • Source date and date accessed
  • Source fact or short excerpt
  • Your observation and unresolved questions
  • Owner, proposed next step, and link to the team’s work

From an interesting record to a reviewable note

Suppose a clearance under a code you follow prompts a question about your own product scope. Save the original record link and identifier, the date you accessed it, and the exact source fact that raised the question. State the question without claiming that the competitor’s record proves anything about your own device.

Assign an owner to assess the relevance. If the team proposes a change, connect that proposal to its own requirements, risk assessment, and evidence. The research note is an input; it is not an approval or a completed regulatory assessment.

Sources

This guide explains public-record research and product behavior. See our editorial standards and data coverage.

Turn research into a documented team decision →

Useful context

Keep this research moving.

Follow ten competitors and ten product codes. Get matching changes in your dashboard and a weekly brief, for $49/month.

Start a 14-day free trial ↗