Custom app for inspection visits at the production site
During a surveillance inspection, the certification body itself selects an item from production. The supplier provides the identification of that item and the data associated with its application in advance, checks it and releases it for testing. That is a series of actions on the shop floor, under time pressure, with someone watching.
What happens during a visit
After a certificate of quality has been issued, the certification body carries out periodic assessments. The assessment of the quality system covers, at the very least, the presence of a person responsible for managing the quality system, the presence and effective operation of the internal quality monitoring scheme, the measuring and testing facilities along with their calibration and state of maintenance, and the records of the measurement and test results, as well as the results themselves.
These are all things that are verified on the shop floor. The inspector walks around, asks for a document, wants to see a measuring instrument and asks about the latest calibration. If you have to fetch that from someone who isn't there at that moment, you lose the visit to waiting.
At a verification inspection, the designated element comes on top of this. The body selects an element from production, preferably an assembled specimen, and the supplier provides the identification and the data relating to the application in advance. During testing, a limited adjustment to the product is permitted at verification inspections.
What is found during the visit determines everything that follows. A finding with no owner and no deadline stays open until the next visit, and then it is the first topic of conversation. The sanction policy follows the body's procedures, and those are built up in stages.
How we build this
The core is the visit itself. A day with a visitor asking questions, and an organisation that has to be able to show, there and then, what it does.
The documents and data belonging to this scheme are ready, so the visit doesn't start with searching.
The designated specimen receives its identification and application data and is recorded as released for testing.
Whatever is found is recorded with a photo and location while the inspector is still standing there.
Every finding gets a name and a date, because that is what a sanction process either stalls or moves forward on.
What the app actually does
Recording during the visit carries the whole process. What else you need depends on the number of certificates and the number of sites.
The visit as a file
Date, body, scheme and attendees, with everything established that day linked to it.
Release the element with evidence
Identification, application data and a photo of the designated specimen, recorded before testing begins.
Calibration at the instrument
A code on the instrument shows the latest calibration and maintenance status, at the moment someone asks for it.
Finding with image and location
What was found, where, and what it looked like. Later, that is the difference between understanding and trying to remember.
Works without signal
Production halls rarely have good coverage. The app works locally and syncs as soon as there is a connection.
Follow-up until closed
From finding to action to proof that it has been resolved, in a single trail until the next visit.
Who we build for
Who guides the visit differs from company to company. Four situations.
Quality staff
They walk alongside the inspector and are the ones who have to be able to show something on the spot.
Production managers
They have to release an element without bringing ongoing production to a halt.
Multiple sites
If you produce in more than one place, you get the same visit at every site, with different people and different habits.
Companies with multiple certificates
For them, someone visits several times a year, each time with their own checklist.
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 and bodies change their procedures. Checklists, fields and schemes should be configurable rather than hard-coded into the app.
Why Appfront
A visit is a day, not a document
Whatever isn't recorded on the day gets reconstructed from notes a week later. We build the recording for the moment itself.
The designated element needs preparation
Identification and application data must be in place before testing begins. That isn't paperwork for afterwards.
Calibration is requested at the instrument
Not in a list at the office. A code on the measuring equipment gives the answer where the question is asked.
We don't certify
The verdict stays with the certification body. We make sure you go into the visit with what you need.
Security and privacy
What is recorded during a visit includes measurement results, findings and images of your production. That is commercially sensitive, and the body that visits you sometimes visits your competitor too. We set access per role and per location, give an auditor temporary, limited access, and log that access. Whatever is stored locally on the device is encrypted and can be wiped remotely if a device is lost.
For this subject, the reliability of the moment is the point. A finding reworded after the visit, or a release that has been backdated, undermines exactly what the certificate is meant to demonstrate. We record observations immutably with time, location and person, even when the sync happens later, and turn a correction into a visible correction alongside the original entry. How we handle security ourselves is set out in our information security policy.
Frequently asked questions about inspection visits at the production site
Among other things: the officer who manages 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.
The body designates an element from production, preferably an assembled specimen. The supplier provides the identification and the data related to its application in advance, checks the element and releases it for testing.
Because a week later a finding is a note, not an observation. With a photo and location attached, you can still see later exactly what was found.
Yes. Production halls rarely have good coverage. The app works locally and syncs as soon as there is a connection again, preserving the original time.
In the certificate file, where scope, visit schedule and follow-up are tracked. We describe that on our page about software for certificate scope and factory inspections.
Yes. Each scheme keeps its own checklist, but the visits and findings sit in a single track. See our approach to building an app.
How long did the searching take at your last visit?
Take the report of the last inspection visit and count how many points were only supplied afterwards. Each of them would have been available on the day itself if someone had been able to look it up. We build this as a standalone app and as part of a broader app development project.