Manage evidence expiry and requirement revisions
Keep approvals connected to the requirement version and evidence actually reviewed, with clear ownership for expiry and change.
By Power CM Software · Product workflow guide
Treat approval as a dated decision
An approval needs context: product, market, requirement version, evidence version, reviewer and review date. Without that context, an old approval may look current even after the underlying product or document has changed.
EU Commerce Desk connects evidence approval to requirement revisions. Use the history to explain the decision, rather than assuming the latest document automatically inherits an earlier approval.
Distinguish expiry from a scheduled review
A document expiry date and an internal review deadline are not interchangeable. Record the applicable expiry from the document where it exists; use a review date for your team’s planned reassessment. Do not invent validity periods for documents that do not state one.
Assign an owner for items approaching expiry. Record whether renewed evidence is required and allow time for the supplier and internal reviewer. Keep outstanding work visible in the calendar and requirement records.
Reassess after material changes
A new product revision, supplier change, new target market or revised requirement may affect existing evidence. Record what changed and determine which approvals need another review. Not every edit has the same significance, so preserve the reviewer’s reasoning.
For example, an updated requirement may ask for evidence that the previous document did not cover. Treat the new review as a separate decision instead of merely changing an old status to green. This is an operational example, not a rule for a specific product category.
Make readiness explainable
Use the matrix to find missing, expired or unreviewed evidence and assign actions. Keep incidents and closure evidence connected where they are part of the review. The goal is to explain why a recorded status exists and what the next step is.
Readiness reflects the records and rules your team has reviewed. The software is not a certification body or an automatic legal-update service. Review current official sources and product-specific obligations before relying on the result for a market decision.