Define the review question.
State the decision you are asking the specialist to make. A broad request to “check everything” can hide uncertainty about the scope. Explain the product, intended markets and the event that prompted the review.
A file being present does not mean it has been reviewed.
The specialist should confirm the scope and any information needed before a substantive conclusion is recorded.
Identify the exact record.
Include the product name and current revision. Gather the files relevant to the question, with dates and version references where available. Keep unknown or conflicting information visible.
Use a short index that explains each attachment. A large archive with no guide can make a small question harder to review.
List the open questions.
Separate missing facts from interpretation questions. A missing supplier document needs a different action from a question about legal applicability. Give each unresolved point a clear owner.
Do not fill a gap with an answer that merely makes the form look complete.
Keep the findings attached.
Record the review decision, notes and limitations with the product revision. Turn follow-up work into actions and request a fresh review when the record changes materially.
This handover method helps organise the work. It does not define the qualifications, assessment scope or legal standard required for a particular product.
An organisational workflow guide. This article does not define regulatory obligations or certify a product. Specialist regulatory guidance has a separate review gate.
Download a blank organiser →
