1. Define the request and the evidence boundary

Confirm the audit scope, relevant period, requested records and responsible contact. Identify the requirements or criteria being assessed and who can clarify them. Different assessments may need different evidence. A generic checklist is a starting point for discussion, not confirmation that it covers an applicable standard.

Build a request list that records the item, owner, source and status. Distinguish records already reviewed from those still being collected or questioned. Agree how the reviewer will receive the evidence using your organization's access and disclosure process.

2. Check records before presenting them

Locate the relevant instruction and revision, approvals where applicable, and completed records for the period. Check identifiers, dates and source context. Retrievable information is not necessarily correct or sufficient for the request. Record gaps and assign follow-up rather than treating a status indicator as proof of conformity.

Do not assume that an outside reviewer has direct access to every system or that a particular read-only portal is available. Demonstrate the current viewing/export options and confirm the agreed access arrangement before sharing records.

3. Explain history and close open questions

A record history can help explain who performed an action and when, depending on what the system captures. Check the actual fields, scope and permissions. It may not describe every event or the reason behind a decision. Supplement it with the relevant decision evidence rather than assuming a log automatically proves compliance.

Illustrative workflow: a team prepares evidence for a sample procedure change. It locates the relevant revision, approval record and staff acknowledgement where applicable. It identifies an incomplete record, assigns the question to its owner and records the resolution or remaining limitation. This is a proposed preparation task, not a guaranteed audit result.

Test the process before the assessment

Run a representative request from start to finish and note time spent, help needed and gaps. Agree who responds to questions and follows up actions after the review. Compare the work with a consistent baseline if you want to assess whether a process change helped.

The QMS software evaluation guide helps structure a demonstration. Use the document and record review guide for version and source checks. Confirm current software options rather than assuming automatic collection, complete audit logs or standard-specific checklists.

Reference: ISO's public quality-management overview, checked 7 October 2026, supplies general context. Detailed assessment criteria need the applicable requirements and qualified review. Technology supports preparation; it does not establish an audit outcome or year-round certification readiness.