GSPR Checklist
Requirement-by-requirement applicability, justifications, compliance methods and exact supporting evidence references. Prepare working Word and PDF outputs for your team’s review.
GSPR & Standards Compliance
Know what applies. Show what supports it.
Bring requirements, applicability decisions, compliance methods and evidence revisions into one reviewable workflow. Spend less time rebuilding compliance matrices and more time resolving the gaps that need your expertise.
Where the time goes
The hard part is not adding another row.
It is finding the right test report, checking which revision was reviewed and explaining why it supports this requirement for this device. When that reasoning lives across separate spreadsheets and folders, every update brings another round of checking.
Bevrik’s approach keeps the requirement, method, evidence version and review context together. Your specialists can focus on applicability, evidence quality and the changes that need attention.
01 / A matrix your team can follow
Make applicability a decision you can explain.
Work through the General Safety and Performance Requirements (GSPR) with the source text and device context in view. Record what applies, what does not and why. An undecided requirement remains undecided; a blank cell is not a justification.
Aster Flow portable surgical suction system: a device-specific applicability rationale, an ISO 14971 method reference and the supporting risk-file revisions.
Illustrative workspace—not an actual product screenshot. Aster Flow is a fictional device; documents, links and review states are examples, not verified evidence. Topic summaries are not official regulatory or ISO clause text and do not establish compliance or approval.
View full size02 / A matrix your team can follow
Put the evidence beside the requirement.
See the document name, number and exact revision behind a row, together with the reason it supports that requirement. Reuse one document across relevant clauses without losing each clause’s own rationale. Missing, proposed and established support remain distinct.
Fictional risk, verification and instructions-for-use documents sit beside each requirement topic. Revision checks, missing support and review needs remain visible.
Illustrative workspace—not an actual product screenshot. Aster Flow is a fictional device; documents, links and review states are examples, not verified evidence. Topic summaries are not official regulatory or ISO clause text and do not establish compliance or approval.
View full size03 / A matrix your team can follow
Know which standard edition supports the work.
Keep the standard edition used for your device separate from publisher information about newer editions and the relevant regulatory citation status. Link compliance methods to the selected edition and clause references. A newer edition is not automatically applicable, harmonized or adopted.
An illustrative ISO 14971:2019 register entry connects risk-management topics to Aster documents. Publisher checks and regulatory citation remain unverified.
Illustrative workspace—not an actual product screenshot. Aster Flow is a fictional device; documents, links and review states are examples, not verified evidence. Topic summaries are not official regulatory or ISO clause text and do not establish compliance or approval.
View full size04 / A matrix your team can follow
Keep the reasoning behind an edition change.
Retain your manufacturer-authored Edition Change Impact Assessment for each old-to-new transition. Document clause changes, device impact, justification, supporting evidence and any actions or retesting. Earlier records stay available; detecting a new edition does not silently replace the edition in use.
A historical 2007-to-2019 edition-change example shows manufacturer-authored review questions and open actions—not an official ISO change summary or a completed transition.
Illustrative workspace—not an actual product screenshot. Aster Flow is a fictional device; documents, links and review states are examples, not verified evidence. Topic summaries are not official regulatory or ISO clause text and do not establish compliance or approval.
View full sizeUseful working records
A clearer checklist. A stronger explanation.
Standards Compliance Matrix
Clause-level applicability, rationale, methods and evidence references tied to the standard edition used for the device. Keep gaps and unresolved items visible.
Edition Change Impact Assessment
Your manufacturer-authored comparison, device-impact reasoning, evidence and action or retest records, retained for each transition rather than overwritten.
Working records are not a compliance certificate or regulatory approval. A linked document is not proof that a requirement has been met. Your qualified team checks the evidence, makes the decisions and completes formal document approval in its own quality process.
Keep the boundaries clear
A status should explain the work—not hide a gap.
Source text stays source text
Keep authoritative GSPR wording distinct from explanations and AI interpretations. Licensed standard content requires appropriate access rights; a summary is not a replacement for the original.
AI feedback stays advisory
A suggested evidence link or positive assessment does not establish compliance. Missing support, stale inputs and reservations must remain visible for human review.
Changes need context
A document or edition change may affect more than one requirement. Retain the earlier versions and review the affected decisions instead of silently carrying old conclusions forward.
Standards impact assessments are manufacturer-authored, not AI-generated. Live publisher checks, automated monitoring and cross-module connections are not implied by this page; available workflows and scope are confirmed during discovery.
The evidence relationship
Follow the reasoning, not just a hyperlink.
1
Requirement
The source clause and its applicability to your device.
2
Method
A selected standard and clause, or another justified compliance method.
3
Evidence version
The exact document revision, source location and explanation of support.
4
Qualified review
Your team evaluates the evidence, gaps and conclusions.
Conceptual relationship—not a product screenshot or a claim of automatic data transfer. Clinical, risk and test records may support this work where relevant and authorized; their original evidence and review context still matter.
Part of the Bevrik subscription
Not another separate module plan.
GSPR and Standards Compliance sit alongside Clinical Evaluation and Risk Management in the same subscription. All generally available standard modules are included within the agreed scope, with availability, usage and support limits confirmed before you sign.
From research to your next step
Continue with your task.
Read a practical guide, find a starting document and explore how Bevrik supports the work.
Review risks and supporting evidence
Start with the assessment, then connect controls and requirements to the evidence behind them.
Understand
Read about performance thresholds and risk →Start
Risk Assessment Template →Manage
Explore Risk Management →- Explore GSPR & Standards →
Start with one recurring task
Which requirement takes the most work to explain?
Pick the task that takes too much preparation. Walk through the Bevrik approach, confirm the available workflow and identify the review your team would still need to do.