The incident work, done and queued for one look
It reads every incident your Procore account holds, drafts the changes that follow, and hands you a card for each one before a single incident moves.
Open the incident. Check it against something else. Write the change. Move to the next one. That is the Procore afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a incident until you approve it.
What it can do is exactly what Procore exposes to an account you authorise and nothing beyond it: 5 operations, no reads and 5 writes. In practice that means it can create a timesheet, create a submittal and create a RFI, and work across the incidents, manpower logs and rfis.
The Procore API stops at Procore. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the incidents or ask you for them?
In the tab.
Procore exposes no read operation to a connected account, so a companion opens Procore in the session you are already signed into and reads the screens you would.
The incidents are what most of this inventory is about, alongside the manpower logs. A companion can hold all 5 of these operations and forty open tabs in the same pass, which is how an afternoon of Procore admin becomes a queue you review.
What happens before it can create timesheet?
All 5 write operations wait for you.
A companion can create a timesheet, create a submittal and create a RFI, and each one is staged on an approval card first: you see the incident, the field and the new value before it lands in Procore.
Nothing in Procore is sent, changed or deleted on your behalf without that click, and a rejected card leaves the incident exactly as it was. The gate is the same one on every surface, described at security.
- Create Timesheet
- Create Submittal
- Create RFI
- Create Manpower Log
- Create Incident
Does the incident sweep have to be asked for every time?
Yes.
Saved as a routine, the Procore incidents pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the planning, the Procore incidents sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents