The artifact suite

A chat answer is not a deliverable. A document is.

The RCA artifact suite is what Onepane actually delivers: fifteen audit-grade documents and structured records, per incident, monthly, and at the commercial milestones, that a regulator, a customer and a problem-review board will all accept. Every one is available today.

Per-incident artifacts

Delivered for every accepted RCA, inside the SLA window.

01

Root Cause Report

The Root Cause Report is the master RCA artifact: incident identity and severity, impact, full timeline, the causal chain stated as trigger → propagation → failure, contributing factors held distinct from the root cause, an evidence index linking every claim to telemetry or a change record, corrective actions with named owners, and an explicit confidence statement.

What it contains →
02

Executive Incident Summary

The Executive Incident Summary is a one-page, plain-language version of the RCA for the CIO, the executive review or the board packet: what broke, what it cost, why it happened, and what stops it recurring.

What it contains →
03

Customer-Facing RCA

A customer-facing RCA is the sanitised, external version of a root-cause report that a B2B vendor sends to the enterprise customer it owes one to after a Sev1: no internal hostnames, no employee names, no raw logs, no unnecessary architectural disclosure, written to survive the recipient's vendor-risk and procurement review, and delivered inside the contractual window.

What it contains →
04

Evidence Pack

The Evidence Pack is the audit trail behind a root-cause report: every query run, every data source touched, timestamps, and a content hash so the bundle can be shown to be unaltered. It is the answer to "how do you know?"

What it contains →
05

Change Attribution Record

The Change Attribution Record identifies which deployment, configuration change, IaC apply or cloud-provider event is implicated in an incident, with the diff and the approver, framed as "what changed", never "who broke it".

What it contains →
06

Service and Ownership Snapshot

The Service and Ownership Snapshot captures the service map as it existed at the moment of the incident, with the owning team for each failing and dependent service, proving the attribution, and quietly becoming the CMDB you wish you had.

What it contains →
07

Confidence and Abstention Statement

The Confidence and Abstention Statement records what Onepane concluded, at what confidence, what evidence was missing, and what could not be determined, because a confidently wrong root cause is worse than none.

What it contains →
08

Problem Record Payload

The Problem Record Payload is the RCA delivered as structured fields, cause, cause code, evidence links, corrective actions, owners, written directly into ServiceNow, Jira Service Management or your ITSM of record, not as a PDF in someone's inbox.

What it contains →
By audience

Which artifact should you lead with?

FAQ

About the artifacts.

What is an RCA artifact suite?

The set of documents and structured records a managed root-cause service delivers for each incident and each month: the Root Cause Report, an executive summary, a customer-facing version, the evidence pack behind it, change attribution, ownership snapshot, a confidence/abstention statement, and a problem record written into your ITSM, plus periodic problem-review, known-error, CAPA and SLA-attainment reports.

Why does the deliverable matter more than the investigation?

Because a chat answer is not something a regulator, a customer or a problem-review board will accept. A document with an evidence index is. That is also what justifies services pricing instead of tooling pricing.

Are these artifacts available now or on a roadmap?

Available now. Audit-grade artifact generation is what Onepane does today, not a roadmap item.

Can we customise the templates?

Yes. Section order, branding, sanitisation rules for the customer-facing version, and the ITSM field mapping are all configured per account during onboarding.

See the artifacts on your own Sev1s.Not on our demo data.

Not a demo. A replay on your own incidents, scored against the RCA a human actually wrote. Two weeks, no cost.