Site Incident & Claims Manager
Log minor accidents, third-party damage and client claims, flag overdue response deadlines, and calculate the total cost exposure across your project.
Download resource
Enter your email and the download starts right away.
What's included
Who it's for
A minor accident, damage to a neighbor's property, or a client claim each get handled on their own as they come in — until one of them has gone weeks without a formal response, and the cost is no longer just the case itself, but the cost of leaving it open.
This isn't the quality non-conformance skill: this one is for the case with a legal or economic angle — accidents, third-party damage, client or developer claims, and serious quality incidents that have already opened a formal file.
The skill calculates the log's overall status, identifies incidents with an overdue response deadline, analyzes risk by type and severity, and calculates the total estimated cost exposure, flagging cases where the insurer hasn't been notified. It returns a status summary, the detail on blocking incidents, the breakdown by type and the cost at stake.
Download the skill free with your email. Copy and paste it into any conversational AI — no integration or new account required.
How to use it with judgment: start with one real, well-defined case, enter only data you can verify, and keep the reviewed version. The goal is not to fill in another document for its own sake, but to turn a project decision into a record that someone else can understand and review later.
Before making it part of your process, check three things: the inputs come from an identifiable source, the calculations or wording match the actual project, and it is clear who must approve the result. If one is missing, treat it as working material rather than final project documentation.
How to prepare the input: start with a real case and define which question the skill must answer, which period the data covers, and which fields cannot be missing. Mark estimates or incomplete sources before requesting the analysis.
How to review the output: check that conclusions can be traced back to your data, inspect the rows or documents behind each alert, and discuss priority cases with the person responsible for the project. A skill helps organize judgment; it does not replace technical, contractual, or financial approval.
How to make it part of the workflow: keep the prompt, the source data, and the reviewed result with the project. This lets you repeat the analysis when progress changes, compare periods, and explain why a recommendation was accepted, rejected, or sent for review.
How to put it to work on a real project
The idea isn't to download another file and forget it in a folder. Use it with a specific case: a pending certificate, a coordination meeting, a cost overrun or a handover to the developer. Fill in the resource with real data from your project, validate the result with your own technical judgment, and keep it as an internal reference to repeat the process next time.
Talk to Bloqbase about your case