Connectors

/

Procore

/

Review Procore delay logs
Report

Total Procore delay logs by cause and vendor

For project teams who want delays totalled and checked against weather and notes, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Review Procore delay logs
Review the delay logs on Riverside Tower between 1 September and 31 October and show total delay and the main causes.
Riverside Tower recorded 42.5 hours of delay across 17 entries between 1 September and 31 October. - Top cause: weather, 21 hours - Top vendor: Contoso Concrete, 14 hours - Cause and weather mismatch: 3 entries cite rain on dry days - Units: all durations are in hours Want the full table of the 17 entries with cost codes and comments?
Procore
Sample figures. Your results come from your own account.
procore-get-viewer-documents-accessible-tools
procore-get-delay-logs
procore-get-daily-logs-delay-log-types
procore-get-notes-logs
procore-get-daily-logs-weather-logs

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Procore

Procore
Run it on your own Procore data.

Connect Procore, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Delay entries are never totalled by cause or vendor

A delay claim needs a documented record, but Procore delay entries are not totalled by cause or vendor. Adding durations and matching them against weather and notes takes hours across several logs.

Without PopdockAI

  • Open the delay logs for the date range
  • Add up durations by hand
  • Group by cause and by vendor in a spreadsheet
  • Check weather and notes entry by entry

With PopdockAI

  • Delay logs and type names are pulled together
  • Total delay is grouped by cause and by vendor
  • Notes and weather give context for each date
  • Mixed units are flagged, never added together

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Review the delay logs in {project-name} between {from-date} and {to-date} and show the total delay and its main causes.

**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 delays**

Call `procore-get-delay-logs` with the `project-id` and `date.from` / `date.to` set to the range, and `procore-get-daily-logs-delay-log-types` to read the delay type names.

**Step 3: Add context**

Call `procore-get-notes-logs` and `procore-get-daily-logs-weather-logs` for the same dates to check whether notes or weather explain the delay.

**Step 4: Report**

Output a table: date, vendor, cost code, duration, comments. Total the duration, group by cause and by vendor, and list delays where the weather or notes do not match the stated cause.

**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.
* Do not treat durations in different units as equal; if units differ, say 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

Contract administrators

Build the delay record

Get total delay by cause and vendor for a period, with the weather and notes that support or contradict it.

Summarise delay logs on Fabrikam Depot from 1 July to 30 September by cause and vendor.

Project managers

See who is causing delay

Find which vendor accounts for the most delay time so you can raise it at the next coordination meeting.

Which vendor has the most delay hours on Contoso Warehouse in October?

Project controls analysts

Test the stated causes

Spot delay entries that blame weather on days the weather log says were fine.

On Northwind Plaza, list delay logs for September where the weather log does not match the stated cause.

How it works

What PopdockAI does when you ask

You name the project and dates and your AI assistant reads delay logs, notes and weather in Procore. It marks missing values, says when a read hit its cap and creates no delay entry.

Ask

You name the project and the date range.

Your AI tool

Pull

It resolves the project and reads the delay logs with their delay type names.

procore-get-viewer-documents-accessible-tools
procore-get-delay-logs
procore-get-daily-logs-delay-log-types
procore-get-notes-logs
procore-get-daily-logs-weather-logs

Add context

It reads the notes and weather logs for the same dates.

No items found.

Report

You get the delays, total duration by cause and vendor and any entries the weather or notes do not support.

Your AI tool

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.

get-data

procore-get-viewer-documents-accessible-tools

Returns Procore viewer documents accessible tools records from the Project Management area. Filter by project and by the record's own fields; reads only, nothing is changed.
get-data

procore-get-delay-logs

Returns delay log records from Procore daily logs: the delay type, duration and notes on a project. Filter by project and date range.
get-data

procore-get-daily-logs-delay-log-types

Returns Procore daily logs delay log types records from the Project Management area. Filter by project and by the record's own fields; reads only, nothing is changed.
get-data

procore-get-notes-logs

Returns notes log entries from Procore daily logs, with the date, author and note text. Filter by project and date range.
get-data

procore-get-daily-logs-weather-logs

Returns Procore daily logs weather logs records from the Project Management area. Filter by project and by the record's own fields; reads only, nothing is changed.
Read only.Nothing in Procore Changes

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.

How Popdock AI secures your data

The outcome

A delay record ready to support a claim

Try PopdockAI free
Get a live demo

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.

Try PopdockAI Free
See Documentation