V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryInspection Record
Records · The complete guide

Inspection Record

In short

Connect manufacturing inspection evidence to the exact item and criteria revision without confusing an observed result with a human disposition.

4,126 words · ~19 min read
Inspection Record illustration linking a machined housing, a digital caliper and recorded dimensional observations
Inspection evidence connects the item, applicable criteria and observations; disposition is a separate decision.
On this page
  1. 01What an inspection record establishes
  2. 02Inspection record versus neighbouring quality artifacts
  3. 03The fields that make inspection evidence interpretable
  4. 04From recorded observations to human decisions
  5. 05Worked case: an incoming catheter-hub dimension
  6. 06Worked case: an electrical result after rework
  7. 07Worked case: final flow evidence with a validity concern
  8. 08Regulatory scope and the limits of guidance analogies
  9. 09Preserving the record across systems and interruptions
  10. 10Failure modes that make an inspection record misleading
  11. 11A practical implementation and review check
On this page · 11 sections
  1. 1What an inspection record establishes
  2. 2Inspection record versus neighbouring quality artifacts
  3. 3The fields that make inspection evidence interpretable
  4. 4From recorded observations to human decisions
  5. 5Worked case: an incoming catheter-hub dimension
  6. 6Worked case: an electrical result after rework
  7. 7Worked case: final flow evidence with a validity concern
  8. 8Regulatory scope and the limits of guidance analogies
  9. 9Preserving the record across systems and interruptions
  10. 10Failure modes that make an inspection record misleading
  11. 11A practical implementation and review check
AI · Explain it for MY operation

How does Inspection Record 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.

Your scale

01What an inspection record establishes

An Inspection Record is a manufacturing evidence artifact that links an inspected item, lot or serial number to the exact criteria revision, inspection method, observations, inspector and time. It answers a practical question: what evidence exists that an identified manufacturing subject was examined against identified criteria? Its value lies in those connections, rather than in the document’s title or layout.

The artifact can arise during incoming inspection, an in-process examination or final inspection. Each context identifies a different subject or manufacturing stage. This article concerns the resulting evidence, not the sequence of inspection activities; the evidence model below explains the relationship between inspected samples and their source population.

Paper, electronic and hybrid records can carry the same evidence relationships. A signed paper sheet may reference an instrument file, while an electronic entry may reference a controlled drawing and retained images. The record need not contain every supporting file or reproduce the specification. As a practical design principle, its references should let a later reader retrieve the particular supporting material associated with that examination, rather than merely the latest available version.

Here, inspection record is a manufacturing practice term—not a universal statutory form, generic checklist, complete device history record, or vehicle or building inspection report.

02Inspection record versus neighbouring quality artifacts

In manufacturing practice, these artifacts answer different questions, even when stored together. An inspection plan describes intended checks; a completed inspection record identifies the checks and evidence actually recorded. Document titles alone do not establish that distinction.

ArtifactPrimary question answeredRelationship to the inspection recordWhat it does not establish by itself.
Inspection recordWhat was inspected, against which criteria, with what observations?The evidence artifact for the identified inspection.Completion of every manufacturing activity or authorization to release product.
Inspection planWhat checks are intended?Defines planned characteristics, methods and criteria referenced by the record.That any planned check actually occurred.
Blank checklist or formWhere should information be entered?Provides a structure for capturing inspection evidence.Results, execution or the identity of inspected product.
Test recordWhat did a particular test produce?May supply supporting data or itself function as an inspection record.Coverage of characteristics outside that test.
Supplier certificateWhat does the supplier attest about identified material?Provides supplier-origin evidence associated with the received material.That the receiving manufacturer performed an inspection.
Nonconformance recordWhat departure was identified and how was it addressed?Links the exception to relevant inspection evidence.The complete set of inspected characteristics and observations.
Device history record or broader manufacturing historyWhat manufacturing activities and decisions concern this product?Contains or references inspection records alongside other production evidence.Detailed inspection results merely because a history entry exists.

A completed checklist can serve as part of an inspection record when its entries establish the necessary context. Test records and inspection records can overlap; they are not mutually exclusive categories. Broader histories, such as a device history record or batch record, contain or reference inspection evidence. A nonconformance record instead links to that evidence to address a specific departure.

