Two supervisors visit the same location with the same form and score it differently. That is the moment a franchise audit checklist stops being useful, because the scores can no longer be compared across locations. The problem is almost never the auditor. It usually sits in a checklist that says what to look at, but not when an item counts as met.
While a network has three locations, the supervisor’s memory is enough. With thirty, and franchisees who are not your own employees, it is not. An audit only works if every location is measured with the same yardstick. That does not come from each auditor’s experience. It comes from the checklist, together with how you calibrate it, version it and apply it where there is no signal.
Here you will see what a location audit covers and how to build a base checklist with modules by location type. You will also see how to calibrate auditors and how to change the checklist without losing your historical series.
What does a franchise location audit cover?
A franchise location audit verifies that each location meets the network’s standard. It reviews operations, brand image, customer service, inventory, cleanliness and safety. Everything is checked against the same checklist, so one location can be compared with another.
In practice, the control points fall into six blocks:
- Opening and closing: the location opens and closes following the brand protocol.
- Image and display: storefront, signage, visual merchandising and staff presentation.
- Product and inventory: prices, expiration dates, stockouts and stock control.
- Customer service: compliance with the service protocol on the floor and at the register.
- Cleanliness, equipment and facilities: floors, restrooms, working equipment, lighting and air conditioning.
- Occupational health and safety: fire extinguishers, clear exits, safety talks and delivery of protective equipment.
Occupational health and safety is not a location format. Because it cuts across every format, it belongs in the common core and not in a module.
Also, in a franchise location audit, the relationship with the audited party changes depending on who audits. When the franchisor audits its own locations, it is a first-party audit. When it audits a franchisee, it is a second-party audit.
How to build a franchise audit checklist with modules by location type
The most stable way to standardize a franchise audit checklist is to split it into two layers. The first is a common core for every location. The second is a set of modules that only apply to certain location types.
The common core of a franchise audit checklist
The core contains what the brand promises in any location: image, service, cleanliness, safety and process compliance. These items are not edited per location. They are also the ones that feed the network’s comparable score.
Each item should be written as a criterion, not as a topic. “Condition of the sales floor” is a title. “No boxes in walkways” is a criterion, because it only allows pass or fail. Finally, each item needs its evidence, usually a photo.
DataScope is a platform for field operations. Its checklist question type evaluates several items with the same options, such as Pass, Fail and Not applicable. Each item can also carry comments and images.
Modules by location type
A module groups items that only exist in a given format. The key rule is that the location type defines the module, not the auditor. That removes the classic “we have no stockroom here, so that item does not apply.”
- Retail store: opening and closing, inventory control, visual merchandising, service protocol and sales floor cleanliness.
- Food outlet or café: cleanliness, order, equipment operation, stock and staff presentation. Some networks inspect these daily.
- Pharmacy: compliance with brand standards, inventory control and the points that can end in a fine.
- Shopping center: inspection rounds with photos and comments, and alerts by urgency.
- Facility maintenance: air conditioning, light fixtures and paint. A failed item should open a work order, not just be noted down.
In DataScope, the base checklist and each module can live in a single form with conditional questions. The auditor selects the location type and the form skips the questions that do not apply. Answers are also tied to a place within a hierarchical structure, which organizes them by location.
Why a standard checklist stops being comparable
A checklist starts out standard and stops being so on its own. It almost always happens in four ways, and each one breaks something different.
| What happens | Why it seems reasonable | What it breaks |
|---|---|---|
| Each location adapts the checklist to its reality | “We have no stockroom here, that item does not apply” | Scores can no longer be compared across locations |
| The auditor interprets the criterion | The item says what to look at, but not when it passes | Two auditors, two results for the same location |
| Items are added on the fly | A new problem showed up and needs coverage | The checklist grows unchecked and the visit gets longer |
| The version changes without notice | A confusing wording had to be fixed | The historical series breaks and nobody notices |
The first two are solved with modules by location type and with calibration. The last two, in contrast, need a decision about who owns the checklist.
In a franchise network, that decision belongs to the franchisor. Franchisees can propose changes, but they should not edit the checklist.
Auditor calibration: getting two visits to give the same result
Two auditors reach the same result when each item defines when it is met and their judgment is calibrated on a regular basis. Calibration is not an initial training session. It is a task that repeats.
The ISO and IAF guidance on the effective use of ISO 19011 makes the same point: auditor competence should be monitored and periodically re-evaluated for improvement. It also notes that competence belongs to the team and not only to each person, combining generic knowledge with sector-specific knowledge. In a network of locations, that means calibrating auditors as a team and not one by one. You can read the original in the ISO and IAF guidance document, which is published in Spanish.
That 2020 guidance describes the 2018 edition of ISO 19011. ISO published a fourth edition in May 2026, which replaces the 2018 one. ISO 19011 is a guideline for auditing management systems and applying it is not mandatory. Even so, it provides the method that is usually missing when a network builds its first checklist.
How to calibrate in five steps
A basic calibration takes five steps:
- Two auditors walk the same location on the same day, separately and without comparing notes.
- The results are compared item by item.
- Where they differ, the item is rewritten with a more precise criterion.
- A sample photo is added showing what passes and what does not.
- The exercise is repeated periodically and every time a new auditor joins.
Where two auditors differ, the problem almost always lies in the wording of the item and not in the person. Measuring how many items match in each calibration also works as an indicator of the audit itself.
Each answer in DataScope is recorded with the user who submitted it, its date, its time and its photos. That way, comparing auditors is done with data and not from memory. Paid plans also include unlimited users and pricing is based on actions, not on users. Adding auditors or franchisees does not add a per-user cost.
How to change the checklist without losing historical comparison
You can change the checklist without breaking the series if every version is identified and every item keeps its code. You also need to tell apart fixing a wording from changing what is required.
Many networks do not solve this in time, and it costs them later. A franchise audit checklist has to change because the operation changes. The problem is that each change splits the historical series.
Three rules avoid most of the problems:
- The version and date are stored with each result. Without that, comparing two visits means comparing different things while believing they are the same.
- Items are identified, not just numbered by position. If item 14 becomes item 12 when a new one is added, any comparison by number is wrong.
- Fixing is not the same as changing. Correcting a confusing wording keeps the series. Changing what is required breaks it, and it is best to state that from day one.
When what is required changes, the item gets a new code. The historical series is then compared only on the items that stayed the same.
What to do in DataScope when you publish a new version
In DataScope you can duplicate a form to create the new version. Then you rename it, for example with the version and the date. After that, you can deactivate the previous one so it stops appearing in the app. If you delete a form, its answers remain available in the system.
There is a detail that is easy to miss. An auditor who was offline may keep using the previous version. That is why the version should be visible in the form name. Each device must also be updated from Settings, with the Update Lists option.
Also, whoever manages the checklist should not be the one who applies it. The ISO and IAF guidance separates managing the audit program from carrying out each audit. In small organizations, both can fall to the same person.
Which locations to audit and how often
The right frequency depends on risk, not on the calendar. Visiting every location equally often is easy to plan, but it is the first thing worth reviewing. With a franchise audit checklist, visits are still limited, so it pays to use them where the most is at stake.
The risk-based approach is one of the seven auditing principles of ISO 19011 since the 2018 edition. The 2026 edition reinforces risk analysis.
Some prioritization criteria hold up on their own:
- Locations with repeated findings in recent visits.
- Locations with a recent change of manager or staff.
- New locations, during their first months.
- Locations nobody has visited in a long time, even without a history of problems.
The last criterion is the one most often forgotten. A location with no findings may be spotless or may simply be unvisited. In a spreadsheet, the two situations look the same.
For the rest of the process, see our guide to audit best practices.
How to audit a location with no signal
A franchise location audit can be done without a signal if the checklist works offline and syncs later. Stockrooms, back rooms and basements often have no coverage. Yet those are the spaces where critical points are checked, such as storage and emergency exits.
If the checklist needs a connection to save, the auditor ends up writing on paper and transcribing later. That is back to square one, with an extra step.
DataScope is designed to work offline. Answers are saved on the device and sync automatically when the network returns. From the app you can also add photos, signatures and geolocation.
Before entering the back room, it is best to update the device. That way the auditor carries the current version of the checklist.
From finding to action plan
A franchise audit checklist only changes something if its results are comparable. That is why it pays to fix the checklist, calibrate auditors and version every change. But that solves half the problem. The other half starts with each finding: who fixes it, by when, and how you verify it was closed. In many networks, that follow-up travels by email. That is where what the audit gained gets lost.
The next article in this series covers that step: the action plan in retail audits and how to follow up without depending on email.
Frequently asked questions
It is the scheduled visit that verifies whether each location meets the network’s standard. It uses a common checklist so results can be compared across locations. The franchisor can audit its own or franchised locations. Each visit leaves evidence and findings.
When the franchisor audits its own locations, it performs a first-party audit. When it audits a franchisee, it performs a second-party audit. The checklist can be the same. What changes is the relationship with the audited party, which in a franchise is usually set in the contract.
Items written as criteria, not as topics, so they only allow pass or fail. Each item needs associated evidence, such as a photo. The checklist is also split into a common core and modules by location type. That way every location is measured with the same yardstick.
Almost always because the item does not define when it counts as met. The problem is in the wording of the checklist, not in the person. That is why calibration helps: two auditors visit the same location separately and compare results item by item. Where they differ, the item is rewritten.
The series holds if each version is identified and items keep their code. Fixing a wording does not break the series. Changing what is required does, and it is best to state it. After that, only the unchanged items are compared.
Yes, if the checklist works offline and syncs later. Stockrooms and back rooms often have no signal. In DataScope, answers are saved on the device and sync automatically when the network returns. Before entering, update the app so you have the current version.
