Step 1
Create one row per document and link it to the product and revision under review.
Practical review guide · Free worksheet
Build a supplier document acceptance log
Direct answerRecord received, pending review, accepted for a defined purpose and rejected as separate states. The log should explain the scope of every acceptance decision.
Reviewed by ComplyFolio. Sellers and reviewers maintaining product evidence and preparing publication decisions.
Get the working templateReview procedure
These are suggested operational checks to apply to your own evidence. They are not additional legal requirements or claims that the workspace automates this entire task.
Step 2
Record the review purpose and the checks performed by a named owner.
Step 3
Keep rejected or superseded files visible in history while excluding them from current evidence selections.
Step 4
Require a reason and supporting reference when changing status, especially from pending to accepted.
Worked example
A team marks a whole folder approved even though one declaration refers to a discontinued model.
What the reviewer finds
- Folder-level approval hides an unrelated declaration.
- No reviewer or review purpose is attached to the status change.
Resulting record
A document decision ledger that distinguishes receipt from review completion.
Boundary: Accepted in this workflow means accepted for the recorded review purpose, not certified legally compliant.
This scenario is fictional. It illustrates a review decision, not a customer outcome or a compliance determination.
Download the blank working record
The Markdown worksheet includes the procedure, the fields below, and space for findings, evidence, owners and retests. It contains no pre-approved findings. Edit it locally without an account.
- Document reference
- Review purpose
- Status
- Decision reason
- Reviewer
Record what you observed, including unknowns. Link each decision to a source and keep unresolved questions assigned to an owner. Share completed records only through an appropriate authorized route.
Primary references and scope
The references provide the legal or technical context. The procedure and worksheet are ComplyFolio working suggestions, not official forms or a certification standard.
- GPSR — product safety, operator and distance-sale requirements (legal context)
- European Commission — product safety and business resources
Accepted in this workflow means accepted for the recorded review purpose, not certified legally compliant.
Connect the review to your product record
Use the free workspace for an initial public product-page review, then add the manual evidence and decisions this guide requires. A page scan cannot inspect private supplier files or complete every user journey.
Start with a public product page