What this is
What is a customer visit report?
What is a customer visit report?
A customer visit report is the record of a customer's visit or audit of your site: who came, what they toured, what records they reviewed, what they raised, and how the visit closed. It covers the whole visit, not just a complaint raised during it, which is what separates it from the complaint-specific templates in the same programme.
Who completes a customer visit report?
The host who accompanied the visitor, working with quality. The host has the walk-round detail; quality has the record-keeping discipline and the link to findings, CAPA and any trend review the visit needs to feed.
What happens to a finding a customer raises?
It is tracked the same way an internal finding is: given an owner, a due date, and a link forward to a finding or CAPA record. A customer finding closed only with a polite letter back, and no internal record of what changed, will be raised again at the next visit.
Scope
When is a customer visit report required?
This record covers the whole visit. Its most common misuse is being reached for only when the visit goes badly, so that a clean visit with no findings never gets logged at all.
Use this template when
- A customer or their representative is visiting or auditing the site, announced or not
- The visit has happened, or is about to; the record is opened at that point rather than reconstructed later
- Findings raised during the visit need an owner, a due date, and a link through to Finding or CAPA
- You are running the Nonconformance and Complaints programme and this is the visit step in it
- A returning customer's previous findings need to be checked as closed before the new visit starts
Do not use it for
- Customer Complaint Record, for a complaint that arrives on its own, outside a visit, with what the customer experienced and what they want
- Complaint Investigation Record, which traces a complaint back to the batch, line and shift that made the product
- Complaint Response Record, which records what was said back to the customer, when, and by whom
- Complaint Trend Review, which looks for a pattern across complaints rather than recording one visit
- An internal or second-party audit of your own management system, which is a different programme with a different owner
Compliance mapping
Which ISO 9001 cl.8.2.1 requirements does this satisfy?
ISO 9001 does not name a customer visit report as a required record. It requires that customer communication be determined and that nonconformity be corrected, and a visit report is where the evidence for both ends up.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.2.1 | Communication with customers, including handling of their property and specified requirements | Header |
| ISO 9001 cl.5.1.2 | Customer focus: ensuring customer requirements are determined, understood and met | Preparation |
| ISO 9001 cl.7.5.3 | Control of documented information, including records made available for review | Areas covered |
| ISO 9001 cl.10.2.1 | Reacting to nonconformity and evaluating the need for corrective action | Findings raised |
| ISO 9001 cl.9.1.2 | Monitoring customer perception of the degree to which requirements have been met | Outcome |
| ISO 9001 cl.9.1.3 | Analysis and evaluation of data arising from monitoring, including customer feedback | Outcome |
What it does not cover
- Customer Complaint Record, which is opened when a complaint arrives outside a visit and records what the customer experienced.
- Complaint Investigation Record, which traces a complaint back to the batch, line and shift responsible.
- Complaint Response Record, which records the specific communication sent back to the customer.
- Complaint Trend Review, which looks across complaints for a recurring cause rather than recording a single visit.
- The corrective action itself, which belongs in the CAPA record the finding links forward to, not in the visit report.
Global
Customer Visit Report requirements by country
A customer visit report is a contractual instrument more than a statutory one. What differs by region is which certification scheme a customer's audit is likely to be measured against, and how much weight regulators place on ISO 9001 certification itself.
FDA food safety regulation and buyer-driven certification (SQF, GFSI-benchmarked schemes)
No statute requires a customer visit report. Retail and foodservice buyers commonly require evidence of supplier audits as a condition of the commercial relationship.
The record exists to satisfy the customer's own supplier-approval programme, and its absence can affect standing as an approved supplier independent of any regulatory action.
BRCGS Global Standard for Food Safety, widely required by UK and Irish retailers
Customer and second-party audits are a recognised part of the supplier assurance model that BRCGS certification sits alongside.
A visit report that shows previous findings closed before the next visit is exactly the evidence a BRCGS or retailer audit will ask to see.
ISO 9001:2015
Clause 8.2.1 requires customer communication to be determined; clause 9.1.2 requires customer perception to be monitored.
A certification auditor will treat a maintained visit report as direct evidence for both clauses, and its absence as a gap in customer communication rather than a paperwork shortfall.
How to complete it
How to complete a customer visit report, step by step
The form prompts for what happened during the visit. The parts that determine whether the record is useful afterwards are what happens to what the customer raised.
The record is raised at the moment the visit happens rather than reconstructed from memory once the visitor has left. A report written the next week from recollection loses the sequence of what was toured, what was asked, and what was said in response, which is exactly the detail a returning customer's audit will probe.
This is asked as a preparation question rather than left to be discovered mid-walk, because an open finding from the last visit is the first thing a returning customer checks. Answering it honestly before the visit, rather than during it, gives the host time to close or explain the gap instead of being asked about it in the moment.
A report that lists only what went wrong reads as a defensive document even when the visit went well. Recording what the customer noted favourably is part of the same evidence base, and it is what makes a Passed outcome distinguishable from a visit where nothing was checked closely enough to raise anything.
A finding raised during the visit is not closed by writing a good response; it is closed by the action the finding link points to being verified. Give each finding an owner and a response due date at the point it is raised, and let it feed Finding or CAPA rather than being answered and forgotten inside the visit report.
What auditors find
Most common customer visit report findings
The customer visit report almost always exists after the visit; the shortfalls are in what it is missing and in what happens to the findings once the visitor has gone.
| Finding | Clause | What fixes it |
|---|---|---|
| Visit not logged when the outcome was clean, so only problem visits are on record. | ISO 9001 cl.9.1.2 | Raise the record for every visit regardless of outcome; use Passed rather than skipping the entry. |
| Previous findings from the last visit still open when the next one starts. | ISO 9001 cl.10.2.1 | Verify prior findings closed as a preparation step, not discovered mid-visit by the customer. |
| Finding raised with no owner, no due date, or no link to Finding or CAPA. | ISO 9001 cl.10.2.1 | Assign an owner and a response due date at the point the finding is written down. |
| Report reconstructed days after the visit, losing sequence and detail. | ISO 9001 cl.8.2.1 | Open the record during or immediately after the visit, inside the stated two-day window. |
| Response sent after the due date, or sent with no evidence the underlying action was verified. | ISO 9001 cl.9.1.2 | Track Response Sent against Response Due Date, and verify the action before marking it sent. |
| Visit report used to record a complaint the customer raised separately, outside any visit. | ISO 9001 cl.8.2.1 | Route a standalone complaint to Customer Complaint Record; reserve this record for the visit itself. |
Case in point
Case in point: the finding that came back a second time
A customer's technical team toured a packing line and raised a Major finding on allergen segregation in the culture room, along with two Observations elsewhere. The host completed the visit report the same afternoon, logged the finding, and sent a response confirming the segregation issue would be fixed. The response went out inside the customer's stated window and the visit was recorded as passed with findings.
Nine months later the same customer returned, unannounced, and raised the identical allergen segregation finding in the same area. The visit report from the first visit had never been linked forward to a CAPA record, so the fix described in the response letter had never been assigned an owner internally and was never verified as done. The letter had satisfied the customer on paper; nothing had actually changed on the floor.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- QUA-028
- Archetype
- Record
- Record ID
- CVR-2026-000
- Scoring
- Not scored
- Direction
- n/a
- Singleton
- No
- Basis
- ISO 9001 cl.8.2.1
- Links
- Feeds Finding, CAPA
- Tags
- Quality, Customer
- Sections
- 5
- Fields
- 39
- Follow up fields
- 0
- Repeating sections
- 1
- Links out
- 3
Header
11 fieldsVisit ID*
Auto sequence. Format CVR-2026-0000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Visitor Organisation*
Visit Type*
Routine visit, technical audit, unannounced audit, new business or complaint follow up.
Visit Date*
Host*
Number Of Visitors*
Preparation
6 fieldsAdvance Notice Given*
Agenda Received*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Previous Findings Closed Before Visit*
Open findings from the last visit are the first thing an auditor checks.
- Yes, all3 pts
- Most1 pt
- No0 pts
Visitor Induction Completed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
GMP Requirements Explained*
- Yes3 pts
- No0 pts
Allergen And Health Declaration Completed*
- Yes3 pts
- No0 pts
Areas covered
4 fieldsAreas Toured*
Records Reviewed
Staff Interviewed
Product Sampled
Findings raised
Repeats7 fieldsFinding Description*
Finding Grade*
- Critical0 pts
- Major1 pt
- Minor2 pts
- Observation3 pts
Area
Response Due Date*
Owner*
Finding ID
Links to FDN-015 Finding ID
CAPA ID
Links to FDN-014 CAPA ID
Outcome
11 fieldsOverall Outcome*
- Passed3 pts
- Passed with findings2 pts
- Conditional1 pt
- Failed0 pts
Score Given
Findings Raised*
Positive Observations
Response Due Date*
Response Sent
Next Visit Expected
Host*
Signature*
Quality Manager*
Second Signature*
QUA-028 · record IDs look like CVR-2026-000 · Feeds Finding, CAPA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The report itself gets written. What slips is the loop back: whether a finding actually reached CAPA, and whether the response sent to the customer matches what was verified internally.
Holds the visit report against the site register, checks previous findings closed before the next visit, and routes new findings to Finding or CAPA.
Watches response due dates against what has actually been verified, and flags a response sent with no completed action behind it, before it goes to the customer.
Confirms GMP and allergen induction was actually delivered to the visitor, rather than the box being checked from memory.
Keeps the records a visitor reviewed, and the response letter that followed, attached to the same visit for when the same finding is asked about again.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Customer Visit Report definitions and key terms
- Finding grade
- The severity a visitor assigns to something raised during the visit: Critical, Major, Minor or Observation, ranked in that order of consequence.
- Positive observation
- Something the customer noted favourably during the visit, recorded alongside any findings so the report is not only a list of problems.
- GMP
- Good Manufacturing Practice: the site's basic hygiene and conduct rules that a visitor is inducted into before entering production areas.
- CAPA
- Corrective and Preventive Action: the record that carries a finding's root cause and fix through to verified closure, which a customer finding links forward to the same as an internal one.
- Response due date
- The date by which the customer expects to hear back on a finding, tracked separately from whether the underlying action has actually been completed.
FAQ
Frequently asked questions about customer visit report
What is a customer visit report based on?+
It is built against ISO 9001 clause 8.2.1, customer communication, and connects to clause 9.1.2, monitoring customer perception, and clause 10.2.1, reacting to nonconformity, for the findings a visit raises.
How is a customer visit report different from a customer complaint record?+
A customer visit report covers the whole visit, whatever the customer came to look at, and can close with no findings at all. A customer complaint record exists only when a complaint arrives, whether or not a visit was involved. Using the visit report for a standalone complaint, or the complaint record for a routine audit, produces records that are hard to report on later.
What sections does the customer visit report contain?+
Five: header, preparation, areas covered, findings raised, and outcome. Together they hold 39 fields, 29 of which are required, with findings raised repeating for each item the visitor noted.
What happens to a finding a customer raises during a visit?+
It is given an owner and a response due date on the spot, and linked forward to Finding or CAPA the same way an internally-raised finding is. A response letter to the customer is not the same as verifying the underlying action was completed.
Does a clean visit with no findings still need a report?+
Yes. Overall Outcome includes Passed for exactly this reason. A record that only exists for visits that went badly leaves no evidence of the routine visits that did not, which matters if the relationship or the certification is later questioned.
Can the customer visit report template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the links to Finding and CAPA come with it. Most sites install it as it is, run it through a few visits, then adjust the areas and records-reviewed options to match their own layout.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Nonconformance and Complaints
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Product Nonconformance Report
Records product that does not meet specification
Process Deviation Report
Records a process that ran outside its set limits, even where the product still passed
Hold and Release Record
Places suspect product on hold and records the decision to release, rework or scrap it
Rework Authorization
Authorises rework on nonconforming product and sets out exactly what will be done
More in Complaints
Customer Complaint Record
Records a complaint from a customer, with what they experienced and what they want
Complaint Investigation Record
Investigates a complaint back to the batch, line and shift that made the product
Complaint Response Record
Records what was said back to the customer, when, and by whom
Complaint Trend Review
Pulls together complaints over a period to show the patterns behind them
Customer Feedback Record
Captures feedback that is not a complaint, including praise, suggestions and survey results
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 clauses 8.2.1, 9.1.2, 9.1.3 and 10.2.1
- BRCGS Global Standard for Food Safety, supplier and customer audit provisions
- GFSI-benchmarked scheme requirements for supplier assurance
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.