03The fields that make inspection evidence interpretable

The following field groups are a practical evidence design, not mandated fields or a required database schema. Their purpose is to let a later reader reconstruct what was inspected, against which criteria, and how each observation was obtained.

Inspected subject. Give the inspection record its own identifier: it identifies the evidence artifact, not the product. Separately identify the item or part, applicable lot, individual serial and sample. A sample identifier points to the actual inspected unit or specimen and its source population. Record which units were sampled; keep their observations distinguishable from any subsequent conclusion about the larger lot. A lot identifier does not replace a serial identifier where unit-level traceability is needed. This model prescribes no sample size.

Applicable criteria. Use criteria_revision_id to identify the exact controlled criteria set applied. specification_revision identifies the governing specification edition; characteristic_id identifies the particular feature within that context; method_revision identifies the procedure edition used to inspect it. Preserve these revisions directly or through resolvable controlled references. A link that silently opens the current edition cannot establish which criteria applied at inspection. Keep characteristic identifiers interpretable within their revision context when specifications change.

Inspection event. Capture inspector identity and performance time with time-zone context. Keep later entry, review and decision times separate rather than treating an upload timestamp as the inspection time. Where equipment is used, identify the instrument and reference relevant status evidence applicable when the work occurred, such as calibration status and suitability for the measurement. This supports attributable recording without implying that every unaided visual observation needs an instrument reference.

Individual observations. For each characteristic, preserve its description, relevant inspection location or orientation, acceptance rule, method, applicable unit and observation. A numerical measurement pairs a value with its unit; a categorical observation records the observed condition; a calculated result retains its inputs, units and calculation definition or revision. Keep observed values, not merely a summarized pass indication. Numerical limits are not applicable to every visual characteristic. Link raw files or images to the specific observation they support, with enough file and capture context to identify their origin.

Exceptions and human decision references. Link exceptions to the affected event, sample or observation rather than leaving them as unattached notes. Reference subsequent human decisions by identifier and retain their author and time. Interpretation of acceptance and disposition belongs in the following section.

Practical evidence relationships: Inspection record → inspected subject + inspection events Source population → identified sampled units → observations Inspection event → inspector + performance time + instrument evidence Observation → characteristic + criteria revision + method revision + raw evidence Exception and human decision references → affected evidence

The arrows represent traceable relationships, not mandatory database joins. This traceability data model allows an event to contain multiple observations while each remains connected to its subject and criteria.

Inspection record evidence relationships

Inspected subject

Identifies the inspected manufacturing scope.

  • subject_id
  • item_id
  • lot_id
  • serial_id
  • configuration_revision

Criteria revision

Preserves the applied evaluation basis.

  • criteria_revision_id
  • specification_revision
  • method_revision
  • characteristic_id
  • acceptance_rule

Inspection event

Connects subject, criteria and provenance.

  • inspection_id
  • subject_id
  • criteria_revision_id
  • inspector_id
  • performed_at
  • instrument_id

Observation

Stores characteristic-level evidence and units.

  • observation_id
  • inspection_id
  • characteristic_id
  • observed_value
  • unit
  • evidence_uri

Exception

Links concerns to affected evidence.

  • exception_id
  • inspection_id
  • observation_id
  • nonconformance_id
  • status

Human decision

Attributes an explicit, scoped outcome.

  • decision_id
  • inspection_id
  • decision_scope
  • decision_type
  • outcome
  • approver_id
  • approved_at
Identifier links connect subjects, criteria, observations, exceptions and separately recorded human decisions.

04From recorded observations to human decisions

An inspection record supports a decision without being the decision itself. In manufacturing practice, its lifecycle connects a defined inspection scope to evidence and an authorized human conclusion. The following model describes the artifact, not a complete inspection workflow or a universal legal requirement.

Identify item and inspection scope → bind applicable criteria revision → capture evidence → link exceptions → review evidence → record scoped human decision → preserve later amendments.

  • Observation: what was seen or measured, before drawing a conclusion about acceptability.
  • Characteristic evaluation: comparison of the evidence with the applicable criteria for that characteristic.
  • Inspection acceptance: an authorized human decision about the defined inspection scope, not everything known about the product.
  • Disposition: the decision determining how affected material is treated, such as rework, return or scrap.
  • Product release: a separate authorization concerning product availability for its intended next use or distribution; an inspection acceptance does not itself establish release.

