A findings register
Every gap, inconsistency and weak document, listed against the clause or requirement it fails. Not a general impression — a numbered list someone can work through.
Technical Documentation Review
Most rejected files are not missing anything
They contradict themselves. A model list that grew after testing, a laboratory outside its accreditation scope, three documents naming the manufacturer three different ways. We read the file the way a conformity body will, and tell you what it will say — while you can still do something about it.
To review a file we need:
- The technical file as it stands
- Product and model list
- Saudi HS code
The Premise
A document can be genuine and carry no weight
Exporters tend to assemble technical files as collections: a certificate here, a report there, whatever the supplier sent. Each item is real, and the folder looks convincing. What decides the outcome is something narrower — whether each document is still live, whether its issuer was competent for that specific test, whether its scope covers the product you are actually selling, and whether the documents agree with each other about what that product is.
A conformity body applies those tests in a few hours. The difference is that when they apply them, the answer arrives as a query on their timetable, with a shipment behind it. This review applies the same tests first.
The Deliverable
What you get back
A review that returns an impression is not worth commissioning. Six things come back, and all of them are actionable.
A severity call on each one
What will stop the application, what will draw a query, and what is untidy but survivable. The three are treated very differently and conflating them wastes money.
A named test list, if testing is needed
Where evidence is missing, we say which standard and which clauses, so you can quote it. We do not send you back to a laboratory for a full programme you may not need.
A sequence for closing it
Which items block others, which can run in parallel, and what the realistic order is. The order is usually worth more than the list.
A go or no-go on submission
A plain answer on whether the file is ready for a conformity body today, and if not, what the shortest path to ready looks like.
A conversation with whoever has to fix it
Findings go back to the engineer, the supplier or the agent who owns them, in language they can act on rather than as a forwarded PDF.
Process
How the file is read
Five steps, in this order. The first one is the step most self-assessments skip, and skipping it makes the rest meaningless.
Fix the requirement first
A file cannot be assessed in the abstract. We take the Saudi HS code, identify the technical regulation and the standards it names, and establish the edition in force. Everything after this is measured against that, not against general good practice.
Inventory what you actually have
Certificates, reports, drawings, declarations, artwork, component lists. Listed as documents with dates, issuers and scope — which is usually the first time anyone has seen the file as a whole.
Test each document for standing
Is it live, is the issuer competent for this, does its scope cover the product, is the edition current, does it name the right manufacturer. A document can be genuine and still carry none of the weight it is being asked to carry.
Reconcile the documents against each other
Model names, ratings, manufacturer addresses and product descriptions compared across every document. Most rejected files are not missing anything — they contradict themselves.
Report the gap, not the ideal
We describe what is needed to pass, with severity and sequence. A review that returns a wish list is a review that gets ignored.
What To Send
The whole file, not the highlights
Send what you have, including the parts you suspect are weak. A review of an edited file reviews the editing.
Product identity
- Model and variant list, as it will appear on the certificate
- Product description and intended use
- Saudi HS code, or the classification you intend to declare
- Rating plate and marking artwork
- General arrangement drawings or product photographs
Test evidence
- All test reports, in full rather than summary pages
- CB, IECEx or other scheme certificates, with the reports behind them
- Laboratory accreditation certificates and their scope annexes
- Any previous conformity certificates for other markets
Manufacturing and declarations
- Manufacturer name and the producing plant address
- Quality system certification, where the scheme calls for it
- Declaration of conformity as currently drafted
- Critical component or bill of materials list
Commercial context
- Saudi importer details, if one is appointed
- Any correspondence or queries already raised by a conformity body
- The deadline you are working to, and what is driving it
Findings
What we keep finding
Six patterns that account for most of what a technical review turns up, across every product family we handle.
A report against a retired edition
Testing that was correct when it was done and is no longer measured against the standard in force. Common on files assembled over several years.
Accreditation that does not cover the test
A genuinely accredited laboratory reporting against a standard outside its scope annexe. The certificate on the wall does not make every report usable.
Models in the catalogue, not in the evidence
The range grew after testing. Variants that need a justified family grouping or their own evidence, rather than an assumption that they are covered.
Three documents, three manufacturer names
A trading name on the invoice, a legal entity on the certificate and a plant on the report. All correct, none matching, and the file reads as three products.
A declaration that claims too much
A declaration of conformity citing standards nothing in the file supports. It is the single easiest thing for an assessor to disprove.
Marking that contradicts the file
Ratings on the nameplate that no report demonstrates, or a mark the product is not entitled to carry. Cheap to correct on artwork, expensive once tooling is cut.
Timing
The same finding, two prices
Nothing in the left column is easier than the right. It is the same defect — the only difference is who found it and when.
Found at review
- A named gap and a decision about how to close it
- Testing scoped to clauses rather than to a whole standard
- Artwork corrected before the print run or the tooling
- Your own timeline, with the sequence in your control
- One conversation with the supplier, while you still have leverage
- Cost measured in review time
Found at technical review
- A query from a conformity body, on their clock
- Testing scoped defensively, because nobody wants a second query
- Artwork already printed, sometimes already applied
- A deadline set by a shipment that is already booked
- A supplier who has been paid and has moved on
- Cost measured in laboratory fees, delay and demurrage
When To Run One
Six moments worth spending it on
A review is not an annual ritual. These are the points where a file changes underneath you.
First entry into Saudi Arabia
A file built for another market, being pointed at a Saudi regulation for the first time. The overlap is usually large and never complete.
A conformity body has raised queries
One query is a document problem. Three is a file problem, and answering them one at a time is the slowest way to resolve it.
The manufacturer or plant has changed
A second source, a moved line or a new contract manufacturer. The evidence still describes the old arrangement.
The range has grown
New variants added since certification, and no one has established whether the family grouping still holds.
Renewal is approaching
Standards move between certificate cycles. A renewal is the cheapest moment to discover that, and the worst one to be surprised by it.
You are buying the file, not building it
A supplier or trading partner has supplied the dossier. Reviewing it before you rely on it is ordinary diligence.
Worked Example
Thirty-one documents, and the best two were worthless
A machinery exporter with an eleven-year-old product line, a dossier assembled from three suppliers, and a conformity body query already open.
Requirement fixed
The HS code put the range under a regulation naming two standards. One of them had moved edition twice since the newest report in the file.
File inventoried
Thirty-one documents, four of them duplicates, two of them drafts that had never been finalised, and one report belonging to a product they no longer sold.
Standing tested
Two reports came from a laboratory whose accreditation scope did not cover the standard cited. They looked like the strongest evidence in the file and carried no weight at all.
Contradictions resolved
The manufacturer appeared under three names across the documents. One entity was named, the rest were reissued or annotated with a documented relationship.
Submitted
Delta testing on nine clauses instead of a full reassessment, the open query answered in a single response, and the certificate issued without a further round.
The Gate
What ready looks like
Six conditions. A file that meets all six is ready for a conformity body; a file that misses one is ready for a query.
- Every document in the file is live, in scope and current for its standard
- The model list on the evidence matches the model list you intend to certify
- One manufacturer identity runs consistently through every document
- The declaration of conformity claims only what the file demonstrates
- Marking and artwork agree with the ratings the reports support
- Any remaining gap is named, scoped and sequenced rather than unknown
Keep Going
Related pages
What belongs in a file, how the evidence behind it is judged, and the later check that protects the shipment.
FAQs
Review questions
Scope, turnaround and what happens to the findings.
What is a technical documentation review?
It is an assessment of your technical file against the Saudi regulation that will actually be applied to it, carried out before you submit to a conformity assessment body. The output is a findings register: what is missing, what is weak, what will draw a query, and in what order to fix it.
How is this different from a pre-shipment review?
A pre-shipment review checks the documents for one consignment against that shipment, shortly before it moves. This checks the technical file behind the product against the regulation, much earlier. One protects a container, the other protects a certification programme.
Can you not just tell me the requirements and let me check it myself?
The requirements are published, and we set them out on the requirements page. What is hard is not knowing the list — it is judging whether a specific report, issued by a specific laboratory, against a specific edition, actually covers the product you are selling. That judgement is the service.
What if the review finds the file is fine?
Then you submit with more confidence than you had, and the review cost a fraction of one delayed shipment. It happens, most often with manufacturers who have certified into demanding markets before. It is not the common outcome on a first Saudi file.
Do you need the full test reports or will summaries do?
The full reports. Summary pages tell you a product passed; the body of the report tells you what was tested, in what configuration, against which clauses, at which laboratory. Almost every substantive finding we make comes from the part of the report that summaries leave out.
Our supplier will not release their test report. Can you work around it?
Not really, and that is itself a finding. A conformity body will need to assess the evidence, so a report you cannot obtain is a report you cannot rely on. There are routes — direct release to the assessor, a confidentiality undertaking, or the supplier holding the certificate themselves — and choosing between them early is far better than discovering the problem at submission.
How long does a review take?
It depends on the size of the file rather than the complexity of the product. A single product with a tidy dossier is quick; a range assembled from several suppliers over a decade takes longer to inventory than to assess. We give you a turnaround when we see what is in the file.
Will you fix the problems as well as find them?
We will scope and coordinate the work — naming the testing, briefing the laboratory, reconciling the documents and taking the file through to certification if you want that. The review itself is deliberately separable, because some clients only need to know where they stand.
Does a review guarantee the certificate will be issued?
No, and anyone promising that is describing something other than an independent review. What it does is remove the failures that are knowable in advance, which is most of them. The conformity body still makes its own assessment.
Is this worth doing if a conformity body has already queried us?
That is one of the better moments for it. Queries tend to arrive one at a time, and answering them individually means several rounds, each costing a week. Reviewing the whole file at that point usually reveals the remaining queries before they are asked, and they can be answered together.
Find out what a conformity body will say before they say it
Send the file as it stands, the model list and the HS code. You get back a numbered findings register, a severity call on each item, and a plain answer on whether it is ready to submit.