/
/
Log a Procore delay once, on the right day
For field teams who want a delay on record the day it happens, without opening the daily log or logging it twice, just by asking.
On this page
Connector
Connect Procore, pick your AI tool and paste the prompt.
The problem
Delays are logged late, or twice
A delay is often keyed in days afterwards from memory, or by two people for the same event. A late or duplicate entry makes a later delay claim harder to defend.
Without PopdockAI
- Open the daily log for the right project and date
- Scroll past delays someone else may have entered
- Type the delay from memory a few days later
- Find a duplicate or vague entry when a claim is prepared
With PopdockAI
- The project and the day's log header are found for you
- Delays already logged that day are shown before you decide
- You confirm the exact entry before it is saved
- One delay is created and read back to confirm it landed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Record a delay in {project-name} on {delay-date} with comments {comments}.
**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: Find the day's header and existing delays**
Call `procore-get-daily-log-headers` with the `project-id` and `log-date.from` and `log-date.to` set to {delay-date} to get the `daily-log-header-id`. Call `procore-get-delay-logs` with `date.from` and `date.to` the same to see delays already logged.
**Step 3: Confirm and create**
Show the user the exact values you will send, the project, and anything you could not resolve, and ask for an explicit yes. Do not call the write tool until the user confirms in this conversation. Then call `procore-create-delay-log` with the `project-id`, `date`, `comments` and the `daily-log-header-id` if one exists.
**Step 4: Verify**
Call `procore-get-delay-logs` again for the date and confirm the entry.
**Step 5: Report**
Report the delay entry created with its date and comments, and any delay already logged that day, or the exact error.
**Rules & Guidelines:**
* The only write tool you may call is `procore-create-delay-log`, and only once, after the user confirms. Do not call any other create, update, delete, send or bulk tool.
* Never invent an id, name or date. If a required value is missing or a lookup is ambiguous, ask.
* If the write fails, report the exact error and stop. Do not retry with changed values.
* Duplicate delays on the same day are likely; show existing entries before asking for confirmation.
**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
Site superintendents
Log the delay from the field
Describe what held the job up in one message and have it on the daily log the same day, with the date and wording confirmed.
Log a delay on Fabrikam Plaza for today, crane out of service from 10am to 2pm.
Project managers
Keep the delay record clean
Check what is already logged for a day before another entry is added, so claims rest on one clear entry per event.
What delays are logged on Riverside Tower for 5 November, and add one for late steel delivery.
Foremen
Get it recorded before you go home
Tell your assistant what happened at the end of the shift instead of leaving it for someone to remember tomorrow.
Record a delay on Northwind Distribution Centre for yesterday, inspection rescheduled by the city, 4 hours lost.
How it works
What PopdockAI does when you ask
You describe the delay in plain words and your AI assistant checks the day's log. Nothing is written until you have seen the entry and said yes, and it adds one delay only.
Ask
You give the project, the date and what caused the delay.
Check
It finds the day's log header and shows delays already logged.
Confirm
You see the exact entry and say yes before anything is written.
Record
It creates one delay and reads the day's delays back to confirm.
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-daily-log-headers
procore-get-delay-logs
procore-create-delay-log
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
Delays on record the day they happen
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)
