---
id: KB-IC-003
url: https://app.codecontract.io/help/reports-and-quality/the-report-for-an-auditing-customer
idioma: en
categoria: informes-y-calidad
subcategoria: informes
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-IC-001, KB-CF-003]
citadoPor: [KB-IC-006, KB-IC-010, KB-IC-016]
---

# The report an auditing customer asks for

_What to show, in what format, and what not to send by email._

**Responde a:** compliance report for a customer · my customer audits me what do i send · documentary evidence for a customer audit · supplier report for a customer

A large customer auditing you does not want a pretty report: they want to verify that what you say is true. That changes what you send and, above all, how.

## The three blocks they actually want

| Block | What it demonstrates |
| --- | --- |
| Current status | How many of your suppliers are up to date, with the real number |
| How you control it | That there is a process, not a review when someone remembers |
| What happened when it failed | That you detect and correct, with concrete cases |

> [!IMPORTANT]
> The third block separates a credible report from a cardboard one. Nobody believes a report where everything is perfect: showing two non-conformities detected and closed demonstrates the control works far better than a spotless hundred per cent.

## Link or export

If they only need to verify, give scoped read access: they see what they need, what they looked at is logged, and no copy of your data sits in their inbox. Exporting is for when they must keep it.

> [!WARNING]
> Do not email a report with your own suppliers' documentation inside. That is third-party information they never authorised you to share with your customer, and it is overlooked far too easily.

## What makes next year's audit go the same way

**En corto**

- Producing it identically each time, so it is comparable.
- Numbers coming from the system, not from a separate spreadsheet.
- Being able to show the detail behind any figure if asked.

> [!NOTE]
> If the same customer audits you annually, build their questionnaire as a process. What they ask changes little, and the second time costs an afternoon.

**Can I give access only to their part?**

Yes, scoped to the audited scope.

**Is what they consulted recorded?**

Yes, with date and time.

**What if a figure does not add up?**

Better to say so before they find it: explaining it yourself is worth far more than justifying it afterwards.

## Ejemplos

**A company sends its customer a report showing 100% of suppliers up to date.**

- Adds the two non-conformities detected and closed that year

→ The auditor believes it, and the conversation moves from checking figures to discussing improvements.

**A client asks for a quarterly compliance report and it is prepared by hand each time.**

- Checks the period's already-calculated data
- Saves the format as a template
- Schedules it to go out by itself

→ The quarterly report stops taking an afternoon and goes out even in a busy week.

**Each client asks for the same figure in a different format.**

- Checks once and adapts on sending

→ The underlying work happens once.

**The report is sent and there is no record of what went out.**

- Records what was sent, with its date

→ It can be compared with next quarter's.

**The report includes other clients' data.**

- Reviews the scope before sending

→ Information does not cross.

**The client asks about a figure in the report and it has to be hunted.**

- Keeps the breakdown with the report

→ The question is answered in minutes.