/
/
Find failed inspection items with no observation raised
For quality and operations teams who want failed inspection items matched to observations, by asking their AI assistant.
On this page
Connector
Connect Procore, pick your AI tool and paste the prompt.
The problem
Failed items are logged but nobody checks the follow-up
Procore logs failed inspection items, but few teams check whether an observation was raised for each one. Doing it means opening every inspection and matching items to observations by hand.
Without PopdockAI
- Open each inspection on the project
- Work out which responses count as failing
- Search for an observation for each failed item
- Miss the failures that were never followed up
With PopdockAI
- Inspections and items are pulled for the period
- Your own response set decides what counts as failing
- Each failed item is matched to an observation
- Failures with none are listed with counts per inspection
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Find the failed or non-conforming items on inspections in {project-name} since {from-date} (default 30 days ago) and check whether each led to an observation.
**Step 1: Resolve the project**
Call `procore-get-viewer-documents-accessible-tools` with `project-name` equal to {project-name} to resolve the project id. If nothing matches, retry with `project-name.contains`. If more than one project matches, list them with their ids and stop and ask which one. If the user named a Procore company, pass it in the `company` parameter on every call.
**Step 2: Pull the inspections**
Call `procore-get-checklist-lists` with the `project-id` and `date-created.from` set to {from-date}.
**Step 3: Pull the items**
Call `procore-get-checklist-list-items` with the `project-id`. Use `procore-get-checklist-responses` to learn which response names map to a failing corresponding status, and keep items whose `response-name` is one of those.
**Step 4: Check for follow-up**
Call `procore-get-checklist-list-item-observations` with the `project-id` and match `checklist-item-id` to the failed items.
**Step 5: Report**
Output a table of failed items: inspection, item name, response, responder, and whether an observation exists. List failed items with no observation. Give the failure count by inspection.
**Rules & Guidelines:**
* This prompt is read-only. Never call any create, update, delete, bulk, send, restore or sync tool (for example `procore-create-rfi`, `procore-update-punch-item`, `procore-delete-incident` or `procore-send-punch-item-email`).
* Report only what the tools return. Do not guess missing dates, amounts or names; mark them as missing.
* Counts come from the records returned, and `max-records` caps each call, so say when a call returned its cap and the picture may be partial.
* Only treat a response as failing when the project's own response set marks it so.
**Validation:**
* If the project cannot be resolved, stop and say so. Do not read records from an unresolved project.
* If the main read returns nothing, say the project has none and stop. Do not fill the gap with assumptions.
Who it's for
One answer, three teams that use it
Quality managers
Close the loop on failures
See which failed items never led to an observation, so each one is raised or consciously dropped.
Which failed inspection items on Fabrikam Depot in the last 30 days have no observation?
Safety officers
Review non-conforming items
Get failures per inspection and who recorded them, to see where problems cluster.
Show failure counts by inspection on Contoso Warehouse since 1 October.
Superintendents
Prepare for a walkthrough
See what failed since your last walkthrough and whether the follow up exists before you walk the site.
Find failed items on Northwind Plaza since 10 November and show whether each has an observation.
How it works
What PopdockAI does when you ask
You name the project and your AI assistant reads inspections, items and observations in Procore. It marks missing values, says when a read hit its cap and creates no observation.
Ask
You name the project and a start date, or leave it for the last 30 days.
Pull
It resolves the project and reads the inspections and their items.
Judge
It uses the project's own response set to decide which responses count as failing.
Report
You get the failed items with whether an observation exists, the ones with none and a failure count per inspection.
What PopdockAI provides
The tools behind the answer
Ready made tools for Procore and one secure connection to your AI tool. No code, no exports.
procore-get-viewer-documents-accessible-tools
procore-get-checklist-lists
procore-get-checklist-list-items
procore-get-checklist-responses
procore-get-checklist-list-item-observations
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
Every failed item either has a follow-up or is on the list
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
