AI photo review for FreshCheq

Overview

A FreshCheq log tells you the task was done, on time, by a named person. It does not tell you what the camera saw. FreshCheq built you the logs and checklists during onboarding, the crew takes them on a phone or tablet, photos go to the cloud instead of the device, and above-store leaders get alerts on missed deadlines plus a report every morning. Completion is solved. What is left is the pile of pictures behind the completed logs, which nobody opens once you pass a handful of stores. RapidEye reads that pile: it takes the photos on your FreshCheq logs, checklists, follow-ups and audits, with the store, the log and who completed it, and returns one finding per thing it sees.

How it works with FreshCheq

FreshCheq gives each store the same set of tools every day, so the checks follow the tools rather than inventing a new routine on top of them.

• Line checks and temperature logs. FreshCheq names the photo on a temperature log as a way to hold employees accountable, and that photo is usually the only picture of the line all shift. RapidEye reads it for what the reading cannot carry: product held uncovered, a rail pan with the wrong item in it, a probe photographed against a surface rather than in the food.
• Opening and closing checklists. The close is the log most likely to be finished from the door. Photos of the same corner every night make drift visible: grease creeping up the fryer surround, a mop sink that has been the same three weeks, a bin that was never taken out. RapidEye compares tonight's frame against the same store's own history.
• Cleaning and training tasks. A cleaning task photographed after the work is either a clean shelf or an angle chosen to avoid one. RapidEye says which, and names the spot in the frame.
• Follow-ups on failed items. FreshCheq lets a failed item's corrective action carry a photo. That photo is the proof the fix happened, and it is the one photo an operator most wants a second pair of eyes on. RapidEye reads the before and the after together and tells you if the corrective action photo shows the same problem.
• Self audits in the audit portal. A store scoring itself before an EcoSure, Steritech or NSF visit has an obvious reason to score generously. RapidEye reads the audit photos against your standard, not the store's, so the self audit and the real one stop disagreeing.

Each finding names the store and the area, where in the frame it sits, what kind of issue it is, how serious, the picture it came from and the one before it, and a suggested next step. It lands in the RapidEye dashboard, and in a Slack channel or an inbox next to your FreshCheq morning report if you want it there. You decide whether that becomes a follow-up, a re-audit or a phone call; RapidEye writes nothing back. If your teams document with video walkthroughs, or with a checklist format of your own that is not in this list, that is a setup conversation rather than a limit: RapidEye reads the documentation a team already produces and scores it against the standard you actually care about.

How to connect FreshCheq to RapidEye

1. A FreshCheq account with your stores on it. The logs and checklists the FreshCheq team built for you during onboarding stay exactly as they are. Nothing about the crew's day changes.
2. The logs that carry a photo step. Tell us which ones: the line check, the open and close list, the cleaning list, the audit, the Follow-Ups record. If a checklist you care about has no photo step today, RapidEye can send a capture link that opens on any phone with no install, and the crew shoots a fixed set of angles before they close the log.
3. Add RapidEye as a user. FreshCheq puts no limit on how many users a location has, and describes a role that can take logs without the ability to edit. That is the one we want. The modal has the details.

What a FreshCheq log actually holds

Checked against FreshCheq's own product and FAQ pages, September 2026.

FreshCheq is digital food safety and store operations software built, in its own words, for restaurant people by restaurant people, and it is also used by fitness centres, cafeterias and cinemas. It is deliberately narrow: no required hardware, unlimited users and unlimited logs per location, and a set of named tools the FreshCheq team configures for each store during onboarding. According to FreshCheq's product documentation (freshcheq.com), those tools are the ones below, and only some of them are places a photo can live.

Photo step marks the tools where FreshCheq describes a picture being taken or attached. The rest carry numbers and timestamps, which are already unambiguous and need nobody to read them.

Around the tools sits the reporting layer, and it is the part multi-unit operators actually live in. Push notifications fire when a log is not completed on time. A report lands every morning covering the previous day across every store, and additional exports can be scheduled ahead. Log taking is built for phones and tablets, reporting is done on a computer, and the app uploads on its own once it is back on wifi, so a walk-in with no signal does not lose the record. Gamification sits on top: streaks for consecutive days of completed logs, leaderboards, and reports the crew can see themselves ranked in.

Are FreshCheq photos stored, and who looks at them?

Stored, yes. FreshCheq's FAQ answers this directly: you are able to take pictures for your logs, and the pictures are not stored on the device, they are stored in the cloud. So a chain running FreshCheq across twenty stores is quietly accumulating a photographic record of every line check and every close, indexed by store, by log and by the person who took it.

Looked at is the other half. Nothing in FreshCheq's documentation describes anything reading those photos: the alerts are about deadlines, the morning report is about performance and completion, the streak is about consecutive days. All of that is the right design for the problem FreshCheq set out to solve, which is getting the log done at all, in a store where the paper version was being backfilled at ten at night. But it means the photo is checked only when a human opens it, and the person best placed to open it is the above-store leader who has eighteen other stores that morning. That is the whole of what the integration adds: the pictures are already there, in the cloud, attached to the right store and the right log, and RapidEye is the thing that reads all of them.

FreshCheq integration FAQ