How to prepare an audit file without rebuilding it each visit

Start with a plain list covering the site master file, organisation chart, approved vendor list, equipment qualification files, water system logs and HVAC differential pressure charts. Add stability chamber records, the training matrix, the calibration schedule, the CAPA tracker, the annual product quality review and recent batch records for each product. Writing the list takes an afternoon, but it shows at once which registers are current, which are a year behind and which nobody has opened since the last visit.

Next to each item, write where it lives today, and expect many to sit in three places at once: a folder, a spreadsheet and someone’s head. Mark the memory-only items.

That marked list is your real plan. Treat it so.

Audit folders hold PDF copies. Copies go stale. A linked record holds one version. A deviation links to its batch, its equipment, its investigation and its corrective action, so changing one place changes the view everywhere.

The keys are few: batch number, lot number, equipment ID, employee ID, vendor code and SOP number, each of which every register should carry in an identical format. With those keys in place, a question like which batches ran on the blender in March is answered from one screen without opening a single folder. Where a vendor code, an equipment ID or an employee number is typed differently in two registers, the link breaks and the report silently omits that record. Clean the codes first.

Fix the keys first. Label the sieve. Software cannot link a sieve in the sifter room or a stability sample in the chamber that nobody labelled, however carefully the registers are cleaned.

Set standing reports. Keep them few. Overdue calibrations, expired training, open deviations past their due date and vendors without a current qualification should all appear in reports that the QA lead reviews every month. The monthly review leaves a dated trail, which shows an inspector that the system is read routinely and not only before a visit.

The notice arrives. The work is checking, not building. You print the training matrix from the system instead of reconciling three sheets, and the gaps you find are the ones you already know about.

Stamp each report with its review date. Inspectors read that stamp as routine.

Name who answers questions on each area. The QA lead covers the quality system and OOS investigations, the production head covers granulation through to blister packing, and the warehouse head covers lot status and quarantine. The maintenance engineer covers calibration and the water loop.

Rehearse a mock inspection once a year. Invite a retired QA manager or a colleague from the sister plant to play the inspector, and ask someone from another department to request five records at random. Time how long each takes. Slow answers show where links are weak. The mock inspector should ask awkward questions, such as the training record of the analyst who ran one assay or the calibration certificate behind a balance used last March.

Give each person read-only access to their own area for the day, so nobody edits a record while an inspector is watching the screen. Nothing more.

Enter each observation as a record that names its owner, carries a deadline and links to the evidence of correction, such as a revised SOP or a requalified instrument. Never leave it in the report alone.

Review open observations at the monthly QA meeting. When the next inspector arrives, you can show not only the finding but also the closure, the date and the check that the correction held, without any photocopy hunt.

Do one thing this week: pick the three records on your list that live only in memory and give each an owner.