Audit Management
Mobile audits use tablets or phones to plan, perform and record internal, supplier or process audits at the point of work, capturing checklist responses, photos and findings that link directly to nonconformance and corrective action.
Read the full summary
The device improves evidence capture; the auditor's judgement still determines findings.

On this page · 18 sections
- 1What a mobile audit is
- 2Plan the audit programme
- 3Controlled checklists
- 4Capturing evidence
- 5From finding to action
- 6Connectivity and data integrity
- 7Common pitfalls
- 8Inside V5: audits connected to NCR and CAPA
- 9Explain it for your operation
- 10Types of audit that suit mobile capture
- 11Auditor competence and independence
- 12Trending findings across audits
- 13A practical mobile audit
- 14Rolling out mobile audits without losing control
- 15A proportionate implementation plan
- 16Internal review questions
- 17Records and evidence to retain
- 18Questions to ask when evaluating software
How does Audit Management apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What a mobile audit is
A mobile audit runs the audit programme on a handheld device: the auditor opens a scheduled audit, works through a controlled checklist, records observations, attaches photos and raises findings on the spot.
It replaces paper checklists that are later retyped, reducing transcription errors and delay.
02Plan the audit programme
ISO 19011 describes an audit programme with objectives, scope, criteria, frequency, competence and records. Mobile tools should carry that structure rather than random checklists.
Schedule audits by risk: areas with recent deviations, supplier changes or new processes deserve more attention.
03Controlled checklists
Checklists should be approved, versioned and tied to criteria such as procedures or standards. Questions should ask for evidence, not just yes/no.
Allow auditors to record observations outside the checklist; good audits follow the evidence.
04Capturing evidence
Photos, document references, batch numbers and interview notes make findings verifiable. Record time, location and auditor identity.
Respect photography restrictions in clean areas and supplier sites, and avoid capturing personal or confidential information unnecessarily.
05From finding to action
Classify findings consistently, assign owners and due dates, and link to nonconformance or CAPA where warranted. Track open findings until verified closed.
The value of the audit lies in follow-through, not the report.
06Connectivity and data integrity
Production and warehouse areas may have poor connectivity. Understand whether the tool works offline and how later synchronisation is recorded.
Audit records should be attributable and protected against unrecorded change.
07Common pitfalls
Pitfalls include checklist fatigue, auditing only easy areas, overusing photos without context and leaving findings unassigned.
Rotate auditors, review checklist effectiveness and trend findings across audits.
08Inside V5: audits connected to NCR and CAPA
V5 supports internal and supplier audits whose findings route to nonconformance and CAPA records, with evidence and audit history on tablets used on the floor.
V5 does not decide whether something is a finding or its severity; the auditor and quality team do.
09Explain it for your operation
Convert one existing paper audit into a controlled mobile checklist, run it in one area for a month and compare time to close findings with the previous paper process.
Adjust questions that consistently produce no useful evidence.
10Types of audit that suit mobile capture
Internal system audits, layered process audits on the shop floor, GMP walk-throughs, supplier audits, line-clearance checks and housekeeping or 5S audits all benefit from structured capture at the point of observation.
Each type needs its own criteria and frequency. A short layered audit performed daily by supervisors is different from an annual system audit by a trained, independent auditor, and the records should make that clear.
11Auditor competence and independence
ISO 19011 emphasises auditor competence and objectivity. Auditors should not audit their own work, and should be trained in the criteria and in interviewing and sampling techniques.
A tablet can prompt the right questions, but it cannot judge whether evidence is sufficient. Calibration sessions where auditors compare findings on the same area improve consistency.
12Trending findings across audits
Consistent finding categories and locations let quality teams see recurring themes across areas, shifts and suppliers. Recurring minor findings may indicate a systemic weakness that deserves a CAPA.
Report trends with the number of audits performed, so a rise in findings caused by more auditing is not mistaken for deterioration.
13A practical mobile audit
An auditor performing a line-clearance audit finds a previous batch's label roll on a packaging line. She photographs it, records the line and batch, and raises a finding linked to the line-clearance procedure.
The finding becomes a nonconformance assigned to the packaging supervisor; investigation leads to a clearer roll-return step, and a follow-up audit verifies it.
14Rolling out mobile audits without losing control
Moving audits from paper to tablets or phones changes how evidence is captured, so the rollout should be planned like any other process change.
- Start with one checklist, such as a GMP walkthrough, and convert it question by question with clear pass, fail and not-applicable rules.
- Decide which questions require a photo, comment or measurement when they fail, so findings are useful later.
- Confirm what happens when the device is offline and how records sync without duplicates.
- Agree who can edit a completed audit and make sure changes are visible in the history.
- Link failed questions to corrective action so findings have an owner and a due date.
- Run paper and mobile side by side for a short period and compare results before retiring paper.
Measure success by how quickly findings are closed and how many repeat, not by how many audits are completed. A fast audit that produces no follow-up has not improved quality.
15A proportionate implementation plan
- Confirm the applicable requirement, product scope and decision owner.
- Map the current method and the records already available.
- Define terms, responsibilities, evidence and exception handling in the approved procedure.
- Pilot the method on one representative process and challenge a difficult exception.
- Train affected roles, approve the change and monitor whether the method works as intended.
- Review after significant change and retain a transparent history of decisions.
Scale the formality to risk and complexity. A small operation still needs clear responsibilities and reconstructable evidence, while a multi-site operation also needs harmonised definitions, governance and comparison rules.
16Internal review questions
- Can a reviewer identify the source, owner, method and current approved version?
- Do summaries reconcile to original records and include unfavourable or missing evidence?
- Are exceptions visible, assessed and linked to the affected material, product or process?
- Are actions assigned, overdue items escalated and effectiveness reviewed?
- Have changes in product, supplier, equipment, method or regulation triggered reassessment?
- Does the record distinguish system support from the decision an authorised person made?
17Records and evidence to retain
- Approved scope, definitions and responsibilities for Mobile Audits.
- Source records and identifiers that let a reviewer reconstruct the work.
- Methods, assumptions, calculations, exclusions and any data-quality limitations.
- Exceptions, investigations, decisions, approvals and resulting actions.
- Version history showing when the approach changed and why.
Records should be proportionate to the decision and usable by someone who was not present. Preserve original evidence and corrections rather than replacing it with an unexplained summary.
18Questions to ask when evaluating software
- Can users trace every summary value back to its source record and version?
- How are roles, permissions, signatures and corrections recorded?
- Can the workflow reflect our approved procedure without inventing a universal rule?
- What happens during an outage, and how are later entries distinguished?
- Can we test the highest-risk exception with realistic data before committing?
- Which decisions remain explicitly assigned to an authorised person?
Frequently asked questions
Q.What is Mobile Audits?+
Mobile audits use tablets or phones to plan, perform and record internal, supplier or process audits at the point of work, capturing checklist responses, photos and findings that link directly to nonconformance and corrective action. The device improves evidence capture; the auditor's judgement still determines findings.
Q.Is Mobile Audits required in every operation?+
The applicable product rules, market, risk and approved quality system determine what is required. The method should be justified for the operation rather than copied without context.
Q.Can software make the final decision?+
No. Software can organise records, calculations and workflow, but authorised people remain responsible for planning commitments, scientific, quality and disposition decisions.
Q.How should a site start?+
Choose one bounded process, define the decision and evidence, test the method with real records, correct gaps, then expand under change control.
Q.What evidence should be retained?+
Keep the approved method, source records, assumptions, exceptions, review, decision, approval and any resulting action with enough context to reconstruct the work.
Q.Can mobile audit photos be used as evidence?+
Yes, if they are captured within the audit record, linked to the question and finding, and protected from undetected change. Sites should define what a photo must show and avoid capturing people's faces or confidential information unnecessarily.
Primary sources
Explore this topic
Audit Management sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.
Where each shop-floor system fits and what it owns vs the ERP above it.
Root-cause toolkit, SPC, capability and the rest of the QA practitioner's bench.
Want to see how Audit Management could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