Evidence review asks whether the observations support the proposed conclusion: are they attributable, interpretable and applicable to the inspected material? An unresolved deviation can constrain that conclusion even when individual results appear acceptable.

Record completeness and material status are independent dimensions. A complete record can document unacceptable material. Conversely, an apparently conforming measurement can sit within an incomplete record or one with unresolved validity concerns. Neither a completed form nor a passing value alone establishes readiness for release.

Useful decision metadata includes decision type, scope, outcome, authorized person, decision time, rationale where appropriate and linked exceptions. Local procedures determine authority; the inspector may also be the decision maker. Where release is documented separately, link the inspection conclusion to the release authorization record rather than treating the two as interchangeable.

Preserve amendment lineage by connecting a later correction to the original evidence, its reason and any affected decision. Make clear whether the correction changes the conclusion or only its supporting description, without silently replacing the earlier account.

Lifecycle of the inspection evidence
  1. 1
    Identify scopeName the item, lot, serial and inspected samples.
  2. 2
    Bind criteriaAssociate the exact specification and method revisions.
  3. 3
    Capture evidenceConnect observations, units, inspector, time and supporting artifacts.
  4. 4
    Link exceptionsConnect discrepancies to their affected evidence and subjects.
  5. 5
    Review basisAssess completeness, interpretability and unresolved concerns.
  6. 6
    Record decisionAn authorized human records the scoped outcome.
  7. 7
    Preserve lineageKeep amendments and reinspection linked to original evidence.
Record development and review, not an inspection procedure or automatic product-release sequence.

05Worked case: an incoming catheter-hub dimension

Assume a hypothetical medical-device manufacturer receives catheter hubs identified by the supplier’s lot identifier. A controlled local sampling plan identifies the units examined; drawing revision C defines the relevant outside-diameter criterion in mm. The example assumes a valid measurement and an observed diameter above the applicable upper limit. These are illustrative local arrangements, not mandated tolerances or sampling rules.

Follow sampled hub H through its sample identification and handoff to the inspection entry below. Here, d represents the recorded numerical diameter and U the drawing’s numerical upper limit; the actual record contains those values, not merely the symbols.

EntryExample record content
IdentitySupplier lot identifier; sampled hub H; local sampling-plan reference and revision
Characteristic and criterionOutside diameter at the drawing-defined location; drawing revision C; upper limit U mm
Method and equipmentLocal diameter-measurement method revision B; instrument asset reference linked to its status at use
Observation and provenanceDiameter d mm, with d > U; inspector identity and measurement timestamp
ExceptionDimensional criterion not met; linked nonconformance identifying hub H and its supplier lot

Calculate the upper-limit margin as U mm − d mm = (U − d) mm. Because d > U, the margin is negative: this observation does not meet the dimensional criterion. Retain the value and margin with the drawing feature so the reviewer can identify which characteristic caused the exception.

The nonconformance links back to this observation rather than replacing it with a lot-level failure label. The authorized reviewer places the received lot on hold. The designated disposition authority decides its treatment under the manufacturer’s procedure, using the sample-to-population relationship described in the evidence model. No sampling acceptance rule is inferred from this example.

06Worked case: an electrical result after rework

Assume a hypothetical medical-device pump subassembly undergoes a nondestructive electrical continuity measurement, with resistance recorded in Ω. The manufacturer’s controlled method specifies the connection points, measurement conditions and upper acceptance limit applicable to the identified assembly configuration. For this example, the same method and criterion remain applicable after authorized connection rework; no numerical limit is assumed.

The initial observed resistance exceeds that upper limit. Record the actual measured value and unit, not merely a failed status, against the assembly’s serial number and pre-rework state. Identify the exact method and acceptance-criteria revisions, instrument, inspector and measurement time. Link this observation to the resulting exception record, then link that exception to the authorization defining the permitted connection rework.

