Assessment
Outage chronology for a closed or disputed incident
A reconstructed hour-by-hour account of one incident using tickets, counters, and plant notes the operator already holds.
- Who it is for
- Incident managers and regulatory liaison staff who need a single narrative
- What is left with the desk
- A chronology with timestamps, sources, and remaining gaps marked as gaps
- Duration
- One to three days depending on ticket volume
- Where it happens
- Remote reading of documents, with one scheduled call
- How it is priced
- Quoted per incident — see rates.
Included
- Source list (which ticket system, which counter file, which plant log)
- A timeline that distinguishes confirmed events from inferred ones
- A short note on what the quality counters did during the same hours
Left out
- Legal representation or expert-witness appearance unless separately agreed in writing
- Any claim that Releasegridpath operated the network
How the days run
- You send the incident identifier and the documents you are willing to show.
- We order events, flag contradictions, and return a draft chronology.
- One revision pass for factual corrections from the desk.
Preparation
Export tickets with original timestamps. Do not summarise them into a slide first.
Constraints
If two source clocks disagree, both are shown; we do not pick a favourite clock.
Next step
Email the incident identifier to contact@releasegridpath.digital. Correspondence details are on the correspondence page.