Custom software for certificate scope and factory inspections
A manufacturer with certificates rarely has just one. There are several, from several certification bodies, each with its own assessment guideline, its own visit frequency and its own list of products that fall under it. The question that most often goes wrong is the simplest one: does this product actually fall under this certificate?
What happens outside the production file
Before a quality declaration is issued, the certification body carries out an admission assessment. This checks whether the declared values of the essential characteristics are met, assesses the other product characteristics, determines the performance in the application, assesses the processing instructions and establishes the conditions of use. For an attest-with-product-certificate, the production process, the quality system and the internal quality control scheme are added to this.
After issue, periodic assessments follow. The visit frequency is not the same for everyone: assessment guidelines link it to the turnover associated with the certified product, and companies with an ISO 9001 certificate can be given a lower frequency. This reduction only applies if the company's management declaration states that production complies with the requirements of the assessment guideline.
During this assessment, the body looks at, among other things, whether there is a person responsible for managing the quality system, whether the internal quality control scheme is in place and operating effectively, the measuring and testing facilities with their calibration and state of maintenance, and the recording of the measurement and test results, as well as the results themselves.
In addition, during control inspections the body itself designates an element from production. The supplier provides the identification of that element and the data related to its application in advance, and releases it for testing. That is a process with a lead time, not something done on the day itself.
How we build this
At the core are the certificate and its scope. What falls under it determines what gets inspected, what may appear on a declaration and what a new product first needs.
Which products, which systems and which production sites fall under which certificate, from which certification body and under which guideline.
The frequency follows from the scheme and from your situation. The system plans ahead instead of waiting for an announcement.
What the inspector requests, which element they designate and which documents must be ready beforehand all depend on the visit itself.
Every finding gets an owner and a final date, because follow-up is where a sanction process gets triggered.
What the software actually does
Scope management holds everything together. What else you need depends on the number of certificates and on whether you have multiple production sites.
Scope as the first question
For every product you can see which certificate it falls under and whether it already did when it was delivered.
New product as a process
A product outside the scope first needs an admission assessment. That is a project with steps, not a tick box.
Visit calendar per scheme
Multiple certificates means multiple rhythms. The system puts them side by side instead of in separate calendars.
Prepare the designated element
The certification body designates an element, and you supply the identification and application details in advance. The system keeps that record.
Findings and follow-up
What was found, by whom, with what deadline and what was done about it. At the next visit, that is the first thing discussed.
Calibration and facilities at a glance
The certification body assesses the condition of your measuring equipment. You should know what has expired before the visit.
Who we build for
Who keeps track of this differs from company to company. Four situations.
Quality managers
They monitor several schemes at once and only discover during a visit that two of them require something different.
Manufacturers with multiple sites
For them, the scope differs per site, while the certificate is discussed at company level.
Companies that are expanding
A new product or a new system is not automatically covered by an existing certificate. That takes time, which should be planned in advance.
Leadership
She signs the management declaration on which a lower visit frequency is based, and wants to know whether that claim still holds.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
Assessment guidelines get revised, certification bodies change their procedures and new schemes are added. Certificates, scope rules and frequencies should be configurable rather than hard-coded.
For inspection companies that need to schedule re-inspections per object within the deadline, there is our inspection planning software for inspection companies.
Why Appfront
Scope is the first question, not the last
Whether a product falls under a certificate determines everything that follows. We build that as the core rather than as a feature.
A new product is a process
An admission assessment has a lead time. Treat it as an administrative step and you find out too late that you are not yet allowed to deliver.
Multiple schemes are not simply additive
Two certificates sometimes require different things of the same production. That conflict should be visible before an inspector sees it.
We don't certify
The verdict stays with the certification body. We build the overview you take into the visit.
Security and privacy
Your certificate files contain product specifications, measurement results and findings that reveal something about your production. They are competitively sensitive, and sometimes shared with a body that also visits your competitors. We set access per role and per location, give an auditor temporary, limited access, and log that access. Integrations to your existing software run through secure connections.
For this topic, the reliability of the moment is what matters. A finding that was reworded after the visit, or a scope that was retroactively widened, undermines exactly what the certificate is meant to demonstrate. We record changes immutably with timestamp and person, and make a correction visible alongside the original entry. How we handle security ourselves is set out in our information security policy.
Frequently asked questions about certificate scope and inspections
The certification body checks whether the declared values of the essential characteristics are met, assesses the other product characteristics, determines performance in the application, assesses the processing instructions and sets the conditions of use. With an attestation-with-product-certificate, the production process and the quality system are added.
In assessment guidelines, it is linked to the turnover associated with the certified product. Companies with an ISO 9001 certificate can be given a lower frequency, but only if the management declaration states that production complies with the requirements of the guideline.
Among other things, the person responsible for the quality system, the presence and operation of the internal quality control scheme, the measuring facilities with their calibration and maintenance status, and the recorded measurement results and the results themselves.
No. Anything outside the agreed scope needs assessment first. That is a process with a lead time, and it is the most common reason a delivery has to wait.
This is about the outside view: scope, visits and findings. The daily checks, measurements and calibrations from your guideline are covered on our page about certificate management and BRL files.
Yes, and that is usually the very reason to build something. Each scheme keeps its own rules, but they all appear in one calendar and one list of findings.
Is your newest product already covered by your certificate?
Take the last product you put into production and look up which certificate covers it and since when. If that turns out to be an assumption, the same question will come up at the next visit. We build this as a standalone application and as part of a broader software development project.
If you want to record the visit yourself on the shop floor, take a look at the app for inspection visits at the production site.