After the authorized work is completed through the applicable rework routing, create a distinct reinspection event. Retain the same assembly serial number but identify its changed state through the completed rework record. Link the event directly to the original failed observation and record the new resistance in Ω, together with its measurement provenance and applicable criteria revisions. Assume this subsequent resistance meets the criterion.

The later result does not replace the earlier result: the physical assembly changed between measurements. Each observation describes a different product state. Preserve both so a reviewer can distinguish an unsuccessful original connection from an acceptable reworked connection. This is genuine reinspection, not correction of a transcription error; the FAQ addresses that separate decision. A record view can show the current outcome while keeping the earlier observation and its relationships accessible.

Using the decision distinctions covered above, an authorized human reviews the rework authorization, completion evidence and linked reinspection result, documents the decision and permits the assembly to proceed to the next operation.

07Worked case: final flow evidence with a validity concern

Assume a hypothetical final inspection of a serial-numbered medical-device pump. The local method measures delivered volume in mL over elapsed time in min and derives average flow in mL/min. The inspection record identifies the pump serial number, method revision and exact acceptance-criteria revision. Assume the calculated flow falls within that revision’s specified band.

Let V be the recorded delivered-volume observation in mL and t the recorded positive elapsed-time observation in min. The calculation is explicit: average flow = delivered volume ÷ elapsed time = V mL ÷ t min = (V ÷ t) mL/min. Preserve both observations alongside the calculated result, rather than retaining only an in-band indicator. This lets the reviewer reconstruct the calculation against the applicable criteria revision.

Before product release, review of an equipment check raises doubt about the volume-measuring instrument’s validity when the inspection occurred. The numerical comparison remains in-band; the concern is whether the evidence supports acceptance. Relevant as-found calibration evidence helps assess the instrument’s condition without treating a later adjustment as proof of its earlier accuracy.

Link the instrument issue to this inspection record, its equipment identifier and the affected pump serial number. Assess whether other serial numbers inspected during the suspect period belong in the same impact assessment. Keep the original observations and calculated flow unchanged: an unresolved validity concern is not a measured out-of-band flow result.

Under the hypothetical procedure, the authorized reviewer holds acceptance pending impact assessment. Suitable replacement evidence from an authorized repeat inspection resolves the concern; the reviewer documents acceptance and links the replacement evidence to the original record. The disposition decision records that rationale, using the separate decision relationships described above.

08Regulatory scope and the limits of guidance analogies

For US medical-device manufacturing, consult the current text of the FDA Quality Management System Regulation for applicability. Do not substitute former Part 820 provisions or audit-document citations for a current-law analysis. Keep that analysis separate from the practical record-design choices described here; the QMSR versus ISO 13485 comparison provides related context. ISO 13485:2016, Medical devices — Quality management systems — Requirements for regulatory purposes, concerns medical-device quality management systems; it is not treated here as an inspection-record template.

For medical-device audits using MDSAP, the Auditing Technical Documentation section lists quality-assurance procedures and specifications, acceptance criteria, and quality-assurance equipment among its technical-documentation topics. Use this as an audit-guidance reference, not as a standalone statement of current US medical-device law. For record design, the useful connection is between the inspection evidence and the controlled documents that explain how it was generated and evaluated.

In NASA engineering practice, Table 5.3-1 of the Systems Engineering Handbook illustrates including the location of, or a link to, verification artifacts in verification reports. This is an engineering analogy for a retrievable evidence reference, not a US medical-device legal obligation or a prescribed manufacturer’s inspection form.

For pharma, supplements, food and chemicals, the proposed record structure remains manufacturing practice. Select fields and evidence relationships through the applicable jurisdiction, product category and controlled procedures—not through an assumption that sectors share legal fields, forms, sampling quantities or retention intervals. A practical quality-assurance process can distinguish the basis for each record element: an applicable obligation, a controlled procedural choice, or supporting information that makes the inspection interpretable.

09Preserving the record across systems and interruptions

A practical integration design assigns ownership before moving inspection evidence. Manufacturing or inventory records commonly own item and lot identity; controlled specifications own criteria and revision; instruments or manual-entry records originate observations; quality records hold exceptions; and authorized human review produces decisions. In MES–QMS integration, identify which record carries the authoritative decision rather than letting copied status fields become competing answers.

