Logging Issues On the Spot with Ad Hoc Findings
An Ad Hoc Finding is the simplest type of report in InspectU. It’s for any issue you spot right now that needs to be documented — even when no scheduled audit is underway.
Think of it as a quick issue report that anyone on your team can submit from any device. No template to set up, no audit to schedule. You see something, you log it, it gets routed to the right person, and it’s tracked until it’s resolved.
When to Use It
- You spot a food safety issue mid-shift and need to document it immediately
- A piece of equipment starts acting up and you want to flag it before it becomes a bigger problem
- You notice something during a walk-through that doesn’t fit into any scheduled audit
- A staff member or guest reports something and you need to create an official record on the spot
- You find something between scheduled audits that needs to be tracked and followed up on
How It Works
| 1 | Open InspectU on your device (phone, tablet, or desktop). |
| 2 | Select “New Finding” or “Ad Hoc” from the main menu. |
| 3 | Describe the issue briefly. Be specific — location, what you saw, when. |
| 4 | Attach a photo. This is the single most useful thing you can do for any finding. |
| 5 | Select the issue type and urgency level so it can be routed correctly. |
| 6 | Submit. The right person is notified automatically and the issue is in the system. |
What Good Looks Like
Signs of effective ad hoc reporting Issues are logged in real time, not reported verbally and then forgotten. Photos are attached. Every finding has an issue type and urgency level. The team uses ad hoc findings to supplement scheduled audits, not as a replacement for them. |
What Happens After
- The finding is automatically routed to the right person or team based on issue type and site
- Urgent issues can be escalated immediately with a notification to the site manager
- The finding stays in InspectU as an open item until it’s resolved and marked closed
- Ad hoc findings can be grouped with audit data in trend reports, so “one-off” issues don’t stay invisible
| Best frequency | Any time — whenever an issue is observed |
| Who runs it | Anyone on the team. No prior audit experience needed. |
| Time to complete | 2–5 minutes |
| Key output | Logged finding, routed to the right person, tracked to closure |