PlaybookExecutive3 weeks · 8 stepsUpdated 1 November 2026
Start three weeks out: get the auditor's checklist, give every line one owner and a date, and collect evidence from where it already lives. Review open items twice a week and chase supplier documents first. By audit day, the work is one folder and a calm walkthrough, with no late-night scramble.
Who it is for, and how long it takes
Who it is for
How long
What you need
What you end with
Executives and quality heads preparing for a buyer, brand or vendor audit.
Three weeks, with two short reviews a week.
The auditor's checklist or last year's report, access to where records are kept, and one owner per area.
Every checklist line backed by a file in one folder, open gaps named with owners, and a short note for next time.
Key takeaways
An audit war room is usually three weeks of missed follow-ups packed into three days. Start early and it is not needed.
Every checklist line needs one owner, one date and a named piece of evidence.
Evidence counts when you can open it. A colleague saying it exists is a follow-up.
Brand and vendor audits ask for evidence that usually exists already, spread across inboxes, shared drives and someone's desk. The war room happens when nobody collects it until the week of the audit. The steps below spread that work over three weeks, with clear owners and two short reviews a week. In the example, Vaultex is preparing for an Adidas vendor audit next month.
Worked example. The examples use Vaultex, a safety-footwear manufacturer in Greater Noida and GeniOS's first design partner. The buyers, orders and dates are for illustration only.
PrepBefore you start
Line these up before week one.
The audit date confirmed in writing, plus the auditor's checklist or scope, or last year's report.
One executive who owns the whole audit and can get an answer from any team the same day.
Named owners for each area: quality, production, purchasing, finance and dispatch.
One shared audit folder, with a file name or subfolder for each checklist line.
A list of documents you need from outside the company, such as supplier certificates.
Two 30-minute review slots a week for three weeks.
One person outside the team who will run the mock walkthrough in week three.
StepsThe steps
3 weeks · 8 steps
Get the checklist early
Ask the brand for its checklist or audit scope three weeks or more before the date. If none is shared, start from last year's report. At Vaultex, the Adidas audit will ask for IS 15298 test reports, batch records and raw-material certificates.
Give every line one owner
Turn the checklist into a list where every line has one owner, one date and the evidence that proves it. Quality owns the test reports, Anushka in production owns batch records, and Mayank in finance owns invoices and payment records. No line is owned by "the team".
Collect evidence from where it already lives
Most evidence is already in email attachments, shared folders and supplier threads. Ask each owner to link the actual file into one audit folder, named by checklist line. A description of a file is a follow-up for its owner.
Chase supplier documents first
Supplier certificates take longest, because they depend on someone outside the company. Request them in week one. At Vaultex, the steel toe-cap supplier, already in a thread about its 8% price rise, also owes a material certificate.
Review twice a week from the open list
Hold two short reviews a week, owner by owner, from what is still open. Each owner shows a link for what is done, or gives a new date. GeniOS helps by sending each owner the open item with its date, and closing it only when the file or email shows it is done.
Run a mock walkthrough in week three
Pick five lines at random and have someone outside the team ask for the evidence, as an auditor would. Time how long each file takes to open. Anything slower than two minutes needs a better link or a clearer name.
Name the gaps honestly
Some lines will not be ready in time. Write each one down with the reason and a fix date, and share it if the auditor asks. A named gap with a plan earns more trust than a vague answer.
Write the after-note
Within a week of the audit, write down what was hard to find and what the auditor asked that was not on the checklist. Store it where the next audit owner will read it, so the next audit starts from that note.
TemplateCopy this supplier document request
Send this in week one to every supplier who owes you a document.
Subject: Documents needed for our [brand] audit on [date]
Dear [name],
We have a [brand] vendor audit on [date]. For it we need the following from you by [date, at least ten days before the audit]:
1. [document, for example the material certificate for steel toe caps, with the batch or lot number]
2. [document]
Please send them as files in reply to this email. If any document will be late, tell us the date you can send it.
[Your name], [role]
Keep the audit tracker to five columns: checklist line, owner, evidence file, status and date due.
ExampleWorked example: Vaultex and the Adidas audit
How three weeks might run before the Adidas vendor audit next month.
Week one. The scope asks for IS 15298 test reports, batch records, raw-material certificates and dispatch logs. Quality owns the test reports, Anushka owns batch records and Mayank owns invoices and payment records. The same day, purchasing sends the supplier request to the steel toe-cap supplier, which is already in a thread about its 8% price rise and owes a material certificate.
Week two. At Tuesday's review most lines have a linked file. Two batch records exist only on paper, so Anushka scans them into the folder. The supplier has promised the certificate "next week" by email. With GeniOS reading email, that promise comes back to purchasing as intelligence when the date passes with no file attached.
Week three. A colleague from sales runs the mock walkthrough on five random lines. Four files open in under a minute. One test report is filed under the wrong batch number and is renamed the same afternoon.
Audit week. One gap is still open: a re-test for one PU sole batch, booked after the audit date. It is written down with the reason and a fix date. The audit itself is a walkthrough of the folder. Within a week, the after-note records that the auditor also asked for calibration records for the test equipment, which were not on the checklist.
MistakesCommon mistakes
Five habits that turn an audit into a war room.
Starting in audit week. Three weeks of follow-ups packed into three days is how a war room starts.
Lines owned by "the team". Nobody chases what everyone owns. One name per line.
Accepting "it exists" as evidence. Ask for the link. A file nobody can open is still a follow-up.
Chasing suppliers last. Outside documents take longest. Ask in week one.
Hiding gaps. An auditor who finds a gap you did not mention trusts the rest of the folder less.
What good looks like after
Every checklist line has an owner, a date and a file you can open in under two minutes.
Supplier documents arrived in week one or two, well before the audit.
The final week is a walkthrough, with no late nights.
Gaps are written down with owners and fix dates.
The after-note exists, and the next audit starts from it.
If you are already inside the final week, skip to step five and run it every day.
Three weeks works for most buyer and brand audits. Audits that cover several sites need longer, so start as soon as the date is set.
Who should own the whole audit?
One executive who can ask any team for evidence and get an answer the same day. Each area still has its own owner, and the executive owns the open list and the reviews.
What does GeniOS add?
GeniOS reads email, chat, files and calendars, so audit items reach their owners with a date, and promised documents that never arrived show up early. It closes an item only when the email or file shows it is done, so the open list stays honest.