Use stable identifiers for the inspection, inspected item, source observation and linked exception. Retain the originating system and its event identifier when an observation crosses an interface. For derived values, preserve the input references, original values and units, transformation rule and version, and resulting units. MES–historian integration mappings can then distinguish an instrument observation from a calculated value without treating them as independent measurements.

  • Delayed imports: reconcile against original event identity and expected records; receipt order is not inspection order.
  • Duplicate transmissions: match the source system and event identifier before accepting another observation. Route conflicting payloads for review rather than silently overwriting or appending them.
  • Identifier mismatches: hold unmatched evidence for resolution instead of guessing the destination lot or serial.
  • Offline capture: retain local event identity and operator attribution, then reconcile uploaded records against the capture log.

Distinguish occurrence time, receipt time and correction time. Record time-zone context and investigate suspect sequencing through clock drift monitoring, rather than replacing the occurrence timestamp with import time. Recovery evidence should identify the interrupted transfer, affected records, reconciliation result, unresolved discrepancies and responsible reviewer. Preserve links between corrections and original events so a reviewer can reconstruct what changed. These are proposed manufacturing data-integrity controls, not universal legal requirements.

10Failure modes that make an inspection record misleading

A complete-looking inspection record can still invite the wrong conclusion. These practice-based controls target ambiguity in record structure, rather than adding more boxes to complete.

Misleading structureTargeted control
A current-specification link opens the latest criteria, obscuring the revision actually applied.Use a revision-bound reference that resolves to the applied criteria. During review, check the destination, not just the displayed document title.
A manually copied unit label makes an observation appear to use a different unit from the original measurement.Preserve the original value and unit together. Show any converted value separately, with its conversion basis; compare the entry against the original observation.
An aggregate result hides which samples were inspected and which observations contributed.Link the summary to identified sample-level results. Check that the linked sample set matches the population described by the summary.
An ambiguous characteristic name allows measurements from different locations to appear interchangeable.Use controlled characteristic identifiers tied to a drawing feature or defined measurement location. Check that operators can distinguish adjacent or similar features.
A broadly worded acceptance entry appears to approve a larger population or later manufacturing stage.Record the decision’s item or population boundary, inspection stage and supporting evidence references. Preserve the boundaries discussed in the decision section above; avoid labels that imply subsequent batch release.

A useful control review also challenges display defaults. A blank result should not look like a zero reading, and an omitted characteristic should not look like a completed visual inspection. Preserve the difference between not performed, not applicable, unavailable and an actual observation. For a conditional check, retain the condition that made it applicable or inapplicable. These are proposed record-design controls; the implementation exercise below tests whether the distinctions remain understandable to another reader.

11A practical implementation and review check

Test the proposed record model with a representative inspection record and its linked evidence. Ask an authorized reviewer who did not perform the inspection to reconstruct its basis without relying on the original inspector’s memory. Treat this as a usability exercise, not a statutory checklist or compliance assessment.

  • Can the inspected subject be identified?
  • Can the applied criteria be reconstructed?
  • Can each conclusion be traced to observations?
  • Are exceptions and decisions linked?
  • Can the original evidence still be retrieved after an amendment?

Have the reviewer demonstrate each answer by following the actual references, rather than accepting a statement that the information exists elsewhere. Include the amendment history in the exercise; a related audit trail review can help examine how changes remain attributable. Note broken references, ambiguous decision ownership and any point where reconstruction depends on an undocumented explanation.

Then check the same relationships against the worked cases above: does the incoming-material record distinguish inspected samples from the lot addressed by the decision? Does the rework case preserve the connection between the changed product and its reinspection? Does the final-flow case keep the validity concern visible alongside the calculated result and human decision? Revise relationships that cannot express these differences without overwriting evidence.

Assign responsibility for resolving each identified gap and repeat the reconstruction after changes. Clearer reconstruction, explicit responsibility and less ambiguity are design objectives—not promised performance results or compliance certification.

Frequently asked questions

Q.Can a supplier certificate replace our own incoming inspection record?+

