Most plants prepare for an inspection by cleaning. That helps, but it is not what decides the outcome. An inspection is an evidence exercise: the officer is checking whether the system you described in your licence application is the system actually running on the floor.
Now that FSSAI has moved to a risk based inspection and audit framework, the result matters beyond the day itself. A plant that presents well is inspected less often than one that does not.
The first fifteen minutes
Officers tend to establish three things early, and the tone of the visit is usually set by what they find.
Does the licence match the operation? The product categories endorsed on the licence are compared against what is being made, what is in the finished goods store, and what the labels claim. A mismatch here is the single most damaging thing an inspection can find, because it calls the entire file into question.
Is there a trained food safety supervisor present? Licensed businesses are required to have trained supervisors in proportion to their workforce. If nobody on shift can produce the training certificate, the officer knows immediately how seriously the system is taken.
Is the layout as declared? The layout submitted with the application is compared to the building. Walls moved, rooms repurposed and a store converted into a production area are all common, and all noticed.
Flow, which is where most observations come from
The officer will walk the process from raw material intake to dispatch, looking for paths that should not cross:
- Raw materials and finished goods sharing a route or a store
- Personnel entering production without a proper change sequence, or change rooms that exist on the drawing but are used for storage in practice
- Waste leaving through the production area
- Returns and rejects held in the same space as released stock
- No physical quarantine for material awaiting test results
These are design problems more often than discipline problems, which is why a layout drawn by someone who has never read Schedule 4 tends to produce a plant that cannot pass an inspection no matter how well it is run.
Records, and the giveaway of the backdated file
Records are examined for whether they were written when the work happened. Experienced officers can tell, and the tells are consistent:
- An entire month of cleaning records completed in the same pen with the same handwriting
- Temperature logs with no variation at all across a season
- In-process checks recorded for a batch on a day the machine was under maintenance
- Corrective action columns that are always blank, which means either nothing has ever gone wrong or nothing is ever recorded
A record showing a deviation and a documented corrective action is far stronger evidence of a working system than a record with no deviations at all. Do not train your team to keep the file clean; train them to keep it true.
The records most commonly asked for are pest control, water testing, calibration, cleaning and sanitation, medical fitness of food handlers, in-process checks, batch records, and supplier approval with incoming material inspection.
Physical checks
Storage practice is examined closely: material off the floor and away from walls, first-in-first-out actually followed rather than posted on a sign, chemicals stored well away from food, and allergen containing materials segregated.
Water gets specific attention, because it is both an ingredient and a cleaning medium. The officer wants a current report from an NABL accredited or FSSAI notified laboratory covering the water actually used in the process.
Personnel hygiene is assessed on the floor rather than in the policy: hand washing at entry, protective clothing worn correctly, no jewellery, and medical fitness records that are current.
The five observations we see most
- Records completed retrospectively rather than at the time of the activity
- Layout on the ground differing from the layout submitted with the application
- Water test report expired, or from a laboratory without the right accreditation
- Product categories on the licence not matching the products actually manufactured
- An FSMS plan that is a downloaded template describing a different factory
Every one of these is preventable at zero marginal cost, and every one of them costs real money once it has been written into an inspection report.
How to prepare properly
Run a mock inspection a fortnight before you expect a visit, using someone who did not write your documentation. Ask them to trace one batch end to end: purchase order, incoming inspection, storage, batch record, in-process checks, finished goods testing, label, dispatch. If the trail breaks anywhere, that is the same place a real inspection will break.
Then fix the gap in the system rather than the file. Fixing the file works once. Fixing the system works every time, and under a risk based framework it earns you fewer visits.