Technical incident report for a non-technical client
biz-sum-03suite v1.0text
Exact prompt sent to every model
Below is an internal incident timeline and root-cause analysis from an IT provider about a 6-hour email outage at a law firm. Write the client-facing incident summary (under 350 words) the provider will send to the firm's managing partner: what happened in plain language, when, impact, root cause, what was done, and what changes prevent recurrence. No jargon without a one-phrase explanation. No blame language. Must be accurate to the timeline, including the fact that the provider's own change caused the outage.
A private fixture (biz-sum-03/incident-timeline.md) is shown to the model but not published.
Responses
Latest published run: gemini-3.8-flash. For each model the repeat closest to its published median is shown; every repeat is in the repository.
No published attempts for this task yet
When the run is published, every model's raw response, per-dimension scores, judge rationales, human review notes and rendered artifacts appear here side by side.