A supplier certificate can support an acceptance decision, but does not document an inspection your manufacturer performed. Where the approved acceptance approach relies on certificate review, record that activity accurately: identify the certificate, covered lot, criteria checked, reviewer and decision. If your procedure calls for physical examination or measurement, retain those results through your incoming inspection record.

Q.When can one inspection record cover several lots or serial-numbered units?+

A shared record is practical when each result remains unambiguously attributable to its inspected population or individual unit. Use separate entries for lot or serial identity, applicable criteria revision, observations, exceptions and decision scope. For hypothetical medical-device housings, a shared dimensional report could cover several serials if every reading maps to the correct housing. Split the record when grouping would obscure different methods, criteria or dispositions. Serialized unit tracking helps explain the identity relationships; grouping alone does not establish traceability.

Q.What should happen if the specification changes after inspection but before disposition?+

Preserve the criteria revision actually used; do not relabel earlier results as inspections against the new revision. Before disposition, have an authorized person assess the change’s applicability to the affected product and whether existing observations support the revised criteria. For hypothetical medical-device components, a tighter dimensional limit might permit reevaluation of retained measurements, while a new characteristic could need additional inspection. Record the assessment, any supplemental results and the human decision. Keep this assessment connected to controlled recipe versioning where relevant.

Q.How should an incorrect reading be corrected after the record has been reviewed?+

Make a traceable correction rather than silently replacing the reviewed value. Preserve the original entry, identify who corrected it and when, explain the reason, and reference the evidence supporting the replacement. Distinguish a transcription error from a new measurement: remeasurement produces another observation, not proof that the original observation never occurred. Route the amended record for review and assess whether the correction changes acceptance or affects downstream product. These are practical data integrity controls, not permission to reconstruct missing evidence.

Q.Can the person who performed the inspection also approve its acceptance?+

Do not assume that performing an inspection grants acceptance authority. Check the applicable requirements and your approved role assignments before combining the responsibilities. Where that arrangement is permitted, use the decision references described above to record both roles accurately. Consider an additional reviewer for borderline results, unresolved exceptions or conflicts of interest. The QA disposition step explains the decision boundary. Keep the assigned authority visible in the record rather than inferring it from a signature alone.

Q.What should a reviewer do when an image or instrument file cannot be retrieved?+

First determine whether the missing file contains evidence needed to substantiate the recorded result or is merely a supplementary illustration. If it is essential, leave the affected acceptance decision pending and investigate retrieval, identity and file integrity. A filename or thumbnail does not establish the missing content. Document recovery attempts and assess whether justified reinspection is possible; do not assume later measurements reproduce the original condition. Use exception-based review to focus attention on the evidence gap without overlooking affected product.

Q.Can an unsampled unit be described as inspected when its lot was accepted?+

Use terminology consistent with the evidence model above. A report for an accepted connector lot can show its sampled-unit list and lot decision without producing individual inspection entries for untouched connectors. Where a customer asks for unit-level evidence, explain which characteristics were checked individually and which were assessed through the lot-level sampling plan. Preserve that distinction when exporting summaries or merging results; copying the lot’s status into every unit’s inspection-history field would misdescribe the actual examination.

Q.How should a manufacturer select a retention period for inspection records?+

Use a documented retention assessment rather than a convenient storage default. Identify applicable product and jurisdictional requirements, contractual commitments, and the records needed for investigations, complaints and traceability. Define the retention trigger as well as the duration, and address attachments, criteria revisions and instrument files needed to interpret the record. Coordinate disposal with any investigation or preservation hold. The practical objective is a retrievable, intelligible evidence set throughout its assigned life; record retention and archiving covers the broader controls.

Primary sources

  • FDA MDSAP Audit Approach AU P0002.009, 6 August 2024
  • NASA Systems Engineering Handbook Rev 2, engineering practice not medical-device law

Further reading

  • Medical Device eDHR Software
    Evaluate production-record software through a device build and human record-review example.
Software that covers Inspection Record
V5 Ultimate (FDA Compliance)
V5 Ultimate is a single-platform FDA compliance system for US manufacturers regulated under 21 CFR — pharma (210/211), medical…
Talk to us about Inspection Record

Want to see how Inspection Record could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
Medical Devices
Related terms
  • → Inspection Lot
  • → Incoming Inspection
  • → DHR

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC