Skip to content
Get started

Evidence-linked incident review

Organise incident chronology, impact, source-confirmed causes, hypotheses and action follow-up with exact evidence and visible unanswered questions.

Input

Incident title: Packaging line interruption Incident evidence records: id,date,kind,status,impact,owner,deadline,text,criterion E1,2026-11-02,event,recorded,high,,,The line stopped after the temperature alarm., E2,2026-11-02,impact,recor…

Result

The temperature alarm and 25-minute interruption remain source facts. A blocked cooling path remains an unconfirmed hypothesis, with any event links clearly proposed for review. The inspection action retains its owner, 2026-11-05 deadlin…

Bring an incident chronology, recorded impact, cause claims, hypotheses and action follow-up into one reviewable table. The AI selects substantive source passages and proposes related event or impact references. The server retains the original classification and copies owners, deadlines and effectiveness criteria without rewriting them into assurances.

Your texts, pages and images are processed on our own servers in the EU. Trust Center

Try it now Pricing

Who it is for

Operations, service and quality teams reviewing a documented incident before an internal follow-up meeting. Appropriate for organising evidence and identifying missing information; it is not an autonomous root-cause determination or a safety authorisation.

Typical uses

  • Separate observed events and impact from source-confirmed causes and unconfirmed hypotheses.
  • Review proposed evidence links with exact supporting passages.
  • Track supplied action owners, deadlines, effectiveness criteria and reported control status.
  • Expose missing information and overdue open actions without inventing a resolution.

Example

Input

Incident title: Packaging line interruption Incident evidence records: id,date,kind,status,impact,owner,deadline,text,criterion E1,2026-11-02,event,recorded,high,,,The line stopped after the temperature alarm., E2,2026-11-02,impact,recorded,high,,,Production was paused for 25 minutes., H1,2026-11-02,hypothesis,open,high,,,A blocked cooling path is suspected but has not been confirmed., A1,2026-11-03,action,open,high,Maintenance lead,2026-11-05,Inspect the cooling path and record the findings.,No temperature alarm during the documented validation run. Reference date: 2026-11-03 Review focus: All Cause classification filter: All Action status filter: All Impact filter: All Maximum selected records: 16 Excerpt detail: Detailed excerpts Display order: Chronology

Result

The temperature alarm and 25-minute interruption remain source facts. A blocked cooling path remains an unconfirmed hypothesis, with any event links clearly proposed for review. The inspection action retains its owner, 2026-11-05 deadline and supplied validation criterion; it is not marked effective or completed.

A fixed example, shortened. Real results are AI-generated: please check them.

Price and limits

Price
usually 1–3 credits
Available with
Free, With package
Input limit
One page with up to 50,000 characters of HTML

Privacy

Processed on our own servers in the EU (Poland). Inputs and results are deleted after 7 days (Free) or 30 days (packages), or right after you see the result if you choose not to store them. Images are deleted right after processing.

In the API

Tool name: incident_review. Create a job with POST /api/v1/jobs and fetch the result with GET /api/v1/jobs/{id}. You find your API key in your account.

curl -X POST https://do4u.eu/api/v1/jobs \
  -H "Authorization: Bearer d4u_…" -H "Content-Type: application/json" \
  -d '{"tool": "incident_review", "url": "https://example.com/"}'

Full API documentation →

Questions and answers

Can a hypothesis become a confirmed cause?

Not through model wording. A cause row must already be explicitly classified as confirmed in the submitted source record. Even that label is a reported source claim, not an independent verification.

Are proposed evidence links proof of causality?

No. The model proposes relationships to existing event or impact IDs. Exact text and valid IDs establish traceability, not causal sufficiency; a human must review each link.

Does a completed action count as verified?

No. done and verified are separate supplied statuses. Missing effectiveness criteria and unverified outcomes remain visible when evidence-gap questions are enabled. No test or corrective action is executed.

Is my text stored?

Only as long as needed: 7 days on Free, 30 days with a package – or not at all if you choose not to store it. Processing happens on our own servers in the EU (Poland).

Can I use the result right away?

Results are AI-generated. Please read them before you publish or send them.